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 ]  

STM32L476 Discovery board not able to flash through system workbench

Posted by Jagdish Thummar on 2019-08-04 06:06

I am facing below issue while flashing STM32L476 through openSTM32 workbench
Error Log :

09:28:55 **** Programming project L4_LEDBlink on chip ****
“C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.externaltools.openocd.win32_1.23.0.201904120827\tools\openocd\bin\openocd.exe” -f stm32.flash.54460803324782151.cfg -s “E:\Embedded Data\STM32L476 Discovery Projects\STM32WB workspace\L4_LEDBlink” -s “C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_2.5.0.201904120827\resources\openocd\st_scripts” -c “program Debug/L4_LEDBlink.elf verify ” -c shutdown
Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)
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
padded zone erase set to 1
adapter speed: 8000 kHz
adapter_nsrst_delay: 100
Info : clock speed 8000 kHz
Info : STLINK v2.1 JTAG v34 API v2 SWIM v25 VID 0x0483 PID 0x3752
Info : using stlink api v2
Info : Target voltage: 3.231012
Error: init mode failed (unable to connect to the target)
in procedure ‘program’
in procedure ‘init’ called at file “embedded:startup.tcl”, line 495
in procedure ‘ocd_bouncer’

    • OpenOCD init failed **

shutdown command invoked


09:28:56 Build Finished (took 469ms)

Reads: 3429
Link
Posted by glenl on 2019-08-09 20:15

“unable to connect to the target”

This can be due to many problems. Lack of driver or board not plugged in or another program has control of the USB device. Does it show up in the device manager?

Link