This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Little compilation mistakes in new SDK 11

Hello,

Some little compilation errors.

in ble_radio_notification.h
typedef uint8_t nrf_radio_notification_distance_t; => is no more defined in SDK but used here

in ble_radio_notification.c
sd_nvic_xxx => NVIC_xxx and error codes are removed. 

in nrf_drv_spi, line 519
ASSERT(p_tx_buffer != NULL || tx_buffer_length == 0); 
ASSERT(p_rx_buffer != NULL || rx_buffer_length == 0);
=>
 ASSERT(p_xfer_desc->p_tx_buffer != NULL || p_xfer_desc->tx_length == 0);
 ASSERT(p_xfer_desc->p_rx_buffer != NULL || p_xfer_desc->rx_length == 0);
Parents
  • Thanks for reporting this Fabien, I will create a case for this. I will also find out why these modules were release without even been able to compile them.

    in ble_radio_notification.h add typedef uint8_t nrf_radio_notification_distance_t;

    in ble_radio_notification.c add #include "nrf_nvic.h" => because sd_nvic_xxx functions are moved and no longer SVC calls.

    The ASSERT is only valid when you define either DEBUG_NRF or DEBUG_NRF_USER (please check nrf_asser.h file) If you define it then I agree that your suggestion needs to applied.

    in nrf_drv_spi, line 519

    ASSERT(p_tx_buffer != NULL || tx_buffer_length == 0); 
    ASSERT(p_rx_buffer != NULL || rx_buffer_length == 0);
    =>
     ASSERT(p_xfer_desc->p_tx_buffer != NULL || p_xfer_desc->tx_length == 0);
     ASSERT(p_xfer_desc->p_rx_buffer != NULL || p_xfer_desc->rx_length == 0);
    
  • Any chance that the listed errors are resolved very soon? I find it very inconveniant to edit the SDK files, especially for open source projects that are used by other people.

Reply Children
No Data
Related