Search Results

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

Hi, Here you go: wiki.segger.com/J-Link_Command_Strings#JLinkDevicesXMLPath wiki.segger.com/J-Link_Command…ng_J-Link_Command_Strings

The EDU mini is not guaranteed to work with 1.8V targets, only with 3.3V ones. BR Alex

Sounds strange... Is it possible that the USB hub, the J-Links are connected to, is not powered externally or its external power supply is broken? This would cause the hub and all J-Links connected to it to be fed from the USB cable that goes to your PC. Maybe it is just too much for that port and it cannot deliver sufficient current, so USB works unstable then? I still not see why it should affect your screen in any way but it would explain the "ding" which indicates USB detach + reattach/re-en…

Agree or not, your choice. Fact is: All J-Link flash loaders are designed to work with the natively memory-mapped space of the chip. For the RP2040 this is 16 MB, according to the datasheet. This means, J-Link will be able to program & verify 16 MB of QSPI reliably. Moving the 16 MB “window” to another portion of the flash (so effectively configure the QSPI controller to use fixed high-bits != 0 during memory mapped accesses) is not supported and there is no plan to do so. (Even though it would …

Hi, If the memory-mapped region supports max. 16 MB, this is what your flash loader does support as well. All our flash loaders support max. what is mapped in the address space of the MCU. So what you describe is not a bug and no, we have not “misinterpreted” the datasheet. If flashing beyond 16 MB on this MCU somewhat / half-way works, consider yourself lucky but don’t rely on it. If you want to have support for space beyond that (which is not XIP and therefore not “directly” debuggable anyhow)…

While RTT Stop-Mode in general might be working for the J-Link you use, stop-mode support on the RM48 may require further features that are specifically needed for RTT on RM48 in general, but these are not provided by the J-Link in use. In general, the J-Link you use is a V8 model which is pretty likely 10+ years old and has been out of support and maintenance, so there is no support, bugfixing or even analysis done on it. If the same issue comes up with a current model, we recommend to open an …

Not sure what you mean with “There must be a simpler way”. What do you have in mind? Can you describe the “simpler” setup you have in mind? As RTT goes through the debug interface, you need an active debug session that does all the RTT handling and you can attach to via TELNET.

How about this? mem32 0x21BC460, 1 wiki.segger.com/J-Link_Commander#Mem32