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 Allen: “I can create a Template_CortexM.elf with SEGGer Embedded Studio, if is the .elf the "RAMCode"? ” Yes the resulting application is the RAMCode. Regarding the demo project for the STM32F469_Discovery board, please note that we can't share this sources in public. But you can request this via our support system. Simply open a ticket in the J-Link support group requesting the sources. How to open a ticket is explained in my signature. Best regards, Nino

  • Hi, OK that looks weird. It seems like it depends on the system fond used. Which host OS are you running on? I do not see this behaviour on Win10. Best regards, Nino

  • Hello, Thank you for your inquiry. Currently JFlashSPI will always first try to detect the Flash ID. This is to make sure that a reliable connection to the chip is established so no damage can be done. So unfortunately you would have to use your workaround in this specific case. Alternatively you can also purchase the J-Link SDK and create your own version of the J-Flash SPI that handles such special cases: segger.com/products/debug-prob…nk/technology/j-link-sdk/ Best regards, Nino

  • Hello Karsten, Thank you for your inquiry. Are you using custom hardware or an eval board? You can find an example project for the STM32MP15X-EVAL on our Wiki: wiki.segger.com/STM32MP15x#Tracing_on_STM32MP15x Could you give the TMC/ETB trace sample a try? Does it work for you as well? If not could you check the following troubleshooting steps and provide a screenshot of the Commander session? wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection Best regards, Nino

  • Hello, Thank you for your inquiry. J-Link supports two programming modes. Direct and indirect. wiki.segger.com/Programming_External_SPI_Flashes If you want to do direct programming, all you have to do is to wire the SPI Flash to the J-Link debug interface as documented and you are good to go. The following Flashes will work automatically: segger.com/products/debug-prob…es/supported-spi-flashes/ Other similar Flashes can be added manually using J-Flash SPI: segger.com/products/debug-probes/j-link…

  • Hello, Quote from hs2: “Yes, I'm using the latest non-beta JLink package and also ensure Ozone is not running when installing JLink. ” Ok thank you for verifying. Quote from hs2: “No, as mentioned since it happens sporadically (and luckily not very often) I don't see how to provide a reproducible test case. ” Yes that is why we would like to investigate this further, but without a reproduction scenario that works on our developer PCs it is near impossible to fix this. To understand better what y…

  • Hello, Thank you for your inquiry. We received your request via our support system in parallel. To make sure no information gets lost between channels this thread will be closed now and the correspondence will continue via e-mail. Best regards, Nino

  • Hello Alessio, Quote from ballotz: “We noticed that RT106x processors are not listed anymore in JLinkDevices.xml (JLink in Ozone 3.20b). ” Yes this is intended behaviour as the QSPI flash loader is now compiled into the J-Link dll. Quote from ballotz: “Using NXP Boot Utility we found that probably the boot header got corrupted since it showed occasionally a zero sector size of the flash. ” Did you adjust your Ozone project as explained in your other thread? Missing RAM functions from Execution P…

  • Hello, Thank you for your inquiry. Sounds like Ozone sets the initial breakpoint on the first mention of main() in the elf file. We would like to look into this and improve Ozone if possible. Could you provide the elf file for reference? As a workaround you can set the initial breakpoint symbol in Ozone under Tools->System Variables->VAR_BREAK_AT_THIS_SYMBOL Best regards, Nino

  • Hello, Thank you for your inquiry. Try using __ARMCC_VERSION instead. We will update the RTT sources accordingly with our next software package release. Best regards, Nino

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

  • Hi, that is also unwanted behaviour and will be improved in future versions. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. It appears that the clock initialization of your target application is not correct. For reference could you give the attached example project a try? You can rebuild and flash it using Embedded Studio: segger.com/products/development-tools/embedded-studio/ If you now start the SWO Viewer. Does it work as expected? The default clock in this example is 16 MHz. If you edit the example project to initialize the core to 168 MHz. Do y…

  • Hello Maxim, Thank you for your inquiry. The reported behaviour is reproducible and no intended. This will be fixed. Best regards Nino

  • Hello Thomas, Thank you for your inquiry. Embedded Studios C++ library is based on the STLPort and can be installed via the Package Manager. However due to low demand it is based on the C++98 standard with a couple user requested extensions of more modern features but so far no feature from C++17. Currently our core market is C where we are currently moving our complete toolchain to our own SEGGER toolchain with some heavy optimization and great features for embedded targets. You can find some m…

  • Hello Fränz, Thank you for your inquiry. For autocomplete to work quickly the indexer must index the project first. Could you check if the indexing process is completed? You can see the progress e.g. in the Source Navigator window. After the indexing is done auto completion should work instantly. Best regards, Nino

  • Hello, Thank you for your inquiry. It appears the guide is a bit outdated. I assume you are stuck at the part which says to install J-Link drivers with COM support. Just download and install the latest J-Link software and you should be good to go: segger.com/downloads/jlink/ Should that still not work please note that we do not provide any support for the conversion to J-Link as stated in the guide. As the Spansion Board you are using features a 9-pin debug header for external debug probes we re…

  • Hi Alessio, Ok I was able to Flash the application now. However it gets stuck in the ROM bootloader at 0x00200000 for me. I have the same jumper settings like on your board. Anything else that might need to be considered? If you do a erase of the external e.g. with J-Flash or J-Link Commander and then try to Flash the application you have attached. Does it run for you as expected? Regarding the profiling of RAM data via SWO, it is currently not fully supported but we are looking into it. Regardi…

  • Hello, Quote from Zeke: “Here are some logs. These are from after I closed Ozone via task manager. ” Thank you for providing the logs. The J-Link log does not seem to be saved correctly. Is Ozone the only tool in this instance that is connected to your J-Link or are there also other tools? You write that this issue appears on your own eval boards. I believe we should have them in our office as they are using J-Link OBs. Could you provide an example project for your boards with reproduction steps…

  • Hi, Thank you for providing the information. Could you send us the J-Link log and Ozone log file for reference? wiki.segger.com/Enable_J-Link_log_file and for Ozone log start Ozone via commandline with parameter -logfile <filepath> Best regards, Nino