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


java.lang.NullPointerException when trying to Debug

Hi, i’ve succesfully got my discovery Board to work with CubeMX and System Workbench.

Now I wanted to get my custom Board with an 32F405RG on it to work.
Configured it in CubeMX and Generated the Code.

Imported the Project into System Workbench, compiled and try to debug it.

First Error was Could not find Binaries. After a project Refresh Binaries showed up, so no Problem with that.

But when I try to launch a Debug Session: Debug As -> AC6 ....
A Window Pops up and closes with no further information.

When I try to set a custom Debug Configuration, with Double Click on the AC6... Template, it shows me a java.lang.NullPointerException Error.

So I can’t create a Debug Coniguration.

This worked with the DiscoveryBoard without a Problem (besides the Binaries could not be found)

Any Help would be great

It would be nice to know if the 32F405RG talks to the ST-Link app.

Hi, yes, i am using an st-linkv2.

With the link utility i can read out and flash/erase the mcu, no problem at all.


The target definition file may not be correctly formed. This is the xml file file in the same directory as your .project file.

In this file check that the value of board id element is in quotes as such as < board id =”custom”>

Found from this user post
http://www.openstm32.org/tiki-view_forum_thread.php?comments_parentId=875Question

This is an issue in the stm32cube mx v4.9.0 and 4.10.0 and apparently has been reported to ST.