Debug Port Inaccessible – MCU Issue, Not Boot

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

Debug Port Inaccessible – MCU Issue, Not Boot

451 Views
samjalkh
Contributor I

I’d like to share a problem I encountered while working with the EVK-MIMXRT1024 board.

This is not a boot loader issue – it’s an MU-level problem. When attempting to debug, I consistently get the following errors:

15: Target error from Read Memory
Debug port inaccessible after access at location 0x402D8004
Debug port inaccessible after access at location 0x402D8008
Debug port inaccessible after access at location 0x402D8010
Debug port inaccessible after access at location 0x402D8014
Debug port inaccessible after access at location 0x402D8024
Debug port inaccessible after access at location 0x402D8040
Debug port inaccessible after access at location 0x402D8044
Debug port inaccessible after access at location 0x402D8064
Debug port inaccessible after access at location 0x402D8084
Debug port inaccessible after access at location 0x402D80C4
Debug port inaccessible after access at location 0x402D80E4
Debug port inaccessible after access at location 0x402D80E8
Debug port inaccessible after access at location 0x402D80EC
Debug port inaccessible after access at location 0x402D80F0
Debug port inaccessible after access at location 0x402D8100
Debug port inaccessible after access at location 0x402D8118

Debugging context: evkmimxrt1024_hello_world Link Server Debug

The debug port becomes inaccessible after memory access attempts at specific addresses in O CRAM. This strongly indicates an MU-side fault rather than a boot loader misconfiguration

 

0 Kudos
Reply
1 Reply

416 Views
Gavin_Jia
NXP TechSupport
NXP TechSupport

Hi @samjalkh ,

Thanks for your interest in NXP MIMXRT series!

Did this issue occur during the debugging phase after you accessed a specific register address? However, based on the log, this address appears to be an ENET peripheral register rather than one in OCRAM. If that's the case, the discussion in this post may be helpful to you: https://community.nxp.com/t5/i-MX-Processors/Simple-question-regarding-memory-access/m-p/1575898

Best regards,
Gavin

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2329020%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EDebug%20Port%20Inaccessible%20%E2%80%93%20MCU%20Issue%2C%20Not%20Boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2329020%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EI%E2%80%99d%20like%20to%20share%20a%20problem%20I%20encountered%20while%20working%20with%20the%20%3CSTRONG%3EEVK-MIMXRT1024%3C%2FSTRONG%3E%20board.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20is%20%3CSTRONG%3Enot%20a%20boot%20loader%20issue%3C%2FSTRONG%3E%20%E2%80%93%20it%E2%80%99s%20an%20MU-level%20problem.%20When%20attempting%20to%20debug%2C%20I%20consistently%20get%20the%20following%20errors%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E15%3A%20Target%20error%20from%20Read%20Memory%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8004%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8008%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8010%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8014%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8024%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8040%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8044%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8064%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8084%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D80C4%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D80E4%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D80E8%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D80EC%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D80F0%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8100%3CBR%20%2F%3EDebug%20port%20inaccessible%20after%20access%20at%20location%200x402D8118%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EDebugging%20context%3A%3C%2FSTRONG%3E%20evkmimxrt1024_hello_world%20Link%20Server%20Debug%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20debug%20port%20becomes%20inaccessible%20after%20memory%20access%20attempts%20at%20specific%20addresses%20in%20O%20CRAM.%20This%20strongly%20indicates%20an%20%3CSTRONG%3EMU-side%20fault%3C%2FSTRONG%3E%20rather%20than%20a%20boot%20loader%20misconfiguration%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2329338%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Debug%20Port%20Inaccessible%20%E2%80%93%20MCU%20Issue%2C%20Not%20Boot%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2329338%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F89955%22%20target%3D%22_blank%22%3E%40samjalkh%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20interest%20in%20NXP%20MIMXRT%20series!%3C%2FP%3E%0A%3CP%3EDid%20this%20issue%20occur%20during%20the%20debugging%20phase%20after%20you%20accessed%20a%20specific%20register%20address%3F%20However%2C%20based%20on%20the%20log%2C%20this%20address%20appears%20to%20be%20an%20ENET%20peripheral%20register%20rather%20than%20one%20in%20OCRAM.%20If%20that's%20the%20case%2C%20the%20discussion%20in%20this%20post%20may%20be%20helpful%20to%20you%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fi-MX-Processors%2FSimple-question-regarding-memory-access%2Fm-p%2F1575898%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fi-MX-Processors%2FSimple-question-regarding-memory-access%2Fm-p%2F1575898%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3CBR%20%2F%3EGavin%3C%2FP%3E%3C%2FLINGO-BODY%3E