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

how to update HIC,LMP,Bluetooth controller

Hello,Vidar Berg

the Posts had closed,so i can't reply.

nRFConnect SDK Sample not working (periodic_adv _sync) - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

i test your 6201.periodic_sync.zip  5706.periodic_adv.zip ,it work well.

i copy your .config_periodic_sync's configs to ncs1.8.0 or ncs1.7.1/periodic_sync/prj.conf ,it Compilation failed with many errors.

i compare your log output, my HCI and LMP version is 5.2, Bluetooth controller (0x00) Version 223.20160.

but see your log output,your HCI and LMP version is 5.3, Bluetooth controller (0x00) Version 2.7.

how to update it?

and can you upload your periodic_sync full folder here?I want to learn it.

i install by Toolchain Manager v0.9.3

thank a lot

Parents
  • Hello,

    Sure, here are the projects I built with SDK 1.8.0:

    - 3426.periodic_sync.zip

    - 3021.periodic_adv.zip

    Note that the only modification I made was to add CONFIG_BT_LL_SW_SPLIT=y to the prj.conf files.

    I suggest you try to build them from the command line if you still get the same result with these (i.e. Softdevice controller gets selected instead of zephyr) as a way to narrow down the problem. Maybe Segger Embedded studio is pointing to the wrong SDK version?

    Building from the command line:

     1. Open the windows command line from the toolchain manager

    2. cd to the project you want to build

    3. Run west to build and flash the sample

    4. Open a UART terminal to view the log output.

Reply
  • Hello,

    Sure, here are the projects I built with SDK 1.8.0:

    - 3426.periodic_sync.zip

    - 3021.periodic_adv.zip

    Note that the only modification I made was to add CONFIG_BT_LL_SW_SPLIT=y to the prj.conf files.

    I suggest you try to build them from the command line if you still get the same result with these (i.e. Softdevice controller gets selected instead of zephyr) as a way to narrow down the problem. Maybe Segger Embedded studio is pointing to the wrong SDK version?

    Building from the command line:

     1. Open the windows command line from the toolchain manager

    2. cd to the project you want to build

    3. Run west to build and flash the sample

    4. Open a UART terminal to view the log output.

Children
Related