I have just started to learn bout these boards selling for $4 from Vilros.
It's got a dual core processor and loads of storage but only 26 IO pins.
It can programmed in MicroPython, C/C++ and Arduino IDE, dunno what else.
I have just started to learn bout these boards selling for $4 from Vilros.
It's got a dual core processor and loads of storage but only 26 IO pins.
It can programmed in MicroPython, C/C++ and Arduino IDE, dunno what else.
Its great. What is your question?
there is a W version with WiFi chip on board and the Pico Arduino core by Earle F. Philhower has a bundled WiFi library for Pico W.
btw the Pico arduino core had the first release exactly two years ago
You can get all important info about Raspberry Pi Pico from here:
www.theengineeringprojects.com/2022/04/getting-started-with-raspberry-pi-pico.html
Currently I am using one. It has many convenience and some inconveniences too. Pico W is better because it has in-built wifi.
The most amazing feature of Rasberry Pico is it Pio machine.
Since when does there have to be a question in starting Bar posts?
Got an answer for that?
I've got a dozen of them. I buy only the PicoW now because it's only $6 so why not.
I haven't bothered installing any Arduino stuff on them. MicroPython and the C++ SDK have supplied everything I've needed. I'm with @b707 on the PIO.
So now question: how is that RAM shared?
I had an Amiga1000. The RAM ran double speed. Every other RAM cycle the CPU and graphics had access transparent to the other, roads never crossed.
C/C++ SDK for whose compiler/IDE?
If using Earl's core:
Multicore Processing β Arduino-Pico 3.1.0 documentation
The RP2040 chip has 2 cores that can run independently of each other, sharing peripherals and memory with each other. Arduino code will normally execute only on core 0, with the 2nd core sitting idle in a low power state.
By adding a
setup1()
andloop1()
function to your sketch you can make use of the second core. Anything called from within thesetup1()
orloop1()
routines will execute on the second core.
setup()
andsetup1()
will be called at the same time, and theloop()
orloop1()
will be started as soon as the coreβssetup()
completes (i.e. not necessarily simultaneously!).See the
Multicore.ino
example in therp2040
example directory for a quick introduction.
Do you mean between the two cores? I know it is shared between the two cores but I'll have to look at the data sheet to figure out if it's interleaved or not.
Arduino's attempt at a REPL (for MicroPython) is not worth installing. I use Thonny on the Mac and on a Raspberry Pi 4 but I think there are other options including one that is more command line oriented if that's your preference. Some people hate Thonny for some reason but it works fine for me.
I prefer not to use Adafruit's CircuitPython because it's not directly compatible with standard MicroPython.
I see no advantage in using the Arduino core for C++ unless you prefer its IDE environment. There seem to be some problems with it based on posts here.
For those interested, the basics are listed here:
CircuitPython β Adafruit CircuitPython 8.1.0-beta.0 documentation
Differences from MicroPythonο
CircuitPython:
- Supports native USB on most boards and BLE otherwise, allowing file editing without special tools.
- Floats (aka decimals) are enabled for all builds.
- Error messages are translated into 10+ languages.
- Concurrency within Python is not well supported. Interrupts and threading are disabled. async/await keywords are available on some boards for cooperative multitasking. Some concurrency is achieved with native modules for tasks that require it such as audio file playback.
I'm only familiar with MicroPython on the Raspberry Pi Pico/PicoW boards but the first two items are true for MicroPython on those boards as well. Interrupts definitely work and the _thread module provides some of full Python's threading capability which admittedly is not that great to begin with.
Adafruit's CircuitPython fork of MicroPython makes a lot of sense for them from a business standpoint, I just prefer not to use their proprietary libraries.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.