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. I assume you are using the J-Link Commander, is this correct? The J-Link Commander itself does not provide such functionality currently. But you can purchase the J-Link SDK which comes e.g. with the J-Link Commander source as reference so you can implement such functionality in your own tool. More information about the SDK can be found here: segger.com/products/debug-prob…nk/technology/j-link-sdk/ Best regards, Nino

  • Hello, Great to hear that it is working reliably with Ozone. We are happy about any new Ozone user we can win for us This thread will be considered solved now. Best regards, Nino

  • Hello Udo, Thank you for your inquiry. There are no technical restrictions in the non commercial/evaluation version of Embedded Studio. This sounds like a connection setup issue. What target device are you looking to connect to? Is it a custom board or eval board? If eval which one? Is connection working using J-Link Commander? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander Best regards, Nino

  • Hello, Great to hear that you are up and running again. As you correctly found out the Flash must be erased before programming new data. This is common on most Arm microcontrollers. Production Programming mode does all required steps automatically. We will consider this thread as solved now. Best regards, Nino

  • Hello, Thank you for your inquiry. True Studio is not a SEGGER product so unfortunately we can't offer support here. The J-Link in this setup is simply a receiver of commands from the IDE. So if a particular window is not doing what it should it is usually an issue with the IDE itself, so we suggest contacting Atollic support in this regard. To take the IDE out of the equation could you give our debug software Ozone a try? segger.com/products/development-tools/ozone-j-link-debugger/ It works wit…

  • Hello, We were able to fix the issue. To be notified when the new updated version of Ozone is available you can subscribe here: segger.com/notification/subscribe.php?prodid=178,7 Best regards, Nino

  • Hello, Thank you for providing the project. This is reproducible and we are currently investigating. Keep you posted. Best regards, Nino

  • Hello, Thank you for your inquiry. The default buffer size is 512 bytes. But the MTB can be configured to use more RAM if available for tracing. How to configure this is explained here: wiki.segger.com/MTB_specifics Best regards, Nino

  • Hello, Good to hear that the RTT linking errors are gone. The remaining errors are explained by the linker output. In your main.c you are using HAL functions that are undefined. Make sure to include all needed files. Please understand that we are not allowed to assist you further here as this remaining issue is not related to SEGGER products. For questions about uVision and how to setup generic projects we recommend contacting Keil support. Best regards, Nino

  • Hello Thomas, Thank you for your inquiry. Such an issue is not known to us. Could you provide an example project for reproduction? Best regards, Nino

  • Hello Markus, Thank you for your inquiry. Yes this is possible with SEGGER Linker. A how to is shown here: wiki.segger.com/Placing_extern…mbols_at_specific_address This would also work with gcc linker. However it would be about 30 lines of code instead of 3. Best regards, Nino

  • Hello Stefano, According to your map file the base address of the elf file is 0x8000000. So not sure what the error should be. If you just want to flash and debug the firmware at 0x8020000 then make sure the bootloader image is not part of the elf file. Alternatively if you want to keep the bootloader and FW in one image you can set the PC and SP in AfterTargetDownload and AfterTargetReset as explained here: wiki.segger.com/Debug_on_a_Target_with_Bootloader With the difference that you want to l…

  • Hello, Thank you for your inquiry. The connection issues on macOS and Linux were reproducible. We are currently investigating. @francium, on Windows everything worked though so I assume your reported behaviour is not related to the other ones. Could you open another thread with more information about your setup? What target device? Custom or eval board? Example project for reproduction., etc. Best regards, Nino

  • Hello Markus, The files referenced in the documentation are the generic samples which come with Embedded Studio and are locate in the studio install folder under targets/Cortex-M. I just brought up the package variant with the SEGGER Linker as it provides you with a solution that runs out of the box. The generic files are as the name suggests generic and require user configuration to make it fir your particular setup. Feel free to use that approach if you prefer it. Best regards, Nino

  • Hello, Thank you for your inquiry. To retarget e.g. printf to use RTT the following steps must be considered in your setup: wiki.segger.com/Keil_MDK-ARM#RTT_in_uVision Additionally it appears that uVision V5 requires some changes in the syscalls file. This will be fixed in the next J-Link software release. You can also do this manually if you edit the SEGGER_RTT_Syscalls_KEIL.c as follows: Source Code (11 lines)and Source Code (38 lines)If you make these changes and consider the setup info from …

  • Hello, Thank you for your inquiry. Please note that J-Link SDK related topics may not be discussed in public as this would be a license violation. Please open a regular support ticket through the known channels. This thread will be closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. From your description it appears that CudeIDE is setting incorrect preprocessor defines. In that case I am not sure what you expect us to do? The error is on STM32CubeIDE side so we recommend contacting ST support in that regard as we are not planning on setting incorrect preprocessor defines in our SystemView sources. As a workaround you can add the incorrect preprocessor define to your copy of the SystemView sources or add the correct preprocessor define to y…

  • Hello Stefano, Great to hear that it is working for you now. Quote from ugolini: “The function callback on a breakpoint would be a bit more cumbersome. We would need to modify our test sequence so the firmware would hit the breakpoint only at the end of the test sequence. ” I see, but it would be the "clean" way. As the delay is a software delay on host PC the test results can be different between different test runs and this is usually something one wants to avoid when running tests. Breakpoint…

  • Hello, Thank you for your inquiry. As you already mentioned you can solve this with the hook function on a BP hit as explained here: wiki.segger.com/Automated_Tests_with_Ozone Could you elaborate why this solution would not work for your setup? A timeout dependent approach should also work by calling Util.Sleep. So you could execute your complete test in OnProjectLoad() and to the exports after the timeouts. Keep in mind though that if you are exporting the instruction trace window the target mu…

  • Hello Markus, Thank you for your inquiry. The easiest thing would be to use the SAM-E package where the SAME70 devices are part of. You can install it under Tools->Package Manager->Microchip->SAM-E The remaining steps are explained here in a video: segger.com/products/developmen…o/technology/cpu-support/ With that package you can now create a target specific project and have a linker file and memory map set up for your specific target device including TCM. Best regards, Nino