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 Tony.He over 5 years ago in reply to Stephen Theobald

Hi Stephen,

I really appreciate your reply. I tried to trace, but encountered another error. Can you help to check? To be honest, I'm new to the powerful software DS-5 and hardware DSTREAM. I'm not sure if I made a stupid mistake.

"Command" view:

trace start DSTREAM
ERROR(ECMD3): Error attempting to start Trace capture device DSTREAM

"Error log"view:

Caused by: com.arm.rddi.RDDIException: Command Error (Could not find a supported trace connector)
	at com.arm.rddi.RDDI.checkResult(RDDI.java:1860)
	at com.arm.rddi.RDDI.access$1(RDDI.java:1847)
	at com.arm.rddi.RDDI$Trace.start(RDDI.java:1563)
	at com.arm.debug.dtsl.components.DSTREAMTraceCapture.startTraceCapture(DSTREAMTraceCapture.java:496)

Best regard,

Tony

Reply

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

Hi Stephen,

"Command" view:

trace start DSTREAM
ERROR(ECMD3): Error attempting to start Trace capture device DSTREAM

"Error log"view:

Caused by: com.arm.rddi.RDDIException: Command Error (Could not find a supported trace connector)
	at com.arm.rddi.RDDI.checkResult(RDDI.java:1860)
	at com.arm.rddi.RDDI.access$1(RDDI.java:1847)
	at com.arm.rddi.RDDI$Trace.start(RDDI.java:1563)
	at com.arm.debug.dtsl.components.DSTREAMTraceCapture.startTraceCapture(DSTREAMTraceCapture.java:496)

Best regard,

Tony

Children

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

Hi again Tony

Here's some things for you to check.

1) Are you trying to collect trace either
a) via the on-chip Embedded Trace FIFO (ETF) to be retrieved via simple JTAG connector, or
b) via the Trace Port Interface Unit (TPIU) for off-chip trace collection via a trace-compatible connector.

Whether TPIU trace is possible or not for you might be determined by the connector on the board. Which one of http://www2.keil.com/coresight/coresight-connectors/ is on the board?

2) If b) above, have you connected DSTREAM to your board via a suitable cable, e.g. 20-Pin Cortex Debug + ETM connector, or Mictor connector?

3) Have you enabled trace collection in the "DTSL Options" for the Debug Configuration?

4) What does the comand "trace list" return?

5) Trace can be easily controlled via the GUI. Have you tried opening the Trace view (Window > Show view > Trace)?
Cancel
Up 0 Down

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

Hi Stephen,

1). I checked http://www2.keil.com/coresight/coresight-connectors and found my board supports 20-Pin ARM Standard JTAG Connector,

A. So, I only can debug and can not trace, right? If yes, I am disappointed because I want to study this amazing function. Can I ask a HW engineer to fix this?( For example, pull pins from board?) ?

B If HW engineer can not fix, I would like to buy a one board with trace-compatible connector. Any recommendation?

C)Another question is the third warning in my original post related to the 20-pin ARM Standard JTAG? if there is 20-Pin Cortex Debug + ETM connector, or Mictor connector, does it mean this warning is gone?

3) Yes

5)Yes.

Best regards,

Tony
Cancel
Up 0 Down

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

PCE detected an ETF (Embedded Trace FIFO) and ETR (Embedded Trace Router) in the QCA IPQ4019, so it should be possible to retrieve saved trace from system memory via JTAG, even if the board only has a 20-pin ARM Standard JTAG connector.

The 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).

To do so, in the DTSL Options for the Debug Configuration:

In the Trace Capture tab, select Trace capture method = System Trace memory Trace Buffer (CSTMC/ETR)

In the ETR tab, tick "Configure the system memory trace buffer" and enter your chosen base address in RAM

In the Cortex-A7 tab, tick "Enable Cortex-A7 core trace, and select the cores from which you want to collect trace

Click OK to exit the DTSL dialog, then Debug to start debugging.

After running, then stopping code execution, trace should appear in the Trace view.

Hope this helps you to start tracing successfully!
Cancel
Up 0 Down

Cancel

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

Hi Stephen,

After stopping code execution, no trace appear in the Trace view. I exported trace to a file, the file shows as below:

Debug stop (x2)
		Trace buffer contains no trace for this core. (x2)

I'm not sure if this issue is related with another issue I am fighting with. That issue is I can not enable OS support when I load kernel symbol file. It shows "WARNING(ROS60): Could not enable OS support as the OS does not appear to be initialized. This might be caused by a mismatch between the loaded symbols and the code on the target or because the OS is not up and running. Enabling OS support will be re-attempted when the target next stops.". But I can set breakpoint after loading kernel symbol file. For example, I set a breakpoint in kernel icmp_echo function and I see it was triggered after pinging the target. Below is the "Command" view. Sorry for so many questions because I have been working high-level software and not encountering such low-level issue. Thanks for your time again.

Signals handled by operating system
Connected to running target QCA - QCA-IPQ4019 on USB:002273
cd "/home/tony/DS-5-Workspace-v5.29.2"
Working directory "/home/tony/DS-5-Workspace-v5.29.2"
file
interrupt
Execution stopped in SVC mode at N:0xC0209F48
On core Cortex-A7_0 (ID 0)
N:0xC0209F48   MOV      pc,lr
add-symbol-file /project/qsdk/vincent/openwrt.git/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/linux-3.14.77/vmlinux
WARNING(ROS60): Could not enable OS support as the OS does not appear to be initialized. This might be caused by a mismatch between the loaded symbols and the code on the target or because the OS is not up and running. Enabling OS support will be re-attempted when the target next stops.
wait
continue
break -p "/project/qsdk/vincent/openwrt.git/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/linux-3.14.77/vmlinux"::"icmp.c"::icmp_echo
Unable to set software breakpoint, falling back to hardware breakpoint
Hardware breakpoint 1 at N:0xC05E8A74
	on file icmp.c, line 816
	on file icmp.c, line 820
