"Target is not responding, retrying..." ST LoRaWAN AT_Master/End_Node programms not working on NUCLEO-L073RZ

MLiso.1 · ‎2022-01-08

I've read all topics regarding this error on the forum but nothing helped.

The borad connected to Arduino connector is USI® WM-SG-SM-42.

Projects build succesfully and connect with the board through ST-Link v3. This is the output I get when debugger and low power work is not enabled(set to 0):

STMicroelectronics ST-LINK GDB server. Version 6.0.0

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

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.9.0-RC01

-------------------------------------------------------------------

ST-LINK SN : 0667FF343339415043031750

ST-LINK FW : V2J39M27

Board : NUCLEO-L073RZ

Voltage : 3.26V

SWD freq : 950 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 : --

Memory Programming ...

Opening and parsing file: ST-LINK_GDB_server_a16776.srec

File : ST-LINK_GDB_server_a16776.srec

Size : 61876 Bytes

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 483]

Download in Progress:

File download complete

Time elapsed during download operation: 00:00:05.730

Verifying ...

Download verified successfully

Target is not responding, retrying...

Shutting down...

Exit.

When debugger is enabled console output is the same, without the "Target is not responding, retrying..." part. Program just falls into HAL_PWR_EnterSLEEPMode() or HAL_PWR_EnterSTOPMode() fuction depending on low_power mode configuration. It stays there forever, which isn't an expected behaviour.

Here is a debugg configuration:

I ve spend quite a lot of time trying to find the solution and I ve run out of ideas so i will be realy greatefull for help.

TThir.1 · ‎2023-03-16

Hello!

I'd really like to know if you managed to find a solution to this problem. I'm in the same predicament as you were (still are? I hope not.).

Kind regards,

Thines

McLovin · ‎2023-03-16

Hey there, I've seen this error before and only way I know is to enable the debug.

Try to find \Core\Inc\sys_conf.h header file and set the following definitions as such.

DEBUGGER_ENABLED 1
LOW_POWER_DISABLE 1

Have you tried this?