Skip to main content
Associate
July 12, 2023
Question

Debogage

  • July 12, 2023
  • 5 replies
  • 2622 views

 

Hello,

I've developed a program using the I-CUBE LRWAN package, but I'm having a problem debugging it. Here is the configuration I used for debugging:

2.png1.png

The errors I'm encountering are as follows:

STMicroelectronics ST-LINK GDB server. Version 7.3.0
Copyright (c) 2023, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 3334
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled

Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.13.0
-------------------------------------------------------------------

 

Log output file: /tmp/STM32CubeProgrammer_QeW0K1.log
ST-LINK SN : 002800105553500C20393256
ST-LINK FW : V3J11M3B5S1
Board : STLINK-V3SET
Voltage : 5,02V
Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
2nd connect tentative with frequency (8MHz)
ST-LINK SN : 002800105553500C20393256
ST-LINK FW : V3J11M3B5S1
Board : STLINK-V3SET
Voltage : 5,03V
SWD freq : 8000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x447
Revision ID : Rev Z
Device name : STM32L07x/L08x/L010
Flash size : 192 KBytes
Device type : MCU
Device CPU : Cortex-M0+
BL Version : 0x41

 

Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_D2Mvn3.srec
File : ST-LINK_GDB_server_D2Mvn3.srec
Size : 80,23 KB
Address : 0x08000000


Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 641]
Download in Progress:


File download complete
Time elapsed during download operation: 00:00:07.085

 

Verifying ...

 


Download verified successfully


Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Target is not responding, retrying...
Shutting down...
Exit.

 

Do you have any ideas on how to solve this problem?

Thanks in advance for your help!

    This topic has been closed for replies.

    5 replies

    ST Technical Moderator
    July 12, 2023

    Hello @eljohrikm,

    Check powering jumpers. Try to connect Under reset mode.

    Hope this helps. 

    Imen

     
    In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
    eljohrikmAuthor
    Associate
    July 12, 2023

    Hello @Imen.D 

    STMicroelectronics ST-LINK GDB server. Version 7.3.0
    Copyright (c) 2023, STMicroelectronics. All rights reserved.

    Starting server with the following options:
    Persistent Mode : Disabled
    Logging Level : 1
    Listen Port Number : 3334
    Status Refresh Delay : 15s
    Verbose Mode : Disabled
    SWD Debug : Enabled
    InitWhile : Enabled

    Waiting for debugger connection...
    Debugger connected
    Waiting for debugger connection...
    Debugger connected
    Waiting for debugger connection...
    -------------------------------------------------------------------
    STM32CubeProgrammer v2.13.0
    -------------------------------------------------------------------

     

    Log output file: /tmp/STM32CubeProgrammer_KIfvGy.log
    ST-LINK SN : 002800105553500C20393256
    ST-LINK FW : V3J11M3B5S1
    Board : STLINK-V3SET
    Voltage : 5,04V
    Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
    2nd connect tentative with frequency (8MHz)
    ST-LINK SN : 002800105553500C20393256
    ST-LINK FW : V3J11M3B5S1
    Board : STLINK-V3SET
    Voltage : 5,04V
    SWD freq : 8000 KHz
    Connect mode: Under Reset
    Reset mode : Hardware reset
    Device ID : 0x447
    Revision ID : Rev Z
    Device name : STM32L07x/L08x/L010
    Flash size : 192 KBytes
    Device type : MCU
    Device CPU : Cortex-M0+
    BL Version : 0x41

     

    Memory Programming ...
    Opening and parsing file: ST-LINK_GDB_server_nIAQ6w.srec
    File : ST-LINK_GDB_server_nIAQ6w.srec
    Size : 80,23 KB
    Address : 0x08000000


    Erasing memory corresponding to segment 0:
    Erasing internal memory sectors [0 641]
    Download in Progress:


    File download complete
    Time elapsed during download operation: 00:00:07.085

     

    Verifying ...

     


    Download verified successfully


    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Target is not responding, retrying...
    Shutting down...
    Exit.

     

    eljohrikmAuthor
    Associate
    July 12, 2023

    I did that, but the same problem persists.

    ST Technical Moderator
    July 13, 2023

    Make sure to upgrade your ST-Link firmware and using latest release of tools.

     

    In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
    Tesla DeLorean
    Guru
    July 13, 2023

    Makes sure the code isn't purposefully disabling or reconfiguring the SWD pins.

    Disable the firmware from sleeping the MCU, and turning off power to the debug circuits.

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..