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

Review RTOS options for running ESP32 radios #20

Open
3 tasks
tcr opened this issue Feb 18, 2017 · 0 comments
Open
3 tasks

Review RTOS options for running ESP32 radios #20

tcr opened this issue Feb 18, 2017 · 0 comments
Assignees
Labels

Comments

@tcr
Copy link
Member

tcr commented Feb 18, 2017

This probably falls into the category of "use what's in the dev kit", but: We should determine what OS the ESP32 needs to run in order to meet Reach's criteria.

In the past (see the SAMD21 running on T2) we've used a self-written firmware that runs directly on the metal to power our hardware applications. We also (in the T1) have integrated with Wifi radio event loops in a bare metal environment. FreeRTOS, which the esp-idf ships with, is higher level than what we've worked with before, and represents a set of trade-offs we should be explicit about. If the alternative is to run a bare-metal firmware, or an alternative RTOS like NuttX, etc. we want to pick the best tool for the job.

TODO:

  • Determine if the ESP32 requires the FreeRTOS stack to power its radio stack
  • See if bare-metal code examples running on the ESP32 exist
  • Create a tradeoffs list for each of our options and select a path forward for A) prototyping and B) production (these may be different)
@tcr tcr self-assigned this Feb 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant