Commit Graph

12 Commits

Author SHA1 Message Date
RetiredWizard
5effb26cd1 Pin name consistency changes 2023-10-22 03:21:03 -04:00
RetiredWizard
12a3a62ae5 Add GPIO pins broken out on Mabee connector 2023-10-21 22:49:34 -04:00
RetiredWizard
9d1b9b3c0d Add/Remove correct board level devices 2023-10-21 15:46:05 -04:00
RetiredWizard
8cc9038af0 Makerfabs pin name changes for consistency 2023-10-21 14:30:01 -04:00
RetiredWizard
8e85358a72 DotClick Touch Screen pin fixes/additions 2023-10-20 00:45:21 -04:00
Scott Shawcroft
d6b284ebb0
Merge pull request #8411 from tannewt/update-idf
Update to ESP-IDF 5.0
2023-09-22 09:45:35 -07:00
Jeff Epler
67e15bb6a2
makerfabs_tft7: rename properties to match docs 2023-09-18 10:35:49 -05:00
Scott Shawcroft
952118f6c3
Update new boards. Reduce memory use in S2 2023-09-14 11:19:38 -07:00
Jeff Epler
5e26862b2c
Allow use of CONFIG_SPIRAM_USE_CAPS_ALLOC
.. and switch makerfabs tft7 over to it as a test.

We have our existing way of "reserving" PSRAM for esp-idf (we actually
control it all but add back the "reserved" part). However, this does
not work with off the shelf esp_lcd, which only will allocate a
framebuffer in PSRAM if CONFIG_SPIRAM_USE_CAPS_ALLOC (or CONFIG_SPIRAM_USE_ALLOC)
is defined, not if CONFIG_SPIRAM_USE_MEMMAP is.

This new way is possibly compatible with more esp-idf code, but it complicates
CircuitPython's initial startup since nothing until port_heap_init is
permitted to use the CP heap or supervisor allocator. In practice this
seems to be OK today.

Right now this doesn't change the setting across all boards with PSRAM and so
it does not revert esp-idf to its prior state. Instead, what I'm thinking is
that we can do it during or just after the IDF5 update when sdkconfig files
will be getting an overhaul anyway.
2023-09-05 12:43:22 -05:00
Jeff Epler
9dcc0b5056
fix those pesky pid/vid duplicates 2023-08-30 10:58:52 -05:00
Jeff Epler
fb15c7ca51
Fix timings table & remove redundant comment 2023-08-30 10:50:16 -05:00
Jeff Epler
494aee62b3
Add makerfabs 7" 800x480 TFT
this is working, though it has to be down-clocked to 6.5MHz to prevent
display glitching
2023-08-30 10:30:54 -05:00