Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi, What FINE speed are you working with? I recommend 1 MHz as 2 MHz is challenging for most setups. Does the connect always fail or does it work if you start J-Link Commander a 2nd / 3rd time?

  • The -xc option is for GDB not GDBServer. These are 2 different products from 2 different vendors. gdbinit files are for GDB, not GDBServer. I need to check why the "GDBInit file:" output for GDBServer actually exists because it does not really make any sense.

  • Hi, The GetBMI and SetBMI commands in J-Link Commander have been added for the Infineon J-Link OB XMC4200 / 4500 only, as these are super device specific commands that need the probe to support very device-specific protocols. They are not available for any other model. You have an incompatible model. The only thing the regular J-Links support is the automatic switch from ASC_BSL to SWD0 which is done automatically and has been confirmed to be working recently.

  • The J-Link in use is an illegal clone. Thread has been closed / disabled.

  • V7.58a fixes the problem and is available for download:…twareAndDocumentationPack

  • The memory read / write speed mainly depends on the following factors: - Selected TIF (JTAG, SWD, …) speed - Target MCU speed - J-Link model Any SBC should be easily able to achieve USB speeds of > 1 MB/s or even 3 MB/s, so even the ULTRA+ / PRO models should be able to unleash their potential on these SBCs. Here you can find a list of SBCs that have been tested with J-Link:…_software_package_support

  • More a question for a Linux forum. J-Link does not use any special names etc. for the COM port enumeration under Linux. The name is chosen by Linux, as well as the numbering etc. Usually, the 1st J-Link that enumerates gets ttyACM0, the next …1, and so on.

  • Can you please follow this:…ty_using_J-Link_Commander and send a screenshot that shows the complete output?

  • Then you need to create one of these: and implement the SEGGER_OPEN_Read() routine in it: You need to assign a "virtual" address for your SPI flash, as all J-Link tools (like a CPU) work address-based. These are the samples we have:…ortex-M_template_projects We do not have one for non-memory-mapped flash. If you are interested in having SEGGER to write it for you as a service, please…

  • Is the external SPI flash memory mapped? So can it be read like RAM etc. by the EFM32?

  • Can you please send a screenshot of J-Link Commander that shows the S/N, HW version, FW version, … of your J-Link?

  • Once you exit a utility like JLinkExe or RTTViewer in a clean way (not killing the process!!!), JLINK_Close() is called which does restore the debug bits amd does what you are asking for.

  • Again, I do not see any misbehavior on the J-Link side. The PUSH is a breakpointed instruction, so the core is halted on a BP. Now you tell GDB to do an single instruction step. What you should see is: Remove BP Step Set BP What GDB actually does is: Remove BP Set BP Go So it looks like GDB does not do what you told it to do and the core is halted immediately again because it hits the BP. J-Link is not allowed to overstep the BP on its own because. GDB expects to do stuff like this by itself, no…

  • From the logs, I do not see anything being „stuck“. Looks normal from what I can say. But if source level stepping is a problem, while instruction stepping works, it most probably is an issue with GDB not being able to read the debug information of the ELF file properly and then calculating wrong addresses for source BPs to be set etc. A few hints: Did you use the same GCC + GDB version as recommended by the tutorial? Did you make sure that the GDB used for debugging, comes from the same toolcha…

  • What you describe is true but known behavior. So, where is the bug here? Did you see different behavior with versions before V7.00?

  • Erase, without any further parameters, will erase all flalsh banks known to J-Link for the selected MCU. This means, for a MCU with 2 MB flash, it will erase 2 MB. Loadbin erases the affected ranges. Meaning if your bin file is 512 KB in size, only 512 KB (rounded up to complete sectors) will be erased + programmed. So if you do not care about the other ranges, you may skip the extra erase step.

  • First you write that with XMCFlasher and J-Link PLUS you cannot even connect. Then you write that J-Link Commander connects but cannot reset, halt, … the target while XMCFlasher can. One of these statements is incorrect… Which one? Nnote that XMCFlasher is NOT a SEGGER utility but an Infineon utility. It may require the probe to report certain capabilities that are only repored by the OB because it is especially designed for Infineon eval boards anf XMCFlasher is especially designed to work with…

  • Hi, Log files do not have any documented structure / format. The format may change from one version to another, without further notice or even a release note entry. The way to go is checking the return value of the application, not parsing the log file. Note that J-Link Commander is not designed for automation and production purposes. It is a utility for basic troubleshooting. You may automate things up to a certain extend though:

  • Hi, You did get it wrong. You cannot power a target via SWD isolator. Actually, the SWD isolator needs to be powered by the target. It has 2 sides: Emulator / J-Link Target The Emulator side is powered by J-Link via pin 19. The target side is powered by pin 1 and draws current from the target on this pin.

  • Hi, This is not a genuine J-Link, but an illegal clone. These are excluded from any support and must not be used with the J-Link software (see license terms) This thread will be closed and probably also deleted.