Replies: 1 comment
-
Good idea re discussions, enabled! :) I’ve been thinking about it too. Most of the Pico-umac code is rp2040/2350 specific, ie video output and tinyUSB stuff (tho the latter ought to work on other tinyUSB platforms). We could split it into RP2 platform vs ESP etc., each providing video output and other HW-specific code. I have an ESP32-C3 which has a reasonable amount of SRAM; I haven’t yet played with the SDK tho. There’s at least no assembler so nothing Armv6m-specific. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
More a question than anything (maybe it'd be a good idea to open GitHub Discussions for this project so that we don't have to use Issues for questions):
How RP2040 specific is this code?
How hard do you think it would be to port this to, e.g., the ESP23-S3? Part of the reason I am asking this is that there are relatively inexpensive clones of the ESP32-S3-DevKitC-1 featuring
At this point the work should probably stay focused on one target system rather than different ones, so I am not saying the hardware platform should be changed, I am just genuinely wondering how closely coupled to the RP2040 this code base is.
Beta Was this translation helpful? Give feedback.
All reactions