ducalex

I think you should start over with this PR, it should really only include rg_input.c. I think we got out of sync a bit...

But your code is still incompatible with https://github.com/ducalex/retro-go/commit/8def604d5360fe4a6149f03ee926add5022cf021 because I removed driver 32. You should move your change to the `RG_GAMEPAD_DRIVER == 1` block instead, something like: ```` #ifdef RG_TARGET_RETRO_ESP32...

1. The only prerequisite is having a functional [esp-idf environment](https://docs.espressif.com/projects/esp-idf/en/v4.1.3/get-started/index.html), it already contains the python dependencies. 2. You can follow the [ODROID-GO schematics](https://github.com/hardkernel/ODROID-GO/blob/master/Documents/ODROID-GO_REV0.1_20180518.pdf) and you can look at the `components/retro-go/targets/odroid-go.h`...

It still works on the esp32, the worst HWM I can achieve is 1060 which is low but still fine. So it probably has to do with you compiling for...

> E (584) spi: spi_bus_initialize(756): SPI bus already initlized. > I'd like to use separate SPI buses for SD card and LCD, but I suppose it's impossible due to lack...

Thanks for looking up the backtrace. I don't know why esp-idf itself would crash. My best guess would be a SPIRAM issue. You can try commenting line 854 in rg_system.c...

Yeah 4MB is what we'd expect. I'm not sure it's a SPIRAM issue per se but something seems to be corrupting the heap table? Because it seems to crash when...

I've tested esp-idf 4.4.1 compiling retro-go for target odroid-go and it boots correctly on a bare esp32-wrover module (as far as I can tell, I don't have a compatible LCD...

The first problem I see is that you use GPIO16 and 17 but on the WROVER they are used by PSRAM¹ (I don't think they are even exposed, so this...

If I may suggest maybe you can try getting it to work with the original pinout first, and then try moving peripherals around. > PS. I'm still learning the ESP...