Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

openOCD Wrong device detected

Posted by VanVince on 2018-05-14 15:57

Hello,

I’m tryng to run a simple program on my STM32 Discovery Kit Iot Node (STM32L475VGT6), just a blinking led. I use Eclipse IDE with System Workbench for STM32 into it. When I run the project OpenOCD shows me the following messages:

Open On-Chip Debugger 0.10.0-dev-00275-gd486ac2-dirty (2017-03-06-15:22)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
padded zone erase set to 1
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_assert_srst
adapter speed: 1800 kHz
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : clock speed 1800 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2 JTAG v28 API v2 M v18 VID 0x0483 PID 0x374B
Info : vid/pid are not identical: 0x0483/0x3748 0x0483/0x374B
Info : using stlink api v2
Info : Target voltage: 3.212042
Error: init mode failed (unable to connect to the target)
in procedure ‘program’
in procedure ‘init’ called at file “embedded:startup.tcl”, line 473
in procedure ‘ocd_bouncer’

    • OpenOCD init failed **

shutdown command invoked


Anybody know why? I suppose that the STLINK version is wrong but I am not capable of change it. Obviously other board work fine, with the correct version of STLINK.

Reads: 9050
Link
Posted by maxim221 on 2019-12-06 12:32
It’s because of some kind of problem at using SCK and DIO ports of MCU. After flashing a program it’s no longer can be used as SWD. I’ve erased chip with attaching a hardware button to reset state pin and gnd. Than I go to “right click on a project -> Target -> erase chip...” Finally just before erase start I’ve pressed hardware button and released it. It works. Chip erased and ready just for one more debug. After that it’s no longer able to use SWD. I’s not very comfortable to do so after every debug, But my chineese version of ST-Link v2 dongle doesn’t use reset pin. The voltage level on it stay’s the same at any kind of debuger settings such as “connect under reset”, software or hardware reset either. I’m looking for solution right now.
Link