2 years ago.
the NUCLEO-L452RE is presented as mbed-enabled (http://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-l452re.html) but still unavailable on mbed board list. When it will be added?
Thanks in advance!
1 year, 9 months ago.
This board is not planned to be added on mbed for the moment by the ST team.
Here some instructions to add it:
We'll review the pull-request.
1 year, 5 months ago.
Dear Support Team,
I've just bought STM32L452RE-P Nucleo Board, and I'm having the same problem.
Do you found the right solution to use mbed with this board ?
I already tried to create the target on my own, and I'm having a lot of trouble (Errors).
Is it possible that you include this board on mbed ??
Errors Encountered: mbed compile -m NUCLEO_L452RE_P Building project mbed-os-example-blinky (NUCLEO_L452RE_P, GCC_ARM) Scan: . Scan: mbed Scan: env Compile [ 0.3%]: AnalogIn.cpp [Error] mbed_rtx.h@105,2: #error "INITIAL_SP is not defined for this target in the mbed_rtx.h file" [Error] stm32l4xx_hal_dfsdm.h@144,3: 'DFSDM_Channel_TypeDef' does not name a type [Error] stm32l4xx_hal_dfsdm.h@216,3: 'DFSDM_Filter_TypeDef' does not name a type [ERROR] In file included from ./mbed-os/rtos/TARGET_CORTEX/mbed_rtx_conf.h:25:0, from ./mbed-os/rtos/TARGET_CORTEX/rtx5/RTX/Config/RTX_Config.h:31, from ./mbed-os/rtos/TARGET_CORTEX/rtx5/RTX/Include/rtx_evr.h:31, from ./mbed-os/rtos/TARGET_CORTEX/rtx5/RTX/Source/rtx_lib.h:38, from ./mbed-os/rtos/TARGET_CORTEX/mbed_rtos_storage.h:43, from ./mbed-os/rtos/Mutex.h:28, from ./mbed-os/platform/PlatformMutex.h:29, from ./mbed-os/drivers/AnalogIn.h:25, from ./mbed-os/drivers/AnalogIn.cpp:17: ./mbed-os/targets/TARGET_STM/mbed_rtx.h:105:2: error: #error "INITIAL_SP is not defined for this target in the mbed_rtx.h file"
- error "INITIAL_SP is not defined for this target in the mbed_rtx.h file" ^~~~ In file included from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/device/stm32l4xx_hal_conf.h:227:0, from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/device/stm32l4xx_hal.h:48, from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/TARGET_STM32L452xE/device/stm32l4xx.h:221, from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/TARGET_STM32L452xE/device/cmsis.h:35, from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/TARGET_STM32L452xE/objects.h:33, from ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/device.h:38, from ./mbed-os/platform/platform.h:29, from ./mbed-os/drivers/AnalogIn.h:19, from ./mbed-os/drivers/AnalogIn.cpp:17: ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/device/stm32l4xx_hal_dfsdm.h:144:3: error: 'DFSDM_Channel_TypeDef' does not name a type DFSDM_Channel_TypeDef *Instance; /*!< DFSDM channel instance */ ^~~~~~~~~~~~~~~~~~~~ ./mbed-os/targets/TARGET_STM/TARGET_STM32L4/device/stm32l4xx_hal_dfsdm.h:216:3: error: 'DFSDM_Filter_TypeDef' does not name a type DFSDM_Filter_TypeDef *Instance; /*!< DFSDM filter instance */ ^~~~~~~~~~~~~~~~~~~
[mbed] ERROR: "/usr/bin/python" returned error code 1.
Thank you in advance.
Best regards, Rodrigo Iga.
To post an answer, please log in.