Arduino RP2040 Cloud Setup

billyc9419 · February 3, 2024, 9:12pm

I just purchased a RP2040 and am having issues getting it to connect to the Arduino Cloud from several Windows 11 machines.

I have installed Arduino Create and it appears its having issues installing the drivers. I am getting the following error in the create debug window:

{
  "OS": "windows"
}

downloadtool windows-drivers latest arduino keep

downloadtool bossac 1.7.0 arduino keep

downloadtool fwupdater latest arduino keep

downloadtool rp2040tools latest arduino keep

{
  "DownloadStatus": "Pending",
  "Msg": "Downloading tool windows-drivers from http://downloads.arduino.cc/tools/drivers-arduino-windows-1.8.0.zip"
}

{
  "DownloadStatus": "Pending",
  "Msg": "The tool is already present on the system"
}

{
  "DownloadStatus": "Success",
  "Msg": "Map Updated"
}

{
  "DownloadStatus": "Pending",
  "Msg": "The tool is already present on the system"
}

{
  "DownloadStatus": "Success",
  "Msg": "Map Updated"
}

{
  "DownloadStatus": "Pending",
  "Msg": "The tool is already present on the system"
}

{
  "DownloadStatus": "Success",
  "Msg": "Map Updated"
}

{
  "DownloadStatus": "Pending",
  "Msg": "Unpacking tool windows-drivers"
}

{
  "DownloadStatus": "Pending",
  "Msg": "Installing drivers"
}

{
  "DownloadStatus": "Pending",
  "Msg": "post_install.bat"
}

{
  "DownloadStatus": "Error",
  "Msg": "exec: \"post_install.bat\": cannot run executable found relative to current directory"
}

ptillisch · February 4, 2024, 6:07am

Hi @billyc9419.

Thanks for reporting this. I did an investigation and was able to find that it is caused by a bug in Arduino Create Agent. I have now submitted a fix for the bug:

github.com/arduino/arduino-create-agent

Fix failure to execute tool post-install script on Windows

arduino:main ← per1234:fix-post-install

opened 05:26AM - 04 Feb 24 UTC

per1234

+2 -1

### Background #### Tool Dependency Installation **Arduino Create Agent** …performs installation and updates of the tool dependencies required for direct communication between the local machine and the target board. It might be necessary to execute some sort of installation process in addition to placing the files from the tool archive on the user's hard drive. This capability is provided by a "post-install script" system. If a post-install script file (`post_install.bat` on Windows, `post_install.sh` other host operating systems) is found in the tool installation, **Arduino Create Agent** automatically executes it as part of the tool installation operation. One of the tool dependencies is `arduino:windows-drivers`, which provides the Windows device drivers for the official Arduino boards. This tool contains a post-install script that installs the drivers from the tool archive. It is essential for this script to be executed as the presence of the driver files alone doesn't have any effect. #### Go `exec` Package From the Go 1.19 release, the behavior of the `exec` package was changed to make it more secure: https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory > as of Go 1.19, this package will not resolve a program using an implicit or explicit path entry relative to the current directory. That is, if you run exec.LookPath("go"), it will not successfully return ./go on Unix nor .\go.exe on Windows, no matter how the path is configured. Instead, if the usual path algorithms would result in that answer, these functions return an error err satisfying errors.Is(err, ErrDot). ### Problem The code that executes the post-install script on Windows depended on the previous permissive behavior of the `exec` package. Ever since the version of Go used to build **Arduino Create Agent** was updated to 1.19 (https://github.com/arduino/arduino-create-agent/pull/744), the script has not been executed. This means **Arduino Create Agent** never installed the drivers from the `arduino:windows-drivers` tool on the machines who weren't using it before the [1.3.0 release](https://github.com/arduino/arduino-create-agent/tree/1.3.0). The failure to execute the post-install script results in **Arduino Create Agent** attempting installation of the `arduino:windows-drivers` tool on every Arduino Cloud session. Even if the user is not impacted by the lack of drivers (either because it is not required for their board, or because they installed the drivers via some other mechanism), they will still be annoyed and confused by the frequent appearance of [the "**Installing drivers**" dialog](https://github.com/arduino/arduino-create-agent/blob/6aa81834ef7d0113a1be1d9039fe7b35fa471c8c/tools/download.go#L234) that is produced by **Arduino Create Agent**'s post-install script execution code. #### Demonstration 1. Start a build of **Arduino Create Agent** that does not contain the patch proposed here on a Windows machine. 1. Open the **Arduino Create Agent** "Debug Console". 1. Type the following [command](https://github.com/arduino/arduino-create-agent/wiki/How-to-use-the-agent#download-a-tool) into the input field on the bottom of the Debug Console web page: ```text downloadtool windows-drivers 1.8.0 arduino replace ``` **ⓘ** This specific command is used to force an installation of the `arduino:windows-drivers` tool even if you already have the latest version installed. 1. Wait for the "**Installing drivers**" dialog to open. 1. Click the "**Yes**" button in the dialog. 🐛 Arduino Create Agent does not execute the `post_install.bat` batch file. You can see the cause in the Arduino Create Agent debug console: ```text { "DownloadStatus": "Error", "Msg": "exec: \"post_install.bat\": cannot run executable found relative to current directory" } ``` ### Additional Context I planned to add test coverage for [`github.com/arduino/arduino-create-agent/tools.Tools.installDrivers`](https://github.com/arduino/arduino-create-agent/blob/6aa81834ef7d0113a1be1d9039fe7b35fa471c8c/tools/download.go#L223) in order to avoid another such regression in the future. However, this is challenging to do for Windows due to [the "**Installing drivers**" dialog](https://github.com/arduino/arduino-create-agent/blob/6aa81834ef7d0113a1be1d9039fe7b35fa471c8c/tools/download.go#L234). It seems it would be necessary to mock [`github.com/arduino/arduino-create-agent/tools.MessageBox`](https://github.com/arduino/arduino-create-agent/blob/6aa81834ef7d0113a1be1d9039fe7b35fa471c8c/tools/shell_windows.go#L30), which would require selecting a mocking framework for the project. --- I chose the approach that followed the system previously established in the code. A more elegant solution would be possible through the use of the the [`github.com/arduino/go-paths-helper` module](https://github.com/arduino/go-paths-helper), which is already used elsewhere in the project. However, I feel that should be done as part of comprehensive migration to using the module for all path-related operations, which is out of scope for this PR. --- I didn't have time to investigate it, but it is possible this will fix https://github.com/arduino/arduino-create-agent/issues/856. --- Originally reported at: - https://forum.arduino.cc/t/initial-configuration-of-board-failing/1207822 - https://forum.arduino.cc/t/arduino-rp2040-cloud-setup/1219617

