Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One firmware build for esp32s3 #137

Closed
bwhitman opened this issue Sep 11, 2023 · 1 comment
Closed

One firmware build for esp32s3 #137

bwhitman opened this issue Sep 11, 2023 · 1 comment
Labels
tulipcc Tulip CC hardware

Comments

@bwhitman
Copy link
Collaborator

As we see things like the T-Deck happen we should just have one build, as right now tulip.upgrade() will fail on T-Deck. It doesn't seem to matter about NVS size (8,16,32), but we could do boot time checks for hardware and then load in the right "drivers". Likewise for screen size.

@bwhitman bwhitman added the tulipcc Tulip CC hardware label Sep 19, 2023
@bwhitman
Copy link
Collaborator Author

bwhitman commented Jan 20, 2024

TODO here:

  • use variants under esp32s3 for any esp32-s3 build, conditional ifdefs for compiling, pinouts, display type, etc
  • support tulipr10 (N32R8) (temporarily, MaTouch 7 N16R8 until release)
  • support tdeck (N16R8)
  • support bare esp32-s3 N16R8 and N32R8 (for r9 board, or breakout / breadboard)
  • build system that builds all 4 and puts bins for OTA on Tulip World
  • startup FS included part of package -- probably separate bin
  • tulip.upgrade() detects platform and pulls correct bin for partition type and board type
  • tulip.upgrade() also upgrades FS (?) (optionally?)
  • factory flashing setup for r10 when ready
  • test on DIY tulip and TDECK

bwhitman added a commit that referenced this issue Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tulipcc Tulip CC hardware
Projects
None yet
Development

No branches or pull requests

1 participant