I had some of this in a different thread, but figured I'd open up thing here in case other people have some ideas.
As of a "while" ago, I've been having problems flashing firmware updates using my mkII programmer and Studio 6. It is consistently in the same location in memory (0x17c00) and it always complains that it read the value 0xff. In a few cases I've been able to find a version which I can flash, but I believe that's because that memory location happens to be 0xff anyway (unconfirmed). In fact, the only firmware I'm able to flash right now is the dev default/tinyg.hex.
Some of the things I've tried:
1. Reflashing the firmware for the programmer itself.
2. Changing out XMEGA chips(!) to rule out chip memory issues.
3. Changing USB cables and different USB busses.
I really don't want to reinstall Studio 4 to test it's programmer, but I might try that if I get desperate. I can also try to use a Linux-based programmer, or try the experimental bootloader bootstrapping from the one firmware I can load.
Anyone else have any suggestions on what the problem might be, and a fix?
Thanks,
-Matt
I assume you are using AtmelStudio6 for this? Can you list your settings so I can compare to what I use?
Also, have you tried using the bootloader? It's experimental now but is working well for a few folks that are testing it. It's in the dev branch and documented here:
OK, this thread just saved my bacon. I bricked my board trying to install the latest firmware using Studio 6 SP2. Upgrading to Studio 6.1 beta fixed it for me too. Thanks!
Thanks for setting up this thread, I am going to make sure I have 6.1 and the new firmware installed before I attempt this for the first time. Just to be crystal for someone who hasn't done this before, I need to download and unzip the contents of the github under: TinyG/Firmware and then in Atmel Studio, I will navigate to and load the Tinyg.hex file located in the default folder. Is this correct? I'm not really a computer guy and though the wiki is great, I am a little green to feel 100% comfortable not bricking the thing with the directions currently up there. Thanks!
Just to point it out to the admins, the link to the latest firmware from the Wiki for 0.94 and earlier is incorrect. Updating that may help new users not be too worried about whether or not they have the right .hex file.