My trusty J-Link EDU recently started booting to bootloader mode when connected through USB. J-Link Commander sees this, and attempts a firmware restoration.
More often than not, this firmware restoration fails and the device becomes unresponsive. When I then unplug/replug the device, the process starts over.
Command line output from J-Link Commander on Linux Ubuntu 18.04 LTS:
$ JLinkExe
SEGGER J-Link Commander V6.82b (Compiled Jul 23 2020 16:45:46)
DLL version V6.82b, compiled Jul 23 2020 16:45:35
Connecting to J-Link via USB...Updating firmware: J-Link V10 compiled Jul 17 2020 16:23:38
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
The above results in a GUI dialog with the following output:
New firmware: J-Link V10 compiled Jul 17 2020 16:23:38
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 successfull
[/quote]
Sometimes the firmware restoration does succeed, and when it does, the J-Link EDU functions as it used to.
I see multiple posts here about similar issues (forum.segger.com/index.php/Thr…irmware-Restoration-fail/, forum.segger.com/index.php/Thr…for-new-firmware-to-boot/, forum.segger.com/index.php/Thr…loader-mode-won-t-update/).
One of these posts mentions a fix for what sounds like a similar problem with the J-Trace PRO v2. This fix was included in version V6.82a (2020-07-21). Is a similar fix needed for the J-Link EDU?
Please advice.
More often than not, this firmware restoration fails and the device becomes unresponsive. When I then unplug/replug the device, the process starts over.
Command line output from J-Link Commander on Linux Ubuntu 18.04 LTS:
$ JLinkExe
SEGGER J-Link Commander V6.82b (Compiled Jul 23 2020 16:45:46)
DLL version V6.82b, compiled Jul 23 2020 16:45:35
Connecting to J-Link via USB...Updating firmware: J-Link V10 compiled Jul 17 2020 16:23:38
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
The above results in a GUI dialog with the following output:
New firmware: J-Link V10 compiled Jul 17 2020 16:23:38
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 successfull
[/quote]
Sometimes the firmware restoration does succeed, and when it does, the J-Link EDU functions as it used to.
I see multiple posts here about similar issues (forum.segger.com/index.php/Thr…irmware-Restoration-fail/, forum.segger.com/index.php/Thr…for-new-firmware-to-boot/, forum.segger.com/index.php/Thr…loader-mode-won-t-update/).
One of these posts mentions a fix for what sounds like a similar problem with the J-Trace PRO v2. This fix was included in version V6.82a (2020-07-21). Is a similar fix needed for the J-Link EDU?
Please advice.