GP2040 VS pico-sdk

I think they use https://github.com/FeralAI/GP2040

I've had a great experience with Arduino Pro Micro's running the DaemonBite firmware, and the RPi Pico GP2040 firmware should be similarly great. Both have extremely low latency. The Brook Universal board is another good one. Other than that, I usually just use either a DualShock 3 pad over USB or a wired 360 pad. I also like the iBuffalo SNES pad and Logitech Precision pads.

My third revision of this and looking for feedback to improve. I'm using an secondary USB-C port here to test this schematic before using it on other builds where the Pico placement is constrained by board clearances and mounting holes. The Pico is running GP2040, https://github.com/FeralAI/GP2040, which allows the device to work on multiple systems. I'm new to PCB design and have grabbed some examples posted here before and hopefully following guidelines in the wiki.

It might also be worth checking out the pi pico as the brains, though I believe you need a second piece of hardware to make it work on ps4. The pi pico itself should only be 10$~ not sure how much the ps4 adapter thing would cost. The firmware to look into is https://github.com/FeralAI/GP2040

Hi, does anyone know how to add a PS Home button to your controller? I have a DURAL hitbox which uses GP2040 Firmware (https://github.com/FeralAI/GP2040). I was planning on going to an offline event and needed to make my controller PS4 proof for which I was hoping to use a PS3 to PS4 adapter. However I would still need the PS Home button because PS4 is weird. If anyone knows a solution help would be greatly appreciated.

Microsoft totally does. That's why GP2040, an open source controller firmware, doesn't support Xbox or PS. The way it's typically done now is to have a require a real controller to handle the authentication, with the 3rd party input in between the real controller and the console (passthrough in that chart)

In the Pico SDK repository, find the external/pico_sdk_import.cmake file

https://github.com/raspberrypi/pico-sdk/ links to a PDF about connecting to the interwebs with a pi pico.

micropython/micropython//ports/rp2/boards/RPI_PICO_W: https://github.com/micropython/micropython/tree/master/ports...

raspberrypi/pico-sdk /lib: btstack, cyw43-driver, lwip, mbedtls, tinyusb https://github.com/raspberrypi/pico-sdk/tree/master/lib

raspberrypi/pico-examples//pico_w/wifi/access_point/picow_access_point.c:

https://github.com/raspberrypi/pico-examples/blob/master/pic...

There's an iperf opkg pkg, or is it just netperf (which works with fluent)?

raspberrypi/pico-examples//pico_w/wifi/iperf/picow_iperf.c:

Relevant link: https://github.com/raspberrypi/pico-sdk/issues/979

There is an official sdk in C and C++ as well as a really thorough sdk guide, and a separate "getting started" guide which shows you how to upload files using command line and vs code.

Arch is using Gcc 13.0.1 and there's a bug fix that I had to manually apply so that uint16_t could be resolve. See https://github.com/raspberrypi/pico-sdk/pull/1318/files.

the LED of the W is hooked to the wireless chip. in the c sdk, the function to tell the chip to set it's gpio pin(s) is: cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, 1); where CYW43_WL_GPIO_LED_PIN is the macro to the LED. (https://github.com/raspberrypi/pico-sdk/blob/master/src/rp2_common/pico_cyw43_arch/include/pico/cyw43_arch.h line 468)

The latest release of the Pico Software Developer Kit (SDK) version 1.5.0 is a significant milestone in that evolution. This new version includes many exciting features, the most notable of which is Bluetooth support. Read More - https://bit.ly/3Yyb0qi