Search Results

Hi, In the list you have sent a link to, none of the devices are supported by J-Link. J-Link supports debugging on the MSP0 and MSP432 derivatives (Cortex-M based) The “legacy” MSP430 are only supported by Flasher for production programming. No debug support. You may be lucky with J-Link + OpenOCD for MSP430 support though.

Sounds like it has to do with the “working directory” (en.m.wikipedia.org/wiki/Working_directory) When you click the bat file, the working directory of the bat file code is the location of thw bat file. That working directory is inherited by JLink.exe, so when opening the relative(!) file path <Example.bin> the file is searched in the working directory (same location where the bat file is) When you call the bat file from within LabVIEW, the working directory is most probably the location of your…

Sorry for the delay in response. We have no intentions to remove the open flash loader (OFL) support. We also do and will continue to support CMSIS algorithms, as stated here: wiki.segger.com/J-Link_Device_Support_Kit#DSK_availability (The SEGGER flash loaders provide more optimizations over the OFL and CMSIS, so are usually faster) The price for the DSK is more a compensation for support + to make sure that it does not end up in "the wrong hands". Quote from dsherman28: “Unfortunately, the deve…

Hi, Sure you can connect 5x Flasher Compact using a standard USB hub. Here you can find an example to program multiple targets in parallel: wiki.segger.com/UM08003_JFlash…tiple_targets_in_parallel

Hi, to 1) See here: segger.com/products/debug-prob…#technical-specifications and look for VIF. 1.2 - 5V are fine for VIF (VTref) to 2) While it is a bit unusual to shared TRACED0 with SWV because SWV is usually shared with TDO, I can see why SiLabs did it. As their EFM32 do not support JTAG, there is no TDO signal to be shared with. Actually, sharing SWV with TRACED0 is a clever move because you so not lose anything. If you enable & use trace, the SWV data is merged into the trace stream and als…

Can you please PM me the S/N of your J-Trace unit?

Not being able to specify the SWO speed is bad… Having it on “max possible” is OK but not being able to change that setting is a bad thing because different models have different max. speeds May be worth opening a ticket at Renesas for this because it should not be a big change for them (nothing would change for 99% of their users) But 67 MHz SWO speed has a high probability of being problematic. Many I/Os are not capable of speeds beyond 50 MHz (if that high at all). You can easily mess things …

Hi Steven, I see that you have been in touch with Richard W. at TI. A very capable guy… Pretty sure he can help you out. As J-Link’s Cortex-M4 support is generally working and we are not talking about an issue with our flash algo etc. but a connect works and a simple halt command is not accepted / acknowleged by the core, it can only be something chip-specific like the M4 being held in reset. My suggestion is to get one of TI’s example projects up and running that blinks an LED or so on the M4. …

I doubt that it is a problem with the ULTRA+ firmware but more a setup issue. Probably you have set the SWO speed to “max” and the ULTRA+ (which is capable to handle up to 100 MHz SWO speeds) leads to settings that exceed the max. speed of the MCU’s I/Os. What SWO speed do you use? Did you check if selecting a fixed speed of 1 or 4 MHz for SWO works with both probes?

Hi Pedro, What unit do you use? (Can you please PM me the S/N?) There is currently no official way to do this via J-Link Commander but we should be able to add something like that. Way easier than adding a whole command line handling to a heavy, almost GUI-only utility like the Configurator. BR Alex

Hi Steve, Sounds a bit like the M4 is clocked, so the AHB-AP debug domain is accessible but the core itself is still held in reset. This would explain why it is not responding to halt requests etc. Is that possible in your case?

Hi, There is no RTT support for ARM11, as ARM11 does not support background memory access. The “emulation mode” is also not available for ARM11

That’s not how J-Link is intended to work. Nope, there is no possibility doing what you plan to do, with the available script etc. APIs. We strongly recommend to not further pursue this path but select the correct device in the IDE.

Hi, I see. I will discuss this internally. In the meantime: Current (Windows) installers do not need admin rights for installation. You can also select “install only for this user”, then not even Program Files is touched but the software is installed to C:\Users\…

There is no “reset” API function available from within a script file because the reset itself may call script file functions like BeforeReset(), AfterReset() and ResetTarget(). What core are you working on? Cortex-M…, Cortex-A…, RISC-V, …?

Hi, Why do you think you need the manual update? What is the problem with the regular update path? We manual update is more something like a last resort for units that have a correctly signed etc. but faulty functioning firmware that can no longer be reached via USB or IP. Something that has not happened in years, so the manual update was not needed for a while… BR Alex

Not sure if you understood Fabian’s post… “Sinply pulling nReset” is something that can disturb a debug (and so RTT) session. Pulling the reset pin may also reset the debug interface and cause a connection loss. Even if it does not, it may cause memory access errors or garbage being read from the buffers (e.g. the startup code re-initializes the control block to 0 while J-Trace is currently evaluating the buffer positions). Such error cases may lead to an RTT “safety shutdown” where the buffer i…

I do not specifically know the KV30 into much detail but have worked on many of the various Kinetis flash algorithms for J-Link. For all Kinetis I have encountered, the debug interface does not provide a way to get the backdoor key into the chip. The manual said that the user is responsible to implement a way of receiving the key (e.g. via UART, SPI, …) and then the user application must copy it into the backdoor key comparison registers, to actually trigfer the temporary unlock. If the applicat…

Are you serious? You are wondering that something prevents your target from entering low power modes after you KILL GDBServer and so do not even give it a chance to perform a clean shutdown & clearing debug bits that very possibly may inhibit low power modes? What the… How about this? wiki.segger.com/J-Link_GDB_Server#-singlerun

Is the target a 3.3V one? If not, that’s the culprit, as the EDU Mini does not have level shifters and therefore only supports 3.3V debug signals. Another thing is TRST. Not sure if the AM33 59 needs that pin… BR Alex