I am getting very frustrated from this board.... I tried to upgrade the Nina firmware of my board, but it refuses to to it in any way.
My OS is Windows 10 PRO 21H1
My first attempt was via IOT cloud.
The Arduino create agent keeps on shutting down. I have disabled all security features of my PC
Sometimes the Update proces starts, but then times out after some minutes in the first action "Checking Firmware".
Windows then gives an error on the USB device, and I need to reboot my system to be able to use the Nano board again. Tried this like a 100 times....
I resetted the board several times by forcing the bootloader ( jumper on GND and REC) then copied the file blink.ino.elf.uf2 to the RP-2 directory after removing the jumper. the boards then starts the blink sketch.
then I downloaded arduino fwuploader and followed the instructions . I unzipped it to C:\firmware-uploader, then I connected my board and checked the COM port, which was COM5 in my case.
I opened the command prompt and navigated to the directory C:\firmware-uploader and typed following instruction:
arduino-fwuploader firmware flash -b arduino:mbed_nano:nanorp2040connect -a COM5 -m NINA@1.4.8
the response was: Error getting firmware for board: arduino:mbed_nano:nanorp2040connect
Thanks khoih-prog, that did the trick. 2021-09-22 20_29_34-Window|477x500
I experience many USB connection failures, I can only upload a sketch once, and after a change the upload fails and windows gives an error on the USB device (the Nano2040). Only after a reboot I can upload a sketch again....!
Re. USB connection issue in Windows, I have no idea and experience as I'm using Linux Ubuntu. Normally, some other software (virus, other communications SW, etc.) interferes with the operation of the port, which is required to be dedicated to the Arduino IDE.
For RP2040, in Linux, you have to run post_install.sh after the core installation.
While for Portenta_H7, in Windows, you have to run post_install.bat. But I don't know why there is no need for RP2040.
Anyway, I don't have Windows system to check, and it's better you post a separate issue to ask for help, if still necessary.
This didn't work for me but I was able to find the uf2 file that was generated when uploading FirmwareUpdater.ino.elf.uf2 in the user temp directory and manually added to the RPI RP2 drive in Windows. It would make life easier and would have saved me a whole day trying every other option to upload if the FirmwareUpdater.ino.elf.uf2 file was hosted for download somewhere.
