nRF52840 / Raytac MDBT50Q-CX dongle not responsive after flashing openthread

I have a Raytac MDBT50Q-CX and cannot seem to flash it correctly. The flash succeeds, but the device is no longer recognized by Windows or (raspberry pi) Linux. 

My goal is to set up an rpi5 as a Home Assistant OTBR and HA server using the MDBT50Q-CX. 

I was able to build openthread's coprocessor from github (openthread/openthread, under nrf/samples/openthread/coprocessor) per these instructions: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/thread/tools.html#configuring-a-radio-co-processor

However, after flashing the device via VS Code using:

nrfutil pkg generate --hw-version 52 --sd-req=0x00  --application nrf/samples/openthread/coprocessor/build/merged.hex --application-version 1 nrf/samples/openthread/coprocessor/build/zephyr/zephyr.zip

nrfutil dfu usb-serial -pkg nrf\samples\openthread\coprocessor\build\zephyr\zephyr.zip -p COM3

This flashed successfully and reset the device, but it is no longer found by Windows or Linux.

I also tried building openthread/ot-nrf528xx from the WSL Ubuntu cli, using:

[openthread] $ ./script/cmake-build posix

[ot-nrf528xx] $ ./script/build nrf52840 USB_trans -DOT_BOOTLOADER=USB

From there I flashed either ot-cli-ftd or ot-rcp to the device using nRF Connect with the same effect. The flash completed successfully, with the device being unrecognized afterward.

I also tried flashing some of the pre-build images in nrf_sdk_for_thread_and_zigbee_v4.2.0.zip (e.g., thread/cli/ftd/usb/hex/nrf52840_xxaa_mbr_pca10059.hex)

I assume I'm missing something obvious given how consistent the results are. What do I need to do to get the device to register with the OS?

Parents Reply Children
No Data
Related