Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

[ prev topic | next topic ]  

ST-Link issue

Posted by fahadmirza on 2017-06-21 18:42

I have a custom board with STM32L051 on it. I am using an example from ST (I-Cube_lrwan). For some reason, once I load the firmware I cannot access the MCU anymore using ST-Link Utility and ST-Link/V2. It always throw “Cannot connect to target”. But if I press the reset button before I press “Connect” (in ST-Link Utility) and release the button right after I press “Connect” , ST-Link/V2 can find my MCU.

But... when I use ST-Link/V2-1 from a Nucleo Board, it works perfectly. To me, its like ST-Link/V2-1 can reset the MCU properly where ST-Link/V2 cannot for some reason.


Can anyone suggest me what should I do if I want to use ST-Link/V2, in my case?

Reads: 10930
Link
Posted by IdeoG on 2017-06-22 03:04

Hi,
Have you tried to run “under reset” mode?
Check your SYS config in your project. Might be you did’t set SWD pins or redefined it.
Regards,
Alex.

Link

Posted by fahadmirza on 2017-06-22 20:53

Hello @Alex,

I am using ‘Connect under reset’ option.

Also the HW goes to low power mode (STOP mode) and change the SWDIO and SWCLK pins to analog. I did get the warning on ST-Link Utility (‘Connection to device is lost’) right after I flash FW. For a long period of time I thought this was the problem and that’s why I was using the external RESET button to flash my MCU.

But... the ST-Link from Nucleo can access my MCU, with low-power and changed pin configuration. That’s why I was wondering what are the differences between these two ST-Links.

Link