[ABANDONED] JLINK Plus : detection and programming problem EFM32GG380F1024

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

  • [ABANDONED] JLINK Plus : detection and programming problem EFM32GG380F1024

    Hello,

    I have worked with Jlink Plus for a lot of months, with Jlink V6.14c and then with V6.16f on two different boards but with the same processor : EFM32GG380F1024 . I work with µVision5.22 and I also often use scripts.
    Last week, when I connected to JLink, a message box appeared asking for a Jlink firmware update, and I allowed it.

    Then when I tried to connect to the board, I encountered many problems : Secured EFR32 detected , erasing blocks while debugging when I reset processor, and also when I stop the debugger, target not detected, and many other problems also with scripts and with stable versions.

    I also tried to load a stable version with a script on the other board and the programming fails. I tried Jlink V6.18d, with a new firmware update but the result seems to be the same. And with Jlink V6.14c, I can't make an update with an older version of firmware.

    Attached the detection errors , and one of the result of a programming script with a stable version.

    Any idea to help me ?
    Images
    • Jlink.PNG

      13.71 kB, 1,014×162, viewed 388 times
    Files
    • JlinkErrort.txt

      (2.6 kB, downloaded 263 times, last: )
  • Hi,


    could you please provide us with a script file for reproduction purposes?
    I will then give it a try here.


    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.
  • Hi,

    could you please change the speed to 2000 in the script file, power cycle the J-Link, and try again?
    I could reproduce issues when trying to connect to a EFM32GG395F1024 device with to high speeds.


    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.
  • JLINK Plus : detection and programming problem EFM32GG380F1024

    I tried with Speed to 2000 and the result is the same, we think its an hardware problem, because this script has been used many times at the same speed (50000) :

    Script file read successfully.
    Processing script file...

    J-Link connection not established yet but required for command.
    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Sep 1 2017 17:45:26
    Hardware version: V10.10
    S/N: 600103471
    License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    VTref = 3.619V
    Selecting SWD as current target interface.

    Selecting 2000 kHz as target interface speed


    Target connection not established yet but required for command.
    Device "EFM32GG380F1024" selected.


    Connecting to target via SWD
    Found SW-DP with ID 0x2BA01477
    SWD speed too high. Reduced from 2000 kHz to 1350 kHz for stability
    Found SW-DP with ID 0x2BA01477
    SWD speed too high. Reduced from 1344 kHz to 907 kHz for stability
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    Scanning APs, stopping at first AHB-AP found.
    AP[0] IDR: 0x24770011 (AHB-AP)
    AHB-AP ROM: 0xE00FF000 (Base addr. of first ROM table)
    CPUID reg: 0x412FC231. Implementer code: 0x41 (ARM)
    Found Cortex-M3 r2p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ E00FF000
    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB000 SCS
    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    ROMTbl[0][4]: E0040000, CID: B105900D, PID: 003BB923 TPIU-Lite
    ROMTbl[0][5]: E0041000, CID: B105900D, PID: 003BB924 ETM-M3

    ****** Error: DAP error while reading DP-Ctrl-Stat register.
    Erasing device (EFM32GG380F1024)...

    ****** Error: Failed to download RAMCode.
    Failed to prepare for programming.
    Failed to download RAMCode!
    ERROR: Erase returned with error code -1.

    Downloading file [BootloaderNFC_BASE.bin]...

    ****** Error: Failed to prepare for programming.
    Could not preserve target memory.
    Unspecified error -1

    Downloading file [bootsecteur_force_sur_sect1.bin]...

    ****** Error: Failed to prepare for programming.
    Could not preserve target memory.
    Unspecified error -1

    Downloading file [CS110-0100K001114017_7Jan16-20000.bin]...

    ****** Error: Failed to prepare for programming.
    Could not preserve target memory.
    Unspecified error -1

    Reset delay: 0 ms
    Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
    Reset: Halt core after reset via DEMCR.VC_CORERESET.
    Reset: Reset device via AIRCR.SYSRESETREQ.

    Script processing completed.

    regards,
  • JLINK Plus : detection and programming problem EFM32GG380F1024

    Hello,
    I tried again at 1000 KHz speed and I had again secured EFR32 detection but the programming works. Here is the result:

    SEGGER J-Link Commander V6.16f (Compiled Jul 3 2017 15:58:03)
    DLL version V6.16f, compiled Jul 3 2017 15:57:26


    Script file read successfully.
    Processing script file...

    J-Link connection not established yet but required for command.
    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Sep 1 2017 17:45:26
    Hardware version: V10.10
    S/N: 600103471
    License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    VTref = 3.599V
    Selecting SWD as current target interface.

    Selecting 1000 kHz as target interface speed


    Target connection not established yet but required for command.
    Device "EFM32GG380F1024" selected.


    Connecting to target via SWD
    Device will be unsecured now.
    Found SW-DP with ID 0x2BA01477
    Scanning APs, stopping at first AHB-AP found.
    AP[0] IDR: 0x24770011 (AHB-AP)
    AHB-AP ROM: 0xE00FF000 (Base addr. of first ROM table)
    CPUID reg: 0x412FC231. Implementer code: 0x41 (ARM)
    Found Cortex-M3 r2p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ E00FF000
    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB000 SCS
    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    ROMTbl[0][4]: E0040000, CID: B105900D, PID: 003BB923 TPIU-Lite
    ROMTbl[0][5]: E0041000, CID: B105900D, PID: 003BB924 ETM-M3
    Cortex-M3 identified.
    Erasing device (EFM32GG380F1024)...
    J-Link: Flash download: Total time needed: 6.289s (Prepare: 0.031s, Compare: 0.000s, Erase: 6.255s, Program: 0.000s, Verify: 0.000s, Restore: 0.003s)
    Erasing done.

    Downloading file [BootloaderNFC_BASE.bin]...
    J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (77824 bytes)
    J-Link: Flash download: Total time needed: 0.607s (Prepare: 0.072s, Compare: 0.006s, Erase: 0.000s, Program: 0.484s, Verify: 0.003s, Restore: 0.041s)
    O.K.

    Downloading file [bootsecteur_force_sur_sect1.bin]...
    J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (4096 bytes)
    J-Link: Flash download: Total time needed: 0.075s (Prepare: 0.046s, Compare: 0.001s, Erase: 0.000s, Program: 0.006s, Verify: 0.000s, Restore: 0.020s)
    O.K.

    Downloading file [CS110-0100K001114017_7Jan16-20000.bin]...
    J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (45056 bytes)
    J-Link: Flash download: Total time needed: 0.408s (Prepare: 0.059s, Compare: 0.004s, Erase: 0.000s, Program: 0.313s, Verify: 0.001s, Restore: 0.029s)
    O.K.

    Reset delay: 0 ms
    Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
    Reset: Halt core after reset via DEMCR.VC_CORERESET.
    Reset: Reset device via AIRCR.SYSRESETREQ.
    Script processing completed.you
    So I think the firmware version doesn't work well because I encountered problems after V10 update. I can't work well with the Jlink Plus today. Could you give me the solution to return to previous version?
    Best regards,

    Ghislaine
  • Hi Ghislaine,


    Could you give me the solution to return to previous version?

    How to downdate the firmware is described in UM8001:



    Please let me know if this solves your issue.


    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.
  • JLINK Plus : detection and programming problem EFM32GG380F1024

    Hello NiKlas,

    I have tried to downdate the Jlink Plus firmware but I can't return to the first version because I have done two updates : one with the Jlink 6.16f and one with Jlink 6.18d.
    With version V6.14c, I just return to V10 27 march 2017, the first version with failures.

    So we bought one Jlink base (V10 compiled October 9 2015) and I refused updating it for the moment, because it actually works fine but at 1000kHz only. And I can set the debugger.
    I will try to update it later.

    Regards,

    Ghislaine