Flashing and Debugging Cortex-M7 Firmware on i.MX8M Plus EVK (with and without Cortex-A53)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Flashing and Debugging Cortex-M7 Firmware on i.MX8M Plus EVK (with and without Cortex-A53)

414 Views
Subrahmanyam1
Contributor I

Hello,

I am working with the i.MX8M Plus EVK (8MPLUSLPD4-EVK) and using the MCUXpresso SDK (not MCUXpresso IDE or VS Code) for Cortex-M7 development. I can successfully build my project and generate the output files (.elf and .bin) using the ARM GCC compiler.

Now I need clear guidance on the next step:

Flashing and Running M7 Firmware

  1. With Cortex-A53:

    • What is the detailed process to flash and run the M7 firmware using the Cortex-A53 side (for example via U-Boot commands or Linux remoteproc)?

  2. Without Cortex-A53:

    • What is the detailed process to flash and debug the M7 firmware directly, without depending on the A53 core?

    • How is the M7 firmware typically loaded into OCRAM/TCM, and can it be run fully standalone?

Debugging Tools and Probes

  • Which hardware debug probes are officially supported for connecting directly to the Cortex-M7 on this EVK (e.g., Segger J-Link)?

  • Which probes/tool-chains work well with bare-metal development (no IDE, only MCUXpresso SDK and GCC tool-chain)?

  • Is it possible to debug the M7 independently with JTAG/SWD, or must the A53 be involved for initialization?

    GOAL:

    I need a clear, step-by-step procedure for both development flows:

    • Flashing and debugging via Cortex-A53.

    • Flashing and debugging directly on Cortex-M7 (without A53).

    Any official documentation, application notes, or step-by-step references for these two methods would be very helpful.

Tags (1)
0 Kudos
Reply
0 Replies
%3CLINGO-SUB%20id%3D%22lingo-sub-2168685%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EFlashing%20and%20Debugging%20Cortex-M7%20Firmware%20on%20i.MX8M%20Plus%20EVK%20(with%20and%20without%20Cortex-A53)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2168685%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20working%20with%20the%20i.MX8M%20Plus%20EVK%20(8MPLUSLPD4-EVK)%20and%20using%20the%20MCUXpresso%20SDK%20(not%20MCUXpresso%20IDE%20or%20VS%20Code)%20for%20Cortex-M7%20development.%20I%20can%20successfully%20build%20my%20project%20and%20generate%20the%20output%20files%20(.elf%20and%20.bin)%20using%20the%20ARM%20GCC%20compiler.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ENow%20I%20need%20clear%20guidance%20on%20the%20next%20step%3A%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1974838707%22%20id%3D%22toc-hId-2000457756%22%3EFlashing%20and%20Running%20M7%20Firmware%3C%2FH3%3E%3COL%3E%3CLI%3E%3CP%3EWith%20Cortex-A53%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EWhat%20is%20the%20detailed%20process%20to%20flash%20and%20run%20the%20M7%20firmware%20using%20the%20Cortex-A53%20side%20(for%20example%20via%20U-Boot%20commands%20or%20Linux%20remoteproc)%3F%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3E%3CP%3EWithout%20Cortex-A53%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EWhat%20is%20the%20detailed%20process%20to%20flash%20and%20debug%20the%20M7%20firmware%20directly%2C%20without%20depending%20on%20the%20A53%20core%3F%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EHow%20is%20the%20M7%20firmware%20typically%20loaded%20into%20OCRAM%2FTCM%2C%20and%20can%20it%20be%20run%20fully%20standalone%3F%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FOL%3E%3CH3%20id%3D%22toc-hId-167384244%22%20id%3D%22toc-hId-193003293%22%3EDebugging%20Tools%20and%20Probes%3C%2FH3%3E%3CUL%3E%3CLI%3E%3CP%3EWhich%20hardware%20debug%20probes%20are%20officially%20supported%20for%20connecting%20directly%20to%20the%20Cortex-M7%20on%20this%20EVK%20(e.g.%2C%20Segger%20J-Link)%3F%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EWhich%20probes%2Ftool-chains%20work%20well%20with%20bare-metal%20development%20(no%20IDE%2C%20only%20MCUXpresso%20SDK%20and%20GCC%20tool-chain)%3F%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EIs%20it%20possible%20to%20debug%20the%20M7%20independently%20with%20JTAG%2FSWD%2C%20or%20must%20the%20A53%20be%20involved%20for%20initialization%3F%3CBR%20%2F%3E%3CBR%20%2F%3EGOAL%3A%3C%2FP%3E%3CP%3EI%20need%20a%20clear%2C%20step-by-step%20procedure%20for%20both%20development%20flows%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EFlashing%20and%20debugging%20via%20Cortex-A53.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EFlashing%20and%20debugging%20directly%20on%20Cortex-M7%20(without%20A53).%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAny%20official%20documentation%2C%20application%20notes%2C%20or%20step-by-step%20references%20for%20these%20two%20methods%20would%20be%20very%20helpful.%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E