@max1996 sorry to hear about your confusion. You have mentioned three concepts here which I try to distinguish them. The development of AOT is separate from microTVM and Zephyr RTOS. - AOT is a new runtime where the runtime doesn't need to parse the graph json on the target and therefore can save a lot of memory. - microTVM could use the AOT or use the previous graph runtime. Using AOT allows us to fit larger models since we saved lots of memory by removing graph parser. - And then we have Zephyr RTOS. Currently, we use Zephyr RTOS since it is popular and easy to use for development. However, microTVM and AOT could potentially be implemented in a bare metal microcontroller or other RTOSs (Mbed OS, TI-RTOS, Arduino, ...). That being said, most of our current developments and demos are based on Zephyr. For example: - - [AOT Demo](https://github.com/apache/tvm/tree/main/apps/microtvm/zephyr/aot_demo) implements an AOT demo for microTVM using ZephyrRTOS. - - [Host Driven](https://github.com/apache/tvm/tree/main/apps/microtvm/zephyr/host_driven) implements a demo for microTVM using graph executor runtime again on ZephyrRTOS.
There are efforts on adding [Project API](https://discuss.tvm.apache.org/t/rfc-tvm-project-api/9449) feature which makes integration of any RTOS much smoother. Therefore, the development of AOT and microTVM will be generic and each RTOS will have its own project API development files in TVM. Hope this makes it clear and happy to follow up. --- [Visit Topic](https://discuss.tvm.apache.org/t/what-is-the-current-plan-for-embedded/10304/2) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/6cdd5b17e81fd07d80e06603c34ed7473ad6861fd345f1a55e4efed1609a420e).
