Hi.
I'm using TinyG v8 with old firmware (v412.01).
When used it after a long time, Application has recommended to upgrade it.
I downloaded firmware (v440.20) and tried to upgrade into my TinyG. But I failed it with a lot of "failed" messages.
My environment is Windows 10 Home Edition, so I tried and got failed under Command prompt and TinyG Updater. But both of them gave same result.
If someone knows how to resolve this problem, please let me know.
Hisatoshi Onishi / hisa0211
On command prompt, my result is below.
(snipped)
***failed;
***failed;
***failed;
Writing | ################################################## | 100% 13.45s
avrdude.exe: 118274 bytes of flash written
avrdude.exe: verifying flash memory against tinyg-master-440.20.hex:
avrdude.exe: load data flash data from input file tinyg-master-440.20.hex:
avrdude.exe: input file tinyg-master-440.20.hex auto detected as Intel Hex
avrdude.exe: input file tinyg-master-440.20.hex contains 118274 bytes
avrdude.exe: reading on-chip flash data:
Reading | | 0% 0.00savrdude.exe: error: programmer did not respond to command: set addrOf course I started it with setting TinyG into reset mode.
It has been a long time since I have done a FW download and never under windows, so I need to reboot a few brain cells.
Are you referring to the tinyG Updater built in to Chilipeppr, or to the updater here: https://github.com/synthetos/TinyG-Updater ?
When you say from Command Prompt, are you running CoolTerm (or similar emulator) or might you mean the Chilipeppr console.
I always had reproducible good luck using the direct avrdude method here in the wiki: https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware#updating-tinyg-with-avrdude.
If you are using Chilipeppr, from what browser do you run?
I have never seen anyone try the Edge browser, but that does not mean it does not work for this, just new ground being plowed.
Thanks for reply quickly and sorry for slow answering.
I tried updating again with avrdude(Linux 32bit binary) under Ubuntu 18.04 LTS 64bit.
This command has ran on standard terminal screen of Ubuntu.
sudo ./avrdude -p x192a3 -c avr109 -b 115200 -P /dev/ttyUSB0 -C ../etc/avrdude.conf -U flash:w:/home/hisa/tinyg-master-440.20.hex -l /tmp/failflash.log
I've got same result (failed one) that ran under Windows.
I think that some parameters may be wrong. So, is it correct that parameters of "-p" and/or "-c" options are? Please let me know.
Additionally, I got log file(failflash.log) that how to fail this work.
I'll show top and bottom of that below.
Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.
Programmer supports the following devices:
Device code: 0x7b
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e9744
avrdude: NOTE: Programmer supports page erase for Xmega devices.
Each page will be erased before programming it, but no chip erase is performed.
To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading input file "/home/hisa/tinyg-master-440.20.hex"
avrdude: input file /home/hisa/tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: writing flash (118274 bytes):
Writing | ***failed;
***failed;
***failed;
:
(snipped)
:
***failed;
***failed;
# | 100% 1.47s
avrdude: 118274 bytes of flash written
avrdude: verifying flash memory against /home/hisa/tinyg-master-440.20.hex:
avrdude: load data flash data from input file /home/hisa/tinyg-master-440.20.hex:
avrdude: input file /home/hisa/tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: input file /home/hisa/tinyg-master-440.20.hex contains 118274 bytes
avrdude: reading on-chip flash data:
Reading | avrdude: error: programmer did not respond to command: set addrHisatoshi Onishi / hisa0211
Thanks for reply quickly and sorry for slow answering.
I tried updating again with avrdude(version 6.0.1, Linux 32bit binary) under Ubuntu 18.04 LTS 64bit.
This command has ran on standard terminal screen of Ubuntu.
sudo ./avrdude -p x192a3 -c avr109 -b 115200 -P /dev/ttyUSB0 -C ../etc/avrdude.conf -U flash:w:/home/hisa/tinyg-master-440.20.hex -l /tmp/failflash.log
I've got same result (failed one) that ran under Windows.
I think that some parameters may be wrong. So, is it correct that parameters of "-p" and/or "-c" options are? Please let me know.
Additionally, I got log file(failflash.log) that how to fail this work.
I'll show top and bottom of that below.
Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.
Programmer supports the following devices:
Device code: 0x7b
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e9744
avrdude: NOTE: Programmer supports page erase for Xmega devices.
Each page will be erased before programming it, but no chip erase is performed.
To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading input file "/home/hisa/tinyg-master-440.20.hex"
avrdude: input file /home/hisa/tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: writing flash (118274 bytes):
Writing | ***failed;
***failed;
***failed;
:
(snipped)
:
***failed;
***failed;
# | 100% 1.47s
avrdude: 118274 bytes of flash written
avrdude: verifying flash memory against /home/hisa/tinyg-master-440.20.hex:
avrdude: load data flash data from input file /home/hisa/tinyg-master-440.20.hex:
avrdude: input file /home/hisa/tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: input file /home/hisa/tinyg-master-440.20.hex contains 118274 bytes
avrdude: reading on-chip flash data:
Reading | avrdude: error: programmer did not respond to command: set addrHisatoshi Onishi / hisa0211
This has taxed some old memory bits on my end
See https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware#writing-to-flash-emits-lots-of-failed-lines
I am not sure why -e is only required sometimes, but give the modified avrdude (with -e option) a try
Thanks for your reply.
I tried it with "-e" option again, it has succeeded to flush.
This link says that my question was one of FAQs... sorry for duplicates.
On this note says, "-e" option comes with force erasing before writing onto flush.
> I am not sure why -e is only required sometimes, but give the modified avrdude (with -e option) a try
Maybe, it conflicts with very old programs like this case.
Hisatoshi Onishi / hisa0211
Good to know you are back up and running.
It was 5 or 6 years ago that I stumbled on this.
To best of my recollection, we never really understood why sometimes it was necessary sometimes it was not.
Since avrdude is a generic third party application, there is a possibility that at the time there was concern about flash memory wear.
Hopefully 440.20 will resolve you issues
Back to TinyG Support or the forum archive.