• State Suggested Answer
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 120 subscribers
  • Views 94 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?

Unable to connect to target I.MX8MPLUS

bhardwaj kotha

Hi,

When I am trying to detect my target platform  for i.MX8Mplus processor using the ARM Development Studio v2025.0-1 . I am getting prints like this

[23/09/25 12:02:59] Arm Development Studio v2025.0-1, build number 2025010903

[23/09/25 12:02:59] JTAG Clock Speed : 7500000Hz

[23/09/25 12:02:59] Beginning Autodetection

[23/09/25 12:03:00] --- --- ---

[23/09/25 12:03:00] Connected to Debug Probe

[23/09/25 12:03:00] --- --- ---

[23/09/25 12:03:00] --- --- ---

[23/09/25 12:03:00] Counting devices:

[23/09/25 12:03:00] DR Chain [136]:

00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

00000000

[23/09/25 12:03:00] Device Count: 136

[23/09/25 12:03:00] Detected number of devices = 136, maximum allowed = 128. This problem is usually a result of the scanchain not acting correctly when using JTAG scans to count the number of devices.

[23/09/25 12:03:00] Performing legacy SWD->JTAG switch

[23/09/25 12:03:00] Counting devices:

[23/09/25 12:03:00] DR Chain [136]:

00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

00000000

[23/09/25 12:03:00] Device Count: 136

[23/09/25 12:03:00] Performing Dormant Mode SWD->JTAG switch

[23/09/25 12:03:00] Counting devices:

[23/09/25 12:03:00] DR Chain [136]:

00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

00000000

[23/09/25 12:03:00] Device Count: 136

[23/09/25 12:03:00] --- --- ---

[23/09/25 12:03:00] Disconnected from Debug Probe

[23/09/25 12:03:00] --- --- ---

[23/09/25 12:03:05] JTAG detection failed, trying SWD

[23/09/25 12:03:05] WARNING - Multi-drop SWD is not supported, a single DAP on the scanchain has been assumed.

[23/09/25 12:03:05] The scanchain must be built manually if more scanchain devices are present.

[23/09/25 12:03:07] --- --- ---

[23/09/25 12:03:07] Disconnected from Debug Probe

[23/09/25 12:03:07] --- --- ---

[23/09/25 12:03:07] --- --- ---

[23/09/25 12:03:07] Disconnected from Debug Probe

[23/09/25 12:03:07] --- --- ---

[23/09/25 12:03:07] Unable to connect to device ARMCS-DP

Parents Reply Children
  • 0 Arm Employee Badge in reply to bhardwaj kotha

    Hi again

    Sorry, I meant to add:
    After interrupting u-boot, issue this command:

    u-boot=> bootaux 0x7e0000
    ## Starting auxiliary core stack = 0xEDFE0DD0, pc = 0x28040000...

    In our tests (with an early board/distro) we also needed to issue this command, but sorry, I don't know whether it will be needed for your setup, or whether the values might need to be different:
    u-boot=> md.w 0x30340058 0xFFFFFFFE

    For more information see section 4.7.4.1.2 of

    www.nxp.com/.../UG10163.pdf

    If you still need more help, I suggest you reach out to the NXP Community at

    https://community.nxp.com/

    who are best placed to advise on the specifics of their board boot,
    or "Open a Support Case" with Arm using the Support link at the bottom of this page.

    Stephen