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

incomplete auto platform detection

Hi everyone,

I have a QCA IPQ4019 board. I used auto platform detection and got below warnings. It seems that I can not trace this device because of these warnings.

How can I fix? Also attached the PCE console log and sdf file FYI. Thanks for any advice.

PCE console log:

[02/09/19 10:36:06] ARM DS-5 v5.29.2, build number 5292005
[02/09/19 10:36:06] JTAG Clock Speed : Auto
[02/09/19 10:36:06] Beginning Autodetection
[02/09/19 10:36:07] --- --- ---
[02/09/19 10:36:07] Counting devices:
[02/09/19 10:36:07] DR Chain [1024]:
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
		11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111100000
[02/09/19 10:36:07] Device Count: 5
[02/09/19 10:36:07] The total IR length of the scanchain measured as 30
[02/09/19 10:36:07] Reading IDCODEs:
[02/09/19 10:36:07] DR Chain [160]:
		00000000000000000000000000000000000000000000000000000000000000000000001001011110010000111000010000000000000000000101101101110101
		01101110100000000001000111011100
[02/09/19 10:36:07] Device 0 has IDCODE = 0x009790E1 (Manufacturer ID: 0x070, Part Number: 0x0979, Revision: 0x0)
[02/09/19 10:36:07] Device 1 has IDCODE = 0x000016DD (Manufacturer ID: 0x36E, Part Number: 0x0001, Revision: 0x0)
[02/09/19 10:36:07] Device 2 has IDCODE = 0x5BA00477 (Manufacturer ID: 0x23B, Part Number: 0xBA00, Revision: 0x5)
[02/09/19 10:36:07] Device 3 has no IDCODE
[02/09/19 10:36:07] Device 4 has no IDCODE
[02/09/19 10:36:07] IR Chain [80]:
		11111111111111111111111111111111111111111111111111000000000010000100010000100001
[02/09/19 10:36:07] Device 0 detected IR Length = 11
[02/09/19 10:36:07] Device 1 detected IR Length = 5
[02/09/19 10:36:07] Device 2 detected IR Length = 4
[02/09/19 10:36:07] Device 3 detected IR Length = 5
[02/09/19 10:36:07] Device 4 detected IR Length = 5
[02/09/19 10:36:07] Device 0 detected as UNKNOWN_11
[02/09/19 10:36:07] Device 1 detected as UNKNOWN_5
[02/09/19 10:36:07] Device 2 detected as ARMCS-DP
[02/09/19 10:36:07] Device 3 detected as UNKNOWN_5
[02/09/19 10:36:07] Device 4 detected as UNKNOWN_5
[02/09/19 10:36:07] --- --- ---
[02/09/19 10:36:07] Enumerating AP devices for DAP at scanchain index 2:
[02/09/19 10:36:07] AP buses detected:
[02/09/19 10:36:07] 	AXI-AP
[02/09/19 10:36:07] 	APB-AP
[02/09/19 10:36:07] 	JTAG-AP
[02/09/19 10:36:08] --- --- ---
[02/09/19 10:36:08] 
Looking for ROM tables on AP0 (AXI-AP)
[02/09/19 10:36:08] AXI-AP version = 1, ROM address low word = 64, high word = 0x00000002
[02/09/19 10:36:08] Due to AXI version <=2 indicating erratum, base address high word and low word will be swapped
[02/09/19 10:36:08] AXI-AP ROM table base address detected as 0x0000000200000000
[02/09/19 10:36:08] 
    Reading ROM table for AP index 0, base address = 0x0000000200000000
[02/09/19 10:36:08]     Failed to read ROM table: Failed to read 16 bytes from address 0x200000FF0 on CSMEMAP
[02/09/19 10:36:08] --- --- ---
[02/09/19 10:36:08] 
Looking for ROM tables on AP1 (APB-AP)
[02/09/19 10:36:08] APB-AP ROM table base address detected as 0x80000000
[02/09/19 10:36:08] 
    Reading ROM table for AP index 1, base address = 0x80000000
