Hi there,

I bought a HRAP3 on eBay with the Pi Pico board and GP2040 pre-installed, and it is currently unresponsive on PC, MiSTer and Switch, save for the L3 and R3 buttons, which light up when I test the stick under 'game controllers' on PC. The HRAP shows up as an Xbox 360 controller on PC, a console the firmware doesn't support as far as I'm aware, so I'm wondering if this is an issue with the xinput/dinput/console settings - could you please let me know how to switch between these without opening up the stick, if possible? I've tried uninstalling the device on my PC and seeing if I can get it to register as a generic controller instead, but this didn't help. Is there anything else I can try? (I'm completely unfamiliar with GP2040 itself, but would be up for reinstalling it and doing some tinkering if necessary - please point me in the right direction!)

Thank you very much for your help!

Mike

I don't think many sticks have a native button for RS and LS, wouldn't it be better to but it on a button that is always there and never plugged up like one of B1-4? For example I tend to only use 6 buttons, and I've known people in the past to only use 3 (for VF) or 4 (for SNK) and plug up the rest.

Also, this is a cool project, I ordered a pico and am looking forward to trying it in my stick.

I've added optional configuration for default mode values so that they can be changed on a per board basis. I've also added optional LED support. It's very basic--blink the pressed button if LEDs are configured for that button--but it's enough to prove things out.

The LED setup has two (future) problems:

We're limited to a single LED per button. There are a number of things out there at the moment that have multiple per button. The big hold up is the inability to create an array with #defines, but I'm hesitant to start storing actual variables in the board configuration files. Open to suggestions here. TOML or something would be more muggle friendly, but it's a lot more work than just defining some constants.

It needs to be migrated out of main.cpp into somewhere we can easily manage the current state for animations. Button presses should be telling this class "hey man, animate this button" and not worrying about handling the actual animation.

say you are able to hold down a layer button to temporarily enable the dpad buttons to emulate analog stick(s) output. or a dip switch to change switch to analog stick(L/R) emulation.

There is a relatively common issue where if the Pico/RP2040 device has been previously flashed with something other than GP2040, the area of flash used for emulated EEPROM could contain invalid values causing the firmware to misbehave (locked to certain input type, buttons might not work, etc.).

Add CRC check to the EEPROM data and perform an EEPROM reset if the CRC does not match when loaded.

Hello, I'm thinking about getting a Raspberry Pico to test this, but it seems that there are different memory sizes available, from 2MB to 16MB. From what I've seen the uf2 file is a little less than 2MB, so would the 2MB flash memory be enough or should I get the one with 4MB+?

Create a page in the config app to allow enabling and configuring LED support. This will require some refactoring since the LED code is conditionally included. Should include everything from the RGB LED section of the dev doc: https://feralai.github.io/GP2040/#/development?id=rgb-leds

Define an interface for libraries to be able to plug into GP2040. Would likely have the following traits (plus more I'm sure):

• Main module code will run on core1
• Modules will likely need their own way to setup() and loop() on the core1 thread
• May need to integrate defines in BoardConfig.h
• Can rely upon receiving GamepadState to perform actions (flash LEDs, display status, make noise, etc.)

EEPROM commit no longer commits, but sets a timer for when the next write should happen. Additional writes in that gap will push the timer out so we don't hammer flash memory. When time hits, we also lock out core1 to prevent any weirdness with data access across cores.

Hi @FeralAI, I don't know if this is useful but here you have the image for the default mapping to Xbox360 controller in Windows just in case you want to use it on the documentation.

You can close this issue.

Thank you for your work.

(Same as https://gp2040.info/#/usage?id=buttons)

i have my input mode normally set to xinput with dpad mode to d-pad but it gets randomly switched to left or right analog while i'm using the controller.

Hey folks,

The main GP2040 is no longer being maintained.

We have been working hard at a community edition over at GP2040-CE (https://github.com/OpenStickFoundation/GP2040-CE).

If you need help with either GP2040 or GP2040-CE please check us out on Discord via the new link here: https://discord.gg/qVcrGVDj2h

1.On Win10, Switch Mode can be recognized as: POKKEN CONTROLLER (Vendor: 0f0d Product: 0092).But when I plugged it into the Switch, I couldn't recognize it!

2.Can you increase support for Xbox 360 game console?

Hi, i have an SSD1306 128x64 OLED display, and it freezes about 10 seconds the stick is plugged in. Hot-plugging the OLED makes it work for another ten seconds or so.

Also, after powering down the stick, if i plug it back in right away the display rarely comes up. Hot-plugging the OLED does nothing there.

I have a couple more OLEDs on order from another seller and will try to figure out if the display itself is the issue.

I use latest wizio-pico, and, patch the tinyusb_gamepad commit(Updated to support latest TinyUSB version #79), then, the init adc is not work.

I init adc in Gamepad::setup method, like:

adc_init(); adc_gpio_init(26); adc_gpio_init(27); adc_gpio_init(28);

and, in Gamepad::read method: update joystick like:

adc_select_input(0); state.lx = (adc_read() >> 4) << 8; adc_select_input(1); state.ly = (adc_read() >> 4) << 8;

it worked before, but, now it not work, I am sure it not my hardware problem, and, not the code problem, it must be some latest lib update break something