The debugged session ran into 0xDEADxxxx address after enable flexio3

[sprhawk]

I'm writing a demo to use flexio, used one thirdparty EVK based on i.MX RT1062CVL5B.

When I enabled flexio3, the program ran into 0xDEADxxxx address

The testing code is attached.

To my tests, when I disable timer0 or disable flexio, the program ran well, but it ran into 0xDEADxxxx when enable timer0.

Got no clue why it is so.

[MultipleMonomials]

This type of error is easy to cause if you access the registers to a peripheral before enabling its clock -- the chip just locks up and it's not pretty.  Make sure in the clock configuration menu that you have enabled the FLEXIO2/FLEXIO3 clock and that it's set to a valid frequency (IIRC, up to 120MHz).

[EdwinHz]

Hi @sprhawk,

Please follow the instructions as seen on this knowledge base article to recover the debug session in case you are facing issues with the debugger: RT board recovery for debugger connect issues - NXP Community.

If there are no issues with the debugger, then you can ignore that step.

It is likely that a hard fault is being caused by an incorrect initialization of a module. Please try debugging and running the application step by step to determine in what line of code the hard fault occurs. This step will be crucial to understand what is causing the issue.

BR,
Edwin.