[.pio/build/bluepill_f103c8/zephyr/firmware-pre.elf] Error 1

mrn1041378mrn2 · August 9, 2021, 6:29am

HI guys
I ran into this error while im trying to use HAL drivers in my main code i also included <stm32f1xx.h> in my main.c file .
i dont know what to do to solve this error can anyone help me?
/home/mohammad/.platformio/packages/toolchain-gccarmnoneeabi/bin/…/lib/gcc/arm-none-eabi/8.2.1/…/…/…/…/arm-none-eabi/bin/ld.bfd: .pio/build/bluepill_f103c8/src/main.o: in function main': /home/mohammad/Documents/PlatformIO/Projects/secondP/src/main.c:50: undefined reference to HAL_GPIO_WritePin’
collect2: error: ld returned 1 exit status
*** [.pio/build/bluepill_f103c8/zephyr/firmware-pre.elf] Error 1
please help thanks you.

maxgerhardt · August 9, 2021, 1:21pm

Good question. I’m landing at the same error when trying to use the function.

The config values https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_USE_STM32_HAL_GPIO.html and https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_HAS_STM32CUBE.html#std-kconfig-CONFIG_HAS_STM32CUBE select the STM32 HAL (and GPIO HAL), but these are not “user-assignable” in the prj.confg, rather Zephyr handles them internally. I’ll open an issue about this.

maxgerhardt · August 9, 2021, 1:33pm

Tracked in Using STM32Cube HAL function results in linker error · Issue #37543 · zephyrproject-rtos/zephyr · GitHub.

mrn1041378mrn2 · August 10, 2021, 8:27am

Hi thanks you
Im trying to run that on ubuntu and im keep getting this error i dont know whats the matter with code.
if any solution you got , please aware me tnx.

jbiams77 · August 29, 2021, 12:31am

I’m also running into the same problem. Here is what I’ve found out so far. I’m building for a bluepill so the project is the board is setup as bluepill_f103c8. It gives me this error:

collect2.exe: error: ld returned 1 exit status
*** [.pio\build\bluepill_f103c8\zephyr\firmware-pre.elf] Error 1

When I build a project for the MCU only, STM32F103C8, than it builds fine. For this, the board would be set to genericSTM32F103C8.

I will continue to investigate but I’m quite positive its something within the hardware build directory.

maxgerhardt · August 29, 2021, 12:38am

I was able to solve the issue as someone pointed to the right documentation in the linked issue.

github.com/zephyrproject-rtos/zephyr

Using STM32Cube HAL function results in linker error

opened 01:33PM - 09 Aug 21 UTC

closed 12:37AM - 29 Aug 21 UTC

maxgerhardt

bug Waiting for response priority: low platform: STM32

