Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » Newest OpenOCD fails with STM32L0
 
Thread actions
Print this page
  • Print all pages

    • Newest OpenOCD fails with STM32L0

    Posted by pmusz on 2020-04-27 21:39

    Hello,
    I've serious problem with simple, custom evalboard with onboard STM32L011. Here's my log:

    Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:33)
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    srst_only separate srst_nogate srst_open_drain connect_assert_srst
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 8000 kHz
    adapter_nsrst_delay: 100
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 4444 for telnet connections
    Info : clock speed 8000 kHz
    Info : STLINK v2.1 JTAG v36 API v2 M26 VID 0x0483 PID 0x374B
    Info : using stlink api v2
    Info : Target voltage: 3.257596
    Info : Unable to match requested speed 8000 kHz, using 4000 kHz
    Info : Stlink adapter speed set to 4000 kHz
    Info : STM32L011F4Px.cpu: hardware has 4 breakpoints, 2 watchpoints
    Info : Listening on port 3333 for gdb connections
    Info : accepting 'gdb' connection on tcp/3333
    target halted due to debug-request, current mode: Thread
    xPSR: 0xf1000000 pc: 0x1ff00288 msp: 0x200007a8
    STM32L0: Enabling HSI16
    Info : Unable to match requested speed 8000 kHz, using 4000 kHz
    Info : Stlink adapter speed set to 4000 kHz
    Info : Unable to match requested speed 8000 kHz, using 4000 kHz
    adapter speed: 4000 kHz
    Info : Device: STM32L0xx (Cat.1)
    Info : STM32L flash size is 16kb, base address is 0x8000000

    I've just reinstalled SW4STM32 to newest version (already 2.9) - of course it isn't hardware-related problem or incorrect wiring (this board was earlier used without doubt with STM32F0). I'm using built-in ST-link on Nucleo board, but standalone ST-link doesn't work too.

    I've read some topics about problems with OpenOCD and STM32L0 and L4 - but, what's interesting - brand new Nucelo for L432 works fine.

    Any ideas what's the cause of this problem?
    Thank you in advance!

    Regards,
    Przemek

    Reads: 9280
    Posted by tarek bouchkati on 2020-04-27 21:50 Tunisia

    Hi Przemyslaw ,

    the log you provided does not contain any error information. and you haven't described the unexpected behavior.
    Could you please give more accurate problem description ?

    The only hint that I can give you based on this log, is that your MCU is booting from system memory (bootloader) :

    target halted due to debug-request, current mode: Thread
    xPSR: 0xf1000000 pc: 0x1ff00288 msp: 0x200007a8

    So maybe you need to check the boot pins / option bytes.
    And if you have a flash programming issue, please provide a complete log with the error message.

    Note: the latest version of System Workbench is already one year old, so please consider using a new fresh IDE like STM32CubeIDE

    Kindly
    Tarek

         Posted by pmusz on 2020-04-27 22:12

    Hi Tarek,
    thank you for fast reply. After printing line:

    Info : STM32L flash size is 16kb, base address is 0x8000000

    there is a long delay (maybe 1 min?) and after that only two lines appear in console:

    Error: failed erasing sectors 0 to 0
    Error: flash_erase returned -5

    and "Terminate faliled" as well as:

    Error in final launch sequence
    Failed to execute MI command:
    load /media/DATA/ARMworkspace/temp_test/Debug/temp_test.elf

    Error message from debugger back end:
    Error erasing flash with vFlashErase packet
    Error erasing flash with vFlashErase packet

    alerts are open.

    I've checked BOOT0 pin - it's ok (0V).
    Also I've already installed newest CubeIDE - no change.

    Regards,
    Przemek