19:40 <dormito> Hmmm. For creating target scripts, how are the DBGBASE and CTIBASE (passed to "cti create .." and "target create ...") obtained? Does that need to come from vendor docs, or can it be detected?

19:41 <PaulFertser> dormito: often times when the vendor is sane they're present in "ROM tables"

19:41 <dormito> (for referance: I am attempting to write a config script for the nxp lx2160a rdb, and am looking at target/ls1046a.cfg as the closest example)

19:41 <PaulFertser> dormito: you can try looking at "dap info 0" and other numbers for the decoded ROM tables.

19:42 <PaulFertser> dbgbase can be "autodetected" in some cases. Not sure about ctibase though.

19:42 <PaulFertser> Vendor documentation is another possible source, yes.

19:43 <dormito> Hmmm. it says "no ROM table present". I am not overly familiar with arm, but NXP claims coresight complainace... and I think that means it has to have a rom table?

19:43 <dormito> *not overly familar with arm debuggin/coresight/etc

19:45 <PaulFertser> Probably it's on another DAP.

19:46 <PaulFertser> Or probably it's absent like on many TI parts.

19:50 <PaulFertser> dormito: CTI in CTIBASE stands for "cross trigger interface" (probably that's what's in the docs)

19:50 <dormito> Ahh. I think I found it (maybe). NXP has an AN about "enabling DAP on the qoriq lx2160a", and that seems to list rom clusters, and CTI addresses

19:50 <dormito> PaulFertser: oh, nice thanks