I'll provide instructions you can follow to manually run that post_install.bat file, which will install the drivers:

Start Windows "File Explorer".
Open the folder at the following path:
```
C:\Users\<username>\.arduino-create\arduino\windows-drivers\1.8.0\
```
(where <username> is your Windows username)
Double click on the post_install.bat file you see in that folder.
You might now see a "User Account Control" dialog about dpinst-amd64.exe asking whether you "want to allow this app from an unknown publisher to make changes to your device". Click the "Yes" button in the dialog.

Please let me know if you have any questions or problems while following those instructions.

billyc9419 · February 4, 2024, 5:51pm

Thanks for the quick response.

I have tried your workaround with no success. When I run the .bat file it gives me the prompt whether to allow it or not. I click the "Yes" button and nothing happens after that. So I went and tried to just run the dpinst-amd64.exe manually. It goes through the install process but at the end it says the following drivers failed to install: Adafruit Industries LLC (usbser) Port, Intel Corporation USB, libusb 1.0 (WinUSB) libusb, http://www.intel.com (usbser) Ports, and Silicon Laboratories Inc. (silabser) Ports.

I am also not seeing any drivers missing when I open up device manager to try and manually install any drivers.

EDIT: I have been doing some more research and tinkering. I am starting to think its an issue with my RP2040. I tried it on two additional windows 11 machines and one windows 10 machine. I have installed the Arduino IDE and tried the loop back test with now connections found on the ports.

ptillisch · February 5, 2024, 3:26am

Nice work on identifying the alternative approach to performing the driver installation!

I am able to reproduce this issue of the installation of some of the drivers failing. That should be fixed, however, the drivers that weren't installed aren't important in this context. They only affect support for the Adafruit Circuit Playground, Arduino 101, and 3rd party boards that use the Silicon Labs CP210x USB to serial adapter chips. So the lack of those drivers on your system won't impact the usability of the RP2040 board.

Please add a forum reply here that provides a detailed explanation of what you mean by this, including:

What did you do?
What were the results you expected from doing that thing?
What were the results you observed that did not match your expectations?

Make sure to include the full and exact text of any error or warning messages you might have encountered.

The "loopback" test is not applicable to the RP2040-based boards. This test is only possible with the boards that use a dedicated USB to serial adapter chip separate from the primary microcontroller. The RP2040 is what we refer to as "native USB", where the microcontroller can communicate directly with the computer via USB without the need for a separate adapter chip.

