Sysprogs forums › Forums › VisualGDB › Mbed BSP for v5.1
Tagged: mbed
- This topic has 8 replies, 2 voices, and was last updated 8 years, 1 month ago by support.
-
AuthorPosts
-
August 19, 2016 at 20:48 #8893imanhpParticipant
Hi,
When do you think that it would be possible to update to the latest mbed BSP?
https://developer.mbed.org/blog/entry/Introducing-mbed-OS-5/
https://docs.mbed.com/docs/mbed-os-release-notes/en/latest/5_1/release/
Br
ImanAugust 21, 2016 at 04:39 #8895supportKeymasterHi,
We are planning to update our mbed package after we release VisualGDB 5.2 Beta 1. The current plan is to do this by the end of September.
October 11, 2016 at 20:47 #9263imanhpParticipantAny progress with this?
October 12, 2016 at 05:09 #9265supportKeymasterHi,
Yes, sorry for the delay. We have encountered a few small issues with it and are currently fixing those. The current estimate is 1-2 weeks more.
November 1, 2016 at 21:16 #9400imanhpParticipantHi,
5.2 is is here – https://www.mbed.com/en/platform/mbed-os/releases/
Any progress yet?
November 3, 2016 at 02:11 #9408supportKeymasterHi,
Yes, we’ve encountered some troubles with mbed 5.2.1 requiring bootloader on some targets and a few minor build issues. We will be publishing a beta version of the mbed 5.2.1 BSP in a few days. It won’t work out-of-the-box on 100% targets, but will be usable otherwise.
November 16, 2016 at 21:27 #9519imanhpParticipantI get hundreds of warnings:
“MBED_CONF_NORDIC_UART_HWFC” redefined STM D:\CODE\MBED\STM\<command-line> 1
Any clue of where the fault might be?
November 16, 2016 at 21:33 #9520imanhpParticipantHi again,
Its in the mbed.props file:
<PreprocessorDefinitions>TOOLCHAIN_GCC_ARM;TOOLCHAIN_GCC;MBED_CONF_EVENTS_PRESENT=1;__MBED__=1;TARGET_UVISOR_UNSUPPORTED;MBED_CONF_PLATFORM_DEFAULT_SERIAL_BAUD_RATE=9600;MBED_CONF_PLATFORM_STDIO_CONVERT_NEWLINES=0;TOOLCHAIN_object;TARGET_LIKE_MBED;TARGET_RELEASE;MBED_CONF_PLATFORM_STDIO_FLUSH_AT_EXIT=1;TARGET_RTOS_M4_M7;TARGET_DISCO_F746NG;ARM_MATH_CM7;DEVICE_INTERRUPTIN=1;TARGET_STM32F746;FEATURE_LWIP=1;MBED_BUILD_TIMESTAMP=1478563085.15;DEVICE_LOWPOWERTIMER=1;DEVICE_PORTINOUT=1;TARGET_STM32F7;TRANSACTION_QUEUE_SIZE_SPI=2;DEVICE_I2CSLAVE=1;DEVICE_RTC=1;DEVICE_PWMOUT=1;DEVICE_STDIO_MESSAGES=1;DEVICE_ANALOGIN=1;TARGET_FF_ARDUINO;TARGET_LIKE_CORTEX_M7;__MBED_CMSIS_RTOS_CM;__CMSIS_RTOS;DEVICE_SPI_ASYNCH=1;DEVICE_PORTIN=1;__FPU_PRESENT=1;TARGET_M7;DEVICE_SERIAL_ASYNCH=1;DEVICE_ANALOGOUT=1;DEVICE_I2C=1;DEVICE_PORTOUT=1;MBED_CONF_PLATFORM_STDIO_BAUD_RATE=9600;TARGET_STM;DEVICE_SERIAL=1;DEVICE_SPI=1;TARGET_STM32F746NG;TARGET_CORTEX_M;__CORTEX_M7;DEVICE_TRNG=1;DEVICE_SLEEP=1;DEVICE_CAN=1;DEVICE_SPISLAVE=1;MBED_CONF_RTOS_PRESENT=1;MBED_CONF_NORDIC_UART_HWFC=0;MBED_CONF_NORDIC_UART_HWFC=1;MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC=NRF_LF_SRC_XTAL;MBED_CONF_NORDIC_UART_HWFC=0;MBED_CONF_NORDIC_UART_HWFC=1;MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC=NRF_LF_SRC_XTAL;MBED_CONF_NORDIC_UART_HWFC=0;MBED_CONF_NORDIC_UART_HWFC=1;MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC=NRF_LF_SRC_XTAL;MBED_CONF_LWIP_IPV6_ENABLED=0;MBED_CONF_NSAPI_PRESENT=1;MBED_CONF_LWIP_ADDR_TIMEOUT=5;MBED_CONF_LWIP_IPV4_ENABLED=1;CFSTORE_STORAGE_DISABLE=0;UNITY_INCLUDE_CONFIG_H;MBED_CONF_LWIP_IP_VER_PREF=4;MBED_CONF_LWIP_IPV6_ENABLED=0;MBED_CONF_LWIP_ADDR_TIMEOUT=5;MBED_CONF_LWIP_IPV4_ENABLED=1;MBED_CONF_LWIP_IP_VER_PREF=4;%(ClCompile.PreprocessorDefinitions)</PreprocessorDefinitions>
MBED_CONF_NORDIC_UART_HWFC is defined multiple times. In bold above.
The generation of the PreprocessorDefinitions seems to be buggy. I see several other duplicate definitions.
November 17, 2016 at 19:16 #9531supportKeymasterHi,
Thank for reporting this. We are aware of it and will resolve it in the final release of the BSP. Currently is should be safe to ignore this.
-
AuthorPosts
- You must be logged in to reply to this topic.