While I’m able to see some “giberish” random ASCII characters on the serial console (eg. using Serial 2 on my Mac), I’ve been unable to flash any firmware to it at all.
Whenever I try to flash (from my M1 Mac, a Kali Linux VM or my Windows 10 x64 PC) I get this error message:
$ ./newtmgr.exe -c serial reset
Error: NMP timeout
I went through the tutorial several times, made sure all the drivers are installed. The device shows up on usb and in /dev and as I wrote above I can connect to it using a serial console, but newtmgr is unable to connect. I’ve also been unable to use nrfConnect (eg. the LTE Link Monitor) to connect to the device.
I’ve always tried holding down mode and pressing RST, and the device will flash the yellow and then blink the blue LED after that.
I’m starting to think that something is broken with the device, but maybe I’m doing something wrong?
Is “Pre-check: MCUBoot needs to be enabled in your project before you can use it! Make sure that you have CONFIG_BOOTLOADER_MCUBOOT=y in your prj.conf.” set?
Using Windows, ensure you are using ‘run as administrator’…and make sure you don’t skip the step where you build and then load the binary (build/zephyr/app_update.bin) before sending the reset https://learn.sparkfun.com/tutorials/nr … -debugging - any change?
Also try a different cable just to rule that out; also try a lower baud rate to rule that out too?
I’ve tried multiple different cables (and they all work fine with my selection of ESP32 and other devices).
Recently, I’ve mostly tried to just upload a pre-built blinky.bin or just see if I can get any connection (I assume newtmgr.exe -c serial reset should always work, but I’ve tried uploading builds as well for the first few hours, with the same issue)
I’m not even trying to build anymore (I did this originally, but newtmgr seems to be completely independent from that process, and it fails to upload any kind of binary or run any kind of command)
The CONFIG_BOOTLOADER_MCUBOOT would only be relevant if i’ve actually been able to upload anything at some point, right? newtmgr doesn’t seem to be related to this at all, and it’s failing.
The only other thing I can think to try is maybe try a linux-native machine…but ostensibly the board seems DoA; file for a replacement through exp-tech if nothing else changes :-/