[02/09/19 10:36:08]         ROM table part number = 0x97
[02/09/19 10:36:08]         ROM table JEP ID = 0x70
[02/09/19 10:36:08]         ROM table JEP Continuation Code = 0x0
[02/09/19 10:36:08]         ROM table revision number = 0x0
[02/09/19 10:36:08]         JEDEC used = True
[02/09/19 10:36:08]         RevAnd = 0x9
[02/09/19 10:36:08]         Customer modified = 0x0
[02/09/19 10:36:08]     Valid ROM table entries are:
[02/09/19 10:36:08]         0x00001003 (component base address: 0x80001000)
[02/09/19 10:36:08]         0x00002003 (component base address: 0x80002000)
[02/09/19 10:36:08]         0x00010003 (component base address: 0x80010000)
[02/09/19 10:36:08]         0x00011003 (component base address: 0x80011000)
[02/09/19 10:36:08]         0x00012003 (component base address: 0x80012000)
[02/09/19 10:36:08]         0x00013003 (component base address: 0x80013000)
[02/09/19 10:36:08]         0x00014003 (component base address: 0x80014000)
[02/09/19 10:36:08]         0x00015003 (component base address: 0x80015000)
[02/09/19 10:36:08]         0x00016003 (component base address: 0x80016000)
[02/09/19 10:36:08]         0x00017003 (component base address: 0x80017000)
[02/09/19 10:36:08]         0x00018003 (component base address: 0x80018000)
[02/09/19 10:36:08]         0x00020003 (component base address: 0x80020000)
[02/09/19 10:36:08]         0x00021003 (component base address: 0x80021000)
[02/09/19 10:36:08]         0x00024003 (component base address: 0x80024000)
[02/09/19 10:36:08]         0x00025003 (component base address: 0x80025000)
[02/09/19 10:36:08]         0x00026003 (component base address: 0x80026000)
[02/09/19 10:36:08]         0x00030003 (component base address: 0x80030000)
[02/09/19 10:36:08]         0x00031003 (component base address: 0x80031000)
[02/09/19 10:36:08]         0x00040003 (component base address: 0x80040000)
[02/09/19 10:36:08]         0x00041003 (component base address: 0x80041000)
[02/09/19 10:36:08]         0x00042003 (component base address: 0x80042000)
[02/09/19 10:36:08]         0x00043003 (component base address: 0x80043000)
[02/09/19 10:36:08]         0x00044003 (component base address: 0x80044000)
[02/09/19 10:36:08]         0x00045003 (component base address: 0x80045000)
[02/09/19 10:36:08]         0x00046003 (component base address: 0x80046000)
[02/09/19 10:36:08]         0x00047003 (component base address: 0x80047000)
[02/09/19 10:36:08]         0x0004C003 (component base address: 0x8004C000)
[02/09/19 10:36:08]         0x0004D003 (component base address: 0x8004D000)
[02/09/19 10:36:08]         0x0004E003 (component base address: 0x8004E000)
[02/09/19 10:36:08]         0x0004F003 (component base address: 0x8004F000)
[02/09/19 10:36:08]         0x00051003 (component base address: 0x80051000)
[02/09/19 10:36:08]         0x00052003 (component base address: 0x80052000)
[02/09/19 10:36:08]         0x00053003 (component base address: 0x80053000)
[02/09/19 10:36:08]         0x00054003 (component base address: 0x80054000)
[02/09/19 10:36:08]         0x00055003 (component base address: 0x80055000)
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80001000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x00
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x40
[02/09/19 10:36:08]             PID 1: 0x04
[02/09/19 10:36:08]             PID 2: 0x1f
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x440, JEP-106 code, including continuation = 0x70, DEVTYPE = 0x4, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     Unknown device found at address 0x80001000, peripheral ID = 0x440
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80002000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x62
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x1b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x962, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x63, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     CSSTM found at address 0x80002000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80010000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80010000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80011000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80011000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80012000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80012000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80013000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80013000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80014000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80014000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80015000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80015000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80016000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80016000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80017000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80017000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80018000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSCTI found at address 0x80018000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80020000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x12
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x912, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x11, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:08]     CSTPIU found at address 0x80020000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80021000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x08
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x2b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x908, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x12, DEVARCH = 0x0, Revision = 0x2
[02/09/19 10:36:08]     CSTFunnel found at address 0x80021000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80024000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x09
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x1b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x909, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x22, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     CSATBReplicator found at address 0x80024000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80025000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x61
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x1b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x961, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x32, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     CSTMC found at address 0x80025000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80026000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x61
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x1b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x961, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x21, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     CSTMC found at address 0x80026000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80030000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x00
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x40
[02/09/19 10:36:08]             PID 1: 0x04
[02/09/19 10:36:08]             PID 2: 0x1f
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x440, JEP-106 code, including continuation = 0x70, DEVTYPE = 0x4, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     Unknown device found at address 0x80030000, peripheral ID = 0x440
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80031000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x00
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x40
[02/09/19 10:36:08]             PID 1: 0x04
[02/09/19 10:36:08]             PID 2: 0x1f
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x440, JEP-106 code, including continuation = 0x70, DEVTYPE = 0x4, DEVARCH = 0x0, Revision = 0x1
[02/09/19 10:36:08]     Unknown device found at address 0x80031000, peripheral ID = 0x440
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80040000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x07
[02/09/19 10:36:08]             PID 1: 0xbc
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0xc07, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x15, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     Cortex-A7 found at address 0x80040000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80041000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0xa7
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x9a7, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x16, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     CSPMU found at address 0x80041000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80042000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x07
[02/09/19 10:36:08]             PID 1: 0xbc
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0xc07, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x15, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     Cortex-A7 found at address 0x80042000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80043000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0xa7
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x9a7, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x16, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     CSPMU found at address 0x80043000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80044000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x07
[02/09/19 10:36:08]             PID 1: 0xbc
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0xc07, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x15, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     Cortex-A7 found at address 0x80044000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80045000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0xa7
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x9a7, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x16, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     CSPMU found at address 0x80045000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80046000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x07
[02/09/19 10:36:08]             PID 1: 0xbc
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0xc07, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x15, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     Cortex-A7 found at address 0x80046000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80047000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0xa7
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x5b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x9a7, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x16, DEVARCH = 0x0, Revision = 0x5
[02/09/19 10:36:08]     CSPMU found at address 0x80047000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x8004C000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x56
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x0b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x956, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x0
[02/09/19 10:36:08]     CSETM found at address 0x8004C000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x8004D000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x56
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x0b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x956, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x0
[02/09/19 10:36:08]     CSETM found at address 0x8004D000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x8004E000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x56
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x0b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x956, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x0
[02/09/19 10:36:08]     CSETM found at address 0x8004E000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x8004F000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x56
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x0b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:08]         Peripheral ID = 0x956, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x0
[02/09/19 10:36:08]     CSETM found at address 0x8004F000
[02/09/19 10:36:08]     Reading peripheral and component ID registers of device at address 0x80051000
[02/09/19 10:36:08]         Component ID registers:
[02/09/19 10:36:08]             CID 0: 0x0d
[02/09/19 10:36:08]             CID 1: 0x90
[02/09/19 10:36:08]             CID 2: 0x05
[02/09/19 10:36:08]             CID 3: 0xb1
[02/09/19 10:36:08]         Peripheral ID registers:
[02/09/19 10:36:08]             PID 4: 0x04
[02/09/19 10:36:08]             PID 5: 0x00
[02/09/19 10:36:08]             PID 6: 0x00
[02/09/19 10:36:08]             PID 7: 0x00
[02/09/19 10:36:08]             PID 0: 0x06
[02/09/19 10:36:08]             PID 1: 0xb9
[02/09/19 10:36:08]             PID 2: 0x4b
[02/09/19 10:36:08]             PID 3: 0x00
[02/09/19 10:36:09]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:09]     CSCTI found at address 0x80051000
[02/09/19 10:36:09]     Reading peripheral and component ID registers of device at address 0x80052000
[02/09/19 10:36:09]         Component ID registers:
[02/09/19 10:36:09]             CID 0: 0x0d
[02/09/19 10:36:09]             CID 1: 0x90
[02/09/19 10:36:09]             CID 2: 0x05
[02/09/19 10:36:09]             CID 3: 0xb1
[02/09/19 10:36:09]         Peripheral ID registers:
[02/09/19 10:36:09]             PID 4: 0x04
[02/09/19 10:36:09]             PID 5: 0x00
[02/09/19 10:36:09]             PID 6: 0x00
[02/09/19 10:36:09]             PID 7: 0x00
[02/09/19 10:36:09]             PID 0: 0x06
[02/09/19 10:36:09]             PID 1: 0xb9
[02/09/19 10:36:09]             PID 2: 0x4b
[02/09/19 10:36:09]             PID 3: 0x00
[02/09/19 10:36:09]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:09]     CSCTI found at address 0x80052000
[02/09/19 10:36:09]     Reading peripheral and component ID registers of device at address 0x80053000
[02/09/19 10:36:09]         Component ID registers:
[02/09/19 10:36:09]             CID 0: 0x0d
[02/09/19 10:36:09]             CID 1: 0x90
[02/09/19 10:36:09]             CID 2: 0x05
[02/09/19 10:36:09]             CID 3: 0xb1
[02/09/19 10:36:09]         Peripheral ID registers:
[02/09/19 10:36:09]             PID 4: 0x04
[02/09/19 10:36:09]             PID 5: 0x00
[02/09/19 10:36:09]             PID 6: 0x00
[02/09/19 10:36:09]             PID 7: 0x00
[02/09/19 10:36:09]             PID 0: 0x06
[02/09/19 10:36:09]             PID 1: 0xb9
[02/09/19 10:36:09]             PID 2: 0x4b
[02/09/19 10:36:09]             PID 3: 0x00
[02/09/19 10:36:09]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:09]     CSCTI found at address 0x80053000
[02/09/19 10:36:09]     Reading peripheral and component ID registers of device at address 0x80054000
[02/09/19 10:36:09]         Component ID registers:
[02/09/19 10:36:09]             CID 0: 0x0d
[02/09/19 10:36:09]             CID 1: 0x90
[02/09/19 10:36:09]             CID 2: 0x05
[02/09/19 10:36:09]             CID 3: 0xb1
[02/09/19 10:36:09]         Peripheral ID registers:
[02/09/19 10:36:09]             PID 4: 0x04
[02/09/19 10:36:09]             PID 5: 0x00
[02/09/19 10:36:09]             PID 6: 0x00
[02/09/19 10:36:09]             PID 7: 0x00
[02/09/19 10:36:09]             PID 0: 0x06
[02/09/19 10:36:09]             PID 1: 0xb9
[02/09/19 10:36:09]             PID 2: 0x4b
[02/09/19 10:36:09]             PID 3: 0x00
[02/09/19 10:36:09]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
[02/09/19 10:36:09]     CSCTI found at address 0x80054000
[02/09/19 10:36:09]     Reading peripheral and component ID registers of device at address 0x80055000
[02/09/19 10:36:09]         Component ID registers:
[02/09/19 10:36:09]             CID 0: 0x0d
[02/09/19 10:36:09]             CID 1: 0x90
[02/09/19 10:36:09]             CID 2: 0x05
[02/09/19 10:36:09]             CID 3: 0xb1
[02/09/19 10:36:09]         Peripheral ID registers:
[02/09/19 10:36:09]             PID 4: 0x04
[02/09/19 10:36:09]             PID 5: 0x00
[02/09/19 10:36:09]             PID 6: 0x00
[02/09/19 10:36:09]             PID 7: 0x00
[02/09/19 10:36:09]             PID 0: 0x08
[02/09/19 10:36:09]             PID 1: 0xb9
[02/09/19 10:36:09]             PID 2: 0x2b
[02/09/19 10:36:09]             PID 3: 0x00
[02/09/19 10:36:09]         Peripheral ID = 0x908, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x12, DEVARCH = 0x0, Revision = 0x2
[02/09/19 10:36:09]     CSTFunnel found at address 0x80055000
[02/09/19 10:36:09] End of ROM table
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] Acquiring device info for CSTPIU (0x80020000):
[02/09/19 10:36:09]     Supported Port Sizes: 1-16
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSTFunnel (0x80021000):
[02/09/19 10:36:09]     Port Count: 8
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSTMC (0x80025000):
[02/09/19 10:36:09]     TMC Device Config: ETF
[02/09/19 10:36:09]     Memory Width: 256
[02/09/19 10:36:09]     Ram Size: 8,192 Bytes
[02/09/19 10:36:09]     Device Type: Trace Link
[02/09/19 10:36:09]     Drain Source: ATB
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSTMC (0x80026000):
[02/09/19 10:36:09]     TMC Device Config: ETR
[02/09/19 10:36:09]     Memory Width: 64
[02/09/19 10:36:09]     ETR Buffer Depth: 32
[02/09/19 10:36:09]     Device Type: Trace Sink
[02/09/19 10:36:09]     Drain Source: APB
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSETM (0x8004C000):
[02/09/19 10:36:09]     CSETM (0x8004C000) is OS Locked
[02/09/19 10:36:09]     CSETM (0x8004C000) OS Lock successfully removed
[02/09/19 10:36:09]     CSETM (0x8004C000) successfully powered-up
[02/09/19 10:36:09]     Device supports timestamps
[02/09/19 10:36:09]     Device supports context IDs
[02/09/19 10:36:09]     Device supports cycle accurate trace
[02/09/19 10:36:09]     Device supports data address trace
[02/09/19 10:36:09]     Device supports data value trace
[02/09/19 10:36:09]     Device supports data only mode
[02/09/19 10:36:09]     Device supports trace range
[02/09/19 10:36:09]     ETM Version: 3.5
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSETM (0x8004D000):
[02/09/19 10:36:09]     CSETM (0x8004D000) is OS Locked
[02/09/19 10:36:09]     CSETM (0x8004D000) OS Lock successfully removed
[02/09/19 10:36:09]     CSETM (0x8004D000) successfully powered-up
[02/09/19 10:36:09]     Device supports timestamps
[02/09/19 10:36:09]     Device supports context IDs
[02/09/19 10:36:09]     Device supports cycle accurate trace
[02/09/19 10:36:09]     Device supports data address trace
[02/09/19 10:36:09]     Device supports data value trace
[02/09/19 10:36:09]     Device supports data only mode
[02/09/19 10:36:09]     Device supports trace range
[02/09/19 10:36:09]     ETM Version: 3.5
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSETM (0x8004E000):
[02/09/19 10:36:09]     CSETM (0x8004E000) is OS Locked
[02/09/19 10:36:09]     CSETM (0x8004E000) OS Lock successfully removed
[02/09/19 10:36:09]     CSETM (0x8004E000) successfully powered-up
[02/09/19 10:36:09]     Device supports timestamps
[02/09/19 10:36:09]     Device supports context IDs
[02/09/19 10:36:09]     Device supports cycle accurate trace
[02/09/19 10:36:09]     Device supports data address trace
[02/09/19 10:36:09]     Device supports data value trace
[02/09/19 10:36:09]     Device supports data only mode
[02/09/19 10:36:09]     Device supports trace range
[02/09/19 10:36:09]     ETM Version: 3.5
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSETM (0x8004F000):
[02/09/19 10:36:09]     CSETM (0x8004F000) is OS Locked
[02/09/19 10:36:09]     CSETM (0x8004F000) OS Lock successfully removed
[02/09/19 10:36:09]     CSETM (0x8004F000) successfully powered-up
[02/09/19 10:36:09]     Device supports timestamps
[02/09/19 10:36:09]     Device supports context IDs
[02/09/19 10:36:09]     Device supports cycle accurate trace
[02/09/19 10:36:09]     Device supports data address trace
[02/09/19 10:36:09]     Device supports data value trace
[02/09/19 10:36:09]     Device supports data only mode
[02/09/19 10:36:09]     Device supports trace range
[02/09/19 10:36:09]     ETM Version: 3.5
[02/09/19 10:36:09] 
[02/09/19 10:36:09] Acquiring device info for CSTFunnel (0x80055000):
[02/09/19 10:36:09]     Port Count: 4
[02/09/19 10:36:09] 
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] Detecting topology ... (may take several seconds)
[02/09/19 10:36:09] --- --- ---
[02/09/19 10:36:09] MASTER = CSSTM (0x80002000) (0)  	SLAVE = CSTFunnel (0x80021000) (7)
[02/09/19 10:36:09] MASTER = CSTFunnel (0x80021000) (0)  	SLAVE = CSTMC (0x80025000) (0)
[02/09/19 10:36:10] MASTER = CSATBReplicator (0x80024000) (0)  	SLAVE = CSTMC (0x80025000) (0)
[02/09/19 10:36:10] MASTER = CSATBReplicator (0x80024000) (0)  	SLAVE = CSTMC (0x80026000) (0)
[02/09/19 10:36:10] MASTER = CSATBReplicator (0x80024000) (1)  	SLAVE = CSTPIU (0x80020000) (0)
[02/09/19 10:36:10] MASTER = CSATBReplicator (0x80024000) (1)  	SLAVE = CSTMC (0x80026000) (0)
[02/09/19 10:36:10] MASTER = CSTMC (0x80025000) (0)  	SLAVE = CSTPIU (0x80020000) (0)
[02/09/19 10:36:10] MASTER = CSTMC (0x80025000) (0)  	SLAVE = CSATBReplicator (0x80024000) (0)
[02/09/19 10:36:10] MASTER = CSETM (0x8004C000) (0)  	SLAVE = CSTFunnel (0x80055000) (0)
[02/09/19 10:36:11] MASTER = CSETM (0x8004C000) (1)  	SLAVE = CSTFunnel (0x80055000) (0)
[02/09/19 10:36:11] MASTER = CSETM (0x8004D000) (0)  	SLAVE = CSTFunnel (0x80055000) (1)
[02/09/19 10:36:11] MASTER = CSETM (0x8004D000) (1)  	SLAVE = CSTFunnel (0x80055000) (1)
[02/09/19 10:36:11] MASTER = CSETM (0x8004E000) (0)  	SLAVE = CSTFunnel (0x80055000) (2)
[02/09/19 10:36:12] MASTER = CSETM (0x8004E000) (1)  	SLAVE = CSTFunnel (0x80055000) (2)
[02/09/19 10:36:12] MASTER = CSETM (0x8004F000) (0)  	SLAVE = CSTFunnel (0x80055000) (3)
[02/09/19 10:36:12] MASTER = CSETM (0x8004F000) (1)  	SLAVE = CSTFunnel (0x80055000) (3)
[02/09/19 10:36:12] MASTER = CSTFunnel (0x80055000) (0)  	SLAVE = CSTFunnel (0x80021000) (4)
[02/09/19 10:36:12] MASTER = Cortex-A7 (0x80040000)  	SLAVE = CSETM (0x8004C000)
[02/09/19 10:36:13] MASTER = Cortex-A7 (0x80042000)  	SLAVE = CSETM (0x8004D000)
[02/09/19 10:36:13] MASTER = Cortex-A7 (0x80044000)  	SLAVE = CSETM (0x8004E000)
[02/09/19 10:36:13] MASTER = Cortex-A7 (0x80046000)  	SLAVE = CSETM (0x8004F000)
[02/09/19 10:36:13] MASTER = CSCTI (0x80010000)  	SLAVE = CSTMC (0x80025000)  	Trigger = 1
[02/09/19 10:36:13] MASTER = CSCTI (0x80010000)  	SLAVE = CSTMC (0x80026000)  	Trigger = 1
[02/09/19 10:36:13] MASTER = CSCTI (0x80011000)  	SLAVE = CSTPIU (0x80020000)  	Trigger = 3
[02/09/19 10:36:14] MASTER = Cortex-A7 (0x80040000)  	SLAVE = CSCTI (0x80051000)  	Trigger = 7
[02/09/19 10:36:15] MASTER = Cortex-A7 (0x80042000)  	SLAVE = CSCTI (0x80052000)  	Trigger = 7
[02/09/19 10:36:15] MASTER = Cortex-A7 (0x80044000)  	SLAVE = CSCTI (0x80053000)  	Trigger = 7
[02/09/19 10:36:16] MASTER = Cortex-A7 (0x80046000)  	SLAVE = CSCTI (0x80054000)  	Trigger = 7
[02/09/19 10:36:16] MASTER = CSETM (0x8004C000)  	SLAVE = CSCTI (0x80051000)  	Trigger = 6
[02/09/19 10:36:17] MASTER = CSETM (0x8004D000)  	SLAVE = CSCTI (0x80052000)  	Trigger = 6
[02/09/19 10:36:17] MASTER = CSETM (0x8004E000)  	SLAVE = CSCTI (0x80053000)  	Trigger = 6
[02/09/19 10:36:17] MASTER = CSETM (0x8004F000)  	SLAVE = CSCTI (0x80054000)  	Trigger = 6
[02/09/19 10:36:18] --- --- ---
[02/09/19 10:36:18] Autodetection Complete
[02/09/19 10:38:13] Reading /home/tony/DS-5-Workspace-v5.29.2/v5.29.2-IPQ4019/Boards/QCA/QCA-IPQ4019/QCA-IPQ4019.sdf
[02/09/19 10:38:13] Creating database entry...
[02/09/19 10:38:13] Platform 'QCA - QCA-IPQ4019' built successfully

