New custom board for nRF5340 in existing project

I have a firmware project currently developed in a Nordic nRF52840 chip. I am trying to create a new board ( we are updating the PCB ) to implement the same firmware on a Nordic nRF5340. 

I am using SDK 2.7.0 and whenever I try to create a new board for the chip and compile I'm getting the following error: 

warning: UART_INTERRUPT_DRIVEN (defined at boards/shields/sparkfun_sara_r4/Kconfig.defconfig:24, boards/shields/wnc_m14a2a/Kconfig.defconfig:17, drivers/serial/Kconfig:72) has direct dependencies (NETWORKING && SHIELD_SPARKFUN_SARA_R4) || (NETWORKING && SHIELD_WNC_M14A2A) || (SERIAL_SUPPORT_INTERRUPT && SERIAL) with value n, but is currently being y-selected by the following symbols:
- BT_UART (defined at drivers/bluetooth/hci/Kconfig:8), with value y, direct dependencies BT_HCI && BT_DRIVERS (value: y), and select condition BT_HCI && BT_DRIVERS (value: y)

error: Aborting due to Kconfig warnings


Is there a specific way to this other than using the built in "Create a new board" form? 

My intention is to implement the app in the Application CORE and use the NETWORK core for bluetooth. 

Parents
  • Hi Pablo

    Have you checked out the nRF5340 multi-image builds guide in our documentation? It should help you see how to set two images and set one of them as the child image of the other. Normally the Application Core image is the parent image.

    Note that on NCS 2.7.0, we have started replacing the multi-image buildig for Zephyr's Sysbuild, but either should be fine to use until it's fully implemented. I'd still go for the procedure described in the current documentation for now.

    Best regards,

    Simon

Reply
  • Hi Pablo

    Have you checked out the nRF5340 multi-image builds guide in our documentation? It should help you see how to set two images and set one of them as the child image of the other. Normally the Application Core image is the parent image.

    Note that on NCS 2.7.0, we have started replacing the multi-image buildig for Zephyr's Sysbuild, but either should be fine to use until it's fully implemented. I'd still go for the procedure described in the current documentation for now.

    Best regards,

    Simon

Children
No Data
Related