[ABANDONED] JLink report unknown errors when tested with STM32L552E-EV and Ozone demo project

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

  • [ABANDONED] JLink report unknown errors when tested with STM32L552E-EV and Ozone demo project


    I’m learning embedded development with a J-Trace Pro and an STM32L552E-EV board. After downloading the trace demo project from the segger wiki, I try to debug it with Segger Embedded Studio and Ozone.

    Here is the board information.

    Here is the demo trace project wiki.

    The attach is how I connect J-Trace Pro with the board.

    However, when click the debug button, the panel shows the error information:

    Disabled output of control characters
    J-Link software found at:
    Target core support plugin loaded.: /opt/SEGGER/ozone/3.20.3/Plugins/Core/CorePluginARM.so
    Project.SetDevice ("STM32L552ZE");
    Project.SetHostIF ("USB", "");
    Project.SetTargetIF ("SWD");
    Project.SetTIFSpeed ("4000");
    Project.AddSvdFile ("$(InstallDir)/Config/CPU/Cortex-M33F.svd");
    File path resolved: "$(InstallDir)/Config/CPU/Cortex-M33F.svd" was found at "/opt/SEGGER/ozone/3.20.3/Config/CPU/Cortex-M33F.svd"
    File.Open ("/home/lwq/Downloads/ST_STM32L552_Trace_Example/Output/Debug/Exe/ST_STM32L552_Trace_Example.elf");
    File.Open: completed in 20 ms
    Debug.ReadIntoInstCache: updated instruction information within 2 code ranges (0x08000000-0x080002D2)
    Project.SetTraceSource ("Trace Pins");
    Device "STM32L552ZE" selected.
    Found SW-DP with ID 0x0BE12477
    DPIDR: 0x0BE12477
    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: 0x14770015)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Core found
    AP[0]: AHB-AP ROM base: 0xE00FE000
    CPUID register: 0x410FD212. Implementer code: 0x41 (ARM)
    Found Cortex-M33 r0p2, Little endian.
    FPUnit: 8 code (BP) slots and 0 literal slots
    Security extension: implemented
    Secure debug: enabled
    CoreSight components:
    ROMTbl[0] @ E00FE000
    ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
    ROMTbl[1] @ E00FF000
    ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
    ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
    ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
    ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
    ROMTbl[1][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
    ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CTI
    ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BBD21 Cortex-M33
    Connected to target device.
    Reset: Halt core after reset via DEMCR.VC_CORERESET.
    Reset: Reset device via AIRCR.SYSRESETREQ.
    Elf.GetBaseAddr(); // returns 0x8000000
    Target.ReadU32 (0x08000000); // returns 0x20030000
    Target.SetReg ("SP", 0x20030000);
    Elf.GetEntryPointPC(); // returns 0x800021E
    Target.SetReg ("PC", 0x800021E);
    Failed to erase sectors 0 @ address 0x08000000 (Unknown algo: Unspecified error #1)
    Failed to erase sectors.
    Download failed: J-Link reports an unspecified download error

    Could you please help to figure out the problem?

    • connect.jpg

      247.21 kB, 1,080×1,440, viewed 53 times
  • Hi,
    Thank you for your inquiry.
    We are sorry for the delay in response. We have been very busy with some pressing projects the last couple of weeks.
    Such an issue is not known to us and we are not able to reproduce it:

    - Ubuntu 20.04
    - Ozone V3.20e
    - J-Trace PRO Cortex-M V2

    Could you please try the following:
    - Open the J-Link Commander (JLinkExe)
    - Connect to the device
    - Send the command "erase" (without quotations).
    Does this work as expected?
    Could you please send us a J-Link Log file of both sessions, Ozone and J-Link Commander?

    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.