problem flashing my TinyG

Home Forums TinyG TinyG Support problem flashing my TinyG

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #4251
    selektha
    Member

    so I bougt a tinyG and wanted to test tgFX and discovered that I needed a newer fw to test it, said and done, tried to flash with avrdude via USB and it cant verify the hex, I get:

    C:\tools\avr\bin>avrdude -p x192a3 -c avr109 -b 115200 -P COM3 -U flash:w:tinyg.
    hex

    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: FLASH memory has been specified, an erase cycle will be performed

    To disable this feature, specify the -D option.
    avrdude: erasing chip
    avrdude: reading input file "tinyg.hex"
    avrdude: input file tinyg.hex auto detected as raw binary
    avrdude: writing flash (204800 bytes):

    Writing | ################################################## | 100% 25.36s

    avrdude: 204800 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 raw binary
    avrdude: input file tinyg.hex contains 204800 bytes
    avrdude: reading on-chip flash data:

    Reading | ################################################## | 100% 24.98s

    avrdude: verifying ...
    avrdude: verification error, first mismatch at byte 0x30000
    0x20 != 0x0d
    avrdude: verification error; content mismatch

    avrdude done. Thank you.`
    So after a few tries it only went into bootloader mode and wont start tinyG, connected it to my AVRISP mkII according to instructions(lockbits issue) but the Atmelstudio(6.x) tells me the lockbits where correct, reflased the xboot.hex and it looks fine, downloaded the latest tinyG and trie to flash it and atelstudio says:
    `Unable to parse objectfile C:\Users\selektha\Desktop\tinyg.hex: Unsupported format.

    Timestamp: 2013-07-05 11:10:10.044
    Severity: ERROR
    ComponentId: 20100
    StatusCode: 131106
    ModuleName: TCF command: Modules:add failed.

    Unable to parse objectfile C:\Users\selektha\Desktop\tinyg.hex: Unsupported format.

    I have tried all tinyG.hex I can find on the Github and noone works(xboot.hex works fine to flash). And if I understand everything I should use the one in debug/ for atmelstudio6.1.

    So any idee how I can get my new and fine TinyG to work again? =)
    Sorry if I am unclear but im 100% newbee on this but like to tinker(danger danger! 😉 )

    • This topic was modified 11 years, 4 months ago by selektha.
    #4265
    Riley
    Keymaster

    Well.. I am not sure. See your board had the bootloader loaded on it. All you needed to do was flash via avrdude the tinyg.hex file. I am not sure what “state” your board is in now since you reflashed the bootloader. Unless you changed any “fuses” you should be ok if your reloaded the bootloader.

    That being said… save that file like told you how.. then hit “reset” (led should be flashing) then hit enter with the whole command line that was give via the instructions.

    If you are still having issues shoot me an email at riley &nospace& porter @ gmail.com and I can setup a google hangout or cell phone call to help you out. I we are hackers too I totally get trying to mess with stuff

    Riley

    PS
    To put your mind to rest. Nothing you did should have “bricked” your tinyg. And being that you have an MKII you are gold. This is a speed bump in your road to CNC awesomeness.

    #4269
    selektha
    Member

    Just wanted to say that it now works again with the original master branch TinyG version, but I cant get the dev version to work so I havnt been able to test it yet, the problem was that the files got corupted when I downloaded them.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.