-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
functional with a 32U4? #2
Comments
I forked to https://github.com/jmfriedt/gdb-debug-wire-integrated-server: I see you define each microcontroller characteristics and added my understanding of the 32U4 settings, but am failing to see where you select which microcontroller to target apart the |
This software is failing on Atmega32U4 because of
calling INT7 of EIMSK which exists on the Atmega32U2 (https://ww1.microchip.com/downloads/en/DeviceDoc/doc7799.pdf page 86) but not on the Atmega32U4! (https://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-7766-8-bit-AVR-ATmega16U4-32U4_Datasheet.pdf page 90) |
Do you think you can help describe the open collector communication state machine? I am confused because after replacing PD7 (since INT7 does not exist on Atmega32U4) with PE6, and replacing all references to INT7 with INT6 and PD7 with PE6 (I think), the USB initialization still hangs (no ttyACM0 created). I am tracking |
When setting the target option to
atmega32u4
in theCMakeLists.txt
and checking that indeed-mmcu=atmega32u4
is used during compilation (make VERBOSE=1
), flashing the resultingintegrated_server_elf
in an Olimexino32U4 board by usingfails to create a /dev/ttyACM0 entry as would be expected from the LUFA CDC as seems to be expected from the
avrdude
commands provided in the README.md. Is there an easy way to get this gdb server running on an Atmega32U4 already flashed with the AVR109 bootloader?Thanks.
The text was updated successfully, but these errors were encountered: