To the kind attention of Nordic support team,
Let's please consider this scenario:
PCA10040 with ble secured bootloader already installed
PCA10056 with usb bootloader installed.
I'd like to install connectivity firmware in PCA10056 using the interaction with a usb bootloader installed in PCA10056. Without using jlink and swd protocol.
After having updated firmware in PCA10040, I'd like to reprogram PCA10056, using the usb bootloader, with its original program.
Is it possible with your default connectivity firmware?
Has it been linked to work when a pre installed usb bootloader is present? Maybe we should rebuild the connectivity firmware using the source and compile it in order to be able to execute when a usb bootloader is present? After that we should also be able to exchange data containing the firmware that is meant to update PCA10040.
We don't want it to happen using jlink virtual com.
nrfutil is by default using a virtual com port to send data toward connectivity firmware. We should also change the connectivity firmware in order to exchange data using a USB channel.
May you please tell us how to proceed?
I saw https://github.com/NordicSemiconductor/pc-ble-driver#Compiling-connectivity-HEX-files
and connectivity examples in sdk.
Should we get examples/connectivity/ser_s140_usb_hci example? Compiling it in order to work when a usb bootloader is present?
Please, it is an important subject for us, because, shouldn't be the case and this is not possible with the standard connectivity firmware you provide, we should think to
implement a connectivity firmware ourself. Let me know if I'm clear in what is our need.
Thank you for all your kindness,
best regards
