Hello. I am having an issue when uploading my firmware to the RAK4631. This happens with both Arduino and the arduino-cli
arduino-cli upload -p /dev/ttyACM0 --fqbn rak_rui:nrf52:WisCoreRAK4631Board ../watermark_reader/
2023-03-10 14:35:24,877 Using board at serial port: /dev/ttyACM0
2023-03-10 14:35:24,879 Sending Application image.
2023-03-10 14:35:28,448 LIBUSB_ERROR_ACCESS: Unable to connect to trigger interface.
2023-03-10 14:35:28,449 Serial: Waiting 500 ms for device to enter bootloader 1/10 time
2023-03-10 14:35:28,976 Serial: Waiting 500 ms for device to enter bootloader 2/10 time
2023-03-10 14:35:29,515 Serial: Waiting 500 ms for device to enter bootloader 3/10 time
2023-03-10 14:35:30,034 Serial: Waiting 500 ms for device to enter bootloader 4/10 time
2023-03-10 14:35:30,570 Serial: Waiting 500 ms for device to enter bootloader 5/10 time
2023-03-10 14:35:31,109 Serial: Waiting 500 ms for device to enter bootloader 6/10 time
2023-03-10 14:35:31,646 Serial: Waiting 500 ms for device to enter bootloader 7/10 time
2023-03-10 14:35:32,172 Serial: Waiting 500 ms for device to enter bootloader 8/10 time
2023-03-10 14:35:32,709 Serial: Waiting 500 ms for device to enter bootloader 9/10 time
2023-03-10 14:35:33,253 Serial: Waiting 500 ms for device to enter bootloader 10/10 time
2023-03-10 14:35:33,789 Serial: Device is either not in bootloader mode, or using an unsupported bootloader.
2023-03-10 14:35:34,792 Serial: No ping response
2023-03-10 14:35:35,794 Serial: No ping response
2023-03-10 14:35:36,796 Serial: No ping response
2023-03-10 14:35:37,798 Serial: No ping response
2023-03-10 14:35:38,801 Serial: No ping response
I Thought maybe it was a Linux issue so I tried on windows and got a similar error.
I checked the bootloader and it also looks correct:
UF2 Bootloader 0.4.2 lib/nrfx (v2.0.0) lib/tinyusb (0.10.1-293-gaf8e5a90) lib/uf2 (remotes/origin/configupdate-9-gadbb8c7)
Model: WisBlock RAK4631 Board
Board-ID: WisBlock-RAK4631-Board
Date: Dec 1 2021
SoftDevice: S140 6.1.1
Finally, I tried uploading firmware on windows, but had a similar error with triggering:
[------------------------------------] 0%2023-03-10 15:45:13,740 No trigger interface found for device with serial number: 24D743BAC5216B58, Product ID: 0x8029 and Vendor ID: 0x239A
I also tried jumping TX1 to ground to manually trigger DFU mode but no luck.
I’m a bit stumped at the moment, has anyone else had this problem?