dev_cdc_vcom_freertoc_cm7 example USB app does not work from SDK v12.1 with the 1170 EVK. If I try to debug the code, the debugger crashes and leaves the EVK in a state where I cannot reflash it. See screenshot below of all the unintelligble errors that pop up when trying to flash a simple HelloWorld program.
To overwrite the application with something that is not broken I must hold down the reset button while pressing Debug in MCUXpresso and release reset button when it tries to attach, in this way it can intercept the core before reaching a faulty (low power sleep?) mode.
Very frustrating to work with, I am surprised by how buggy and brittle the flashing/debugging experience still is with the iMXRT1170 EVK...
Hello,
I review your image and I recommend doing a mass erase, with the tool below.
https://github.com/JayHeng/NXP-MCUBootUtility
I recommend reviewing this thread in the chapter Boot Utility to the Rescue!
Regaining Debug Access to NXP i.MX RT1064-EVK executing WFI | MCU on Eclipse
If you have any questions, please let me know.
Best regards,
Pavel
Hi @erling The steps that you need to do is:
1. Open MCUXpresso IDE.
2. Import any example of the SDK. In this guide, I imported the iled_blinky example. In the end, I will explain why you need this project.
3. Go to your RT1170-EVK and locate SW1.
4. Change to serial boot loader
5. At this point, you need to do a power-cycle to your board (disconnect and connect the power), so the changes in SW7 take effect.
6. Go back to MCUXpresso, since you just imported the project, I assume that it doesn’t have any debug configurations if you are using another project that does have debug configurations please delete them.
7. Launch the debug session of the project while in serial downloader.
8. When the debug session is launched, you won’t see that the program stops at the main as it normally does, your debug session will look like the image below. This is because you are in serial downloader mode.
9. Stop this debug session.
10. Delete the debug configuration of the project, as shown in image 2.
11. Go to your board and change the SW1 back to the way
12. Do a power cycle to your evaluation board.
13. That’s it! At this point, you should be able to enter the debug sessions without any problems.
I hope this will help you
Have a good day
Best Regards
Thanks for your suggestion, however it does not work. I had already tried using serial bootloader and the MCU Boot Utility. But it is not able to get contact with the CPU. The LED next to the USB connector (D5?) is just blinking red with constant period. What are my other options?
Your J38 is jumped on 1-2? are you using a cilinder power? or is jumped 3-4 and you are using a usb2 as a power board? check that part, because the last error that you have is no power DAP.
Check this post about to unbrick your board in case that your board is brick https://mcuoneclipse.com/2016/08/01/bricking_and_recovering_opensda_boards_in_windows_8_and_10/
And at last, if nothing of all this no works, you need to unbrick using a j-link, https://community.nxp.com/t5/S32K/Evalboards-S32K146-and-S32K148-unbrick/m-p/1303704
https://mcuoneclipse.com/2021/05/20/recovering-cortex-m-microcontroller-with-a-power-glitch/
https://community.nxp.com/t5/S32K/Evalboards-S32K146-and-S32K148-unbrick/m-p/1306070
I hope this help you and recovery your board.
Have a good day