Yes, I know this is the typical "connection/driver" issue but I've now tried everything to get the Nano 33 IoT working!
I have a development laptop running Windows 7 64bit. All other Arduino things work perfectly - UNO/MEGA/etc. When I plug any of those in they are correctly identified and the appropriate COM port appears.
Not so with the new NANO 33 IoT. If I plug that into the laptop it appears in the "Other Devices" list as "Arduino Nano 33 IoT".
Prior to plugging the board in to the the laptop I'd downloaded the latest version of the Desktop IDE. I'd also followed the board management instructions for the new NANO 33. All went fine (as far as I'm aware).
First off do not rely on memory to write error messages or similar.
Speelung mistooks looc orible too dee siphon
I would guess you re-started the computer after installing the boards package in the IDE (not always needed)
It should have shown in device manager under ports COM & LPT.
Showing in other devices usually does mean a driver error.
It might also be worth dropping back a version on the IDE.
There have been some odd reports about the latest stable version although they tend to deal with AVR issues.
USB 2.0 ports are preferred for Arduinos although we have seen fewer instances of USB 3.0 causing issues.
Laptop restarted a number of times. I've also made sure Windows is completely up to date. Also, only using USB2.0.
I've also tried one of the new Arduino Nano Every boards and that fails to be recognised too.
I uninstalled the IDE (1.8.9) and cleaned up as much as I could. Installation of IDE 1.8.8 followed along with the 1.8.1 version of the NANO 33 board manager package rather than 1.8.2. Then rebooted.
After a reboot I connected a standard UNO - no issues and resolved properly as a serial COM port device.
Connecting an Arduino Every and same as before - "Other Devices - Arduino Nano Every"
Tried the Nano 33 IoT again but same thing too - "Other Devices - Arduino Nano 33 IoT"
Attempting the same steps on a different Windows 7 PC results in the same problem. These drivers just don't seem to work on there.
Annoyingly, this all works perfectly fine in Windows 10 but I can't use that PC for this work!
You seem to have a good selection of computers to play with and that brings me to thinking.
Are these your own personal computers or part of some corporate/educational system ?
If it is the latter then I suspect a security policy or a third party software such as antivirus may be part of the issue.
Also are you installing as ADMINISTRATOR which is also needed on some occasions to bypass user security problems.
I'm having exactly the same problem as you trying to get a working port on Windows 7. On Windows 10 the two Nano 33 IoT's ("N33") I now have do show up as COM ports and in the Tools>Port menu correctly. I also got both N33 devices to load and run a sketch on a MacOS machine (MacOS 10.11.4). In all cases I've installed v1.8.2 of the board into the Board Manager.
On Windows 7 I've tried various versions of the Arduino IDE (1.85 and 1.89) and two versions (1.8.1 and 1.8.2) of the board for the N33's SAMD processor. When it is plugged in, device manager always shows the correct device name but is shows up under "Other devices" tab.
Curiously, the single N33 I had at first did show up in Device Manager on Windows 7 but later it didn't, for which I have no explanation. It didn't show up under the Port menu on MacOS at first either, but at some point it started working on MacOS. After testing it on MacOS, in Windows it showed up again but as an "Unknown device".
Did you ever make any headway on this problem? Any ideas or suggestions on things I can test here?
Something I just tried on Windows 7 with the N33 seems to be working. In desperation, I tried uninstalling the driver (whatever it may heave been) in Device Manager and then tried installing the driver for the Arduino Nano MKR WiFi 1010, which I had read somewhere online that is very similar to the N33. Now the board shows up in the Device Manager (in the Ports tab and also in the main properties window) as "Arduino MKR WiFi 1010 (COM67)", while in the Arduino IDE Port menu it shows up as "Arduino NANO 33 IoT". So far, it seems to be working fine, although I have only tried various Serial interactions with it. I think that I read online that the MKR 1010 driver may not be fully OK for use with the N33, and I continue hoping to learn how to get this fully right and understood.
Bob - yes, corportate prototype work. One Windows 7 laptop has Symantec on, the other Windows 7 laptop does not. It doesn't work on either. Trying Admin privs makes no difference to anything sadly.
Uninstalling drivers, rebooting, re-installing drivers, rebooting - yes, I've been around that cycle many times to no avail.
I've also tried a completely clean install of Windows 7 Pro (again, 64bit). Still no joy. I'm at a loss so can't really continue for the moment.
Whilst I could try using drivers for another board, I'd rather not. This work needs to be reproducible on environments that aren't mine and using a "workaround that may exhibit problems" isn't acceptable. =/
If you would both wait acouple hours and clear you browser cache etc before trying again.
Seemingly a fix has been made available.
1.8.3 would be the new fix for boards.
I can confirm that the update works perfectly for the Nano 33 IoT now.
Do you know if there will be an updated package for the Nano Every? Although I'm not using it at the moment, it is exhibiting the same problems (running Arduino megaAVR Boards v1.8.2 package).
The update to version 1.8.3 of the board for the Arduino NANO 33 IoT did the trick for me on MacOS. I'll be testing with Windows 7 later today. Thanks.
Not sure if this works for the new NANO series but can you try double click the reset button.
It may put it on a new COM port.
If so then try upload either the EXAMPLE BLINK or BARE MINIMUM sketch.
Bob.
Ola!
I've been playing with the Nano 33 tonight and for some reason it just stop working (couldn't detect the Port).
I tried a new nano 33, after uploading my code it also gave the same issue.
The double click of the reset button fixed it for me!
I was then able to upload BLINK sample and it works.
Interestingly, the code I had uploaded when the problem started, keeps breaking it.
I was using the CryptoAuthLib to play with the ATECC608A cryptochip.
I have run into very similar problems with the Nano 33 BLE.
The automatically installed drivers seem to work fine in Windows 10 and I can upload a sketch no problem.
In Windows 7 the Arduino board shows up in Device Manager under 'Other devices' with a yellow exclamation mark and Device status indicates 'The drivers for this device are not installed. (Code 28)'. No COM port is assigned so I can't attempt to upload a sketch. Double-clicking the reset button doesn't resolve the problem
It seems like there was a fix to the driver for the Nano 33 IoT in a later version of the board software. Is a similar fix going to be required for the Nano 33 BLE board?
I'm running Arduino IDE 1.8.9 and Arduino nRF528x Boards (Mbed OS) by Arduino version 1.1.0.
With Arduino Nano Every
Same driver issue as described her before by other users.
OS is Win-7 64bits
IDE is 1.8.10. Before installation previous version was uninstalled.
With board manager installed MegaAVR to support Every.
Rebooted system a few times.
When Every is connected to COM port it appears as 'Arduino Nano Every' in 'Other devices'
Tried with different USB cables to eliminated that this behavior is caused by a faulty cable.
Would say that there is something wrong with the driver for Every.
If it appearing in "other devices" that is most often a sing the driver did not fully or properly install.
Quite often that can be fixed by using the INSTALL AS ADMINISTRATOR option.
Occasionally an over aggressive security program may also cause a similar behavior.
Fix for that is to initially turn OFF any additional security / antivirus etc.
Once that is done you should add the ARduino locations to the exclusions / white list of the security.
Also AVOID installing to cloud / network type locations as they may cause these and other types of issues.
Fix for that is to know a little about those types of scenarios and change the system settings accordingly.
As each cloud network can be different there is no "just do this" fix.
If it was a driver issue we would have many many more reports which we do not have so I suggest its an issue local to you at this point.
