@Dozie I know the IDE is good on Windows 7, but is there an official Nano driver for Windows 7?
It seems to be the common factor when many users can't upload to their Nanos?
I think it’s depends upon which Nano board you are using, Nano everyday MCU can not directly communicate with usb so it had USB to UART converter chip. For Nano RP2040 no need to converter chip.
Just got mail from seller, he is saying board is defective. And he is sending replacement board so once I received new board will post updates.
Got another board but still problem exists. But good thing is with new board at least I can upload default blinking led sketch in bootloader.
Hi, I have similar problem. Tested on 3 different Rp2040 nano connect boards, 4 computers running Win10 Pro 64 bits and numbers of cables, which work just fine with ESP32 and other fast data transfer devices. With GND+REC shorten up the storage appears but it disappears after uploading blink program. It is possible to put new folders and text files, but all are gone when the chip is rebooted. It is surprising RP2040 connect works for some people.
I'm having a similar problem - device wont show up on a port no matter what I do.
If I put jumpers on, it will show up in the filesystem and I can copy blink to it. I unplug it, remove jumpers, and reconnect the USB and the device just sits there not blinking and undetectable on any ports. The interesting thing is that it was working just fine earlier, and it started doing this immediately after downgrading the board support 'mbed os nano boards' to v2.1.0 in an effort to use the wifi module (the current wifi libs require newer firmware that seems to be available).
Double tapping the reset doesn't put it into bootloader mode, only the jumpers. Pretty much stick at this point so if anyone has suggestions I'd really appreciate it, thanks. My intuition is that this is a software issue and I need to somehow get the right firmware on there, but dragging the blink.ino.elf.uf2 I downloaded from the official 'board not detected' instructions isn't having any effect.
Thanks
Right after I posted this I saw in another thread that you have to remove the jumper after it boots up and before you copy the blink over to the device. Prior to doing this, windows wouldn't show any progress indicator and the device would simply reset. With the jumper removed after connecting the USB, when I copy blink over I see windows explorer copy progress window and when the device reboots it is running blink and detected on a port.
I backtracked and reinstalled v2.1.0 of the mbed OS for rp2040 and it once again became unresponsive. Following the steps above fixed it right away. Switching back to the latest mbed OS, I was able to upload a modified blink successfully. So this part is figured out now at least, now back to the original problem I was trying to solve which is how to get the Nina firmware updated so I can use the wifi since apparently the current libs require a newer version.
Thank you for updating this, that's very helpful.
I'm glad to hear it! Thanks for taking the time to share the solution you found.
As you probably noticed, the Arduino IDE's "WiFi101/WiFiNINA Firmware/Certificate Updater" tool does not have the latest 1.4.8 version of the firmware. The reason being that the firmware was released after the time the Arduino IDE was released.
Fortunately, the hourly build of the Arduino IDE does have the 1.4.8 firmware. The process for updating the firmware with the hourly build of the IDE is the same as with the release version of the IDE.
- Open the "Software" page of
arduino.cc: https://www.arduino.cc/en/software#hourly-builds - Under the "DOWNLOAD OPTIONS" section, click the appropriate link for your operating system.
- Wait for the download to finish.
- Extract the downloaded file.
- Run the Arduino IDE executable from the extracted folder.
- Follow the standard firmware update process as described here: https://www.arduino.cc/en/Tutorial/WiFiNINAFirmwareUpdater
(tutorial uses MKR WiFi 1010, but it is the same process for Nano RP2040 Connect)
After that, you are welcome to go back to the version of the Arduino IDE you were using before. The hourly build installation will not interfere with your previous IDE installation. The hourly build is just a convenient way to get the latest firmware version.
Please let me know if you have any questions or problems.
Thanks so much, @pert, for the info on the nightly builds. I had gone down some deep rabbit holes trying to figure out how to find, build and install the latest version of the NINA firmware and your advice was a huge help!
You're welcome. I'm glad if I was able to be of assistance. Enjoy!
Per
I believe the reason for this is explained here:
https://github.com/arduino/Arduino/issues/11638#issuecomment-899283531
Due to the (not so) recent issues with supply chain we're mounting different flash chips depending on availability. While those are mostly compatible with each other, some have slight changes that require fw adjustments. In this specific case the issue can be solved by compiling sketches using the latest core which is of course backwards compatible with all other chips. If you already flashed a board with code compiled with an old core you need to recover by resetting the board while shorting the rec pin with ground. Please make sure you remove the short after reset, before flashing.
Looks like you Arduino team also do not have clear answer for this particular problem. As lot of user facing this problem you guys should stop production of this board and should first resolved problem and then you guys can start shipping these boards. Because for us its very frustrating as we all now in micro-controller programming and for you as a good company its look little unprofessional to release buggy product.
*out of million Arduino fans I am one & I know that I am not qualifies to give you suggestions. But as a customer consider it as a little advice.
No, I don't see this as an issue. OP wants to run a modern device on a sunsetted OS (Windows 7)
I would agree with you if there was an issue on Windows 10 or the last couple versions of masOS, but I don't see that here.
Legacy support is always iffy at best.
Can you provide any evidence for that claim? I don't recall lots of reports of your problem and I didn't find any after a quick search of this forum category.
A list of some of the many other forum topics that must surely exist if a lot of users are facing this problem would be useful for investigating the issue because it might be that additional information has emerged in one of the other topics.
That's a good point and another reason not to use an outdated OS. I do not see anyone rushing out to write new drivers for an outdated OS. However, if OP took this to a modern computer he might be able to update the firmware and then use it with his old computer.
I did it but after the windows explorer copy progress window the the connection with the USB drive resets. I back the jumper and open the flash drive again, only two files inside: INDEX.HTM and INFO_UF2.TXT.
Only the green led is on and no com port detected! 
Note: First time I connected it was working and the original blink program was running. The headache starts after I upload an example program from: examples for arduino nano rp2040 connect > Scheduler > MultipleBlinks.
Now I can't detect the com port and the jumper (REC & GND) works but I can't copy anything to the flash drive. I tried under Windows and Ubuntu.
Unfortunately, I'm facing the same problem and spending some time trying to solve it. I really appreciate if someone can give me a help.
First time I connected the board it was working fine, running the original blink code inside the flash.
Then I uploaded an example program from: examples for arduino nano rp2040 connect > Scheduler > MultipleBlinks. This example was loaded in the example folder after I installed the "Raspberry Pi Pico/RP2040" board manager package... bad choice! probably a wrong example!
After I uploaded it to the board I have only the green led on and it's no more possible to detect the COM PORT.
I did the (REC & GND) procedure on the both ways, keeping the jumper and removing the jumper after my OS detected it (tried Windows and Ubuntu) but all times the connection is lost during the writing operation and when I open the flash memory again I have only the original files: INDEX.HTM and INFO_UF2.TXT. Note that I can read/copy these two files from the memory to my computer.
I tried to replace the USB cable too with no success... as expected.
My last try was to use the FWUPLOADER but how can I use it if there is no COM PORT detected?