Hi All,
When tried "Platform Configuration" on DS-5(Version 5.25) . I am not able to read my Core (ARM1176JZF-S).
When It is trying to read the Core Sight ROM table at 0x80007000. Getting the error "Failed to write 4 bytes to address 0x80007000 on CSMEMAP_1" .
Board Summary:
We have taken the soft core and harden in house and manufacture our own Evaluation board based on ARM1176JZF-S core.
Note:
As per our TRM, Core Sight is mapped to the address "0x68000000" . Do I need to change the Core Sight address in DS-5 ?
Need assistance in Rectifying this error.
Below is the Output log from DS-5 for "Platform Configuration".
ARM DS-5 v5.25.0, build number5250010
Beginning Autodetection
--- --- ---
Counting devices:
DR Chain [1024]:
[00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111110]
Device Count: 1
Reading IDCODEs:
DR Chain [32]:
[01001011101000000000010001110111]
Device 0 has IDCODE = 0x4BA00477
IR Chain [1024]:
[11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111110001]
Device 0 has IR Length = 4
Getting device names:
Device 0 detected as ARMCS-DP
Scanchain:
JTAGDeviceInfo[IDCODE = 0x4BA00477, IR Length = 4, Name = ARMCS-DP]
Connected to DTSL layer
Connected to DAP device
AP buses detected:
AHB-AP
APB-AP
JTAG-AP
Disconnected from DAP device
Disconnected from DTSL layer
Looking for ROM tables on AP0 (AHB-AP)
AHB-AP ROM table base address detected as 0xFFFFFFFF
No ROM table is present on this AP
Looking for ROM tables on AP1 (APB-AP)
APB-AP ROM table base address detected as 0x80000000
Reading ROM table for AP index 1, base address = 0x80000000
Reading ROM table info ...
ROM table part number = 0x0
ROM table JEP ID = 0x0
ROM table JEP Continuation Code = 0x0
ROM table revision number = 0x0
JEDEC used = True
RevAnd = 0x4
Customer modified = 0x4
Valid ROM table entries are:
0x00001003 (component base address: 0x80001000)
0x00002003 (component base address: 0x80002000)
0x00003003 (component base address: 0x80003000)
0x00004003 (component base address: 0x80004000)
0x00005003 (component base address: 0x80005000)
0x00007003 (component base address: 0x80007000)
0x00008003 (component base address: 0x80008000)
Reading peripheral and component ID registers of device at address 0x80001000
Component ID registers = 0x0d, 0x90, 0x05, 0xb1
Component class is CoreSight - identifying:
PID Reg 4 is 0x04
PID Reg 5 is 0x00
PID Reg 6 is 0x00
PID Reg 7 is 0x00
PID Reg 0 is 0x07
PID Reg 1 is 0xb9
PID Reg 2 is 0x3b
PID Reg 3 is 0x00
Peripheral ID = 0x907, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x21, DEVARCH = 0x0, Revision = 0x3
CSETB found at address 0x80001000
Reading peripheral and component ID registers of device at address 0x80002000
PID Reg 0 is 0x06
Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x3
CSCTI found at address 0x80002000
Reading peripheral and component ID registers of device at address 0x80003000
PID Reg 0 is 0x12
PID Reg 2 is 0x4b
Peripheral ID = 0x912, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x11, DEVARCH = 0x0, Revision = 0x4
CSTPIU found at address 0x80003000
Reading peripheral and component ID registers of device at address 0x80004000
PID Reg 0 is 0x08
PID Reg 2 is 0x1b
Peripheral ID = 0x908, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x12, DEVARCH = 0x0, Revision = 0x1
CSTFunnel found at address 0x80004000
Reading peripheral and component ID registers of device at address 0x80005000
PID Reg 0 is 0x13
PID Reg 2 is 0x2b
Peripheral ID = 0x913, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x43, DEVARCH = 0x0, Revision = 0x2
CSITM found at address 0x80005000
Reading peripheral and component ID registers of device at address 0x80007000
PID Reg 0 is 0x20
PID Reg 2 is 0x5b
Peripheral ID = 0x920, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x5
CSETM found at address 0x80007000
Reading peripheral and component ID registers of device at address 0x80008000
CSCTI found at address 0x80008000
End of ROM table
Getting device info ...
Acquiring device info for CSTFunnel (0x80004000):
Port Count: 8
Acquiring device info for CSETM (0x80007000):
CSETM (0x80007000) is powered down
Failed to read device info for device CSETM (0x80007000): Failed to write 4 bytes to address 0x80007000 on CSMEMAP_1
Detecting topology ... (may take several seconds)
Integration test preamble for device CSETB (0x80001000) failed
Integration test preamble for device CSCTI (0x80002000) failed
Integration test preamble for device CSTPIU (0x80003000) failed
Integration test preamble for device CSTFunnel (0x80004000) failed
Integration test preamble for device CSITM (0x80005000) failed
Integration test preamble for device CSETM (0x80007000) failed
Integration test preamble for device CSCTI (0x80008000) failed
Failed to get ATB master topology for device CSTFunnel (0x80004000): Failed to read 4 bytes from address 0x80004FB4 on CSMEMAP_1
Failed to get ATB master topology for device CSITM (0x80005000): Failed to read 4 bytes from address 0x80005FB4 on CSMEMAP_1
Failed to get ATB master topology for device CSETM (0x80007000): Failed to read 4 bytes from address 0x80007304 on CSMEMAP_1
Failed to get trigger topology for device CSCTI (0x80002000): Failed to read 4 bytes from address 0x80002FB4 on CSMEMAP_1
Failed to get trigger topology for device CSETM (0x80007000): Failed to read 4 bytes from address 0x80007304 on CSMEMAP_1
Failed to get trigger topology for device CSCTI (0x80008000): Failed to read 4 bytes from address 0x80008FB4 on CSMEMAP_1
Autodetection Complete
With regards,
-Shravan
Hi Shravan, I understand that you are in discussion with one of my ARM Support colleagues on this issue, so I suggest at this time that you continue to discuss this issue through the ARM Support channel.
But for any future questions in this area, for ARM cores that are on a JTAG-AP, these must be added manually as the Platform Configuration Editor will not attempt to auto-detect these for you.
Regards, Stuart