DFU cycle testing

[ms360]

Hi ! 

I have 5 different bootloaders for 5 pieces of hardware that I would like to cycle test OTA DFU with BLE. 
I have some questions

• Why does nrfutil dfu ble require a COM port? the DFU IOS app does not, seems strange, and also fails because I don't have a COM port connected. 
• What's the shortest path to script a BLE DFU from either
  • Mac M2
  • RPI 5
  • Windows 10 machine

The COM port thing is holding me up in mac/windows. 
The RPI5 lack of modern python support + non x86_64 is making this seemingly simple task in to a can of worms  

[ms360]

I see the COM port is for the BLE interface. How does that work? 

Is that HCI0 on the RPI? 
WHat's the mac and windows equivalent? 

[Menon]

Hello,

I am not sure if I fully understand your query. nrfutil does not require a COM port while performing BLE DFU. Please refer to the section Performing DFU.

The command:
nrfutil dfu ble -pkg app_dfu_package.zip -ic NRF52 -p COM3 -n "MyDevice" -f

In this command, the COM port mentioned is not for the DFU target. Instead, it refers to the COM port of the BLE adapter, while the DFU target is "MyDevice."

Which SDK version are you using? Are you working with the nRF5 SDK?

Kind regards,
Abhijith

[ms360]

Thanks Abhijith. 

I am using nRF5_SDK_17.1.0

Where are you able to see that COM3 is the BLE adapter? Did I miss some documentation?
I've been running python scripts with the bleak library, and not having to supply the adapter. 

[Menon]

Hello,

Sorry for the confusion, I was referring to the nRF Util command mentioned here.

Kind Regards,

Abhijith

[ms360]

As was I Abhijith! 

I am wondering how to use a built in BLE interface that I cannot see enumerated as a COM port. 
Is there a driver I need to install? 

You're using windows and it is on COM3, I don't see any BLE adapters as a COM port in windows, or a /dev/tty on mac or RPI linux.