Hello,
We have a problem with a J-Link Plus that we bought last year. Part number is 8.08.28, version is 10.1.
Our problem is that the J-Link firmware fails to boot, so it falls back to a bootloader firmware that won't even accept USB connections, making it functionally useless. The only reaction we can get out of it is the first time we try to establish a connection with J-Link Commander, it'll detect that we need to update the firmware
then the update seems to complete correctly
but the new firmware fails to boot with the following message.
Here are some text dumps of the logs found in the above pictures (for search discoverability and easy copying) :
Display All
After this failed update cycle, the J-Link won't respond to anything, it just gets stuck on "Connecting to J-Link via USB...", which doesn't timeout even after a whole hour. When the J-Link is in this state, here is what the ShowEmuList command gives us:
Of course, our actual serial number isn't 123456. If we unplug it and plug it back in, we're back on square one: needs to update, "successfully" updates, doesn't work.
Speaking of plugging it back in, when we plug the J-Link into a computer, the status LED:
Here's a list of configurations we've tried:
Is there anything else we could try, or does this look like an RMA? Any help would be appreciated.
Many thanks in advance,
Hugo M.
We have a problem with a J-Link Plus that we bought last year. Part number is 8.08.28, version is 10.1.
Our problem is that the J-Link firmware fails to boot, so it falls back to a bootloader firmware that won't even accept USB connections, making it functionally useless. The only reaction we can get out of it is the first time we try to establish a connection with J-Link Commander, it'll detect that we need to update the firmware
then the update seems to complete correctly
but the new firmware fails to boot with the following message.
Here are some text dumps of the logs found in the above pictures (for search discoverability and easy copying) :
Source Code
- WARNING WINDOW
- J-Link V6.62a Firmware Restoration
- The connected J-Link is running in bootloader mode.
- This happens if no valid firmware has been found on the J-Link.
- Without a valid firmware, J-Link cannot be used.
- O.K.
- FIRMWARE UPDATE WINDOW
- New firmware: J-Link V10 compiled Jan 7 2020 16:51:47
- Current firmware: J-Link V10 compiled Jun 3 2015 BTL
- Starting bootloader... already started.
- Sending firmware data... OK (491520 bytes).
- Waiting for new firmware to boot...
- Waiting for emulator to detach... Timeout, assuming emulator has already re-enumerated.
- Waiting for emulator to attach... OK after 0ms.
- Firmware updated successfully.
- CONSOLE
- C:\Program Files (x86)\SEGGER\JLink_V662a>jlink.exe
- SEGGER J-Link Commander V6.62a (Compiled Jan 31 2020 12:58:42)
- DLL version V6.62a, compiled Jan 31 2020 12:58:08
- Connecting to J-Link via USB...Updating firmware: J-Link V10 compiled Jan 7 2020 16:51:47
- Replacing firmware: J-Link V10 compiled Jun 3 2015 BTL
- Waiting for new firmware to boot
- FAILED: Communication timed out: Requested 4 bytes, received 0 bytes !
- Could not read J-Link capabilities.
- Cannot connect to J-Link
- J-Link>
After this failed update cycle, the J-Link won't respond to anything, it just gets stuck on "Connecting to J-Link via USB...", which doesn't timeout even after a whole hour. When the J-Link is in this state, here is what the ShowEmuList command gives us:
Of course, our actual serial number isn't 123456. If we unplug it and plug it back in, we're back on square one: needs to update, "successfully" updates, doesn't work.
Speaking of plugging it back in, when we plug the J-Link into a computer, the status LED:
- is solid red for a second;
- blinks twice while still red, only lasts about a second;
- switches to a rapidly blinking green which goes away very quickly;
- ends up on a stable solid green.
Here's a list of configurations we've tried:
- 2 different USB cables for the J-Link;
- 4 different computers on Windows (7 and 10);
- different USB ports on a single computer;
- connecting both with and without a USB hub;
- manually changing the driver in the Device Manager;
- different versions of the J-Link tools (some older, some newer).
Is there anything else we could try, or does this look like an RMA? Any help would be appreciated.
Many thanks in advance,
Hugo M.