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


STM32F4DISC1 SPL problem

I am a user of STM32F4DISC1. I recently ran into a problem with SPL on this board trying to run a simple project on STM32F4DISC1 Standard Peripherial Library - pushing a USER BUTTON (PA0) turning GREEN LED on using EXTI.
When I compiled and ran this one, STM had crashed entering the interrupt and hanged LED in one state. It wasn’t a physical problem, because when I wrote code without EXTI just checking state of PA0 in while loop and turning LED on, it worked, so I assumed there is problem with library. I ensured myself because compiling the same code with EXTI in project created on STM32DISCOVERY SPL worked.
What’s more I ran into another problem: when I consulted my problem with a friend of mine who uses STM32F4DISC0 I heard that same code works on his development kit using its (DISC0) SPL library, so I tried to compile code from DISC1 using DISC0 SPL (I guess that DISC1 differs nothing in logical way from DISC0?) and I couldn’t download one on System Workbench in an automatic way. It just stopped after checking and downloading about 120 kB and after starting a project didn’t link a SPL with the project. Reinstalling an environment didn’t help.
Briefly:
Could you check SPL under STM32F4DISC1 because it faces problem with EXTI (I don’t know if it causes any more problems)?
Why my Workbench can’t download SPL library for DISC0?
PS. I use newest version of System Workbench for STM32.
Regards

Hi, What is the board you are using (STM32F407G-DISC1 or STM32F429I-DISC1)?
What is the version of the SPL and the SW4STM32?
I just downloaded a GPIO example project (from Cube FW F4 V1.13) into a STM32F429I-DISC1 and it works.


Hi Maciej Janc,
I used the STM32F4xx_DSP_StdPeriph_Lib_V1.7.1 and especially the EXTI_Example.
One file is missing in the original project (stm324x9i_eval.c)
but after adding it into the project, it compiles and run properly using EXTI.
Attached the updated project for SW4STM32 :
- uncompress the file into your workspace.
- Right-click in the Project Explorer window >> Import >> General >> Existing Projects into Workspace >> Next >> Browse >> Select project folder >> Finish


Hi,

Sorry for waiting, I’ll post in a moment


Hi

My board is STM32F429I-DISC1, although I’m not sure if distributor I bought my STM board from just labeled an STM32F429I-DISC0 with such name. But it differs nothing in physical way?

I just updated the System Workbench for STM32 with 1.11.0.201610101240.

When I create a project with STM32F4DISCOVERY it finds STM32F4-Discovery_FW_V1.1.0. Project works.
After creating project with STM32F4DISC1 (library STM32F4xx_DSP_StdPeriph_Lib_V1.7.1 found) there are 4 errors (arm-none-eabi-g++ not found in PATH, arm-none-eabi-gcc not found in PATH), but project compiles. After running it into a board there’s a problem described in topic (LED freezes).
Trying to create a project for STM32F4DISC0, environment doesn’t find and download SPL.

Thank you for checking these issues, I’ll try then. Moreover, I will try to test other concepts and checking if other things are missed elsewhere.

Thank you for reply


Hi,
I created a new C project :
Right-click in the project explorer window >> New >> C Project >> Project Type Ac6 >> Toolchains Ac6 >> Next >> Next >> Serie = STM32F4 >> Board = STM32F429I-DISCO >> Next >> Download target firmware .... (see snapshots)



Thank you for your time and help. To anyone interested, this problem ended after reinstallation of software. Moreover, the dealer I bought my evaluation board from, paste a sticker DISC1 on DISC0 dev board, so it’s a warning to always check the type of board.