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 Martin, Thank you for your inquiry. The reported behaviour for existing sessions was reproducible. The error was introduced with J-Link Software V6.34. We will fix this as soon as possible. Sorry for any inconveniences caused. For now we suggest using an older J-Link version in such cases. Best regards, Nino

  • Hello Mateusz, Thank you for your inquiry. We tried to reproduce the issue using Embedded Studio and RTT Client under Ubuntu LTS 16.04 and everything was working as expected. Did you use the latest J-Link software version? Does it work if you use Embedded Studio or Ozone? segger.com/products/development-tools/embedded-studio/ segger.com/products/development-tools/ozone-j-link-debugger/ Best regards, Nino

  • Hello, Quote from apullin: “Unfortunately, when I try to connect with JLinkExe in Linux, I get the error: ” You need to specify the exact device you are using to program the SPI Flashes. Just like the example in the Wiki. Quote from apullin: “Our target device is an STM32F412. ” This would be the device you need to set under Chipinfo, Vendor is ST. Keep in mind that any code placed outside of the sections PrgCode, PrgData and DevDescr are not within Arm specification for Flash loaders and will m…

  • Hello, Please understand that we can't offer support in that regard as the pylink project is not our software and not under support by SEGGER. For any issues with pylink we suggest getting in contact with pylink support. Alternatively we suggest using the J-Link SDK directly in your application without the pylink wrapper: segger.com/products/debug-prob…nk/technology/j-link-sdk/ Best regards, Nino

  • Hello Phillipe, Documentation about ES can be found either inside ES when pressing F1 or online: studio.segger.com/ Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. You write that you are looking to simply Flash a binary and you are using J-Link Plus. In that case we suggest using either J-Link Commander or J-Flash which are both part of the J-Link software package. Does Flashing work when using the mentioned software instead of the third party software? Best regards, Nino

  • Hello, Thank you for your inquiry. Currently there are no plans to release a V11 J-Link hardware as the current V10 hardware version has still enough room for software feature upgrades. Examples from the last year would be Cortex-M23/M33 and RISC-V support. An overview of features and hardware revisions can be found here: wiki.segger.com/Software_and_Hardware_Features_Overview Best regards, Nino

  • Hello, Thank you for providing the example projects. We investigated further and found as expected that the issue is related to the third party HAL drivers which keep getting linked to .text instead of section PrgCode. You could try to work around by defining the sections as follows: Source Code (1 line)However this could lead to follow up issues. We do not recommend using external libraries for Flash loader creation as they mostly require that a full SystemInit has been executed which is not th…

  • Hello, Thank you for your inquiry. Glad to hear that you like SystemView. Are you running an application with an ROTS? What are you looking to achieve using user events? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. You seem to be using Embedded Studio commercially so we suggest contacting our official support channels. More information can be found in my signature. Simply fill out the form and state your Embedded Studio license. Best regards, Nino

  • Hello, Thank you for your inquiry. Which version of ES are you using with the Nordic SDK? According to Nordic SDK release notes only version 3.34b is supported. Make sure to use that version. For further assistance with Nordic SDK we recommend contacting Nordic directly. Quote from PhilippeG: “> for merging the two sdk_config.h files (of about 10 000 lines) i had to compare manually and took me a while. is there a tool that can compare definition automatically between two files? ” For merging th…

  • Hello, Thank you for your inquiry. A crash of SystemView was not reproducible on Ubuntu when recording an example embOS application on a Cortex-M4 target device. The crash most likely gets provoked either due to incorrect u-boot config or incorrect SystemView implementation in the Zephyr sources. Please understand that we can't offer support for issues resulting from third party applications that are not officially supported. We recommend to get in touch with u-boot and Zephyr support instead. B…

  • Hello, Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino

  • Hello, We tried to reproduce the reported issue with an LPC4330-Xplorer eval board an everything was working fine as expected with the latest J-Link software V6.34. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Are you using custom hardware or an eval board? Which SPI Flash are you looking to program exaclty? How is the Flash connected to the MCU on your board? Best regards, Nino

  • Hello, Thank you for your inquiry. Quote from apullin: “Does the Ozone trace facility support the Micro Trace Buffer in M0+ cores? ” It does, all you need to do is select "Trace Buffer" as trace source. Quote from apullin: “If so, will it work with an ST-Link onboard converted to J-Link STLink V21 ? ” It will, however keep in mind that the converted J-Link STLink can only be used with Ozone for evaluation purposes. Best regards, Nino

  • micro:bit Jlink

    SEGGER - Nino - - J-Link/Flasher related

    Post

    Hello, Yes should be available since V6.32i. Best regards, Nino

  • Hello, Unfortunately the provided project seems not to be portable. Attached is the error message we get when trying to open it. Could you provide a portable one? Nevertheless we assume that the gcc linker is not working correctly when using certain library functions and tries to link them per default to .text section which of course is not available in the release build. As the current workaround we suggest not using such library functions and use local helper functions instead. We will discuss…

  • Ozone: repeated crashes on MacOS

    SEGGER - Nino - - General

    Post

    Hello, Quick update. Our Ozone department informed me that this issue should be fixed in the current Ozone release version V2.56t. Could you give it a try and report back if everything is working now? Best regards, Nino

  • Hello, Thank you for your inquiry. Keep in mind that this here is no support forum. If you have pressing mattes (especially as a silicon vendor) we recommend using our official support channels, more information can be found in my signature. In your case it would be best if everything gets coordinated over Ruth. Best regards, Nino