machine module contains specific functions related to the board.
import machine help(machine) # display all members from the machine module machine.freq() # get the CPU frequency machine.unique_id() # return the 6-byte unique id of the board (the LoPy's WiFi MAC address)
Resets the device in a manner similar to pushing the external RESET button.
Get the reset cause. See constants for the possible return values.
Disable interrupt requests. Returns and integer representing the previous IRQ state. This return value can be passed to
enable_irq to restore the IRQ to its original state.
Enable interrupt requests. The most common use of this function is to pass the value returned by
disable_irq to exit a critical section. Another options is to enable all interrupts which can be achieved by calling the function with no parameters.
Returns CPU frequency in hertz.
Gates the clock to the CPU, useful to reduce power consumption at any time during short or long periods. Peripherals continue working and execution resumes as soon as any interrupt is triggered (on many ports this includes system timer interrupt occurring at regular intervals on the order of millisecond).
Sets the device in to light sleep mode , where in this mode digital peripherals, most of the RAM, and CPUs are clock-gated, and supply voltage is reduced. Upon exit from light sleep, peripherals and CPUs resume operation, their internal state is preserved.
time_msis the time in milliseconds that the device should wakeup after, if no time is given the device will sleep until the next reset cycle unless another wakeup source is configured.
resume_wifi_bleis a boolean value that enables or disable restoring after wakeup any WiFi or BLE connection that was interrupted by light sleep.
TrueEnable WiFi/BLE connections restoration
FalseDisable Wifi/BLE connections restoration, default option is Disabled
Note: in light sleep mode LoRa/Lte modems are stopped and have to be re-initialized after wakeup.
Stops the CPU and all peripherals, including the networking interfaces (except for LTE). Execution is resumed from the main script, just as with a reset. If a value in milliseconds is given then the device will wake up after that period of time, otherwise it will remain in deep sleep until the reset button is pressed.
Products with LTE connectivity, such as the FiPy, GPy, G01, need to have the LTE radio disabled separately via the LTE class before entering deepsleep. This is necessary because the LTE radio is powered independently, which allows for use cases that wake the system from deepsleep by an event from the LTE network, for example receiving data or an SMS.
Configure pins to wake up from sleep mode. The pins which have this capability are:
P2, P3, P4, P6, P8 to P10 and P13 to P23.
The arguments are:
pinsa list or tuple containing the
GPIOto setup for sleep wakeup.
modeselects the way the configure
GPIOs can wake up the module. The possible values are:
enable_pullif set to
Truekeeps the pull up or pull down resistors enabled during sleep. If this variable is set to
ULPor capacitive touch wakeup cannot be used in combination with
Get the wake reason. See constants for the possible return values. Returns a tuple of the form:
(wake_reason, gpio_list). When the wakeup reason is either GPIO or touch pad, then the second element of the tuple is a list with GPIOs that generated the wakeup.
Returns the remaining timer duration (in milliseconds) if the ESP32 is woken up from deep sleep by something other than the timer. For example, if you set the timer for 30 seconds (30000 ms) and it wakes up after 10 seconds then this function will return
filename of the main script to run after
boot.py is finished. If this function is not called then the default file
main.py will be executed.
It only makes sense to call this function from within
Return a 24-bit software generated random number.
Returns a byte string with a unique identifier of a board/SoC. It will vary from a board/SoC instance to another, if underlying hardware allows. Length varies by hardware (so use substring of a full value if you expect a short ID). In some MicroPython ports, ID corresponds to the network MAC address.
ubinascii.hexlify() to convert the byte string to hexadecimal form for ease of manipulation and use elsewhere.
Returns the high water mark of the stack associated with various system tasks, in words (1 word = 4 bytes on the ESP32). If the value is zero then the task has likely overflowed its stack. If the value is close to zero then the task has come close to overflowing its stack.