Hi,
I've been working with a EFM32GG target and the J-Link Pro for several weeks flawlessly.
IDE is Simplicity Studio.
All drivers and software - as far as I could oversee - is up to date.
Since yesterday (I suppose a firmware update of the J-Link, but I'm not sure any more) I get the following error message within the Simplicity Studio:
The J-Link does connect:
Display All
Is it possible to upload an older firmware to the J-Link in order to fix the problem?

Update:
I exchanged the J-Link pro (updated firmware) by an J-Link base from the stock with an old firmware installed.
and all worked in a sudden!
This is for me the evidence that the bug is within the J-Link pro (S/N 600100399) nonetheless if the EFM32 Studio fom Silicon Labs is
up to date with Segger or not.
My question ist still:
Can this be fixed by a firmware up/down-grade or is this device broken?
Regards.
I've been working with a EFM32GG target and the J-Link Pro for several weeks flawlessly.
IDE is Simplicity Studio.
All drivers and software - as far as I could oversee - is up to date.
Since yesterday (I suppose a firmware update of the J-Link, but I'm not sure any more) I get the following error message within the Simplicity Studio:
Source Code
- Failed to connect to device
- TCF error report:
- Command: DebugAdapter connect "usb.600100399 (USB #0).adapter.mcu", {"exceptionsToCatch":0,"enableITM":false,"connectMethod":"normal","jLinkSpeed":"auto","deviceDescrip...
- Error text: Could not debug with this adapter. Ensure the kit and/or MCU are fully detected.
- Error code: 131073
The J-Link does connect:
Source Code
- SEGGER J-Link GDB Server V5.12e GUI Version
- JLinkARM.dll V5.12e (DLL compiled Apr 29 2016 15:03:58)
- -----GDB Server start settings-----
- GDBInit file: none
- GDB Server Listening port: 2331
- SWO raw output listening port: 2332
- Terminal I/O port: 2333
- Accept remote connection: localhost only
- Generate logfile: off
- Verify download: off
- Init regs on start: off
- Silent mode: off
- Single run mode: off
- Target connection timeout: 5000 ms
- ------J-Link related settings------
- J-Link Host interface: USB
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: EFM32GG380F1024
- Target interface: SWD
- Target interface speed: auto
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link V10 compiled Mar 29 2016 18:45:53
- Hardware: V10.10
- S/N: 600100399
- Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
- Checking target voltage...
- Target voltage: 3.10 V
- Listening on TCP/IP port 2331
- Connecting to target...Connected to target
- Waiting for GDB connection...
Is it possible to upload an older firmware to the J-Link in order to fix the problem?

Update:
I exchanged the J-Link pro (updated firmware) by an J-Link base from the stock with an old firmware installed.
and all worked in a sudden!
This is for me the evidence that the bug is within the J-Link pro (S/N 600100399) nonetheless if the EFM32 Studio fom Silicon Labs is
up to date with Segger or not.
My question ist still:
Can this be fixed by a firmware up/down-grade or is this device broken?
Regards.
The post was edited 1 time, last by martin55 ().