¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. TinyTrak
  2. Topics

Accidentally sent break to TT4 in bootloader - Borked?

 

My TT4 (V1.2b with 644 chip) has been behaving really weird lately.? Using Minicom in linux to reconfigure with 19200 8N1 no flow.

Once in config, it coughs up partial/truncated responses, locks up after a few lines of input, etc.

Decided best thing was to backup config and reflash the software to start fresh.? Went into bootloader, checked the version.? Then attempted to upload the 644.TT4 file.? In the process, I accidentally hit ctl-A F instead of S, which then cause both green & yellow leds to? stop flashing and stay on with a steady stream of ????? emanating from the Minicom terminal.

Unplugged power and repowered up, both leds light up and the ????? continue to pour out of the TT4.? Can't seem to access the bootloader to try and reload the software.

Please note that I do not have access to any Windows equipped computers, all Linux or FreeBSD

Any ideas or suggestions?
 

I've used minicom in LInux and noticed that the data appears to be sent too fast.

I had similar issues with TeraTerm until I found that you can put in a "NewLine Delay".
I just checked and you can try this in minicom as well.? It is in Terminal Settings
? <Ctrl>A T D
In TeraTerm, the value of 1 worked well.? I have not tried this in minicom.

Also, If you have WINE installed, the configuration program will run in Wine.?
I think TeraTerm does as well.

All 3 are worth trying.

Robert Giuliano
KB8RCO



On Thursday, April 1, 2021, 3:17:29 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:


My TT4 (V1.2b with 644 chip) has been behaving really weird lately.? Using Minicom in linux to reconfigure with 19200 8N1 no flow.

Once in config, it coughs up partial/truncated responses, locks up after a few lines of input, etc.

Decided best thing was to backup config and reflash the software to start fresh.? Went into bootloader, checked the version.? Then attempted to upload the 644.TT4 file.? In the process, I accidentally hit ctl-A F instead of S, which then cause both green & yellow leds to? stop flashing and stay on with a steady stream of ????? emanating from the Minicom terminal.

Unplugged power and repowered up, both leds light up and the ????? continue to pour out of the TT4.? Can't seem to access the bootloader to try and reload the software.

Please note that I do not have access to any Windows equipped computers, all Linux or FreeBSD

Any ideas or suggestions?

 

Thanks for the tips.

Issue right now is that I can't even get into the bootloader via minicom.? Just keeps pouring out ??? with leds lit like a Christmas tree

Will try the "official" configuration utility under Wine and see if that helps to debork my TT4
 

The Config tool is a good bet.? I think it just looks for the ? and does the rest.

If that doesn't work, it looks like it the TT4 is looking for input.
Try just sending the file in minicom while the TT4 is sending question marks .

Robert Giuliano
KB8RCO



On Thursday, April 1, 2021, 3:59:31 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:


Thanks for the tips.

Issue right now is that I can't even get into the bootloader via minicom.? Just keeps pouring out ??? with leds lit like a Christmas tree

Will try the "official" configuration utility under Wine and see if that helps to debork my TT4

 

Got my TT4 back via Wine & config software.? Only tricky part was finding the correct comm port.? It is located under ~/.wine/dosdevices.? Look for the ln to appropriate /dev/ttyUSBxx port

Now to see if it behaves any better with Pat to access 2m Winlink

Thanks for the guidance.
 

Tried both sending file with minicom and using cat xxxx644.TT4 > /dev/ttyUSB0 as ??? poured out.? Using cat, the file seemed to upload, but TT4 remained borked.

Only thing that worked was Wine & the config.exe program
 

Glad you were able to recover it!
COMM ports with WINE and Linux can be difficult.
WINE defaults to COM1 -> COM32 being symbolic linked to /dev/ttyS0 - /dev/ttyS31, then adds COM34 on when USB devices are attached.? Since these are all just files, you can override the existing /dev/ttyS# with UDEV rules.? I use one to override ttyS3 (com4 iin WINE) so that the device is within the first few ports and visible to most DOS/Windows applications
??
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="ttyS3", GROUP="dialout"

The idVendor and idProduct are from a generic USB to TTL serial interface.? You will need to find the correct settings for your device.

Robert Giuliano
KB8RCO



On Thursday, April 1, 2021, 5:14:16 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:


Got my TT4 back via Wine & config software.? Only tricky part was finding the correct comm port.? It is located under ~/.wine/dosdevices.? Look for the ln to appropriate /dev/ttyUSBxx port

Now to see if it behaves any better with Pat to access 2m Winlink

Thanks for the guidance.

1 - 7 of 7