Difference: CompilingNopMicroPython (4 vs. 5)

Revision 52020-05-07 - UliRaich

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Compiling Micropython

Forcing the correct module versions

Line: 34 to 37
  modules.png
Deleted:
<
<

Making upysh commands available

In boot.py you find the commands executed when booting up MicroPython. This file is created in ../ports/esp32/modules/inisetup.py. I added the command:

from upysh import *

which gives you access to all upysh commands. Type man to see the commands available.

upysh.png

 

Including user C modules

Sometimes it may be needed to write modules in C, which can be called by MicroPython. A typical example is the readout of the DHT11 when we want to get access to the raw data sent through the DHT11 proprietary protocol. The serial data bits come in too fast to be treated by Python code. To include such a module we add a user_module (could be any name) directory in which we create the module directory (dht11Raw in case of the DHT11). Into this directory we put the C code and a micropython.mk file.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback