Is USB ACM serial DFU possible with ncs v2.6.1?

[khett-ptd]

I am building a BLE audio product that is based on the nRF5340. The application is largely based on the nrf5340_audio ncs example application, but I am modifying the the application so it can be re-configured at run-time instead of using the KConfig #defines.

I started the development of this application using ncs v1.9.x and with each ncs release I have been merging the changes to the ncs nrf5340_audio example into my application so I can keep up with bug fixes and general improvements in the build system.

For this product I have disabled DFU over Bluetooth and enabled DFU over USB serial (ACM com port).  I used to be able to enable the DFU mode by providing the "-m internal" flag to the python buildprog.py script, but in ncs v2.6.1 it looks like that is no longer an option because the new system has switched to using the softdevice Bluetooth controller.

To work around this, I added "CONFIG_AUDIO_DFU=1" to my proj.conf file.  When I compile the system with this option enabled I now get the build error shown in the attached .zip file.  For some reason if I insert the console output into this support ticket, the system will not allow me to post the message.

At first I thought this was because I have added code to my application and it would no longer fit into flash, but after looking into this some more, I now think that the image that does not fit in flash is the "new" softdevice BT controller.  Is this correct?

Is there a way to use the new softdevice controller and enable USB serial DFU in ncs v2.6.1?

Best Regards,
Kristopher

ConsoleOutputErrorMessage.zip

[khett-ptd]

Hi Andreas,

Apologies for my slow response.  I have been able to get the system to fit into the on-chip flash with mcuboot by disabling some of the Bluetooth controller features listed in the child_image/hci_image/*.conf files.  

Now that the code compiles and links, it does not boot correctly, but that is a different issue than the question posed in this support ticket.  I think we should consider this issue closed and I will submit a new issue about debugging the mcuboot process.

Thanks for your help,
-- Kristopher

[AHaug]

Hi,

khett-ptd said:

Apologies for my slow response.

No worries

khett-ptd said:

have been able to get the system to fit into the on-chip flash with mcuboot by disabling some of the Bluetooth controller features listed in the child_image/hci_image/*.conf files.  

Glad to hear that!

khett-ptd said:

Now that the code compiles and links, it does not boot correctly, but that is a different issue than the question posed in this support ticket.  I think we should consider this issue closed and I will submit a new issue about debugging the mcuboot process.

Noted, I'll mark this case as closed for now, but you can always reopen it if you have any additional questions related to what we've discussed in this ticket already.

Kind regards,
Andreas