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

Forum List Topic List

[ prev topic ]  

Multitude of HAL_RCC not resolved errors

Posted by dnbharrin on 2016-11-17 17:55

Trying to program a simple GPIO application on a Nucleo 64 STM32L476 board. During build I get 83 errors, all having to do with HAL_RCC commands that are “not resolved”. Please see attached view of Eclipse IDE.

Does anyone know why?

HAL_RCC Errors.JPG (204.93 Kb)
Reads: 7063
Link
Posted by Vetch on 2016-11-18 12:52

Hi, how did you import the project? Is it coming from CubeMX or from the HAL/FW package?
It seems the include paths are not set.
Import project from CubeMX
- Launch CubeMX >> New Project >> Board Selector tab >> Nucleo 64 STM32L476 board >> OK;
- Project menu >> Settings >> Toolchain / IDE = SW4STM32;
- Project menu >> Settings >> Project Location = C:\STM32_L4_Workspace (for example);
- Project menu >> Settings >> Project Name = L4_Blinky (for example);
- Enable the expected peripherals from the Pinout tab;
- Tune the clock frequencies from the Clock Configuration tab;
- Tune the peripheral configurations from the Configuration tab;
- Project menu >> Generate Code >> Close;
- Launch SW4STM32 and select the workspace (C:\STM32_L4_Workspace, for example);
- Right-click in the Project Explorer window >> Import >> General >> Existing Projects into Workspace >> Next >> Browse >> Select the project folder (L4_Blinky, for example) >> Finish

Import project from HAL/FW Package
- launch SW4STM32 and select the workspace (for example) :
...\STM32Cube_FW_L4_V1.5.0\Projects\STM32L476RG-Nucleo\Examples\GPIO\GPIO_IOToggle\SW4STM32\
- Right-click in the Project Explorer window >> Import >> General >> Existing Projects into Workspace >> Next >> Browse >> Select the project folder (for example ...\STM32Cube_FW_L4_V1.5.0\Projects\STM32L476RG-Nucleo\Examples\GPIO\GPIO_IOToggle\SW4STM32\STM32L476RG_NUCLEO folder) >> Finish
- Right-click on the STM32F4xx-Nucleo project >> Properties >> C/C++ General >> Indexer >> Enable project specific settings >> Remove the Index unused headers >> Apply >> OK
- Right-click on the STM32F4xx-Nucleo project >> Index >> Rebuild
- Right-click on the STM32F4xx-Nucleo project >> Build Project


SW4STM32 Tips & Tricks
- Right-click on the project >> Properties >> C/C++ Build >> Enable parallel build >> Apply >> OK
- Right-click on the project >> Properties >> C/C++ Build >> Settings >> MCU GCC Compiler >> Dialect >> Select the expected C standard (C99) >> Apply >> OK
- Right-click on the project >> Properties >> C/C++ General >> Indexer >> Enable project specific settings >> Remove the Index unused headers >> Apply >> OK
- Right-click on the project >> Index >> Rebuild
- Enable the notifications for the automatic updates in the Window menu :
Windows menu >> Preferences >> Install/Update >> Automatic Updates >> Enable automatically find new updates and notify me
- Configure the Network connection if you are using a proxy :
Windows menu >> General >> Network Connections
- Check fo updates : Help menu >> Check for Updates

Link
Posted by Vetch on 2016-11-18 13:08
- Check the stm32ZZxx_hal_conf.h file too, is HAL_RCC_MODULE_ENABLED defined?
Link

Posted by dnbharrin on 2016-11-18 18:43

Vetch,
Thanks for responding.

I followed your advice. The hal_conf.h file has HAL_RCC_MODULE_ENABLED defined.

I think I found the problem. The default in CubeMX Project >> Settings >> Project >> Toolchain / IDE was set to EWARM instead of STM32

I then ran build in STM32 and got no errors in the Problems window. This was run with Project Properties Build Type set to External Build. I do not know what External and Internal Build means. If I use Internal Build I get the Error 2 message in the Problems Window.

However, with no errors in Problems Window using External Build, it still will not run. I get this error message:

Error starting process.
Cannot run program “C:\STM32 Nucleo Projects\Test1_ST_20161117\SW4STM32\Test1_ST_20161117\Debug\Test1_ST_20161117.elf”: Launching failed
Cannot run program “C:\STM32 Nucleo Projects\Test1_ST_20161117\SW4STM32\Test1_ST_20161117\Debug\Test1_ST_20161117.elf”: Launching failed
Cannot run program “C:\STM32 Nucleo Projects\Test1_ST_20161117\SW4STM32\Test1_ST_20161117\Debug\Test1_ST_20161117.elf”: Launching failed

Is this just because I do not have any code in the users code sections? or is it something else?

Thanks again,

Dave

Link
Posted by dnbharrin on 2016-11-18 19:35

I included a simple toggle of one IO pin and I still get the same error when attempting to run the project. The program in Main.c is this:

while (1)
{
/* USER CODE END WHILE */
HAL_GPIO_TogglePin(GPIOC, GPIO_PIN_0);
/* Insert delay 100 ms */
HAL_Delay(200);
/* USER CODE BEGIN 3 */

}

no errors during complile

Link