spdir flashing, verification error content mismatch

Home › Forums › TinyG › TinyG Support › spdir flashing, verification error content mismatch

Tagged: 

Viewing 15 posts - 1 through 15 (of 47 total)
1 2 3 4
  • Author
    Posts
  • November 22, 2015 at 1:14 pm #8963
    KingBubbaTruck
    Member

    So, I’ve had my tinyg V8 for a few weeks hooked up to my OX CNC.

    One of the first things I did was to use the avrdude update method to update the firmware to tinyg-master-440.18.hex. The update was uneventful and everything worked fine.

    Today, I went to use the CNC and dropped a file into chilipepper. Not sure what happened, but it appears the file was some how corrupt and chilipeppr was just filled with a bunch of ‘garbage’ characters and somehow it locked up the tinyg.

    Ok, So I shut down chilipeppr and sjsp and turned off the tinyg, brought everything back up. sjsp connects and chilipeppr looks fine, but the tinyg just flashes the spdir (bootloader mode).

    So I go back to reflash the tinyg with 440.18 and the flash appears to go normally, (using -e and no failed messages)

    But at the end I get this message.

    avrdude: verifying …
    avrdude: verification error, first mismatch at byte 0x0000
    0x00 != 0x0c
    avrdude: verification error; content mismatch

    avrdude done. Thank you.

    And nothing I can do will get the tinyg to respond or get out of bootloader mode.

    I’ve read through a bunch of topics on this issue and most seem to indicate the following issues

    1) Not using -e on the avrdude command line. I’m using it and it is erasing the memory and appears to load the hex file correctly.

    2) An incorrect hex file. It’s the same exact hex file I have used previously, so I don’t think that could be the issue.

    3) Some kind of fuses or lock issue. Most posts indicate that this was a problem with earlier versions and that it is not an issue with this version of board.

    So I’m at a loss as to how to bring this board back. I’d be willing to buy an avrisp MKII if I had to, but the details on the page says a clone won’t work. About all I can find for sale it seems are ‘compatible’ items.

    So My questions are:

    1) Is there an easy fix for this?
    2) If I need a programmer to fix it, would a compatible one work?

    Any info that can help get me back in business would be greatly appreciated.

    November 22, 2015 at 4:22 pm #8964
    KingBubbaTruck
    Member

    I think I found an answer on the programmer at least.
    From https://github.com/synthetos/TinyG/wiki/Programming-TinyG-with-an-External-Programmer

    Your garden variety AVR programmers will not work, as they only support the AVR ISP protocol and not the PDI programming protocol required by the Xmega.

    And I found one on Amazon that claims to support PDI, Including the Xmega chip.

    Guess I’ll order one of those, as it would be handy to have around at any rate.

    November 22, 2015 at 10:17 pm #8965
    cmcgrath5035
    Moderator

    Hmmm, I have never experienced or heard of an actual verification error. Sooner or later everything happens.

    I’m also at a loss as to how a corrupted Gcode file could affect flash memory or fuse bits, etc.

    What OS are you flashing from?
    What version of avrdude do you have (avrdude –help)?

    You using CLI to run ardude, I assume?

    If you are already in bootloader mode, and know your connection port (COMx or /dev/ttyUSB0, etc), and are running Windows, you could try the FW updater in SPJS 1.86.
    I have been doing a lot of testing , seems to work well on Windows, Linux and Mac are questionable. To try it, get CP connected to SPJS 1.86 and go directly to the FW updater. I would recommend upgrading to 440.20, using the online SYnthetos download offered up by the SPJS updater.

    If no go,come back and I’ll offer up another alternative once I know your OS environment.

    November 22, 2015 at 10:33 pm #8966
    KingBubbaTruck
    Member

    I’m using windows 7, avrdude 6.0.1.

    I’ve tried both 440.18 and 440.20 .hex files, same results.

    spjs 1.86 finds the usb port, but when I try the updated, specifing tinyg v8, and the 440.20 version via the online download, I get an error message saying
    “could not find board arduino:avr:tinyg”.

    Thanks so much for your help!

    November 23, 2015 at 6:18 am #8968
    cmcgrath5035
    Moderator

    spjs 1.86 finds the usb port, but when I try the updated, specifing tinyg v8, and the 440.20 version via the online download, I get an error message saying
    “could not find board arduino:avr:tinyg”.

    OK, that is likely a sanity check of the board by the SPJS programmer code before it initiates the FW upgrade cycle. It would be looking for a sane tinyG on the client end, not the bootloader running.

    avrdude 6.0.1 is what SPJS includes and calls as well, so that is not the issue.

    Try this if you want: Download

    Unzip the archive into a clean directory and read the readme.txt. This is simply all the files you need in one place, but should be same versions as you have already tried.

    I am doubtful my files will help. Seems something is borked in your tinyG.
    If you are in the US, quickest recovery might be to send it back to Synthetos for a brain refresh.

    November 23, 2015 at 10:30 am #8970
    KingBubbaTruck
    Member

    Really appreciate the help. I should have mentioned that I’m on 64bit. I did copy that hex file and tried up upload that with both the -e and -D paramaters for avrdude. No luck.

    I’ll contact Synthetos and see what they have to say. It really is the strangest thing.

    Thanks again!

    November 23, 2015 at 1:54 pm #8971
    cmcgrath5035
    Moderator

    Is this the first time you have tried to upgrade FW?

    I think contacting Synthetos is best path.

    November 23, 2015 at 3:44 pm #8974
    KingBubbaTruck
    Member

    One of the first things I did when I got it was to upgrade the FW so it would work correctly with Chilipeppr. It went just fine.

    This was just so weird. Dropped a file on chilipeppr, all the fields got filled with garbage characters and the tinyg quit working and would not accept the same firmware I had used before.

    I’ve got a gshield and some pololu drivers laying around, so will get that going as a backup while I work on getting this tinyg back in operating condition.

    November 23, 2015 at 7:36 pm #8977
    cmcgrath5035
    Moderator

    Weird – yes, I don’t know how/why bogus stuff in CP could result in tinyG changing fuse or other internal settings. If upgrade worked once already, then fuses should have been set OK.

    Unfortunately, you are on the hairy edge of debug capability.
    The sooner you can get the unit headed to Synthetos for brain fix, the faster it will return.

    November 27, 2015 at 10:11 am #8986
    MockTurtle
    Member

    Hey there,

    Did you manage to get a resolution?

    The exact same thing happened to me just now!

    Was just starting a job to carve out some xmas prezzies for tonight. Dropped gcode into chillipeppr…see garbled text >>> tinyg dead!

    Tried reflashing, got the 0x00 != 0x0c error. Now am stuck.

    All this just from loading gcode via chillipeppr???

    November 27, 2015 at 11:37 am #8987
    KingBubbaTruck
    Member

    Havn’t got a resolution yet, but I’ve been busy the last couple days and it’s COLD out in the shop. I’ll definitely come back once I get something worked out.

    November 27, 2015 at 12:08 pm #8988
    MockTurtle
    Member

    thanks for feedback. really keen if you heard from riley?
    dreaded worst case scenario for me is not being able to carve out anything till next year 🙁

    November 27, 2015 at 12:35 pm #8989
    KingBubbaTruck
    Member

    I just sent the email a few minutes ago. I can’t imagine it’s a fatal issue, just a road bump. Let me know if you find anything else out. Don’t take it the wrong way, but I’m kind of glad its not just me!

    November 27, 2015 at 6:19 pm #8993
    cmcgrath5035
    Moderator

    Mock turtle = Garbled text where in CP?
    Is the Gcode trashed, or ??

    Some other info would be helpful:
    SPJS version, and OS SPJS runs on ?
    what firmware were you running on tinyG? (440.20 most recent)

    How did you attempt to upgrade reinstall FW?
    SPJS firmware updater?

    November 27, 2015 at 6:20 pm #8994
    cmcgrath5035
    Moderator

    Mock turtle = Garbled text where in CP?
    Is the Gcode trashed, or ??

    Some other info would be helpful:
    SPJS version, and OS SPJS runs on ?
    what firmware were you running on tinyG? (440.20 most recent)

    How did you attempt to upgrade reinstall FW?
    SPJS firmware updater?

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 47 total)
1 2 3 4
  • You must be logged in to reply to this topic.