**Describe the bug** I am using PlatformIO to create a Zephyr project for the S…TM32 Bluepill (STM32F103C8, maps to the [`stm32_min_dev`](https://github.com/zephyrproject-rtos/zephyr/tree/zephyr-v2.6.0/boards/arm/stm32_min_dev) (blue) variant). The base project is https://github.com/platformio/platform-ststm32/tree/develop/examples/zephyr-blink. In the firmware I'm trying to use the STM32HAL GPIO functions (such as `HAL_GPIO_Init()`) instead of Zephyr's facilities. So I expand the original code to `#include <stm32f1xx_hal.h>` and call these functions. However, building the firmware then fails at the linking stage (`undefined reference to `HAL_GPIO_TogglePin'`). **To Reproduce** Steps to reproduce the behavior: 1. Have PlatformIO installed (e.g. [in the CLI](https://docs.platformio.org/en/latest/core/installation.html)) 1. Duplicate the [original project](https://github.com/platformio/platform-ststm32/tree/develop/examples/zephyr-blink) 2. Replace `src\main.c` with the code found below 3. Attempt compilation with `pio run` 4. See error `src\main.c` ```c #include <zephyr.h> #include <device.h> #include <devicetree.h> #include <drivers/gpio.h> #include <stm32f1xx_hal.h> /* 1000 msec = 1 sec */ #define SLEEP_TIME_MS 1000 /* The devicetree node identifier for the "led0" alias. */ #define LED0_NODE DT_ALIAS(led0) #if DT_NODE_HAS_STATUS(LED0_NODE, okay) #define LED0 DT_GPIO_LABEL(LED0_NODE, gpios) #define PIN DT_GPIO_PIN(LED0_NODE, gpios) #define FLAGS DT_GPIO_FLAGS(LED0_NODE, gpios) #else /* A build error here means your board isn't set up to blink an LED. */ #error "Unsupported board: led0 devicetree alias is not defined" #define LED0 "" #define PIN 0 #define FLAGS 0 #endif void main(void) { const struct device *dev; bool led_is_on = true; int ret; dev = device_get_binding(LED0); if (dev == NULL) { return; } ret = gpio_pin_configure(dev, PIN, GPIO_OUTPUT_ACTIVE | FLAGS); if (ret < 0) { return; } __GPIOC_CLK_ENABLE(); GPIO_InitTypeDef GPIO_InitStruct; GPIO_InitStruct.Pin = GPIO_PIN_13; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Speed = GPIO_SPEED_HIGH; HAL_GPIO_Init(GPIOC, &GPIO_InitStruct); while (1) { gpio_pin_set(dev, PIN, (int)led_is_on); led_is_on = !led_is_on; HAL_GPIO_TogglePin(GPIOC, GPIO_PIN_13); k_msleep(SLEEP_TIME_MS); } } ``` **Expected behavior** STM32HAL functions are available and compiled in. **Impact** Compilation failure, showstopper. **Logs and console output** ``` c:/users/max/.platformio/packages/toolchain-gccarmnoneeabi@1.80201.190214/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: .pio\build\bluepill_f103c8\src\main.o: in function `main': C:\Users\Max\temp\zephyr_bluepill/src/main.c:46: undefined reference to `HAL_GPIO_Init' c:/users/max/.platformio/packages/toolchain-gccarmnoneeabi@1.80201.190214/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: C:\Users\Max\temp\zephyr_bluepill/src/main.c:51: undefined reference to `HAL_GPIO_TogglePin' collect2.exe: error: ld returned 1 exit status *** [.pio\build\bluepill_f103c8\zephyr\firmware-pre.elf] Error 1 ``` **Environment (please complete the following information):** - OS: Windows - Toolchain: arm-none-eabi-gcc and friends (8.2.1) - Commit SHA or Version used: 2.6.0 (stable release) **Additional context** When I clean the project I interestingly see some STM32Cube files being compiled, just not `stm32f1xx_hal_gpio.c`.. ``` Removed .pio\build\bluepill_f103c8\_pio__modules__hal__stm32__stm32cube\modules\stm32\stm32cube\stm32f1xx\drivers\src\stm32f1xx_hal.c.o Removed .pio\build\bluepill_f103c8\_pio__modules__hal__stm32__stm32cube\modules\stm32\stm32cube\stm32f1xx\drivers\src\stm32f1xx_hal_rcc.c.o Removed .pio\build\bluepill_f103c8\_pio__modules__hal__stm32__stm32cube\modules\stm32\stm32cube\stm32f1xx\drivers\src\stm32f1xx_hal_rcc_ex.c.o Removed .pio\build\bluepill_f103c8\_pio__modules__hal__stm32__stm32cube\modules\stm32\stm32cube\stm32f1xx\drivers\src\stm32f1xx_ll_utils.c.o Removed .pio\build\bluepill_f103c8\_pio__modules__hal__stm32__stm32cube\modules\stm32\stm32cube\stm32f1xx\soc\system_stm32f1xx.c.o ``` Attempting to set [`CONFIG_USE_STM32_HAL_GPIO=y`](https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_USE_STM32_HAL_GPIO.html) in the `zephyr\prj.conf` results in a ``` error: USE_STM32_HAL_GPIO (defined at modules/Kconfig.stm32:189) is assigned in a configuration file, but is not directly user-configurable (has no prompt). ``` error. Adding it in the [board defconfig file](https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-v2.6.0/boards/arm/stm32_min_dev/stm32_min_dev_blue_defconfig) results in the same message. Used packages and ST-STM32 platform version: ``` PLATFORM: ST STM32 (14.1.0) > BluePill F103C8 HARDWARE: STM32F103C8T6 72MHz, 20KB RAM, 64KB Flash DEBUG: Current (stlink) External (blackmagic, cmsis-dap, jlink, stlink) PACKAGES: - framework-zephyr 2.20600.210721 (2.6.0) - tool-cmake 3.16.4 - tool-dtc 1.4.7 - tool-ninja 1.9.0 - toolchain-gccarmnoneeabi 1.80201.190214 (8.2.1) ``` PlatformIO is of the latest dev version (`version 5.2.0b1`).

jbiams77 · August 29, 2021, 1:51am

I’m struggling to find how to set the Kconfig up, I’v reduced my entire code to this:

#include <zephyr.h>
#include <stm32f1xx.h>
#include <stm32f1xx_hal.h>

UART_HandleTypeDef huart3;

int main(void)
{
    HAL_Init();
    return 0;
}

And the output shows the error being caused during linking:

c:/users/brandon/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: .pio\build\bluepill_f103c8\modules\stm32\stm32cube\lib_pio__modules__hal__stm32__stm32cube.a(stm32f1xx_hal.c.o): in function `HAL_InitTick':
C:\Users\Brandon\.platformio\packages\framework-zephyr\_pio\modules\hal\stm32\stm32cube\stm32f1xx\drivers\src/stm32f1xx_hal.c:237: undefined reference to `HAL_SYSTICK_Config'
c:/users/brandon/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: C:\Users\Brandon\.platformio\packages\framework-zephyr\_pio\modules\hal\stm32\stm32cube\stm32f1xx\drivers\src/stm32f1xx_hal.c:245: undefined reference to `HAL_NVIC_SetPriority'
c:/users/brandon/.platformio/packages/toolchain-gccarmnoneeabi/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: .pio\build\bluepill_f103c8\modules\stm32\stm32cube\lib_pio__modules__hal__stm32__stm32cube.a(stm32f1xx_hal.c.o): in function `HAL_Init':
C:\Users\Brandon\.platformio\packages\framework-zephyr\_pio\modules\hal\stm32\stm32cube\stm32f1xx\drivers\src/stm32f1xx_hal.c:157: undefined reference to `HAL_NVIC_SetPriorityGrouping'
collect2.exe: error: ld returned 1 exit status
*** [.pio\build\bluepill_f103c8\zephyr\firmware-pre.elf] Error 1

From the issue you linked, it looks like I can’t use HAL drivers from CubeMX unless I create a Kconfig file. I’m not sure how to set that up. Do you have a project with this as an example you could point me too?

maxgerhardt · August 29, 2021, 11:43am

I don’t think you need to be calling HAL_Init() at all, Zephyr should already take care of base initialization. If you still wish to call it, you need to take care that all sub-dependenceis of the functions are found. The missing HAL_NVIC_SetPriority function is implemented in

github.com

zephyrproject-rtos/hal_stm32/blob/d49fb6dbe780b931eee33cce8656e87c46070fa8/stm32cube/stm32f1xx/drivers/src/stm32f1xx_hal_cortex.c#L165-L167


      
          void HAL_NVIC_SetPriority(IRQn_Type IRQn, uint32_t PreemptPriority, uint32_t SubPriority)
          {
            uint32_t prioritygroup = 0x00U;

Which gets activated by

github.com

zephyrproject-rtos/hal_stm32/blob/ac47229a9809a6d2250c14ff593e1b29625620be/stm32cube/stm32f1xx/CMakeLists.txt#L14-L14


      
          zephyr_library_sources_ifdef(CONFIG_USE_STM32_HAL_CORTEX drivers/src/stm32f1xx_hal_cortex.c)

As a project I used zephyr-blink and created the zephyr/Kconfig file as described in the issue. The values which activate certain HAL subsystems can be looked up in the CMakeLists.txt.

Note that calling STM32HAL functions directly instead of using the Zephyr APIs is very anti-pattern, as they themselves note.

jbiams77 · August 30, 2021, 12:59am

HI, thanks for the help. You’re right, for me to use the HAL library would be avoiding the existing API calls that Zephyr already provides. The problem I’m running into is that I already have a large amount of HAL experience and switching to Zephyr at this point would require better resources and a steap learning curve. For now, I think I will switch back to FreeRTOS/HAL library but am looking forward to Zephyr growing and the community support improving. At first glance, there is a lot I like about it. I am following you on GitHub and will keep an eye on your contributions.