Search Results

Hi Keith, I am sorry to hear that you are facing hassle when using the J-Link SDK in a C# environment. Unfortunately, there are currently no plans to release C# interface / version of the J-Link SDK. Quote: “Who programs in C / C++ anymore on Windows anyway??” The J-Link software is available for Windows, macOS, Linux and Linux for ARM, our middle ware for embedded systems and the firmware of our hardware products are written in C / Assembler, therefore it makes sense that our desktop software i…

Hi Andres, thanks for the update and good to hear that you are up and running! Best regards, Niklas

Hi Andreas, is the reset pin connected? You are using custom hardware (not an evalboard), correct? Best regards, Niklas

Hi, the electrical specifications are the same for both the normal and the compact version, only size and weight differs: segger.com/products/debug-probes/j-link/models/j-link-base/ Best regards, Niklas

Hi Enno, are you using an eval board or custom hardware? On some Ti eval boards, the onboard debug probe needs to separated from the target MCU in order to prevent it from interfering with the debug signals. Example: wiki.segger.com/CC1310_LaunchPad Best regards, Niklas

Hi, It should work when using one instance of Eclipse per core, if there are no issues on Eclipse side in regards to using two instances at the same time. Best regards, Niklas

Hi, It is possible to debug 2 cores in a JTAG-chain at the same time using only one J-Link. 1. Create a setup (e.g. a Ozone project) which connects to the 1st core and test if programming and debugging (stepping, breakpoints etc) work 2. Create another Ozone project for the 2nd core 3. Open two instances of Ozone (= two independent Ozone windows should be open now) 4. Open the 1st project in the first instance in the first instance of Ozone and the 2nd project in the second instance of Ozone. 5.…

Hi Ohnail, Support for Cortex-A53 and other ARMv8 cores is planed(!) for later this year. It will only available for J-Link ULTRA+ / PRO v4 and higher. Best regards, Niklas

Hi, could please share the code you use the init the PSRAM? Best regards, Niklas

Hi, I answered your PM. - Niklas

Hi Skot, Unfortunately, this is currently not implemented. J-Link Commander is intended for development purposes. If the provided functionality for scripting / automated use is useful, we are glad, but we can not invest development time in this direction. However, I will ask on the next J-Link team meeting if we can output the error messages via stderr. As an alternative, you can adjust J-Link Commander yourself by using the J-Link SDK (Part No 8.08.06 on the price list), which ships with the so…

Hi Greg, good to hear that you are up and running again! Best regards, Niklas

Hi Bruno, I just sent the schematics to the mail address specified in your forum profile. Best regards, Niklas

Hi, I just noticed that the JTAG is not supported on the Cortex-M Trace Reference Board at all. Best regards, Niklas

Hi Bruno, Quote: “I sent an email to support several weeks ago and heard nothing. ” I am sorry to hear that. This should not happen. I can see 4 mail threads from sick.com since 01/2017 in the system, all have been answered. Can you tell me the subject of the mail? Best regards, Niklas

Hi, I just set up a sample project for a A2F200M3F and autodetection worked fine. I used the internal RAM for RTT (@ 0x20000000). What Memory do you use @ 0x700679c0 ? Could you provide a reproducer application? Best regards, Niklas

Hi, Quote: “NOTE: sometimes is clean, but it can be 8 - 10 % loss too [..] So it may seems SeggerJLink/GDBServer is too sensitive for connection quality? (Not possible to increase response timeout ? ...” I am sorry, but the direct connection via Ethernet is intended for use in a local network, ideally with a delay of <1ms or 1-5ms in a bigger network. VPN & ping of > 100ms (300ms in your case) will not work, I also asked engineering regarding this, it will not work. However, J-Link Remote server…

Hi, what do you want me to do / how can I help you? Should I just set the old account to a certain password? - Niklas

Hi Greg, I can confirm your observations. int64 was a know variable type up to version 6.16, but was only used internally and did not support 64 bit variables (therefore, it was not officially documented). However, we removed it as we saw that it was used by customers although it was not documented. It was important to remove it as it did not behave as expected. (therefore, it was not officially documented in the first place). We plan to fully support 64 bit variables in script files later this …

Hi Man, we are currently not aware of any issues regarding SetRTTSearchRanges. Which target device are you using? Could you provide us with a reproducer? Best regards, Niklas