I have tried the adafruit-nrfutil.exe with no success as well. It generates “No data is received on the serial port.”
I have also downloaded the RAK Serial Port Tool and can open communication but nothing responds under the “at+version” or “at+get_config+device:status” commands.
This is from a Windows laptop with the Wisblock being powered by an external USB power supply and not by the DAPLINK device.
Any help will be greatly appreciated as I really don’t think this thing is broken so bad that it can’t be recovered.
BlockquoteC:\WisBlock>adafruit-nrfutil.exe --verbose dfu serial --package RAK4630_bootloader-0.4.1.zip --port COM4 -b 11520 --singlebank --touch 1200
Upgrading target on COM4 with DFU package C:\WisBlock\RAK4630_bootloader-0.4.1.zip. Flow control is disabled, Single bank, Touch 1200
Touched serial port COM4
Opened serial port COM4
Starting DFU upgrade of type 3, SoftDevice size: 151016, bootloader size: 39000, application size: 0
Sending DFU start packet
Timed out waiting for acknowledgement from device.
Failed to upgrade target. Error is: No data received on serial port. Not able to proceed.
Traceback (most recent call last):
File “main.py”, line 296, in serial
File “dfu\dfu.py”, line 226, in dfu_send_images
File “dfu\dfu.py”, line 199, in _dfu_send_image
File “dfu\dfu_transport_serial.py”, line 179, in send_start_dfu
File “dfu\dfu_transport_serial.py”, line 243, in send_packet
File “dfu\dfu_transport_serial.py”, line 282, in get_ack_nr
nordicsemi.exceptions.NordicSemiException: No data received on serial port. Not able to proceed.
Possible causes:
Selected Bootloader version does not match the one on Bluefruit device.
Please upgrade the Bootloader or select correct version in Tools->Bootloader.
Baud rate must be 115200, Flow control must be off.
Target is not in DFU mode. Ground DFU pin and RESET and release both to enter DFU mode.
Blockquote
PYOCD
C:\WisBlock>pyocd flash -t nrf52840 wiscore_rak4631_board_bootloader-0.4.3.hex
0002059 C No ACK received [main]
When you connect the DAPLink, make sure that the WisBlock is powered over USB or has a battery attached while you try to flash. The DAPLink is not able to supply the RAK4631.
The possible causes shown from the Adafruit flasher are a wild guess.
The error messages seems to be more related to the module not entering bootloader mode. Which would be normal if the bootloader is missing.
IMHO, firmware update over Bluetooth is not safe. If the update fails, the device is stuck without a working application. Usually the bootloader should still work, but I don’t know what the firmware ZIP file of Meshtastic includes. If it includes the bootloader, then the device needs to be flashed with a DAPlink or a JLink.
