Home › Forums › TinyG › TinyG Support › Flash v8 to 380.08 now TinyG not working
- This topic has 20 replies, 5 voices, and was last updated 11 years ago by cmcgrath5035.
-
AuthorPosts
-
October 17, 2013 at 4:05 pm #4812cmcgrath5035Moderator
Thanks for that! I’ll try it. When it flashed it said it was flashing 204K so it probably didn’t convert correctly if it’s supposed to flash 100K right?
You are correct, that number looks bad – I flashed 102724 bytes.
Was that with your file or my file?
What version of avrdude do you have.
I ran with 5.11.1 on Linux.October 17, 2013 at 8:43 pm #4815areinikeMembercmcgrath, your download seemed to work better.
C:\Firmware\380.08>avrdude -p x192a3 -c avr109 -b 115200 -P com4 -U flash:w:tiny
g.hex:aConnecting 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: 0x7bavrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e9744
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performedTo disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file “tinyg.hex”
avrdude: input file tinyg.hex auto detected as Intel Hex
avrdude: writing flash (102724 bytes):Writing | ################################################## | 100% 12.87s
avrdude: 102724 bytes of flash written
avrdude: verifying flash memory against tinyg.hex:
avrdude: load data flash data from input file tinyg.hex:
avrdude: input file tinyg.hex auto detected as Intel Hex
avrdude: input file tinyg.hex contains 102724 bytes
avrdude: reading on-chip flash data:Reading | ################################################## | 100% 12.49s
avrdude: verifying …
avrdude: 102724 bytes of flash verifiedavrdude done. Thank you.
C:\Firmware\380.08>
Now I guess I have to find a later version of tgFX? It’s not recognizing it. The blinking light turns off, but nothing else comes on except the blue light. Is that right? I used avrdude 5.1.1. Maybe I should try 6.0.1?
October 17, 2013 at 8:45 pm #4816areinikeMemberNevermind. 6.0.1 just keeps failing.
October 17, 2013 at 8:47 pm #4817areinikeMembertgFX stuck on this:
[+]Connected to COM4 Serial Port Successfully.
Getting TinyG Firmware Build Version….
Build 2072
- This reply was modified 11 years ago by areinike.
October 17, 2013 at 8:56 pm #4819areinikeMemberAH!!! I just flashed it again and it worked!
I downloaded the hex file and let it save as .txt. Then thought I should save it as hex directly. Well, the hex one downloaded at 277K but flashed at 102K. That one was a dud. I renamed the .txt one to .hex that was 283K, flashed it and all is well. Finally!
Thanks all for your help. Hope this helps someone. Saving it as .txt and renaming it to .hex worked for me.
October 17, 2013 at 10:05 pm #4820cmcgrath5035ModeratorThis is total speculation on my part – perhaps avrdude on windows expects a .txt file for it’s hex to binary processing to work properly?
I left Windows a long time ago for Linux and have forgotten some of the unusual rules regarding handling binary files.Anyway, sounds like you are up and running.
Might I suggest to check around for CoolTerm – it seems to be a popular low level interface useful for communicating with a TinyG.
I use Putty myself, primarily because it is available Linux and Windows.As for tinyG, review this thread
I am seeing some good results with this latest EDGE (== beta) version that Riley is working on.
-
AuthorPosts
- You must be logged in to reply to this topic.