sdf file:

https://www.dropbox.com/s/6l4vaavlmmamrfx/QCA-IPQ4019.sdf?dl=0

Parents

0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

I'm pleased to hear that you are now getting some instruction trace from your system :)

To answer your questions:

1. The Trace view is cleared when restarting execution after each stop, so I expect your icmp_echo function was collected in the trace up to the breakpoint, but that trace history was discarded after restarting, so it no longer appeared in the trace after a subsequent stop.

2. "Unknown instruction address" can occur when tracing the Linux kernel, because the kernel can self-modify its code.
For example, to support ftrace, calls to _mcount are included at the start of each function when the linux kernel is compiled. When the kernel is loaded, the "bl _mcount" instructions are replaced with NOPs.
ETM trace only records whether branches are taken or not taken - it does not record the source or destination address of direct branches, so a decoder must use the instruction image (vmlinux) to determine which instructions have been executed. If the image does not match what was actually executed (as in this case), then it can lose track of what instructions were actually executed - in this case it mis-decodes a later branch to another address as the (non-existent) branch to _mcount. So the trace decoder is working correctly with the information given to it - it's just that the information given to it is wrong.
To resolve this, use the debugger command "set trust-ro-sections-for-opcodes false". The Debugger will then use the actual instructions read from the target (rather than from the image) for decoding and the "unknown instructions" should disappear.
The Debugger defaults to using the instruction from the image because it is faster than reading it from the target.

