Search Results

Search results 1-13 of 13.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • arm-none-eabi-objcopy -v -O binary XXX.axf XXX.bin Then flash XXX.bin.

  • I found nowhere talking about parity checking in the SWO protocol. Also, I ran the swostability unity shipped with JLink Commander and it encountered numerous errors too. So I suppose it will just happen and no straightforward solutions here?

  • Hi there, I am using ITM to generate some information about software execution. Using Jlink SDK, everything works pretty well except that occasionally some packets are incorrectly decoded, resulting wrong data or unknown packets. It turned out the problem is not caused by the bandwidth limit, because when I decreased the SWO frequency (obtained from the compatible list), it works equally fine. I also make sure that the target ITM buffer is available before sending any ITM data. So overflow shoul…

  • Thank you very much!

  • Hi there, Can I know if JTrace can support the NuMaker PFM-M2351 board out-out-box? The board has a cortex debug+ interface, but I didn't find information on the tested device page (…echnology/tested-devices/). Moreover, can anyone confirm if the board has ETB support? Thanks!

  • Thank you Nino. You are really helpful.

  • Currently, Ozone reported the following coresight components: CoreSight components: ROMTbl[0] @ E00FE000 ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table ROMTbl[1] @ E00FF000 ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33 ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BBD21 Cortex-M33 I suppose th…

  • Hi there, I have a LPC55S69 EVK board and wanted to use the Jtrace to get the instruction trace. Since no trace pin is available on the board, I thought setting trace source to be "trace buffer" should work. Unfortunately, it is not allowed in OZone. I wonder if this is a hardware issue or software issue. More specifically, Is it because the hardware lacks the ETM/ETB support or the JLINK software hasn't supported it yet? Thank you very much!

  • Quote from SEGGER - Nino: “You can get around this by exporting the instruction trace data after each stop. This can also be automated. See here for more details: ” Thanks for the guide. I used Trace.ExportCSV() to export a file on every breakpoint. However, the file name can only be provided with a constant string. Any way to give a distinct file name on each invocation of Trace.ExportCSV()? For example, a self-increasing static/global integer which ca…

  • Quote from SEGGER - Nino: “2: Currently not possible. ” If I buy SDK now, can I get a free update with that feature?

  • Hi Nino, Thanks for the reply. Quote from SEGGER - Nino: “We are currently working on expanding Ozone and J-Trace PRO so you can select to buffer more data into either your host PCs RAM or to one or multiple trace files. ” 1: Do I need a new J-Trace POR hardware to use this feature? 2: Can I use the SDK to save the trace to files already? Thanks!

  • Hello, It seems there is a hard limit on the captured instructions. In my case, the number of instructions is limited at around 67M, even though I set "Maximum instruction count" to 10G. I wonder if this is a hard limit or something configurable elsewhere. In addition, whenever I stop the target, previous trace is lost. Is there an option to retain previous trace when resuming at break point? Thanks!

  • Hello, I need to capture both ETM and ITM trace at the same time. If I understand correctly, if trace pins are used, both ETM and ITM data are routed to J-trace. However, in the manual of Ozone, it is state that "The simultaneous use of multiple trace data channels in Ozone is currently not supported". Here I think data channels refer to trace pins/trace buffer/swo. My question is, if I chose trace pins, can I get instruction trace and ITM data simultaneously in Ozone? If not, is it supported in…