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


Can't flash STM32L476

Can’ JTAG a STM32L476 with a ST_LINK/v2.
I am using openOCD 0.10.0-dev course openOCD 0.9 don’t seam to have suport for STM32L4x

I get a Eclipse error pop-up and this printed in the openOCD log:
///////////////////////////////////////////////
Error: timed out while waiting for target halted
TARGET: stm32l4.cpu - Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer’
///////////////////////////////////////////////

I can flash the device with “STM32 ST-LINK Utility”

are there an bug in openOCD 0.10.0-dev?


Eclipse IDE for C/C++ Developers Version: Neon Milestone 4 (4.6.0M4) Build id: 20151218-1739
OpenSTM32 IDE 1.6.0.201512071631 fr.ac6.feature.mcu.ide.feature.group Ac6
OpenSTM32 Remote debugging support 1.6.0.201512071631 fr.ac6.feature.mcu.debug.feature.group Ac6
openOCD 0.10.0-dev-00287-g85cec24-dirty (2016-01-10-10:13)

Tunisia

Hello Håkan,

Which bard you are using ?

If you have created your own board, ensure that NRST is connected to your board, because openocd is using hardware reset (via NRST pin).

Regards,
Tarekb


Sorry for late reply!

NRST seem to be connected correctly and I guess that pin is used by the “STM32 ST-LINK Utility” too witch successfully can flash the MCU.
All hardware is in the exactly the same configuration only the software is different.

BR Håkan Olsson


Hello Håkan,

Have you managed to flash it before ? I already had the same error because of a debug session not stopped...
Just in case.

Good luck,

Romain


Tunisia

Hello Håkan, Romain,

Håkan,
>> NRST seem to be connected correctly
OK, to confirm that using ST-Link Utilty > Menu (Target > Settings) : select Mode = Connect Under Reset & Reset Mode = Hardware Reset
and check if that ST-Link Utility cann connect to your board.

>> and I guess that pin is used by the “STM32 ST-LINK Utility” too witch successfully can flash the MCU.
No, ST-Link Utility can connect to your device using different reset modes (selectable from Target > Settings):

Connection ModePossible Reset Modes
Connect Under ResetHardware Reset
Normal(Software System / Core / Hardware) Reset
HotplugNo Reset


Romain
>> I already had the same error because of a debug session not stopped...
When a debug session is not stopped a different message appears saying that openOCD cannot connect to MCU, but in this case there is a reset timeout.

Best Regards,
Tarek