channel_sounding_ras_initiator sample not building on v3.0.1 or v3.0.2

Hi, 

I am currently trying to build the channel_sounding_ras_initiator sample without any changes. I was successfully able to build the channel_sounding_ras_reflector. 

I get a long list of prj.conf errors:

warning: BT_TRANSMIT_POWER_CONTROL (defined at subsys/bluetooth/Kconfig:170) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: (!HAS_BT_CTLR ||
BT_CTLR_LE_POWER_CONTROL_SUPPORT) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BT_TRANSMIT_POWER_CONTROL and/or look up
BT_TRANSMIT_POWER_CONTROL in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: BT_CHANNEL_SOUNDING (defined at subsys/bluetooth/Kconfig:191) was assigned the value 'y'
but got the value 'n'. Check these unsatisfied dependencies: (!HAS_BT_CTLR ||
BT_CTLR_CHANNEL_SOUNDING_SUPPORT) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BT_CHANNEL_SOUNDING and/or look up
BT_CHANNEL_SOUNDING in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: Deprecated symbol BT_CTLR is enabled.


/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:7: warning: attempt to assign the value 'y' to the undefined symbol NCS_SAMPLES_DEFAULTS

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:8: warning: attempt to assign the value 'y' to the undefined symbol DK_LIBRARY

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:11: warning: attempt to assign the value 'y' to the undefined symbol BT_NRF_SUPPORT

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:23: warning: attempt to assign the value 'y' to the undefined symbol BT_RAS

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:24: warning: attempt to assign the value 'y' to the undefined symbol BT_RAS_RREQ

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:27: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:28: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN_FILTER_ENABLE

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:29: warning: attempt to assign the value '1' to the undefined symbol BT_SCAN_UUID_CNT

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:41: warning: attempt to assign the value 'n' to the undefined symbol BT_RAS_MODE_3_SUPPORTED

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:42: warning: attempt to assign the value '1' to the undefined symbol BT_RAS_MAX_ANTENNA_PATHS

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:43: warning: attempt to assign the value '1' to the undefined symbol BT_CTLR_SDC_CS_MAX_ANTENNA_PATHS

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:44: warning: attempt to assign the value '1' to the undefined symbol BT_CTLR_SDC_CS_NUM_ANTENNAS

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:45: warning: attempt to assign the value 'n' to the undefined symbol BT_CTLR_SDC_CS_STEP_MODE3

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:48: warning: attempt to assign the value 'n' to the undefined symbol BT_CTLR_CHANNEL_SOUNDING_TEST

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:59: warning: attempt to assign the value 'y' to the undefined symbol BT_CS_DE

/Users/saubin/Desktop/agmuster-workspace/channel_sounding_ras_initiator/prj.conf:60: warning: attempt to assign the value 'y' to the undefined symbol BT_CS_DE_512_NFFT

error: Aborting due to Kconfig warnings

Im using:

nrf connect SDK v3.0.2 (also tried with v3.0.1)

Zephyr version: 4.1.99

nrf54l15dk/nrf54l15/cpuapp/ns

Is the channel_sounding_ras_initiator compatible with v3.0.2? I'm guessing there may be some SDK errors on my end but wanted to check the experimental channel sounding feature was compatible with the version i am running. 

Parents
  • Hi,

    To start off with the usual suspect: could you try either shortening the path length or try changing the name of the sample to something shorter, and see if that helps? The names of these channel sounding samples are so long that it is typically on the edge of the Windows path length limits, people typically have issues with this.

    Regards,

    Elfving

  • Thanks for the suggestion, Elfving. I've condensed the name and but unfortunately it was not the issue. 

    I managed to find i that the path to the zephyr file was wrong, which solved many of the problems. 

    I am left with this:

    /Users/saubin/Desktop/agmuster-workspace/c_init/prj.conf:49: warning: attempt to assign the value 'n' to the undefined symbol BT_CTLR_CHANNEL_SOUNDING_TEST
    
    warning: CMSIS_DSP (defined at modules/cmsis-dsp/Kconfig:7) has direct dependencies 0 with value n, but is currently being y-selected by the following symbols:
     - BT_CS_DE (defined at /Users/saubin/Desktop/agmuster-workspace/nrf/subsys/bluetooth/cs_de/Kconfig:7), with value y, direct dependencies BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y), and select condition BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y)
    
    warning: CMSIS_DSP_STATISTICS (defined at modules/cmsis-dsp/Kconfig:149) has direct dependencies CMSIS_DSP && 0 with value n, but is currently being y-selected by the following symbols:
     - BT_CS_DE (defined at /Users/saubin/Desktop/agmuster-workspace/nrf/subsys/bluetooth/cs_de/Kconfig:7), with value y, direct dependencies BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y), and select condition BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y)
    
    warning: CMSIS_DSP_TRANSFORM (defined at modules/cmsis-dsp/Kconfig:187) has direct dependencies CMSIS_DSP && 0 with value n, but is currently being y-selected by the following symbols:
     - BT_CS_DE (defined at /Users/saubin/Desktop/agmuster-workspace/nrf/subsys/bluetooth/cs_de/Kconfig:7), with value y, direct dependencies BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y), and select condition BT_CHANNEL_SOUNDING && BT_RAS && BT_RAS_RREQ && BT (value: y)
    Parsing /Users/saubin/Desktop/agmuster-workspace/zephyr/Kconfig
    Loaded configuration '/Users/saubin/Desktop/agmuster-workspace/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp_ns_defconfig'
    Merged configuration '/Users/saubin/Desktop/agmuster-workspace/c_init/prj.conf'
    Merged configuration '/Users/saubin/Desktop/agmuster-workspace/c_init/build/c_init/zephyr/.config.sysbuild'
    
    error: Aborting due to Kconfig warnings

    Interestingly, on the reflector sample, the unknown BT_CTLR_CHANNEL_SOUNDING_TEST issue was also there and commenting it out allowed for a successful build. (i can comment it out here too, just included it as it may be a clue for the issues below it)

    CMSIS_DSP is configured like this:

    menuconfig CMSIS_DSP
    bool "CMSIS-DSP Library Support"
    help
    This option enables the CMSIS-DSP library

    With no dependancies or selects.

    Adding CONFIG_CMSIS_DSP=y does not fix the problem either.
    Any suggestions here would be very helpful, thank you
  • So the default sample came with undefined symbols? That is odd. Are you using Windows?

    You are using the entire default sample from the SDK in question, as well as the matching toolchain, correct?

    Regards,

    Elfving

Reply Children
  • Hi Elfving, 

    Thanks for your help. I was attempting to run the samples in my own workspace, which may have had a mismatched toolchain. 

    Working in the 
    /opt/nordic/ncs directory, everything is working (on mac). 

    Ran into the following error when using our custom board at >1m distance - is this something which is common place with boards with poor signal strength?

     

     

Related