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, Quote from dmarples: “According to the documentation it should support baudrates 3.2x10^9/64 and below ...I've tried rates as low as 115.2kbaud. ” This is correct if the target device supports such speeds on the SWO pin as well. Usually the SWO speed equals the Core speed on Cortex-M. This is however not true anymore for cores with significantly higher speeds than e.g. 100 MHz. We assume the iMXRT uses another peripheral clock to set SWO speed which does not equal Corespeed. However most …

  • Hello, Our books are filled with other paid projects currently. It is still on our wishlist/ToDo and is planned to be available this year. Best regards, Nino

  • Hello Markus, Thank you for your inquiry. We are currently in the process to eliminate the gcc linker as soon as possible due to issues and limitations that pop up occasionally. Therefore we created the SEGGER Linker which is available since V3.50. Could you give it a try? It should work more straightforward. The documentation can be accessed through the Embedded Studio help as pictured in the attached image. Best regards, Nino

  • Hello Ricardo, Thank you for your inquiry. 1. This is possible. Open the two files you want to look at in the editor window. Now drag one of the files into another dock. Now they should be next to each other. 2. This is not implemented yet but on our wishlist already. A time schedule for this feature is currently not set. Best regards, Nino

  • Hello, Thank you for your inquiry. What GDBClient are you using in your setup? Keep in mind that all memory ready, breakpoints etc. will be issued by the Client and not GDBServer. GDBServer is only forwarding what the Client is asking and J-Link is executing exactly that. Depending on how efficiently the Client handles BPs it is possible that they get used in the background for other "features". We suggest getting in contact with the GDB Client support. Best regards, Nino

  • Hello, Thank you for your inquiry. As described in the linked post you can edit the mapping yourself. Default is Ctrl + J. Quote from SEGGER - Nino: “You can find the file to edit under File->Open Studio Folder->Studio Folder->/bin/keyboard.xml Before editing Embedded Studio must be closed and we suggest creating a backup of that file should editing go wrong. ” Best regards, Nino

  • Hello, Quote from hiqrf3: “Currently, I do not use SES as the official commercial product development. ” OK, we got the impression that ES is used commercially due to your first sentence in this thread: "I wrote a program using the SES + STM32 platform, which has been running well and has been applied to over a million products, but recently I found that there are occasional hardfault cases." This sounded a lot like commercial use to us. Anyways, does right clicking the disassembly and selecting…

  • Hello, Thank you for your inquiry. The software version you are using is very old and out of maintenance. Could you try to open the elf with the latest version of Ozone? segger.com/products/development-tools/ozone-j-link-debugger/ We tried with the V2.56t and it was working as expected. Best regards, Nino

  • Hello, Thank you for your inquiry. Which version of Embedded Studio are you using? The latest version 3.50 has a project importer for AC6/STM32 Workbench projects which can be created in CubeMX and then imported to Embedded Studio. Do the same issues appear if you import it with the new project importer? Best regards, Nino

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

  • Hello, This thread will be continued via our official support channels. It will be closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. We received your request per e-mail as well. To make sure that no information gets lost over multiple communication channels this thread will be closed now and further correspondence will be held via e-mail. Best regards, Nino

  • Hello, Thank you for your inquiry. For verification could you provide the S/N of the J-Link you are using? Is it the one you registered with? Generally the J-Link V8 you are using does not support Cortex-M4 targets: wiki.segger.com/Software_and_Hardware_Features_Overview That it works in J-Flash is pure chance. Unfortunately the J-Link V8 is out of support and maintenance so we recommend getting a new J-Link V10 model which includes Cortex-M4 debugging and many more new features. Best regards, N…

  • Hello, Thank you for your inquiry. Your questions should be answered by our blog post to this topic: blog.segger.com/current-state-of-the-trace-market/ It basically boils down to a trade off the silicon vendors have to make. Either fast GPIOs that can keep up with 1 GHz devices at 4-bit trace (very expensive in silicon, no trace debug probe available at that speeds), wider trace port width (barely supported, many pins (up to 32) lost for a debug feature), or the so far most popular option, limit…

  • Hello, Thank you for your inquiry. The specified eval board does not support JTAG. SWD must be used instead. A successful connection using an external J-Link can be seen in the attached picture. Best regards, Nino

  • 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