Search Results

Has a fair chance of being a DWARF 5 problem as well (not sure what DWARF version IAR V9.10.2 uses). I will push the DWARF 5 support internally, as this is going to be a growing problem, the more compilers are using DWARF 5 by default.

Flasher shares a lot of APIs and the DLL in general with J-Link. So the log file entries will say JLINK_xxx no matter if a J-Link, Flasher or J-Trace is connected. Regarding the rest: See previous post. This thread will be closed, as the original question was answered.

You can connect pin 1 to the 3.3V output of the adapter. Alternatively, you do not connect pin 1 at all but use this: wiki.segger.com/J-Link_Commander#VTREF and use the value “3300”

What has caught my attention is the line: VTarget = 2.720V Is the target expected to work with 2.7V signals on the debug lines (SWCLK, SWDIO, …)? 3.3V or 1.8V sounds like common target voltages but 2.7V sounds a bit odd. If this is a 3.3V target, the 2.7V could indicate an issue with your wiring and explain the flaky effects you are seeing.

I do not see any confirmation that this guy was really using a J-Link and I doubt it. Fact is that J-Link never supported SPC chips. It was Flasher only since day 1.

No. PowerPC (at least some derivatives) is only supported by Flasher PRO.

If you reduce the SWD speed to let’s say 2 MHz or even 1 MHz, does it become stable? I do not know the exact parameters out of my head but it is very possible that the V8 does not do exactly 4 MHz but more something in the league of 3.2 - 3.9 MHz while the V11 should be able to do the 4 MHz more exactly. Maybe the 4 MHz are too much for the HW design you are using and the V8 is just lucky to be somewhat slower than configured? Just a guess at this point…

Pin 19 of J-Link is a 5V output. This needs to be converted to 3.3V for your target as supply voltage. At the same time, J-Link needs the target reference(!) voltage on pin 1 for its level shifters. This pin is an input to J-Link. You cannot power your target through pin 1.

Actually Andy, what would really help is some cooperation. I did not really ask for a working dylib but more for a reproducer to solve the original problem, as we could verify the fix immediately with your dylib instead of sending preliminary versions back and forth. Regarding the plugin source: It is not in my hands making it open source or not, neither to judge if it has a commercial value for the company. I will report this to my management but cannot promise anything at this point.

Would it be possible to DM / otherwise send us your plugin as an unsigned *.dylib? BR Alex

Closed because it is a duplicate of: Power Board w/Segger JLink Plus Compact

Without knowing the board, I would say: Yes, it is the safe way to disconnect the battery / take it out of the socket.

If you have an < 5V board, you need an adapter between J-Link and board if the board should be powered through J-Link: segger.com/products/debug-prob…rs/target-supply-adapter/

There is no on-board converter on the J-Link but an adapter may be used: segger.com/products/debug-prob…rs/target-supply-adapter/

There is no “getting” back here… Did you notice the difference between your 2 screenshots? Screenshot A) Shows the sectorization for the internal flash of an STM32… device. It clearly says “static sector layout” Screenshot B) Shows the sectorization of the external QSPI flash connected to an i.MXRT1166. It clearly says “dynamic sector layout”. While you cannot change the sectorization of the internal flash because it is built into the chip, you can connect a different WSPI flash with a different…

Good point... We will add some logging for XML file parsing, especially in error case. These outputs will be part of the J-Link log file, they will *not* be output on stdout. wiki.segger.com/Enable_J-Link_log_file

I have no idea what you are trying to tell us with your latest try... I took a Mac Book Pro + J-Link PLUS + J-Link Commander: forum.segger.com/index.php/Att…46b67dee39d5e43fd625f4b33 If you see an output like this, the J-Link is properly detected by the Mac Book and SEGGER software (J-Link Commander). If it is then not listed in VSCode, it is a VSCode / nRF Connect issue. (Probably because NordicSemi is filtering out everything except the on-board J-Links on their dev boards) Then we are back to…

If your target works with 5V and consumes less than 300mA, you can power it via pin 19 of J-Link. Supply specs: segger.com/products/debug-prob…#technical-specifications see "Target supply voltage" and "Target supply current". How to enable the 5V output on pin 19: wiki.segger.com/UM08001_J-Link…Guide#Target_power_supply

Without a complete J-Link log file for both cases: - good (e.g. Windows/Linux) - bad (macOS) it is not possible to help here further. wiki.segger.com/Enable_J-Link_log_file The log file would give more insight if you are actually working with identical settings or you just think you are. I assume that you have written your own flash loader. Are you 100% sure that you are using the same version of the flash loader on the good and bad platforms? Just to make sure that your macOS setup is not using…

You already issued the same question via the ticket system and received an answer there: Quote: “1) J-Link EDU does not include direct support from our engineers through the ticket system, segger.com/products/debug-probes/j-link/models/j-link-edu/ 2) Please note that J-Link EDUs are not allowed to be used in a commercial context but for educational purposes only. Could you please double check and verify the license terms of the J-Link EDU? ”