
Thank you very much.
but I can't get it to work, do you have a recipe how to install the driver??
I downloaded the driver from githu, unzipped it and pressed setup.exe and the driver installed, but it doesn't work
Hi @henrik_t7,
Apologies, but I don't have one of these boards, (or any other experience with them), so I am just looking at the documents on the web in the hope of spotting something useful. It is probable you have already carefully checked these documents, but it is easy to miss a crucial point.
-------------
I assume you are using at least Windows 10, preferably Windows 11. I have no idea whether the driver will work with versions before 10, but I doubt if they will have been tested with them.
------------
Google search took me to: https://content.arduino.cc/assets/ABX00053-schematics.pdf
which is a schematic labelled Nano RP2040 Connect
Assuming this is the board you are referring to, then the schematic shows the USB connects directly to the RP2040 chip.
(Click image to enlarge)
Hence, there does not appear to be a CH340 on the board, because the RP2040 is performing that role.
(A simple Arduino Nano, without the RP2040, would need a USB chip, and the schematic at https://www.arduino.cc/en/uploads/Main/Arduino_Nano-Rev3.2-SCH.pdf shows an FT232RL)
Thus, CH340 drivers are unlikely to be useful. I would recommend uninstalling them, possibly together with any other USB chip drivers you may have loaded, in case they are causing a conflict. Of course, you have other USB devices, like keyboard and mouse, which will be needed for computer operation, and are unlikely to be a problem, so this may require some careful juggling. I don't know what PIRISI USB is.
----------------
I also found the Arduino documentation, at:
https://docs.arduino.cc/tutorials/nano-rp2040-connect/rp2040-01-technical-reference/
This has a short description, with links to the further pages on how to connect it.
It also includes a section entitled "Board Not Detected", with two further procedures to try.
Of course, you have probably already followed this document and its links, but it might be worth another try.
-------------
My limited experience some time ago with the Raspberry Pi Pico board included sometimes finding the board didn't want to accept a new code download, which I think was related to the 'feature' of be able to make the board look like a mass storage device or a development board, and sometimes it would change to the wrong one. I didn't persevere with the board long enough to establish the exact cause and remedy, but did manage to mitigate the problem, by following the published procedure.
Note the strange instruction in the Board Not Detected Section:
4. Upload a basic sketch, such as the blink example to the board (even though it is not visible in the port selection).
You might even want to try it more than once! I don't understand the 'Why and the How', of such behaviour, but I vaguely recall something similar with the Pico.
-----------------
Apologies if this note is just repeating your own efforts, but it is provided in good faith.
Good luck and best wishes, Dave