confirmed
36
edits
Difference between revisions of "AVR Drivers"
→Test the connection
| Line 125: | Line 125: | ||
Now everything is installed and set up. You should be able to plug in your USB programmer with the cable leading to the clip. Attach the clip to the Atmel chip right-side up with at least the 5 critical pins wired correctly. | Now everything is installed and set up. You should be able to plug in your USB programmer with the cable leading to the clip. Attach the clip to the Atmel chip right-side up with at least the 5 critical pins wired correctly. | ||
Be aware that AVRDUDE does not officially support ATtiny13A and you will be using AVRDUDE with ATtiny13 setting "-p t13" instead of unsupported "-p t13a". The difference I found were lockbits when reading with ATtiny13A with it's proper setting compared to ATtiny13 setting. Otherwise it could work if you know what you're doing. | Be aware that AVRDUDE does not officially support ATtiny13A and you will be using AVRDUDE with ATtiny13 setting "-p t13" instead of unsupported "-p t13a". The difference I found were lockbits when reading with ATtiny13A with it's proper setting compared to ATtiny13 setting. Otherwise it could work if you know what you're doing. On a typical Nanjg105C both lock bits are set (zeroed) and programming can only be done after chip erase that is automatically done by avrdude when new flash memory is written with -U parameter. That most likely also prevents reading of the original firmware, which can be read but due to lock bits may be read as garbage/nonsense and cannot be used as backup. | ||
Now open a command window in Windows (or whatever you are in) and typing this command at the C: prompt: | Now open a command window in Windows (or whatever you are in) and typing this command at the C: prompt: | ||