• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 120 subscribers
  • Views 4922 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

How to create configdb entry for debug to conect to coresight using D-STREAM. I put ARMCS-DP in scan chain and try to configure.

Shaibal Dutta

Hi,

I am trying to  create configdb entry for debug to conect to coresight using D-STREAM. I put ARMCS-DP in scan chain and try to configure .

Debug hardware config tool complains Coresight ROM table has failed - failed to read confi item DAP_CONFIG_INFO.

To debug furhter I used CSAT command line tool. I am able to read version ID and power up the DAP..

Here are the commands.

1) Con usb  (connect to DStream)

2) chain  dev=ARMCS-DP clk=20000  (put coresight in JTAG chain)

3) dvo 0  (This should print the ID)

4) drw DPACC.CSW  0x5400000  (Power up DAP)

5)  drr DPACC.CSW  (Please  let know what you read back.)

I am using ARMv8. I want to use dmr command to read some memory location but CSAT doesn't take more than 32 bit addresses.

Any ideas how to overcome this hurdle.

Thanks in advance.

Shaibal

  • 0

    Hi Shaibal,

    If you contact ARM technical support, they will be able to help you with the detail of creating a new configdb entry with your ARMv8 target.

    Thanks,

    Joe

  • 0

    Hi Shaibal,

    Is the device an in-house design? or a commercial product chip?

    It looks like you try to configuration the configuration pattern manually.

    I am trying to add the debug feature into my Cortex-M0 design for demo in course, and now I use an FPGA to valid it.

    Then I use the Debug Hardware configurations tools can auto-detect the ARMCS-DP block if I disable the 'read CoreSight ROM table'.

    And the tools report 'error: CoreSight ROM table read has failed - Failed to connect to the DAP' when I enable the 'read CoreSight ROM table and try to do 'Auto Configure'.

    AHBLITE_SYS1_1223a_bit-read_rom_table2.JPG

    I think it result from the bad content of the system rom table because I still study the IHI-0029D document.

    Maybe these information can give you some hint.

    And I would appreciated if anyone could tell me how to write the system rom table (a physical example would be good osz).

    best regards,

    sieg70