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 two short videos (registration required) highlighting:

System Workbench for STM32


OpenOCD WrongDevice Detected - SensorTile

I have noted that SW4STM32’s debugger - or more accurately, the OpenOCD middleware it uses - has trouble recognizing any device connected to a USB3 host port. If I plug the same board into a USB2-only port on the same computer, it works correctly.

This problem was observed on several different PC’s all running Windows 7 64-bit.

The ST-provided “STM32 ST-Link Utility” application is able to see the STLink on a Nucleo board regardless of what type of USB host port it is attached to. The Atollic debugger also seems to recognize a board plugged into a USB3 port.

I think the problem might have to do with the version of libusb used to build OpenOCD. There have been some other applications I’ve seen that rely on libusb that fail to recognize or work with devices (that they would normally be able to attach to) if they are connected to USB3-capable host ports.

The first thing I’d do would be to get the STM32 ST-Link Utility (if on a Windows machine) and verify that you can connect to your Nucleo board using that. Also check that the two jumpers on the 4-pin header to the left of the ST-Link USB connector on the Nucleo board are both installed.

Hi Teddy,

Libusb has just been updated and should be ok with USB3 ports.
There was an error msg that has gone now (even if it didn’t stop debugging, it was annoying).

Rgds,
Laurent