I got this function hanving the MCU (not right away, though, after approximately 150 seconds after starting up the MCU).
It doesn't hang completely, it enters some sort of a loop and the MCU is still responsive to interrupts.
"I got this function "
(just to avoid this word's entropy to increase at an uncredible speed)
And , is it the only one (Murphy is dead, then)?
Well it is USB_USBTask, as said in the topic title :)
In USB_USBTask() it enters USB_Host_ProcessNextHostState() and stays there...
It is funny, but there is no place for hanging in USB_Host_PRocessNextHostState()
It may be that the stack is somehow corrupt (Guesswork).
The MCU has 8kb of memory where the section data is only 1798 bytes with .bss totally moved to the external memory. So quite a lot for the stack and yet...
Looking for an answer to the question what screws the code I think I've trapped a linker bug: there was a variable defined in three source files as extern and wasn't actually declared anywhere and still that would compile into an .elf file. May we have the avr-gcc lovers in the studio?:)
Locked. You have 5 pages already here https://www.avrfreaks.net/index.p... with the same topic. Please continue there.
Ampertronics Pty. Ltd.
* Electronic Design * Custom Products * Contract Assembly
© 2019 Microchip Technology Inc.