So my Cobra II is stuck in GHI Bootloader Interface mode after trying to update to 4.3.
I’ve used TeraTerm to reload 4.2 firmware and it still comes back in bootloader mode. If I do “R” in TeraTerm to run it comes back with “Bad Firmware”.
YES I did select 1K when uploading.
YES I have tried loading the 4.3 firmware instead.
Updated Raptor. Firmware looks good but it takes so long to connect after a reboot it refuses to take applications.
Updated Hydra with Update.bat. Shows as Hydra but will not respond to Pings.
Updated G120 using TeraTerm version on your site. Transfers the file fine. Shows up and won’t respond to pings. If you use the R key in TeraTerm it reports “Bad Firmware”.
I have 3 devices here and they all do nothing now. I have others that I could test, but it seems rather pointless.
So I’ve managed to sort the Hydra out and USB update addressed the Raptor…
But Cobra II is still dead in the water. After several attempts, I have gotten a critical SDRAM issue reported via TeraTerm. I managed to get the Cobra 2 to take the firmware once but upon reboot it completely fails again.
So I’m really trying to get this up and running to help me with some more drivers (like WiFi for example).
I hit the PC ready to rock this out today.
Part One
I plugged in the Cobra II and the Gods smiled down upon me as it reported it had a firmware but was in bootloader mode. (img 1)
So I deployed the firmware. (img 2)
Everything went perfect, oh happy day! But wait…
I deployed an app, and that also went swimmingly. So I unconnected my CobraII slapped on the VideoOut module and an SD card with the driver and plugged it back in.
What type of serial device are you using with Teraterm?
I’ve found that a native RS232 port is the ideal type but USB - RS232 can work but you need to find an FTDI based one. The PL23xx based ones seem to fail for me and you must not connect through a HUB either.