for comparison with other RP2040:where did you get this pinout?))
WaveShare RP2040 Zero pinout
Raspberry Pico pinout
Seeed Studio XIAO RP2040 pinout, Micropytyon numbers are GP numbers on others pinouts, by example, P27 = GP27; A# equal to ADC;
WaveShare RP2040 Zero pinout
Raspberry Pico pinout
Seeed Studio XIAO RP2040 pinout, Micropytyon numbers are GP numbers on others pinouts, by example, P27 = GP27; A# equal to ADC;
Do you have to connect GP25 with GND to enable the RGB LED???
This is the first time I have seen this!
Post automatically merged:
@Tafty Do you know anything about GP25? Have you seen the pinout which was posted by @szubiennica ?
On that RP2040 the included devices are crazy, by example on the Waveshare RP2040 Zero, there is no "Traditional" LED_BUILTIN per se, only there are a "Neo pixel" LED connected to GPIO 16 (GP16), you can not "turn on and off" the neopixel just putting a GPIO on HIGH or LOW, you need a library and send parameters to it.
On the Seeed Studio XIAO RP2040 there are three normal LEDs connected to GPIO 16, GPIO 17 & GPIO 25 and to to VCC trough a Resistor, so if you like to use them you need to define the pins as Output and on state LOW for turn them ON (yeah contraintuitive), they are MICRO and are near a Red LED of ON which is always turn ON when the RP have power.
The LED_BUILTIN variable is an alias of GPIO 17 (Red one)/
The LEDs have colors, GPIO 16 Green, GPIO 25 Blue and GPIO 17 Red.
The Raspberry Pico have a normal Red LED connected to the GPIO 25 and to GND trough a resistor, so for turn on you need to output HIGH, also the variable alias LED_BUILTIN is GPIO 25.
GPIO 25 is the second pin (up to down) under the Chip, seems what if you put a Switch between GND (the upper pin) you can select if to use GRB or RGB for the NeoPixel
By the Way the Seeed Studio XIAO the Neo pixel is connected to GPIO 12, and the GPIO 11 enable it.
The WaveShare Zero have the Neo pixel always enabled.
By the Way the Seeed Studio XIAO the Neo pixel is connected to GPIO 12, and the GPIO 11 enable it.
The WaveShare Zero have the Neo pixel always enabled.
I didn't even know there was such a thing as a GRB led!!!
I don't like that the firmware uses gp25 to select the rgb mode. What if you use a pi pico with a red led AND also a RGB led on gpio 16?
Attachments
No.
A neopixel RGB on gpio 16 and a normal LED on GP25 like in the photo which I have posted above.
The green highlighted component is a LED. The black component is a 1k resistor.
Post automatically merged:
Would this enable the "GRB" mode?
Post automatically merged:
On this board I found there is a normal LED connected through a resistor to gp25 and a NeoPixel rgb connected through gp16 and a resistor.
Should the gp16 LED be removed?
Last edited by FruithatMods,
no necesary, the GPIO16 led is a normal led, you can keep it for other "output" and yes any LED needs a resistor in series with it.
Maybe the user can just desolder the LED if they don't need it? Or do you think this is too complicated?
The idea behind this is that you can use the board with normal rp2040 firmware images for your other projects. I really don't know if I should keep this led or remove it...
no need to complicate removing things if you don't enable on firmware will be there doing nothing.
I am confused. Isn't this GRB/RGB mode "switch" programmed in the "ubuntu firmware"?
Attachments
I think I will keep the default LED on GP25. It can be removed with a soldering iron if it needs to be removed.
Eyyy, we really need an open source firmware.
Eyyy, we really need an open source firmware.
I need to get a new lite:tm: After accidentally making it an AutoRCM Lite
Yes it is, because if you have a point missing it will tell you which one... Maybe thats for adding an additional led for placement in a more visible location(probably for the light.
Maybe I should order one and find out
Can you show a picture of your pinout on a mariko. I'm using the standard hwfly pinout for an oled chip
Similar threads