billyc9419 · February 5, 2024, 3:57am

Good to know thanks for the information.

I followed all the directions when trying to add a device to a device to the cloud service. Downloaded Arduino create, got the error mentioned in the first post. After trying to resolve that error I continue to receive it in the debug log periodically. The debug log also shows no serial connect.

I expect to be able to connect/add the device to Arduino cloud.

I observed no connection to the computer. The create debug status remained unchanged when plugging in the device. I also cannot observe any Arduino hardware in the windows device manager. I repeated this all today on a windows 10 machine as well.

ptillisch · February 5, 2024, 4:20am

Please just ignore the error. It is completely irrelevant to the real problem you are having and is only acting as a "red herring". It will no longer occur after the next release of Arduino Create Agent, but even now it doesn't cause any actual harm.

Thanks for the clarification. I understand the nature of the problem now.

Make sure the USB cable is completely plugged into both the Arduino board and the PC.

If that doesn't help, you may have a damaged/defective or charge-only USB cable. Try a different cable.

Either of the above can result in the power connections being made (and thus LEDs lit on the board), but no data connections (and thus no port for the board).

billyc9419 · February 6, 2024, 3:16am

I have tried 4 different USB cables all with the same results. I thought I put that in my earlier response, sorry for forgetting to put that in my response.

ptillisch · February 6, 2024, 9:55am

Please try this experiment and then report back with the results:

Connect the Nano RP2040 Connect board to your computer with the USB cable.
Press and release the reset button on the Nano RP2040 Connect quickly twice.
You might now see a notification from your operating system that a new drive named "RPI-RP2". If not, open your computer's file manager (e.g., Windows "File Explorer", macOS "Finder") and check to see whether a drive of that name is listed there.

Now please reply here on the forum thread with the answer to the following question:

Did a new drive named "RPI-RP2" appear on your computer after you performed the above instructions?

billyc9419 · February 7, 2024, 1:55am

I do not see a new drive named "RPI-RP2".

ptillisch · February 8, 2024, 4:57am

OK, there is an alternative procedure for putting the board into a state where it can be recognized by the computer.

Please try this experiment and then report back here with the results:

This procedure is not intended to solve the problem. The purpose is to gather more information.

Disconnect the USB cable of the Nano RP2040 Connect board from your computer.
Use a jumper wire to connect the pin marked "REC" on the board to the pin marked "GND" on the board.
Connect the Nano RP2040 Connect to your computer with the USB cable.
You might now see a notification from your operating system that a new drive named "RPI-RP2". If not, open your computer's file manager (e.g., Windows "File Explorer", macOS "Finder") and check to see whether a drive of that name is listed there.

Now please reply here on the forum thread with the answer to the following question:

Did a new drive named "RPI-RP2" appear on your computer after you performed the above instructions?

Please let me know if you have any questions or problems while following those instructions.

billyc9419 · February 8, 2024, 2:37pm

I still don't see "RPI-RP2" show up in the windows explorer. This time only the solid green light turned on on the Arduino.

ptillisch · February 13, 2024, 2:25pm

Hi @billyc9419. I apologize for being slow to respond.

It is possible for a short or external circuitry connected to the Arduino board to put it into a non-functional state where it can't communicate with your computer.

Make sure the board is not sitting on anything conductive that could short the contacts on the bottom of the board. Make sure there isn't any conductive debris (e.g., strands of wire or component leads) on the board or on the surface the board is sitting on.

If you have a shield or any external circuitry or components connected to your Arduino board, try this experiment:

Disconnect the USB cable of the Arduino board from your computer.
Disconnect any shields, modules, external circuitry, etc. from your board.
Connect the Arduino board to your computer with a USB cable.

Now follow the instructions I provided in my previous reply once again and then check to see if the board produces the drive named "RPI-RP2" this time.

If it does, you know the problem was caused by the external circuitry. You can then focus your attention on identifying the specific problem with the circuit and resolving it.

system · August 11, 2024, 2:25pm

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Connecting to rp2040 Not Working Nano RP2040 Connect	2	2448	September 1, 2023
Adding Nano RP2040 to Cloud fails Cloud IoT	1	219	April 9, 2024
Can't add RP2040 as Arduino Cloud device Nano RP2040 Connect	5	292	August 13, 2024
Configuration error on RP2040 Connect Nano RP2040 Connect	2	198	August 16, 2024
Nano RP2040 Connect does not Connect Nano RP2040 Connect	9	2181	July 11, 2022

Arduino RP2040 Cloud Setup

Related topics