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


OpenOCD WrongDevice Detected - SensorTile

Hello,
I am running into a vexing problem and am hoping someone can give me some clues. Current problem is on MacOS but the same happens on windows 10.

+ Latest version of Workbench. Eclipse: Version: Neon.3 Release (4.6.3) Build id: 20170314-1500

+ Sensor Tile is hooked up to external USB power (tried plugged in as well) and to a Nucleo F411RE + Nucleo is into Mac USB. 2 red lights come on. Board shows up in Finder (Node_F411RE) + Downloaded the STSW-STLKT01-DataLog sample. + Open in Workbench + Compile ok, no error.


Then whether I try to run or run the debugger I always get: OpenOCD WrongDevice Detected
Here is the error log
Open On-Chip Debugger 0.10.0-dev-00007-g58350bc-dirty (2018-01-08-12:15)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
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
adapter speed: 480 kHz
Info : tcl server disabled
Info : telnet server disabled
Info : clock speed 1800 kHz
Error: init mode failed (unable to connect to the target)
in procedure ‘init’
in procedure ‘ocd_bouncer’

And then:
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333

Error message from debugger back end:
localhost:3333: Operation timed out.
localhost:3333: Operation timed out.

+ I’ve tried setting up different board in the setup (both for the sensortile and the F411RE but the message stays exactly the same)

+ By the way, I used to get the “Device already in use message”, that went away when I changed the USB cord.


Help will be much, much appreciated as I’ve been trying to apply the different fixes suggested for similar issues without any luck

Gregory

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


Hi, gmenvielle
Did u solve this problem?
I am having a similar issue using the board STEVAL-STLCS02V1.
I can program the STEVAL-STLCS01V1 using its examples but it always appears OpenOCD WrongDevice Detected when i tried to use the STEVAL-STLCS02V1.

Hi ilton104,

If I’m reading your problem correctly you had success programming the STEVAL-STLCS01V1 (plug or solder) using the plug in mode on the expansion cradle. But when using the STEVAL-STLCS02V1 (solder only) attached to the small cradle you get the “wrong device” error.

If that’s the case, then I’m running into a similar issue. Were you ever able to solve it?

Basically, I bought the development kit, which included the one sensortile that could be plugged into the expansion board, or soldered to the small cradle. I ran through all of the example projects using the sensortile plugged into the expansion cradle with no issue. I then purchased a separate sensortile (STEVAL-STLCS02V1) that I soldered to the cradle, and that’s the one giving me the “wrong device detected” error.

I need the mobility of the small cradle for a project I’m working on. Anyone have any idea what the issue may be here? Bad attachment of the sensortile to the board (looks good from what I can tell)?