Part Number: TMDS64GPEVM
Other Parts Discussed in Thread: AM6442
Hi
On our hardware based on AM6442 I'm trying to utilize uboot trace tool. I follows this tutorial: https://docs.u-boot.org/en/latest/develop/trace.html#environment-variables
but I'm struggling with some crash after invocation of fakegocmd:
fakegocmd=trace pause; trace calls 0x89000000 0x10000;echo profbase: ${profbase}; echo profsize: ${profsize}; echo profoffset: ${profoffset}; save mmc 1:1 0x400000 trace.log ${profoffset};
I guess this is due to the wrong address on which I'm dumping the traces. What addresses on TMDS64GPEVM correspond to SRAM memory? How can I check which memory area is occupied? bdinfo only shows RAM addresses.
The error:
Call list dumped to 89000000, size 0x1c
profbase: 89000000
profsize: 10000
profoffset: 1c
Starting kernel ...
"Synchronous Abort" handler, esr 0x96000010
elr: 00000000808268f8 lr : 000000008086e0b0 (reloc)
elr: 00000000feef18f8 lr : 00000000fef390b0
x0 : 00000000fefbfa88 x1 : 00000000fefbfa68
x2 : 0000000000000600 x3 : 00000000fefbfa78
x4 : 00000000fefbf968 x5 : 00000001fdf7f4e0
x6 : 0000000000000000 x7 : 00000000fcec2810
x8 : 00000000fce9f430 x9 : 0000000000000002
x10: 0000000000001ecc x11: 00000000fce9e7ec
x12: 0000000000000000 x13: 0000000000000200
x14: 000000000000000c x15: 0000000000000020
x16: 00000000fef39054 x17: 0000000000000000
x18: 00000000fceaadb0 x19: 0000000000000000
x20: 00000000fceb8550 x21: 00000000fceac830
x22: 00000000fefcad98 x23: 00000000fcec21d8
x24: 00000000fcec21d8 x25: 00000000fefc8280
x26: 0000000000000000 x27: 00000000feecde00
x28: 00000000fceb6b90 x29: 00000000fce9e8b0
