• State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 123 subscribers
  • Views 11113 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed to detect my target platform using Arm DS-5 Debugger

Raj Srikar

Hi,

When I am trying to detect my target platform having ARM v7 processor using the ARM DS -5 Debugger . I am getting prints like this

[04/09/18 11:05:11] ARM DS-5 v5.29.1, build number 5291003
[04/09/18 11:05:11] JTAG Clock Speed : Auto
[04/09/18 11:05:11] Beginning Autodetection
[04/09/18 11:05:12] --- --- ---
[04/09/18 11:05:12] Counting devices:
[04/09/18 11:05:12] DR Chain [1024]:
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111110
[04/09/18 11:05:12] Device Count: 1
[04/09/18 11:05:12] The total IR length of the scanchain measured as 4
[04/09/18 11:05:12] Reading IDCODEs:
[04/09/18 11:05:12] DR Chain [32]:
00001011101000000010010001110111
[04/09/18 11:05:12] Device 0 has IDCODE = 0x0BA02477 (Manufacturer ID: 0x23B, Part Number: 0xBA02, Revision: 0x0)
[04/09/18 11:05:12] IR Chain [16]:
1111111111110001
[04/09/18 11:05:12] Device 0 detected IR Length = 4
[04/09/18 11:05:12] Device 0 detected as ARMCS-DP
[04/09/18 11:05:12] --- --- ---
[04/09/18 11:05:12] Enumerating AP devices for DAP at scanchain index 0:
[04/09/18 11:05:12] Unable to connect to device ARMCS-DP
[04/09/18 11:05:12] Unable to connect to device ARMCS-DP
[04/09/18 11:05:12] Failed to detect APs
[04/09/18 11:05:12] Autodetection Complete.


Can anybody resolve this issue?

Regards,

Raj Srikar.

Parents
  • 0

    Hi Raj,

    So the good news is that the Arm DAP (Debug Access Port) can successfully be found on your platform, we can see the JTAG IDCODE being read out as :

    0x0BA02477

    So this tells us that the basic JTAG comms look ok.

    What it looks like is happening next is that the Access Port (AP) enumeration is failing, and that could be for a number of reasons,

    - is the target powered up correctly ?

    - is the target powered up but an OS such as Linux is running that has turned off the debug clocks in order to save power ?

    If your target is running Linux by default, and Linux has booted, then try power-cycling the target and then halting it at the (u)boot prompt and then re-run PCE and see if anything changes.

    Please let me know the outcome.

    thanks,

    Stuart Hirons

Reply
  • 0

    Hi Raj,

    So the good news is that the Arm DAP (Debug Access Port) can successfully be found on your platform, we can see the JTAG IDCODE being read out as :

    0x0BA02477

    So this tells us that the basic JTAG comms look ok.

    What it looks like is happening next is that the Access Port (AP) enumeration is failing, and that could be for a number of reasons,

    - is the target powered up correctly ?

    - is the target powered up but an OS such as Linux is running that has turned off the debug clocks in order to save power ?

    If your target is running Linux by default, and Linux has booted, then try power-cycling the target and then halting it at the (u)boot prompt and then re-run PCE and see if anything changes.

    Please let me know the outcome.

    thanks,

    Stuart Hirons

Children
No data