0
votes

So, I programmed an ATMEGA32u4 and when I connect the device, it doesn't run the code. Instead, it gets recognised as an ATMEGA32u4 chip in Windows device manager.

To get the code running I have to open Atmel FLIP and open USB and then have to press the start application button after which it gets recognised as a HID in device manager and works as intended. I don't know why and what is happening.

The reset is pulled high with a 10k and the HWB is pulled down with a 10k and the chip has the factory bootloader on it.(if this helps)

1
Are you expecting Windows to receive some data from the ATMEGA32u4 system, or is there some other indication that the ATMEGA32u4 system is running (e.g. it has a heartbeat LED flash)? - Andrew Morton
If you are asking - if am expecting windows to receive some data during the bootup process, then no, after bootup, yes since it will be working as an HID. I have no indications for during bootup but after launching the application through FLIP the LEDs do light up for custom lighting and the inputs work. The device is a keyboard so it is pretty easy to discern if it is working or not just by shorting the switches. - Arya Kumar Sourav

1 Answers

0
votes

Pulling down HWB is what you do if you want to start the bootloader built into the ATmega32U4. It sounds like you want to run your own code instead of running the bootloader so you should pull HWB up, or disable the HWBE fuse.