Hope this helps
Cancel
Up 0 Down

Cancel

Reply

0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

I'm pleased to hear that you are now getting some instruction trace from your system :)

To answer your questions:

1. The Trace view is cleared when restarting execution after each stop, so I expect your icmp_echo function was collected in the trace up to the breakpoint, but that trace history was discarded after restarting, so it no longer appeared in the trace after a subsequent stop.

2. "Unknown instruction address" can occur when tracing the Linux kernel, because the kernel can self-modify its code.
For example, to support ftrace, calls to _mcount are included at the start of each function when the linux kernel is compiled. When the kernel is loaded, the "bl _mcount" instructions are replaced with NOPs.
ETM trace only records whether branches are taken or not taken - it does not record the source or destination address of direct branches, so a decoder must use the instruction image (vmlinux) to determine which instructions have been executed. If the image does not match what was actually executed (as in this case), then it can lose track of what instructions were actually executed - in this case it mis-decodes a later branch to another address as the (non-existent) branch to _mcount. So the trace decoder is working correctly with the information given to it - it's just that the information given to it is wrong.
To resolve this, use the debugger command "set trust-ro-sections-for-opcodes false". The Debugger will then use the actual instructions read from the target (rather than from the image) for decoding and the "unknown instructions" should disappear.
The Debugger defaults to using the instruction from the image because it is faster than reading it from the target.

