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 - Debugging

Questions about debugging with System Workbench for STM32
Print
List FAQs

Questions

  1. Why are peripheral registers values not displayed ?
  2. Why are "No source file named ..." warnings displayed the debug console ?
  3. Why debug does not launch when my device is connected to USB 3.0 port ?
  4. Why can't I connect to the board, with error "Error in final launch sequence / Failed to execute MI command: / -target-select remote localhost:3333"

Answers

Question: Why are peripheral registers values not displayed ?
Answer 

Peripherals registers cannot be displayed permanently because it would generate too much traffic on the debug link. Also, reading certain registers may have side effects (for UART reception registers for instance, the value may be lost after a read).
To see the values of a peripheral register, the register group it belongs to must be opened and the register must be selected by clicking on it.

Question: Why are "No source file named ..." warnings displayed the debug console ?
Answer 

The undue warning message is refering to sources from another project, it won’t affect the debugging process. The IDE indexer is checking all the open projects and some functions name might be the same between project.

If you want the message not to be displayed, close the unrelated projects.

Question: Why debug does not launch when my device is connected to USB 3.0 port ?
Answer 

Some USB 3.0 Controllers (such as NEC/Renesas) has bug that prevents access to USB devices. Make sure to upgrade to the latest version of the controller driver to fix this issue.

For further information, please visit : https://github.com/libusb/libusb/wiki/Windows#usb-30-supportQuestion

Question: Why can't I connect to the board, with error "Error in final launch sequence / Failed to execute MI command: / -target-select remote localhost:3333"
Answer 

If you get this error, first check your USB cable; some cables, like those delivered with some USB chargers, will only transfer power, but not data.
Open the Windows device manager; if your cable is correct you shoud see your board appear as a STLink dongle (under Universal Serial Bus devices).
Depending on the board (Nucleo boards as well as recent disco or eval boards) you will also see a Mbed Microcontroller device appear under Disk Drives
If you don’t see any of these, try another cable, as this may be the problem.