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 Darren, Thank you for your inquiry. The behaviour change in V6.40 was unintended and will be back to the old behaviour with the next version. Best regards, Nino

  • Hello, Thank you for your feedback. To keep all information in one place this thread will be closed now. Could you open a ticket (see my signature) so the request can be tracked more easily by us? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you try updating to the latest J-Link Software version and report back if the issue persists? Are you using the original JTAG cable shipped with the J-Link Edu? We had many cases where third party cables were the cause of signal issues. Could you measure the JTAG signals at target device side with an oscilloscope and post pictures of your measurements? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you verify general functionality using Ozone? segger.com/products/development-tools/ozone-j-link-debugger/ Are you using an eval board or custom hardware? Is this issue happening with other projects as well or just this particular? Best regards, Nino

  • Hello, Thank you for your inquiry. Normally -auto will execute all settings that you set in your J-Flash project under production, the same goes for the "Start Application" option under tab Production. How are your settings there? Could you post a screenshot or send us your jflash project for verification? The J-Link software version you are using is rather outdated. Could you try the latest one and report back if the issue persists? Best regards, Nino

  • Hello, Thank you for your additional information. Quote from sabdulqadir: “The progress bar in lower left corner says CPU running. ” I could not see that with the provided pictures. Quote from sabdulqadir: “I ruled out a hardware issue as i was able to connect using True Studio from STM (eclipse based IDE). ” Are you certain JTAG was used in that case and not SWD? Could you post a screenshot of a J-Link Commander connect using JTAG? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander Could …

  • Hello Jason, Thank you for your inquiry. It seems that this feature is not documented properly yet, thank you for pointing that out. To use that feature you set your favorite editor as you wrote and to use it keep Shift pressed while double clicking a source file in the project explorer. Then the file should open in the external editor. The documentation will be improved accordingly. Best regards, Nino

  • Hello Kenny, In the security area of Kinetis devices is one bit that will lock a device indefinitely so that not even J-Link can recover it anymore. That is what the allow security device differentiation is for. Why it did not work before for you has two reasons. One is that the startup code was already placing information to 0x400 which you tried to link additional data to which will not work. You can't link different data to the same location. The second issue is that if you do not select the …

  • Hello, We have that board in house. Could you provide us with an example project for reproduction purposes? Best regards, Nino

  • Hello Marcin, Thank you for your inquiry. Such an issue is not known to us. Could you provide us with an example project for reproduction purposes? We have a couple of NUCLEO-L432KC which we could use for testing. Best regards, Nino

  • Hello, Thank you for your inquiry. J-Link will only automatically search for a set default RAM section that we know will always be accessible after reset. This is usually RAM starting at 0x20000000 + accessible RAM size. Should you use some other RAM section it is customer responsibility to make sure it is initialized correctly and the search range has to be set manually to include that RAM as well e.g. with exec command: SetRTTSearchRanges Quote from sincostan: “When the RTT Control Block _SEGG…

  • Hello, Thank you for your inquiry. Are you using the ES CPU support packages by any chance for your project? If yes you should see the following code snippet in the MK64xxx_Vectors.s: Source Code (35 lines)This was implemented by us so our customers do not lock their devices everytime while creating a new project due to the inconvenient lok bit placement on Kineits devices in the middle of Flash. To be able to write this Flash section make sure to put this code block to #if 0 and select the corr…

  • Hello Peter, Yes the issue is reproducible with the example. Embedded Studio is using the ARM gcc and clang compiler so the issue comes from their error handling and not from Embedded Studio itself. GCC simply detects it wrong. If you use the same example and switch to clang in project options as compiler, you will get the correct error message: "expected ';' after enum" This thread will be closed now as this is issue is related to bugs in gcc and not Embedded Studio. For more information we sug…

  • Hello Russ, Thank you for your inquiry. Such an issue is not known to us. We just tried to reproduce the issue with the default Hello World project for a Kinets K66 emPower board that I had lying around. The stack window is shown in the attached picture and is populated as expected. Which target device are you using exactly? Is it on custom hardware or an eval board? Could you provide an example project for reproduction purposes. Best regards, Nino

  • Hello Robin, Thank you for your inquiry. Such an issue is not known to us. Which ES version are you currently using? Could you provide a screenshot of the error message? Best regards, Nino

  • Hello, Thank you for your report. It seems that the CMSIS DSP library has changed its behaviour from V4 to V5 which the ST packages are not compatible to. We will investigate this further and update the ST packages if needed. Until then we recommend using CMSIS 4 for the ST packages. Best regards, Nino

  • Hello, what kind of board are you using? Evalboard or custom hardware? Is the reset pin connected to the debug interface? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Which software are you using for debugging? Eclipse? Could you try Ozone instead with your eclipse output file? Best regards, Nino

  • Hello, Thank you for your inquiry. What would you need this exact version for? It is a beta version so we do not have past versions on the web. You can however download V6.34 on our website which will have the features from V6.33h included. segger.com/downloads/jlink/#J-…twareAndDocumentationPack Simply click on "Older Versions", there you can get the V6.34. Generally we suggest using always the latest version as older versions are not supported. Best regards, Nino

  • Hi Jules, You can, but you would need to implement the Flash loader you self as described in the Wiki. Best regards, Nino