Hope this helps
Cancel
Up 0 Down

Cancel

Children

0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

question 1: Sorry, I did not make me clear. I did not set the breakpoint when I tested trace function. I had set breakpoint before the test to confirm it will be called. Then I removed the breakpoint to test the trace function.

Tony
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Tony.He

Hi Stephen,

Just now, I tried below steps:

set a breakpoint -> start tracing -> ping target -> hit breakpoint in function icmp_echo and stopping trace -> export trace report

I can see the icmp_echo function shows in trace report. It's weird that the behavior is different when breakpoint is set.

Tony
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

Good to hear you can now see your function in the trace :)

The amount of trace that can be stored in the trace buffer is limited, depending on how the trace buffer was configured, trace captured early (e.g. for your function) may have been lost out of the buffer by the time execution was stopped. Instead of breakpoints, consider the use of Trace Start Points and Trace Stop Points - see developer.arm.com/.../setting-a-tracepoint
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

I was OOO these days. Now I'm back.

1.Is the trace buffer in the memory used as circular buffer?

2.I tried set Trace Points , but still did not see the function in the trace report.

3.I changed the dts file and revered a larger buffer whose size is 128MB(only 1MB before), then set the base RAM address to the new buffer. I captured several times(sometimes a few mins and sometimes a few seconds), but I still did not see the function in the any trace report. During the test, I used linux command "ping" to keep pinging the target every one second. In the "Trace view" of DS-5, I saw the "buffer Used" is not over 128MB. I think the trace buffer is big enough, right?

