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

DS-5 is able to see DAP, but nothing beyond?

Hi,

When I am configuring the platform, DS-5 is able to see all the ARM chain like this:

correct.PNG

However after new revision of code is released(NOTHING in ARM is touched), now I am only able to get this:

image (1).png

I used to seen the situation where the DAP is not even observed, and that was when something is wrong with ARM connection inside FPGA. But I don't understand how come that DAP is OK but the chain does not show up.

I am new to FPGA emulation and DS-5, so many thanks to anyone that help!

Regards

Nicole

Parents
  • Hi Nicole,

    What would really help us here is for you to tell us what you see in the text box under the main GUI. This has the results of the auto-detection process.

    What I suspect it happening is that the DAP is detected, but that the CoreSight ROM table read fails, and so as a result, the Cortex-R4 and the CoreSight components are not detected.

    You should see something like the following :

    info: Opening the debug pre-connection to device 1

    info: Powering up the DAP

    info: Connecting to the DAP

    info: Detecting AP buses

    info: DAP_CONFIG_INFO = 2,00:H,01:H

    info: Found AHB-AP on AP0

    info: Found AHB-AP on AP1

    info: Looking for ROM tables on AP 0

    info: Reading ROM table for AHB-AP at AP index 0 :-

    info: ROM table base address = 0xE00FF000

    ...

    ...

    ...

    On your system, the ROM table base address will be different of course.

    The AP-BASE register on the debug APB must be correctly pointing to the start of the CoreSight ROM table on the debug APB. I believe the default address is 0x80000000 for the ROM table.

    So please pass on your text from when you auto-detect.

    Regards,

    Stuart Hirons,

    ARM

Reply
  • Hi Nicole,

    What would really help us here is for you to tell us what you see in the text box under the main GUI. This has the results of the auto-detection process.

    What I suspect it happening is that the DAP is detected, but that the CoreSight ROM table read fails, and so as a result, the Cortex-R4 and the CoreSight components are not detected.

    You should see something like the following :

    info: Opening the debug pre-connection to device 1

    info: Powering up the DAP

    info: Connecting to the DAP

    info: Detecting AP buses

    info: DAP_CONFIG_INFO = 2,00:H,01:H

    info: Found AHB-AP on AP0

    info: Found AHB-AP on AP1

    info: Looking for ROM tables on AP 0

    info: Reading ROM table for AHB-AP at AP index 0 :-

    info: ROM table base address = 0xE00FF000

    ...

    ...

    ...

    On your system, the ROM table base address will be different of course.

    The AP-BASE register on the debug APB must be correctly pointing to the start of the CoreSight ROM table on the debug APB. I believe the default address is 0x80000000 for the ROM table.

    So please pass on your text from when you auto-detect.

    Regards,

    Stuart Hirons,

    ARM

Children