Add Feather RP2040 DVI (plz read)#7695
Conversation
Based on Feather RP2040 SCORPIO, but new USB PID (from MBAdafruitBoards/Production) and pin name changes for GP16-23 (CKN/CKP etc., from board schematic).
|
I am not an expert... but I believe the solderparty_rp2040_stamp is using a mechanism to have multiple "personalities" depending on the daughter board the stamp reside on. PS: I am interested in how the RP2040 bones(?) derived board will be integrated... I really want the DVI and the USB Host one (I already have a Scorpio). |
dhalbert
left a comment
There was a problem hiding this comment.
Looks fine! I added some blank lines for clarity.
I think so. |
|
@PaintYourDragon Note that it's better to create a branch for your PR rather than edit your |
Prob don’t want to merge this as-is, it’s an experiment as I learn the ropes.
There will be a number of incoming boards based on a common RP2040 design…very similar to the SCORPIO design, with an extra eight consecutive GPIO connected to special functions. Most of these should be very simple to add here: copy the adafruit_feather_rp2040_scorpio directory to a new name, then edit the files within to assign this board a unique USB PID and to provide names for the extra GPIOs (e.g. CKN, CKP, etc. in this one). So initially this is just a test to see that I’ve got that aspect right.
Later…the Feather RP2040 DVI will be an odd one in that it’s overclocked (TBD whether this happens on startup or doesn’t switch over until user code specifically enables DVI out)…but also, at very high overclock settings, may need to use QSPI clock div4 instead of div2. No simple settings for these things in the aforementioned files, presumably this will involve digging deeper into CircuitPython source. The USB host Feather might also involve some overclocking.
So, just need to know, do the changes here look about right for one of these future Feathers that just need a name and PID and then names assigned to special pins? None of the weird overclock stuff, just special I/O. Thx.