Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

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

  • 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…

  • Timeline window of Ozone

    SEGGER - Nino - - Ozone related

    Post

    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

  • Hello, Thank you for your inquiry. The recommended way to place variables in Flash with SEGGER Linker is explained here: wiki.segger.com/How_to_place_variables_in_Flash Best regards, Nino

  • Hello Kai, Thank you for your inquiry. It depends a bit on how your project was setup as. If you are using a CPU Package for project setup switching one project "one the fly" to another target device is a bit easier as some settings as architecture etc. will change dependent on the selected target processor. If you are using the generic Cortex-M template you have to set all settings yourself. However in either case you will have to at least fix up the memory map file and most likely other target…

  • Hello, Thank you for your inquiry. You can set additional binary or hex files to be loaded via project option Debug > Loader > Additional Load File[0] Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. It seems though that ES is shipping with older variants of the RTOS awareness scripts. Could you try to load the Ozone RTOS awareness script in ES? Does it work better now? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Which Embedded Studio version are you using exactly? The library that is being build is the C standard library. With ES V7 the runtime library is build on demand to keep the installation and download as small as possible. So this is most likely what you are seeing here. As a sanity check, could you try one of the ES V6 versions in comparison, do you see the same issue there? Best regards, Nino

  • Hello, Thank you for your inquiry. Are you using the GNU Linker or SEGGER Linker? The SEGGER Linker uses different files and formats. segger.com/doc/UM20005_Linker.html Best regards, Nino

  • Hello, Thank you for your inquiry. Yes, memcopy_fast is not available with the SEGGER Runtime Library. The SEGGER Runtime Library provides the standard C API only. However, it is optimized for size and performance. In the project options you can select whether to use the small or fast implementation (or an implementation balanced between both). The balanced and fast variant will use the fastest implementation of memcpy. You can find the setting under Code > Library > Library Optimization Best re…

  • Hello, Thank you for your inquiry. Are you maybe opening projects with the V4 version that you do not have a valid license for? Please also note that V7 projects may not necessarily work with V4 versions and won't open properly. A similar issue is explained here: wiki.segger.com/Embedded_Studio_evaluation_period_error Best regards, Nino

  • Hello, Thank you for your inquiry. What do you mean with map flash to SystemView? If you are asking on how to place the SystemView symbols at specific addresses you have to read the documentation about the toolchain you are using, specifically the linker manual. This has nothing to do with SystemView itself. You have to make sure your application is placed correctly. Best regards, Nino