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():
https://wiki.segger.com/J-Link_script_files
How to use a JLinkScript in Embedded Studio.:
https://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 image to the corresponding memory location and then your application.
Best regards,
Nino
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:
https://wiki.segger.com/UM08001_J-Link…Power_Debugging
Best regards,
Nino
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:
<!DOCTYPE Board_Memory_Definition_File>
<root name="STM32F411VETx">
<MemorySegment name="FLASH1" start="0x08000000" size="0x00080000" access="ReadOnly" />
<MemorySegment name="RAM1" start="0x20000000" size="0x00020000" access="Read/Write" />
</root>And nothing else!
Everything else regarding placement is done via the linker or your code, depending on how you are placing the variable.
Attached you can find a simple example project for your device that places a const string at a specific location in Flash.
This can be of course done with any symbol.
Also you seem to be trying to place data at Flash offset 0. While from Linker side you can of course do so, your Cortex-M will never boot as Cortex-M requires a vector table at that location which at least points to the Reset_Handler address and contains the stack pointer. That is why explicit placement on offset 0 does not work with the default linker script generated by ES because you have this line in your linker script to accommodate this:
place at start of FLASH { block vectors }; // Vector table section
If you change that line to
place in FLASH { block vectors }; // Vector table section
And do an explicit placement of your symbol to 0, then it will be placed there. But again, if that data does not contain the vector table your device will not start.
For more information about the SEGGER Linker see here:
https://www.segger.com/doc/UM20005_Linker.html
Best regards,
Nino
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 this with the V7.12a you are using and same result, all works as expected.
Best regards,
Nino
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:
https://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 specific settings.
So it is not really recommended by us to try switching target devices afterwards.
The more clean and less error prone approach would be to create a new project or the correct target device and just move your sources and project settings over.
Best regards,
Nino
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.
https://www.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 regards,
Nino
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:
https://wiki.segger.com/Embedded_Studi…on_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
Hello,
Thank you for your inquiry.
You can find a SystemView no OS guide in our Wiki:
https://wiki.segger.com/Use_SystemView_without_RTOS
Did you make sure to follow all steps that are explained?
Best regards,
Nino
Hello,
Thank you for your inquiry.
The screenshots do not show SystemView running. Are you sure you are in the right subforum?
ST-Link is also not compatible to SystemView, so not sure why you compare these.
Could you clarify what you are doing and what is working and what not? From your OP this is not clear.
Best regards,
Nino
Hello,
Please note that discussion J-Link API in public is a license violation.
If you have a J-Link SDK in valid support period please contact us via our official support channel as explained in my signature.
This thread will be closed now.
Best regards,
Nino