WARNING(ROS60): Could not enable OS support as the OS does not appear to be initialized. This might be caused by a mismatch between the loaded symbols and the code on the target or because the OS is not up and running. Enabling OS support will be re-attempted when the target next stops.
Execution stopped in SVC mode at breakpoint 1: N:0xC05E8A74
On core Cortex-A7_0 (ID 0)
In icmp.c
N:0xC05E8A74   816,0   {
wait
continue

Best regards,

Tony

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

Hi again Tony

The "WARNING(ROS60): Could not enable OS support as the OS does not appear to be initialized" is not related to your trace issue. Linux OS support and Trace are in separate areas of the Debugger.

When Linux kernel symbols are loaded from the vmlinux file, the Debugger will try to access some locations in the kernel. For example, it will try to read "init_nsproxy.uts_ns->name" to get the kernel name and version. If this step fails, the warning is given. The warning can mean
either:
1) The vmlinux symbol files does not match the binary running on the target (i.e. they are from a different build)
or
2) The OS has not booted far enough to allow the Debugger to start reading its state.

From the look of the addresses you quote where the code execution has stopped e.g. N:0xC0209F48, which I guess are virual addresses and the MMU is already on, I don't think 2) is the cause here. So please can you double-check 1)? In particular, please try the command:
output init_nsproxy.uts_ns->name

To learn more about Linux kernel debug, please take a look at these blogs:

Debugging the Armv8-A Linux Kernel with DS-5:
community.arm.com/.../debugging-the-armv8-a-linux-kernel-with-ds-5

and an older one for Armv7-A:
community.arm.com/.../porting-linux-made-easy-with-ds-5

Regarding not being able to capture Trace, it seems we need to investigate this in more detail, so I suggest you open a Support Case using the "Support > Open a Support Case" option at the top of this page.
Cancel
Up 0 Down

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

I would like to let you know the issue that OS support is not enable has been figured out. In my compiling server, I ran below command.

tony@tony-HP-ProDesk-600-G2-MT:/project/qsdk/vincent/openwrt.git/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/linux-3.14.77$ strings vmlinux |grep tony %s version %s (tony@tony-HP-ProDesk-600-G2-MT) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r35193) ) %s Linux version 3.14.77 (tony@tony-HP-ProDesk-600-G2-MT) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r35193) ) #6 SMP PREEMPT Wed Sep 4 18:38:29 CST 2019
On the target, I ran below command.

root@OpenWrt:/# dmesg |grep tony [ 0.000000] Linux version 3.14.77 (tony@tony-HP-ProDesk-600-G2-MT) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r35193) ) #5 SMP PREEMPT Wed Sep 4 18:37:38 CST 2019

According to the compiling time of output of both compiling server and target, there are two kernel generated during one minute. So I checked my buildroot and did find there are two kernels. The loaded one in DS-5 is with initramfs and the kernel running on the target is without initramfs. The kernel with initramfs was generated later and overwrote the one without initramfs. BTW, actually I have read your both these blogs before my first post here. I went through pre-MMU and post-MMU stages. Everything is OK except this OS support issue. They are really good and detailed. After I went through these two stages, I thought I need to try the trace function because this function is useful for me to study kernel and trace kernel crash issue, so I filed this post. So when seeing you answered my questions, I was very happy. I will think more before I decide to open a support case. Thank you again.

Best regards,

Tony
Cancel
Up 0 Down

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

Hi Tony

Thanks for confirming that your Linux kernel debug support issue is now resolved.
It would be good to get your Trace issue investigated further by the helpful folk in Arm's Support team.

Best regards

Stephen
Cancel
Up 0 Down

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

Hi Stephen,

Sorry for bothering your again. I checked the source code(You can get it from https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/diff/drivers/platform/msm/msm_bus/msm_buspm_coresight.c?h=release/dandelion&id=192f7606b6823413f12f4f61ba10fb993035132a), it seems that it's a driver of coresight for my board IPQ4019 and in my buildroot it's not compiled. May I know if there is coresight driver in your buildroot?

Best regards,

Tony
Cancel
Up 0 Down

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

Hi Tony

No, sorry, I don't know what that file is for. You do not need a CoreSight driver installed in your Linux dist to be able to use non-intrusive ETM Trace via DSTREAM.

Stephen
Cancel
Up 0 Down

Cancel
0 Stephen Theobald over 5 years ago in reply to Stephen Theobald

Hi again Tony

After copying the new .sdf that I sent you into the platform folder, did you clean & rebuild the platform?

That step is needed to create an updated dtsl_config_script.py, that performs the trace setup etc.

Stephen
Cancel
Up 0 Down

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

Hi Stephen,

Yes, rebuilt right the moment when you provided . I feel super thankful and happy that you have been along for the ride. I have been debugging this issue these days and can't wait to give you a update got yesterday. Because of some reason, I chose wrong base RAM address to store data. It seems that I can trace now. See the trace reports of 4 cores(https://www.dropbox.com/s/knok1qngq5aqdel/Trace_Reports-of-4-cores.tar.gz?dl=0). But I still have two questions to clarify.

1. I used a PC to ping target and target replied the PC ,so I expect that function icmp_echo function in net/ipv4/icmp.c should show in the report, but I did not find it. As I said before, I once set breakpoint in this function and I'm sure it was called because the break point was hit.

2. I saw some strings "Unknown instruction address" in the reports, what does that mean?

Tony
Cancel
Up 0 Down

Cancel
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
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