It seems that there is other possible root cause I don't know. I run out of ideas. I wonder if you could do me a favor. Could you try this function at your side in the method of Memory Trace Buffer when you are free? Thanks a lot again.

Tony
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

The buffers are circular in ETB/ETR trace capture, as configured by the Platform Configuration Editor by default. Sorry, the user isn't offered a choice of linear or circular via the GUI tools.

The amount of trace data coming from the board can be huge (multiple cores operating at full speed...), so your function call might be being captured but then overwritten shortly after by later data. The best approach is to see your function is to set a breakpoint a few instructions into your function, then run to the breakpoint. This worked successfully for me - see screenshot.
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

I understand my function call might be overwritten. I set a breakpoint and did see the function in the Trace report. But I still have a few questions.

1. How does the "Buffer Used" in the "Trace" view count? When the buffer is full, does it counts again from zero?

2. I set the buffer 128MB. I did many times of test. Why do I always get a low value(below 2MB)

3. My CPU clock is 717MHz. I guess it means at most 717*4(cores)M =2868M instructions can be executed per second. Assume every instruction are 4 bytes , amount of data is 2868*4M= 11392M bytes(I don't use unit "MB" because 1MB=1024*1024 Bytes, but here it means 1000*1000 Bytes),But in my test, the CPU is 99% "idle". So 11392 *1%M bytes=113.92M bytes, Right? It seems that the buffer is almost full after one second. But I keep pinging the target every second, so even if some same function calls might be overwritten, but still have chance to see one function call as below flow:

Start capture at any time －－>store the first function calls in the buffer－－> overwrite first function calls and store the second function calls in the buffer after about 1 second－－> stop capture after 0.5 second. I expect see the second function calls in the buffer.

But I never saw it. This has been confusing me. May I know what's wrong of my understanding?

Tony
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi again Tony

1. The buffer is a circular buffer. So when it gets full, it remains full (it doesn't start counting again from zero)

2. ETF/ETR allows captured trace to be stored in system memory, at some address of your choosing (i.e. in an area of free RAM that is otherwise unused).

3. Instruction trace information gets highly compressed, but with four cores running at full speed, I'd expect the buffer to fill very quickly.

Did you set this as being 128MB? Do you have an original DSTREAM, or a DSTREAM-ST? (check the label on its underside). The original DSTREAM also has its own internal 4GB trace buffer. DSTREAM-ST doesn't need a buffer for itself because it can stream the trace data direct to your PC.

Sorry, I can't explain why you are only seeing <2MB of trace data. Please can you open a Support Case using the "Support > Open a Support Case" option at the top of this page, so that this can be investigated properly?

Stephen
Cancel
Up 0 Down

Cancel

0 Tony.He over 5 years ago in reply to Stephen Theobald

>Did you set this as being 128MB? Do you have an original DSTREAM, or a DSTREAM-ST? (check the label on its underside). The >original DSTREAM also has its own internal 4GB trace buffer. DSTREAM-ST doesn't need a buffer for itself because it can stream the >trace data direct to your PC.

Yes, i modified the dts file as below and set the target system RAM buffer as being 128MB.

diff --git a/arch/arm/boot/dts/qcom-ipq40xx-ap.dk04.1.dtsi b/arch/arm/boot/dts/qcom-ipq40xx-ap.dk04.1.dtsi
index eb6e1d8e7a5a..f60e811bff8b 100644
--- a/arch/arm/boot/dts/qcom-ipq40xx-ap.dk04.1.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq40xx-ap.dk04.1.dtsi
@@ -30,40 +30,45 @@
 
        reserved-memory {
                #address-cells = <1>;
                #size-cells = <1>;
                ranges;
                rsvd1@87000000 {
                        /* Reserved for other subsystem */
                        reg = <0x87000000 0x500000>;
                        no-map;
                };
                wifi_dump@87500000 {
                        reg = <0x87500000 0x600000>;
                        no-map;
                };
 
                rsvd2@87B00000 {
                        /* Reserved for other subsystem */
                        reg = <0x87B00000 0x500000>;
                        no-map;
                };
+               trace@88000000 {
+                       /* Reserved for trace*/
+                       reg = <0x88000000 0x8000000>;
+                       no-map;
+               };
        };
 
        chosen {
                bootargs-append = " clk_ignore_unused";
        };
 
 };

After that, I compiled kernel again and issued command "grep MemTotal /proc/meminfo" and can see the "MemTotal" becomes less.

I have original DSTREAＭ. The reason why I use target system RAM buffer was discussed in our previous posts(no 20-Pin Cortex Debug + ETM connector, or Mictor connector on my board) .

I think maybe the root cause of this issue that why I always see <2MB of trace data is same with the root cause of the issue why I cannot see the function call(icmp_echo) if not setting a breakpoint because both issues can be caused by the loss of trace data. I will file a case.But if you have more suggestions, please kindly post here for anyone will encounter similar issue in the future. Thanks.

Tony

0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

As well as reserving space in the kernel for trace, the ETR also needs to be configured to use that address range via the Debugger. In your Debug Configuration, have you set the base address & size in the ETR tab in the DTSL dialog?

Stephen
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

Yes. I have set the base address & size as below before so many times of test.

Tony
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

At your side, how big is size of buffer? Can you see the ""Buffer Used" is full as long as the running time of target is enough? If yes,

how much time?

Tony
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Tony.He

Hi Tony

I have only a relatively small ETR buffer of 0x8000 bytes, because that's the normal use-case. And it fills-up very quickly (<1 sec). I'm not sure if there is a limit on the max ETR size. I can't explain why you are only seeing <2MB of trace data. Please do open a Support Case so that this can be investigated properly.

Stephen
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

I would like give you a update.

I find if I ping the target very fast(The option is "-f" for Linux ping command to enable flood mode) , I can see the icmp_echo()function is in the trace report?
I recorded what I have done(How I configured the DTSL options and tested). The video file and trace reports are here https://www.dropbox.com/s/9hm6apaf4wxhes5/video-and-trace-reports-two-cases-about-function-trace-data-loss-or-not.tar.gz?dl=0

Tony
Cancel
Up 0 Down

Cancel
0 Tony.He over 5 years ago in reply to Tony.He

I also filed a case.
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Tony.He

OK, that sounds good. Thanks.
Cancel
Up 0 Down

Cancel