Error while flashing the ble_app_uart exemple into the nRF52840 dongle

[flogui]

Hello,

My goal is to send a binary file by Bluetooth into the nRF52940 board from the terminal. I saw the ble_app_uart example. It seems to be exactly what I want to do but i have some issues. I changed the define in the precompilation in order to have the dongle included and not the PCA10056

I'm curently trying to connect the dongle (PCA10059) with the board (PCA10056) but in the nRFConnect Programmer I have the following error : 

Reopen device failed: Timeout while waiting for device F513C4296DB9 to be attached and enumerated

Nordic DFU Trigger Interface was not found.Please physically reset device.

Device not found due to failure during DFU

I am using the softdevice "s140_nrf52_6.1.1_softdevice.hex".

Thank you in advance for your answer.

Florian

[Einar Thorsrud]

Hi,

This error does not indicate that there was an error during programming. You get this error message because the ble_app_uart example does not include the DFU trigger library. Therefore it is not recognized by nRF Connect programmer, but programming was still successful. You can avoid this message by including the DFU trigger library in your app if you like, or you can simply ignore it. The only practical consequence of not having the DFU trigger library is that you get this error and you have to push the sideways push-button to make the dongle start the bootloader in DFU mode. See nRF52840 Dongle Programming Tutorial for more details.

[flogui]

Hi ,

Ok i understand but my dongle still don't work. I am using the dongle as a central device and the board as a peripheral device.

I want to send a binary file that will be received by the nRF52840 to do a firmware update of an other chip by uart.

So in resume i want :  PC <-ble-> nrf52840(board)<-UART-> other chip.

Do you have any idea from where the error come from ?

And if you don't, is there a better way to do what I want to achieve ?

[Einar Thorsrud]

Hi,

The ble_app_uart is intended to be run on the DK, where the onboard debugger acts as a USB-UART bridge. This is not present on the dongle. The ble_app_uart example does not support CDC UART, so you will not see any UART traffic on your computer unless you connect a USB-UART bridge to the UART pins on the dongle (you can map UART pins to easily accessible GPIO's).

[flogui]

OK that's what I am going to do. But first, the dongle is not recognised at all by the PC (No virtual Com Port), it does not connect to the DK, and there is no led on as it is on the DK.

[flogui]

Thanks to your reply I finaly succeed in what I wanted to do but there is a little thing i wanted to talk. When I send a file to the board over ble all the file is not received. What could be the problem ?

Com19 is the DK and only 878 characters are received

[Einar Thorsrud]

Hi,

I cannot say without more information. You should debug on both sides to see what is actually happening. Is the UART data received on the dongle? If yes, why is it not transmitted to the peer (DK)? Are any error checks being hit? In this case, you have a disadvantage since the nRF52840 Dongle does not have a debugger, so it is difficult to know what is going on. Perhaps you can test with another DK if you have it, or alternate which board is which so that you can debug in both ends (even though not at the same time)?