[SOLVED] Simplicity Studio - EFM32GG - Could not debug with this adapter

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

  • [SOLVED] Simplicity Studio - EFM32GG - Could not debug with this adapter

    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:

    Source Code

    1. Failed to connect to device
    2. TCF error report:
    3. Command: DebugAdapter connect "usb.600100399 (USB #0).adapter.mcu", {"exceptionsToCatch":0,"enableITM":false,"connectMethod":"normal","jLinkSpeed":"auto","deviceDescrip...
    4. Error text: Could not debug with this adapter. Ensure the kit and/or MCU are fully detected.
    5. Error code: 131073


    The J-Link does connect:

    Source Code

    1. SEGGER J-Link GDB Server V5.12e GUI Version
    3. JLinkARM.dll V5.12e (DLL compiled Apr 29 2016 15:03:58)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: localhost only
    11. Generate logfile: off
    12. Verify download: off
    13. Init regs on start: off
    14. Silent mode: off
    15. Single run mode: off
    16. Target connection timeout: 5000 ms
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: EFM32GG380F1024
    23. Target interface: SWD
    24. Target interface speed: auto
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: J-Link V10 compiled Mar 29 2016 18:45:53
    30. Hardware: V10.10
    31. S/N: 600100399
    32. Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    33. Checking target voltage...
    34. Target voltage: 3.10 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...Connected to target
    37. Waiting for GDB connection...
    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.

    The post was edited 1 time, last by martin55 ().

  • Hi,

    From the error message it does not sound like J-Link has a problem, but Simplicity Studio (not a SEGGER product!).
    It sounds a bit like it does not like the connected J-Link and does not even try to debug etc.
    With GDBServer you see that J-Link itself can connect to the target.

    If you want to try a firmware downgrade: J-Link User Guide -> Background information -> J-Link / J-Trace firmware -> Invalidating the firmware

    However, at this point I am not convinced yet that it is a problem on the J-Link side.
    We will give it a try though.
    What version of Simplicity Studio do you use?


    PS: The J-Link with S/N 600100399 is *not* a PRO but a PLUS.


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello Alex,

    Thank you for your response and your hint how to down grade.
    I downgraded to the same version of my coworkers Pro link: 8 of March.
    Unfortunately it does what you guess: didn't helped.

    What I don't understand:
    I have got also an 50101126 (base) which worked on the fly flawlessly, just by exchanging the hardware.
    The Simplicity Studio is the latest and up to date (v3).

    And yes, the Plus (the "flaulty" one) did connect to the target and the Segger Flasher utility can even flash the device.

    I had the same problem yesterday, and after several hours of clicking and updateing and... it worked out of a sudden.
    But today the same problem arise, which I discribed in my first mail.

    By the way: Is it normal, that there is something rattling inside the Link when one is shaking the device?

    Is it possible to run a diagnostic utility to test every possible function?


    Regards.



    Update:

    We just tested the device within my Co-Workers machine.
    The Result is almost the very same, despite that his Pro behaves now the same as with the plus.
    (Whereas on my installation the base still works).

    As if there was a virus transmitted...
    After all I did up to now, combining.... may be there is some think wrong in the windows registry
    upon the simplicy studio depends or is adjusted to.
    This isn't fixed by a reinstall of the Studio (also tried).
    But how can one find out?


    Regards.

    The post was edited 1 time, last by martin55 ().

  • Hi,

    And yes, the Plus (the "flaulty" one) did connect to the target and the Segger Flasher utility can even flash the device.

    O.K., so the J-Link seems to be working in general.

    Are you working under Windows?
    If yes: When starting a debug session, there should be a J-Link tray icon in the lower right corner.
    By clicking this icon, the J-Link Control panel is opened.
    In the settings tab you can set an override for the logfile, if no logfile is selected.
    Can you provide a logfile of a successful session (BASE unit) and of a non-successful one (PLUS unit)?

    By the way: Is it normal, that there is something rattling inside the Link when one is shaking the device?

    Nope, it is not.


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    Log output can be enabled like as follows:
    • Open a connection to J-Link, e.g start J-Link Commander
    • In J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)
    • Open the tab "Settings"
    • Next to the field "Log file" check "Override" and click "..." in order to choose a log file path.

    This is also described in UM8001 Chapter 5 "Working with J-Link and J-Trace", Section 5.7 "J-Link control panel" .

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • In case you do not have any control panel or IDE option for the logfile, you can also set the override via the registry:
    HKEY_CURRENT_USER\Software\SEGGER\J-Link\LogFile

    By the way, the BASE unit isn't working also now.

    Sounds more and more like a Simplicity Studio related problem...


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Alex,
    yes it seems so. This morning I setup a totaly new project. Almost everything was newly created. And surprise - a one time debug was possible.
    After that, nothing worked at all, as it was before.

    The one time success log:

    Source Code

    1. SEGGER J-Link V5.02l Log File
    2. DLL Compiled: Nov 24 2015 09:55:49
    3. Logging started @ 2016-05-06 09:42
    5. T2758 000:000 JLINK_IsOpen() returns 0x00 (0000ms, 0000ms total)
    6. T2758 000:000 JLINK_IsOpen() returns 0x00 (0000ms, 0000ms total)
    7. T2758 000:000 JLINK_EMU_SelectByUSBSN(SerialNo = 50101126) returns 0x00 (0000ms, 0000ms total)
    8. T2758 000:000 JLINK_SetWarnOutHandler(...) (0000ms, 0000ms total)
    9. ....
    10. ...
    11. T2758 2068:292 JLINK_IsHalted() returns FALSE (0000ms, 1348ms total)
    12. T2758 2068:292 JLINK_Halt() returns 0x00 (0004ms, 1352ms total)
    13. T2758 2068:331 JLINK_Close() -- CPU_ReadMem(4 bytes @ 0xE0001000) >0x42 TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> (0002ms, 1354ms total)
    14. T2758 2068:331 (0002ms, 1354ms total)
    15. T2758 2068:331 Closed (0002ms, 1354ms total)
    Display All


    After that:

    Source Code

    1. SEGGER J-Link V5.02l Log File
    2. DLL Compiled: Nov 24 2015 09:55:49
    3. Logging started @ 2016-05-06 11:53


    It looks like that Simplicity Studio doesn't even try to connect.

    I've created a topic at the silabs community and suggest to close this one.

    community.silabs.com/t5/32-bit…ug-has/m-p/168904#U168904


    Thank you very much for your effort so far.

    I'm at a point considering swiching to a different MCU with a different IDE.

    Many Regards.