![Crying or Very Sad :cry:](./images/smilies/icon_cry.gif)
Micropython architecture
Micropython architecture
What should be my answer, if someone asks me to explain the architecture of micropython ![Crying or Very Sad :cry:](./images/smilies/icon_cry.gif)
![Crying or Very Sad :cry:](./images/smilies/icon_cry.gif)
lnsri22 ![Smile :)](./images/smilies/icon_e_smile.gif)
![Smile :)](./images/smilies/icon_e_smile.gif)
Re: Micropython architecture
Interpreter running directly on the hardware without any thing in between.
(which is not correct for the ESP32 Port because this one has RTOS between Micropython an the hardware!)
I think there are many possible right answers to this question.
(which is not correct for the ESP32 Port because this one has RTOS between Micropython an the hardware!)
I think there are many possible right answers to this question.
Re: Micropython architecture
Thomas, thanks for the quick reply!!
This is nice and catchy!!
In other ways to put this question, I would like to understand how modules/sources are inter-linked and how a firmware is built for a particular port
Thanks again!!![Smile :)](./images/smilies/icon_e_smile.gif)
This is nice and catchy!!
In other ways to put this question, I would like to understand how modules/sources are inter-linked and how a firmware is built for a particular port
Thanks again!!
![Smile :)](./images/smilies/icon_e_smile.gif)
lnsri22 ![Smile :)](./images/smilies/icon_e_smile.gif)
![Smile :)](./images/smilies/icon_e_smile.gif)
-
- Posts: 2
- Joined: Wed Oct 02, 2019 9:11 pm
Re: Micropython architecture
could you please tell me why esp32 Port has RTOS between Micropython and the hardware?
I have searched for the reason but I couldn't find the answer, So could you please tell me why and where should I search to get more information about the RTOS implementation.
I have searched for the reason but I couldn't find the answer, So could you please tell me why and where should I search to get more information about the RTOS implementation.
Re: Micropython architecture
The simple answer is that's how the development tools for the ESP32 work -- they (Espressif) provide you with a whole SDK (the "ESP IDF") based on FreeRTOS, so it's definitely a much easier base to work from.
I guess in theory there's no reason someone couldn't adapt the code from the IDF and write a bunch of low level drivers, however some parts of the IDF do not have source code available (e.g. the wifi driver). (I do not know how much these binaries depend on being run in FreeRTOS thoug).
I guess in theory there's no reason someone couldn't adapt the code from the IDF and write a bunch of low level drivers, however some parts of the IDF do not have source code available (e.g. the wifi driver). (I do not know how much these binaries depend on being run in FreeRTOS thoug).