Did I brick an ATmega32U4 by writing flash via Atmel Studio?
Posted: Wed Jun 28, 2017 9:51 am
I am experimenting with ATmega32U4 chip, in the end I hope to achieve to get my Arduino Micro code running in an ATmega32U4 chip (placed on a custom PCB).
I connected the ATmega32U4 chip (which has wiring to micro USB) to my Windows 10 PC via USB. After installing Atmel Studio 7 (installs some drivers too), the chip was successfully recognized, device manager detects an ATmega32U4 chip.
The next thing I did, was attempt to write my .HEX (compiled by Arduino IDE) file via Atmel Studio >> Tools >> Device Programming to the flash memory of the ATmega chip (Atmel stated flash was written successfully).
Here isthe datesheet of atmega32u4
After that, Atmel Studio was no longer able to connect to the ATmega chip (Atmel Studio shows "disconnected" for the ATmega in the Tools >> Device programming dialog). Also the device manager in Windows 10 no longer detects the chip when I reconnect the USB cable to the ATmega chip.
As I said, I am still learning and probably need to learn a whole lot more but:
Did I reprogram the default ISP bootloader on the ATmega, which was solely responsible to communicate over USB?
Or is that complete nonsense, and is it more likely that I damaged the chip electrically and burned something?
Is it a bad idea to flash HEX files via Atmel Studio? I thought that would be my easy way out of using a SPI programmer (which I also never used before)
Hoping for somebody willing to teach me some of the fundamentals here!
I connected the ATmega32U4 chip (which has wiring to micro USB) to my Windows 10 PC via USB. After installing Atmel Studio 7 (installs some drivers too), the chip was successfully recognized, device manager detects an ATmega32U4 chip.
The next thing I did, was attempt to write my .HEX (compiled by Arduino IDE) file via Atmel Studio >> Tools >> Device Programming to the flash memory of the ATmega chip (Atmel stated flash was written successfully).
Here isthe datesheet of atmega32u4
After that, Atmel Studio was no longer able to connect to the ATmega chip (Atmel Studio shows "disconnected" for the ATmega in the Tools >> Device programming dialog). Also the device manager in Windows 10 no longer detects the chip when I reconnect the USB cable to the ATmega chip.
As I said, I am still learning and probably need to learn a whole lot more but:
Did I reprogram the default ISP bootloader on the ATmega, which was solely responsible to communicate over USB?
Or is that complete nonsense, and is it more likely that I damaged the chip electrically and burned something?
Is it a bad idea to flash HEX files via Atmel Studio? I thought that would be my easy way out of using a SPI programmer (which I also never used before)
Hoping for somebody willing to teach me some of the fundamentals here!