everything I attempt to do on the IOT cloud with my official 33 IOT just fails, uploading sketches, viewing the serial monitor, and even pairing the device.
I'm sure I must be doing something wrong for it to fail at literally everything in 5 different ways and taking an hour of retrying everything to get it to work once before failing and having to restart.
I'm using an Arduino Nano 33 IOT
with MacOS Sonoma Version 14.0 Beta (23A5312d)
with the arduino agent 1.3.2-d170a5e.
The browser I'm using is just the standard most up to date version of chrome.
The main cause of a lot of the problems I think is that the nano appears to disconnect from serial very randomly for a few seconds before connecting again.
I've attached many screenshots showing some of the errors which I am getting.
well, some of them, after restarting the dozens of failing steps I'm unable to even get the board to configure so I included that screenshot.
I've never personally used a Nano IOT before, but if your board randomly disconnects from serial it could be that it's not getting enough power. Make sure you are using a good power source with at least 5V and plenty of current. Also make sure you are using a good power cable; try swapping yours out for a different one.
Of course, I could be completely wrong. I've never used one of these boards. This is just something you can try if you are at a dead end.
I'm 99.99% sure that its not a problem with amount of power as MacOS usually gives USB power notifications if it ever limits power, plus the 33 iot shouldn't draw any measurable amount of power when in the bootloader/running nothing since I can't get anything onto it.
Thanks for the idea though.
Even when it's not losing power it manages to get stuck on random steps for far longer than it reasonably should, such as on the third step of device configuration for IOT.
I'm fairly sure power consumption can't be the problem, it's connected directly to a front USBC port on my mac studio, which means it is going through a thunderbolt to USBA dongle, however this is fine powering much more than an arduino.
The system is definitely detecting the serial port properly and it shows up insystem information perfectly fine.
As for the debug console, it does appear perfectly fine, however drops the serial connection for a cycle when it reaches the error if I remember correctly.
*for some reason it decided to work first try to configure and upload and I'm too scared to reset it so this is just a screenshot of the fact that it can definitely be recognised by the create agent. I'll reply to this when I next try to upload something and get the errors again.
Final thing, no, the arduino IDE works mostly fine and certainly never has had problems with serial connections through this cable setup to any of my nano 33s.
Just a final tip (probably you are already doing it).
Please, close the Arduino IDE and Serial monitor if you have them open before programming the board.
Hi, have you tried to use a different computer? For example with Windows, the problem could be the Mac.
I have the Mac with Catalina and it's a disaster to compile codes, I have several modules and they all work perfectly with windows, the problem is that Macs are a disaster! It seems that Apple has the USB protected, it makes me want to throw it away, for example with Windows if I have 10 modules these work perfectly without any problem even in the first try to sync, and with the Mac I can say that only 2 work and almost badly they synchronize, in my opinion using Macs with Arduino and others modules is a disaster, nothing to do with when we compare Windows.
I'm fairly sure the operating system is not the issue. I've never had any problems with any other devices, modules, or other arduinos. Everything works perfectly apart from the IOT cloud with arduino create agent. I could switch to windows but most of what I do doesn't work on windows, plus arduino advertises that it works with macos, even providing arm native versions as far as I can see.
I am a Mac user since 2005 and the truth is that using the Mac with Arduino and other modules works very badly, for example I have a couple of ESP32 modules about 8 and they all work perfectly with Windows from the first minute, I connect and voila, 0 problems but with the Mac only 1 works for me and I spent a couple of hours downloading drives and many others histories to make it work and so with other modules too, for example the Nano 33 BLE ..... It works but in my case with Mac I have to juggle for it to work, something that doesn't happen to me with Windows. That is why I am commenting if you have tried with Windows, it has happened to me not with 2 or 3 modules, I have about 30 modules (from Arduino and AliExpress) and they all work badly with the Mac and with the Windows it is the opposite, they work fine with no problem. Apparently it is that Apple has the usb protected something like that for this it works badly, and I saw that you are using MacOS Sonoma Version 14.0 Beta
I'm not a Mac user, not a Cloud user and not a 33 IoT user.
One thing to know about the serial behaviour is that boards with native USB (like your Nano 33 IoT) is that when an upload is performed, the board is reset by opening and closing the serial port using a baud rate of 1200 baud. This invokes the boot loader. Once the process is complete or times out (no upload instructions), the device falls back to running the sketch.
In the Windows world, you can observe the behaviour in device manager; you will see the 'normal' com port disappear and a different one show when the upload starts. When the upload finishes the different one disappears and the 'normal' one comes back (if there are no bugs in the sketch). While the device is in boot loader mode, the L-led should fade in and out (for approx. 8 seconds if no actual upload is performed).
The inconvenient workaround might be to double-tap the reset button at the moment that you see the message "Upload started".
Part of the code that is uploaded relates to the USB communication (board identification and reaction on the reset); a buggy sketch can damage the variables used by those functionalities and as a result the board will either not be identified or not react on the software reset command. In which case loading blink with the double-tap trick will get your board in it's original state and it should always be recognised and should always react on the software reset.
I have tried forcing it into bootloader at the appropriate time but that also seems very unreliable, also not working a lot of the time.
I have noticed that when uploading it does often fail to initiate the bootloader, however I’m not sure if this is just how the iot cloud works, as uploading clearly works differently - shown by the ability to upload over wifi after the board has been configured.
I think that this issue could be mostly avoided using wireless uploads with the IOT cloud after eventually getting it to configure, however that requires a paid subscription on top of already buying an arduino, which is something I am definitely not yet convinced on from my current experiences.
But IoT Cloud Remote is not fully operational and free for 2 devices? I didn't know that you had to pay for full access, I imagined that the payment method was only when you wanted to use more than 2 devices...
Nahhhh that would be far too useful, they limit the number of compiles, number of “things”, number of devices, number of cloud variables and many more things. The bigger issues are making it so that you can not upload sketches wirelessly without paying, as well as not being able to use any APIs
Im not entirely sure what you mean by usb protected, the closest thing I’m aware of is that iPhones may require authenticating when being plugged into a mac before they allow data transfer to make sure you can’t just get data off them.
I’ve had plenty of arduino boards work perfectly through the IDE and vscode, I think I also used the web editor just fine on a non IOT board as well.
macOS may work differently to windows, but for everything I’ve tried previous to this, it does work. As for the fact I’m using a developer version it really shouldn’t make a difference compared to any other releases as they haven’t changed anything related to this.
Interesting, thankfully as far as I'm aware genuine arduino boards don't have a problem with macos, plus ironically I am using a "hub" anyway which would probably disable whatever security there is.
not entirely sure why you think window's lack of security is a good thing
