How can the Noral BDM unit capture trace data when it only connects to the BDM connector?
The ColdFire CPU outputs trace data on the 4 x PST and 4 x DDATA pins of the BDM connector. The kind of information output on the PST pins is “I executed the next instruction” “I executed a branch instruction – and took the branch” “I processed an exception” “I took an indirect branch to an address” Note that the CPU only tells us the PC value when it has to e.g. when it takes an indirect branch (e.g. RTS instruction). The rest of the time the CPU just outputs the ‘I executed the next instruction’ status. The kind of information output on the DDATA pins is New PC value when CPU branches to an indirect address Data read/write data – this is optional Debug data written to the DDATA pins via the WDDATA instruction in your program The trace buffer in the BDM unit is 1MB long and captures a record each CPU clock cycle (40ms worth at 25MHz). The flex software can process this raw PST/DDATA data into meaningful display data to show you the CPU execution history and optionally the data transfe
Related Questions
- In the Appendix C Demographics Chart, if agencies do not capture data on certain areas of the volunteers, staff, board, and clients, how do they reflect that?
- Why does the Telnet session appear in the data capture trace although I have selected TFTP as the configuration transport protocol?
- How do we use the IP trace? Capture entire payload or abbreviate data?
