[SOLVED] Automatic mass erase on Linux upon connecting to secured device

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

  • [SOLVED] Automatic mass erase on Linux upon connecting to secured device

    Hi Segger team,

    I just want to add +1 vote to make mass erase/unlocking upon detection of a secured chip NOT automatic for all OS versions (especially Linux)!

    Under the assumption that jlink is a cautious and safe tool I bricked a device. Couldn't find a hint to the automatic unlocking in the J-Link User Guide.
    Please change this behaviour, as already discussed in this forum.

    In case I missed something, here's the log. Host is Linux, CLI 'jlink', no prompt or user interaction was possible after selection of device:

    SEGGER J-Link Commander V6.34c (Compiled Aug 23 2018 11:00:02)
    DLL version V6.34c, compiled Aug 23 2018 10:59:29

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V9 compiled Aug 23 2018 09:45:44
    Hardware version: V9.30
    License(s): FlashBP, GDB

    Please specify device / core. <Default>:
    Type '?' for selection dialog
    Device "M451RG6AE" selected.

    Connecting to target via SWD
    Write protected device detected. This could cause problems during flash download.
    Note: Unsecuring will trigger a mass erase of the internal flash.

    Device will be unsecured now.
    Found SW-DP with ID 0x2BA01477
    Scanning AP map to find all available APs
    AP[1]: Stopped AP scan as end of AP map has been reached
    AP[0]: AHB-AP (IDR: 0x24770011)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Core found
    AP[0]: AHB-AP ROM base: 0xE00FF000
    CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    Found Cortex-M4 r0p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ E00FF000
    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    Cortex-M4 identified.
  • Hello,

    Thank you for your inquiry.
    We are aware of this. This feature will be implemented in a future version.
    Our project books are quite full with paid project currently but we hope to make it available some time this year.

    Best regards,
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.