Search Results

Hello, here you can find an overview of the different trace types and what they can do: wiki.segger.com/General_information_about_tracing The exception tracing you are referencing is most likely ITM trace. Currently ITM tracing is only partially available within Ozone and is joined with the ETM trace data received via the trace parallel port from target. That way we have a gapless instruction trace recording with periodic timestamps. However user generated ITM data and events will currently not …

Hello, Thank you for your inquiry. If your chip features multiple possible sets of trace pins you can generally use any combination you want. You just have to make sure that the chosen trace pins fit the ones that you are initializing in your .JLinkScript file. In the linked example project you will find an example script that sets up PE2-PE6. The example script will limit the trace data pins to 1 pin though to make the pictured setup possbile with the flying wires. If you plan on using all 4 tr…

Hello, Thank you for your feedback. Correct there was a mistake in how the suspended state was masked. Will be fixed in the next release. Best regards, Nino

Hello, Thank you for your inquiry. As Frank stated the file is one way or another in your project under that path. If I had to guess you moved the project from one PC to another. So if you use absolute paths for your files that pup up will appear. To avoid this either use relative paths in your projects or un-check the "Show this dialog the next time" in the pop up. Then the warning message should no longer show up for this file. Best regards, Nino

Hello, Thank you for your inquiry. See the following documentation for reference: studio.segger.com/mkpkg.htm studio.segger.com/ide_package_description_file_format.htm Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. Do you see the same behaviour with the latest Embedded Studio v8.10d? If yes, could you provide an example project for reproduction? Best regards, Nino

Hello, Thank you for your inquiry. Do you see the same behaviour with the latest Embedded Studio V8.10d? If yes, could you provide a setup for reproduction that shows this behaviour? Best regards, Nino

Hello, Thank you for your inquiry. The J-Trace Pro models can't be "sidegraded" to different variants of the J-Trace Pro family. But you can always use our trade in program to get a discount on a new one: segger.com/purchase/trade-in-program/ We also have a new flagship model available that can do both Arm and RISC-V: segger.com/products/debug-probes/j-trace/models/j-trace-pro/ Best regards, Nino

Hello, Thank you for your inquiry. For the SAMD51 we do not have a script available due to lack of public trace capable eval boards. But we can provide you with the script sources for the SAME54 eval board. As stated in the SAME54 Wiki article, please contact our support channel for this: Quote from Wiki: “Note: The example is shipped with a compiled .JLinkScriptfile, should you need the original source, please get in touch with SEGGER directly via our support system: segger.com/ticket/. To crea…

Hello, Thank you for your inquiry. Please note that this is a community forum, you appear to have a new J-Trace Pro which is in valid support period. In that case we recommend to contact us via our official support channels as explained in my signature as answers are not guaranteed in our community forum. Generally regarding your inquiry. The Nucleo Boards typically do not support pin tracing out of the box as they do not have a trace header. But on some of the larger Nucleo boards the trace pin…

Hello, Thank you for your inquiry. It is expected that in trace buffer mode you will only see a small fraction of code in the timeline as the buffer is usually only ~4 kB in size. Also there are no timestamps in buffer trace available. With pin tracing you get timestamps and can do the analysis you mentioned to see how long which thread took etc. Just make sure to enable RTOS awareness in Ozone. For more information see the Ozone manual. Also make sure that you set the correct CPU Frequency in O…

Hello, Thank you for your inquiry. External memory support for ST-Link is currently not available in Embedded Studio. But it is on our feature wishlist. To get notified automatically when the feature gets available you can subscribe here: segger.com/notification/subscribe.php?prodid=196 Best regards, Nino

Hello, Thank you for your inquiry. With FreeRTOS V11 and on no more patches are required as SystemView is now build in the FreeRTOS Sources. So all you have to do is enable the trace flags in your SystemView build. For more information see the FreeRTOS documentation. Best regards, Nino

Hello, Thank you for your inquiry. It might be that the default fill value for empty gaps is different for the hex and for the elf file. How does the hex file look like if you open it e.g. in J-Flash or some other hex file viewer? You can set the gap fill value for the extra output format with project option: Code > Linker > Additional Output File Gap Fill Value Best regards, Nino

Hello, Thank you for your inquiry. For DDR RAM inits we recommend to use a JLinkScript and the function SetupTarget(): wiki.segger.com/J-Link_script_files How to use a JLinkScript in Embedded Studio.: wiki.segger.com/J-Link_script_files#Embedded_Studio The image that you want to program to the DDR RAM you can set in ES via project options under Debug > Loader > Additional Load File[0] If everything is set up correctly J-Link will init the DDR RAM after connection and ES will download the DDR ima…

Hello, Thank you for your inquiry. Sleep mode debugging is pretty hit or miss and it is implementation defined by the silicon vendor what theoretically works or not. The error most likely happens because ES is trying to read some memory from the target or checking some target status. If the target does not respond -> Error. Here is a J-Link article that explains some potential workarounds but there is no guarantee that you will find a reliable debug setup: wiki.segger.com/UM08001_J-Link…Guide#Lo…

Hello, Of course we are aware of the different flash bank sizes and it is actually not that uncommon. But it is also nothing the toolchain has to worry about. This is handled by our J-Link flash loaders and in your case also seems to be working otherwise the download and debug session start would already fail. Which is not the case here. All you have to do is supply a valid memory map that describes the complete memory blocks as one unit. So the correct memory map for your device is this: XML So…

Hello, Not sure I understand. Did you now try the M7 Ozone script in ES or not? Does it work better or not? ES will not set the script automatically. So if you have selected the wrong M4 script that is user error. You have to select the M7 script of course if you are using a Cortex-M7. Best regards, Nino

Hello, Not reproducible for me. Attached you can find an example project that runs your script as post build steps. Right now I am calling "python" "Test.py" but I also tested that with the absolute path to the python exe as well as without quotation marks. All variants work for me without any issues and as expected. Could you give the example project a try. Does this work for you? Please note that we generally recommend to use the latest Embedded Studio version if possible. But I also tested th…

Hello, This is the first time we hear from such issue. So I assume it is some issue with the setup which worked on accident before with V7.12. Is the issue reproducible for you on an eval board? If yes, could you provide a reproducer so we can try to replicate the behaviour in house? Best regards, Nino