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

Porting from SDK 1.5.1 to 1.6.1

I'm moving from SDK 1.5.1 to 1.6.1 and when I recreate the project using the new version I get;

C:/Users/randall.philipson/kodiak_core_iot_zephyr/core_iot/prj.conf:88: warning: attempt to assign the value 'y' to the undefined symbol SPI_3

My proj.conf has;

# SPI
CONFIG_SPI=y
CONFIG_SPI_3=y
#CONFIG_SPI_3_NRF_SPIM=y
#CONFIG_SPI_3=y
#CONFIG_SPI_NRFX=y

I'm using a custom board description.  The common .dts file has;

&spi3 {
compatible = "nordic,nrf-spim";
status = "okay";
sck-pin = <19>;
mosi-pin = <18>;
miso-pin = <17>;
cs-gpios = <&gpio0 30 GPIO_ACTIVE_LOW>, <&gpio0 23 GPIO_ACTIVE_LOW>,
<&gpio0 22 GPIO_ACTIVE_LOW>, <&gpio0 21 GPIO_ACTIVE_LOW>,
<&gpio0 20 GPIO_ACTIVE_LOW>, <&gpio0 0 GPIO_ACTIVE_LOW>;

};

Just to be sure, I recreated using 1.5.1 and it generates fine.

Parents
  • Hi 

    In later versions of the nRF Connect SDK there is no longer a need to specify which peripheral instance you want to use in the project configuration, instead this is handled through the dts configuration only. 

    If you simply remove the CONFIG_SPI_3=y line then the example should build. 

    Best regards
    Torbjørn

Reply
  • Hi 

    In later versions of the nRF Connect SDK there is no longer a need to specify which peripheral instance you want to use in the project configuration, instead this is handled through the dts configuration only. 

    If you simply remove the CONFIG_SPI_3=y line then the example should build. 

    Best regards
    Torbjørn

Children
No Data
Related