Search Results

Thanks for the log-files. The problem is pretty clear: V6.14a: PC after reset @ 0x10002F1C (unexpected) V5.02e: PC after reset @ 0x00000160 (expected) What J-Link does is: 1. Reset 2. Perform Download 3. Reset 4. Set BP on main 5. Go 6. Wait until BP is reached In the old version, BP is reached --> CPU halts In the latest version, it is not --> CPU runs We will check if we can reproduce the behavior here. If reproducible, we will of course fix it. Keep you posted. Best regards Erik

Hi, We are not aware of any issues in the latest version of the J-Link software. Can you please send us a J-Link log file of a session where the issue pops up? How to enable the J-Link log file: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards Erik

Hi, In general we do not provide such old versions. Can you please let us know why you are looking for an older version? Please note that a) older versions may include bugs which are already fixed in later versions and b) such old versions are no longer supported. Best regards Erik

Hi Mark, We will add support for the ST STM32L082CZ device in the next version of the J-Link software. Till then, you can use the STM32L083CZ because as you already noticed, they are compatible regarding flash / RAM size. The new version is planned to be available by the end of this week. Would you like to be added to the J-Link software update notification list, so you get informed automatically when the new version becomes available? Subscribe: segger.com/notification/subscribe.php?prodid=7,94…

We have already found the root cause of the issue and fixed it internally. A new version including this fix is planned to be available within the next few days. If you would like to be notified about the availability of new versions, please feel free to subscribe to the J-Link Software and Update notification system: segger.com/notification/subscribe.php?prodid=7,94 Best regards Erik

Hi Dan, We received the same request via e-mail. We got back to you in the e-mail thread. We will update this thread once the case is closed. - Erik

Hi all, Quick update: We found the root cause of the behavior: Under special circumstances, the boot ROM of the LPC43xx brought the SPI flash into a state where it did not accept any commands. We have implemented a fix which is included in any software version >= V6.12i Sebastian already confirmed that the new version is working as expected. -- Case closed -- Best regards Erik

Hi all, Quick follow up: The current implementation works for 99% of our customers and only a very minor group of customers is effected by this (non-standard setup). For those customers, a special configuration (e.g. as part of an script file) is required as auto-detection / the default configuration does not work out-of-the-box. Yes, we could implement that the auto-detection works for some of the devices which require a special connect (at least for your setup) but even after that, for some de…

Hi, Good to hear that you are up and running now! -- Case closed -- Best regards Erik

Hi Marcus, in which application do you see the behavior (IDE, J-Link Commander, J-Flash, ...)? Most probably, the incorrect device is selected as for the STM32H743 no security detection has been implemented so far. Can you please send us a J-Link log file? How to enable it: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File - Erik

Hi Francois, Sorry for the delay. Just too many other interrupts. However, we have just created the wiki-article for the iMX7d. It includes the J-Link script files to connect to both A7 cores as well as the script which allows to connect to the M4 core. Further information regarding this can be found here: wiki.segger.com/IMX7D Best regards Erik

We have just created the wiki-article for the iMX7d. It includes the J-Link script files to connect to both A7 cores as well as the script which allows to connect to the M4 core. Further information regarding this can be found here: wiki.segger.com/IMX7D Best regards Erik

Quick followup: Is it possible that you want to send simple JTAG sequences? If yes, you do not have to perform the "connect" in J-Link Commander. Especially if you do not have any information about your device. You can send the required JTAG sequences using the "wjraw" command which is available before "connect". Apart from this, we would recommend to rather use a J-Link script file to output JTAG sequences as they allow a more c like syntax. Best regards Erik

Hello, you sent us the same request via E-Mail. Update for other customers which might have similar issues: It turned out that an interface speed which is out-of-spec has been used (15 MHz) while the RX63N series is specified with 10 MHz max. JTAG speed. When using a speed within the spec (<= 10 MHz) both J-Links are working as expected. Best regards Erik

Quote: “I believe it is ARM11. (It could also be ARM Cortex-M0, ARM Cortex-M0+, ARM Cortex-M1, SecurCore SC000)” Without having this information, i do not really wonder that the connect fails because you have to at least select the correct core. Best regards Erik

Hi Joan, Quote: “Is it possible to implement the Secure JTAG authentication using J-Link Software and Documentation Pack commands? without J-Link SDK.” Yes, this can be done using J-Link script files. Further information regarding J-Link script files can be found in the J-Link user manual (UM08001). Quote: “How could I read TDO line? How could I write raw value to TDI? (Is it wjraw command? Can you put an example of use?)” Can also be done using J-Link script files. We do not have an example for…

Hi Eric, For "real" single steps (one instruction) the interrupts are always disabled as this does not really make sense. If the interrupts are enabled or disabled when C-level stepping (may be more than one instruction) depends on the IDE. Best regards Erik

Hi Ruehl, What J-Link model do you use? Best regards Erik

Hi, Can you please give the latest version V6.12a a quick try and provide feedback? We have fixed something related this in the V6.1xx release. The version is available for download here: segger.com/jlink-software.html Best regards Erik

Hi, Currently, the J-Link software does not support EEPROM programming for the Kinetis device series. This is something which is already on our list but without a fixed time schedule so far (maybe Q1 2017). If you need urgent support, we would recommend to add support on your own using the SEGGER OpenFlashloader. Further information regarding this can be found here: wiki.segger.com/Adding_Support_for_New_Devices Best regards Erik