google
Easier DFU for MDK
In #408, we add documentation for the MDK. This should be easier, and the deploy script generally allows DFU for other boards than the dongle. Let's check if we break its bootloader before we fix and recommend that, though (see #268).
well , i've following the readme to flash the hex build from develop branch , via nordic dfu programmer , but it break bootloader as well
./deploy.py --board=nrf52840_dongle_dfu --opensk --programmer=nordicdfu and flash by nRF connect for Desktop now pressing reset button failed to enter the bootloader
Did you try pressing reset while plugging the dongle? I think pressing reset while the dongle is powered is something that must be supported by the application, and I don't think this is the case here.
Note that there's also an alternative way to have OpenSK on the nRF52840 dongle or Makerdiary dongle by running on top of Wasefire rather than Tock. See https://github.com/google/wasefire/blob/main/examples/rust/opensk/README.md#board-dongle for instructions.
You'll need to run ./scripts/setup.sh the first time you clone the repository.
Did you try pressing reset while plugging the dongle? I think pressing reset while the dongle is powered is something that must be supported by the application, and I don't think this is the case here.
well, it doesn't works, i can see the hex start address is 0x1000 , which should not break the mbr for open dfu bootloader on the ebyte dongle. Does this firmeware still erasing uicr ?
my dongle is E104-BT5040U Ebyte nRF52840 ble 4.2 ble 5.0 2.4GHz ... , a copy of pca10059
I will use jlink to recovery the bootloader and try it again