E104-BT5040u USB Stick does not enter DFU mode after initial flashing about ot-nrf528xx HOT 4 CLOSED

I guess I should have used the option

-DOT_BOOTLOADER=UART

Instead. The firmware now has

DOT_BOOTLOADER=USB

Enabled. The mystery is, that i can't even see the device with nrf connect in the windows SDK and it's programmer. The Driver is installed, it installed right automatically when i plugged it in for the first time. Before flashing with nrfutil on a different platform.

Now for dummies:

-DOT_BOOTLOADER=UART

Would have worked wouldn't it? And i could probably have used nrfutil over and over again?

from ot-nrf528xx.

This is what happens when i try to use the NRF Programmer.The Windows Device Manager shows COM6 and the Open Thread Device with an exclamation mark. I would switch to -DOT_BOOTLOADER=UART and use nrfutil from now on. But i'm stuck with NRF in windows not communicating with the stick properly? I swear the fimware on the stick is built with script/build nrf52840 USB_trans -DOT_BOOTLOADER=USB -DOT_THREAD_VERSION=1.2

Any recommendations to get it working with NRF Programmer? Am i missing a driver? I'm running windows 10 and it was initlally stated that a driver had been installed for my device. But i think it was the driver for the serial mode of the initial DFU firmware that came with the stick.

from ot-nrf528xx.

I believe that the bootloader on my E104-BT5040u was overridden because i follwed the outdated guide from nordic and generated a package using this command:

$ nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
    --application build/bin/ot-rcp.hex \
    --application-version 1 build/bin/ot-rcp.zip

this command does not include the option "--bootloader" and does not include any bootloader code. This looks suspicious to me. I guess the firmware was flashed to my stick without the neccesary offset 0x1000 and thereby destroyed the DFU mode on my stick, which could have been fine if t included the bootloader, but it didn't. This is just my estimation. After all, this is not arduino and you need to know what you are doing.

I will consider the following steps:

• buy a new E104-BT5040u
• onboard the stick with the nRFConnect utility (to be sure to have the latest and official Bootloder)
• flash the Firmware using nRFConnect checking for the 0x1000 offset and never use nrfutil again
• somehow have a better understanding of nrfutil, packages, bootloaders, offsets, etc.

In the project readme is this note:
For new projects, you should use nRF Connect SDK. nRF5 SDK for Thread and Zigbee is a legacy solution and only provided in maintenance mode.
Question: Am I supposed to build this project, but with the nRF-Connet-SDK? Or am i supposed to use their coprocessor?

I am considering to flash the official RCP Firmware example from nordic. or Zephyr.

Question: Will openthread be compatible with a stick that contains the RCP Firmware example or the coprocessor from Zephyr? It's also menbetter suited because of crypto-Acceleration support and bells and whistles. But how about compatibility as RCP for the latest release of openthread? I think it's not really clear which way to go. Is the RCP approach still a work-in-progress? Is the RCP approach in this project different to the RCP Approach from nordics example?

from ot-nrf528xx.

I would suggest reaching out via Nordic DevZone.

from ot-nrf528xx.