Search Results

Another issue that I found this morning is that exporting to a CSV file will not export all of the variables if more than 5 are being watched. I'm not sure which one is not being exported, but I think it's the first variable that is not exported if there's more than 5.

Quote from SEGGER - Matthias: “Hello, thank you for bringing this to our attention. Would it be possible for you to share an .elf file that can be used as a reproducer to demonstrate these issues? Best regards, Matthias ” I can share an .elf file. Is there a way I can direct message a OneDrive to you? I can't upload it publicly.

Is it just me or does J-Scope 7.62a have broken functionality that makes it very difficult to use? Here's a list of what I've run across. 1) float types are sometimes incorrectly labeled as uints. It's very inconsistent and I can't figure it out. The same variable can sometimes show up as a float, othertimes as a uint. 2) enums cannot be selected, even through they're labeled as uchar in J-Scope. 3) booleans can be selected, but they don't get any data. 4) No smooth resizing between the graph an…

Like the title says, the option to import data into J-Scope version 7.56b is not present. I collected a bunch of data and saved them as raw (instead of CSV) so I could look at it later, but apparently not. How can I view the jraw data that I've collected?

Figured out how to actually change that setting. Go to Options-> Global Settings, and select "load most recent project".

This is on version V7.50A. I clicked the check box that says "Do not show this message again", but the message keeps showing up. I need that message to not show up. I have some debug scripts that flash the bootloader and other needed things ahead of time, and that message box is stopping those scripts from working.

I've got a problem where Ozone will always print "Connection Failed" message when I try to download and run firmware just for the PAC5532. I've successfully used Ozone for other micros, such as the MKV31F family and the nRF52 family. My guess is there's something not configured correctly in the support files, and I'm not sure if it's a Segger problem or an Qorvo problem. The PAC support files for Segger can be found here: qorvo.com/products/p/PAC5532A#evaluation-tools Scroll all the way to the b…

Yeah, that's what I thought but I wanted to make sure I didn't overlook anything. Well that complicates things a bit but that's a problem for me to figure out.

I think I know the answer from the documentation I've read on the J-Trace but I want to be sure: Is it possible to do instruction tracing over just the minimum SWD connection? (SWDIO and SWDCLK). I have a project that's extremely limited on I/O and the trace pins and SWO pins are used for other purposes. Or do you absolutely have to have the trace pins (TRx and TCLK) in order to do instruction tracing?