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.

  • J-Trace and IAR

    SEGGER - Nino - - J-Link/Flasher related

    Post

    Hello Gawie, Yes IAR will utilize the 64 MB on board buffer so depending of the target speed and created trace data this can be enough to reconstruct the last couple of seconds. Best regards, Nino

  • Hello Dirk, Great to hear that you are up and running again. As the initial inquiry has been solved this thread will be closed now. Best regards, Nino

  • Hi Russ, Oh OK, I assumed you already gave our sales team the MAC addresses, sorry for the confusion. When choosing the "right" MAC address we recommend choosing a physical one which is build into your PC, like the Ethernet controller or build in Wifi. If you are not sure which to choose simply provide our sales team with all devices available under ES->Tools->License Manager->Diagnose Problems. They will then figure out the right MAC addresses for you. Best regards, Nino

  • [SOLVED] Ozone

    SEGGER - Nino - - General

    Post

    Hello, Thank you for your inquiry. We received your inquiry via e-mail in parallel. For future inquiries please try to use only one contacting channel, otherwise it can happen that information gets lost between channels which can lead to unnecessarily delayed responses. To answer your question in short (for other forum users too). You should also have received an answer vai e-mail. Downloading multiple files in one session: yes Downloading debug information from multiple elf files at once:no, th…

  • J-Trace and IAR

    SEGGER - Nino - - J-Link/Flasher related

    Post

    Hello, Thank you for your inquiry. IAR unfortunately does not support any streaming trace features. For the best trace experience we recommend using Ozone the J-Link debugger. It can be used for free with a J-Trace PRO and works with IAR output formats. So you can compile your application with your current IDE and debug it in Ozone with all J-Trace PRO features active. segger.com/products/development-tools/ozone-j-link-debugger/ A List with Tested Devices for tracing can be found here: segger.co…

  • Hello, Thank you for your inquiry. Native J-Link support in GHS debugger has been removed by Greenhills a while ago. So at this current point in time we can't give any assistance with Greenhills setups as they are no longer supported. For any setup related issues we suggest contacting Greenhills support. Best regards, Nino

  • Hello, Thank you for your inquiry. Quote from Mron: “I've seen this as an old issue that was fixed about 4 years ago with nRF51 Dongles. Any help is appreciated. ” If that is the case then it should work with nRF52 as all eval boards known to us with nRF and J-Link OB use the exactly same J-link OB. Looking at the referenced dongle it seems like there is not J-link OB at all: nordicsemi.com/Software-and-To…ment-Kits/nRF52840-Dongle Quote from Nordic: “The dongle has been designed to be used as a…

  • Hello, Thank you for your inquiry. We can't find any information about the ZGM130S037HGN. Could you provide a reference link? What Coretype is it? Currently supported devices can be found here: segger.com/products/debug-prob…pported-cpus-and-devices/ Should your Core type be listed you can also add support yourself: wiki.segger.com/Adding_Support_for_New_Devices Best regards, Nino

  • Hello, Thank you for your inquiry. This sounds like an incompatibility of the elf file with current standards. Could you provide us with the elf file so we could check if there is a generic issue with Ozone interpreter? Best regards, Nino

  • Hello Russ, Thank you for your inquiry. If I see correctly you have purchased Mac locked ES licenses. In that case at some point you provided our sales team with MAC addresses of your PCs to lock the licenses to. Additionally you should have received a downloadlink where you can access your licenses. Is this correct so far? Each license should come with its own .zip file which contains the license and a .txt with it. That .txt will show which MAC address the license is locked to. Now you need to…

  • Hi Dirk, Quote from dzabel: “(the "v3" seems strange to me, I have installed the SES v4.10a, but there is no "v4" folder). ” This is due to backwards compatibility as between v3 and v4 there were no changes for package handling so the name was kept to avoid multiple package databases. Quote from dzabel: “I find various *.xml files below the nRF folder, but NO file named "nrf52_Registers.xml". ” You should see the file in SEGGER Embedded Studio\v3\packages\nRF\XML There are files nrf51_Registers.…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Embedded Studio will only display what data it finds in the RTT buffer. So it is save to assume that for some reason "garbage" data is written into RTT Buffer. RTT is provided in source form so it should be easily debuggable when unwanted data is read from the buffer. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. J-Link will usually only delete used sectors and leave everything else untouched. Did you verify that the application that has been downloaded at all? What target devices are you debugging? Is it on custom hardware or an eval board? Could you provide an example project for reproduction on an eval board? Best regards, Nino

  • Hello Joe, Thank you for your inquiry. When importing more complex projects from IAR or Keil to Embedded Studio there are certain steps that need to be considered regarding compatibility. An example guide for a proper import can be found here: wiki.segger.com/SEGGER_Embedde…to_SEGGER_Embedded_Studio The example is for IAR but the same points apply to Keil as well. Should the imported project still fail after following the steps we suggest contacting ST support in regards of ST HAL issues as that…

  • Hello, Thank you for the update. Good to hear that you are up and running again. This thread will be closed now. Best regards, Nino

  • Hello, Thank you for the flowers, we try our best to answer between software projects Quote from Anders: “Figuring it was worth a try and disabling my AMD driver, my build time went from 80 seconds to 19 seconds. I have absolutely no idea why, and upgrading to the latest AMD driver also fixed the build speed while using the AMD GPU. ” This is a good hint. On my private PC I saw significant issues with my AMD card and Win10 in general. What basically happened is that Microsoft autoforces GPU driv…

  • Hello, Quote from pasnew: “the Flash content of 0x08000000 (or system memory, depend on boot0 pin) is mapped at address 0x0 at boot time (refer to RM0444, section 2.5 Boot configuration, page 58). ” Yes we know, and this is exactly why IARs behaviour is not correct here as it assumes the position of boot0 pin. As you wrote yourself at 0x0 can be anything depending on the pin setting. This is not a fixed setting and will vary from customer to customer, so we will not assume that at 0x0 Flash migh…

  • Hello, Thank you for providing the logs. The Flash loader used here has been developed to work with a IMXRT1050-EVKB board. To work on the embedded artists board all QSPI connections must be identical. If not the Flash loader must be recompiled. Additionally for QSPI Flash programming to work several hardware modifications were necessary on the IMXRT1050-EVKB board. This is probably the case for the Embedded Artists board as well. See here for mode details: wiki.segger.com/I.MXRT1050#QSPI_flash …

  • Hello, Thank you for your inquiry. Please be aware that the referenced post is over 4 years old so it is highly unlikely that the issues are related. The J-Link software version you are using is rather old, could you try the latest one and see if the behaviour improves? What target device are you looking to debug here? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us with the latest version. Which J-Link software version are you currently using? Does the behaviour improve when using the latest one? Quote from timurlocumi: “We have been using RTT for many years now and since a few months the logging output became so slow that it's unusable. ” What tool are you using for logging? Your own, or one of the J-Link tools? Quote from timurlocumi: “I've seen post here with the workaround using a olde…