micro_python
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| micro_python [2026/07/16 09:59] – [Micro Python Examples] walkeradmin | micro_python [2026/08/18 21:51] (current) – [Micro Python Examples - Pico] walkeradmin | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| {{ : | {{ : | ||
| ---- | ---- | ||
| - | ===== Introduction ===== | ||
| - | \\ | ||
| - | <color # | ||
| - | \\ | ||
| - | \\ | ||
| - | MicroPython is a tiny, efficient version of Python designed to run on microcontrollers like the Raspberry Pi Pico. If regular Python is a full toolbox, MicroPython is the compact, ultra‑portable version that still lets you build amazing things. | ||
| - | \\ | ||
| - | \\ | ||
| - | Here’s the essence of it: | ||
| - | \\ | ||
| - | ==== What MicroPython actually is ==== | ||
| - | MicroPython is: | + | ==== Micro Python Examples |
| - | + | \\ | |
| - | * A lightweight Python interpreter | + | Here are some Micro Python programs for you to try. Please bear in mind that these examples will likely require you to build some basic hardware (A Pico with, LEDs or buttons etc) before you can test the Micro Python code itself. In the Projects Section, there will be files for building the project hardware, software and 3D print files for the casing etc. Many of these examples will work with Raspberry Pi and other RP based devices. |
| - | + | ||
| - | * Designed for small, low‑power devices | + | |
| - | + | ||
| - | * Fast to start (boots in milliseconds) | + | |
| - | + | ||
| - | * Able to control hardware directly (GPIO, I2C, SPI, PWM) | + | |
| - | + | ||
| - | It gives you the power of Python, but trimmed down so it fits into devices with **tiny memory and low CPU power.** | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | === Why MicroPython exists === | + | |
| - | + | ||
| - | Traditional Python needs: | + | |
| - | + | ||
| - | * An operating system | + | |
| - | + | ||
| - | * Lots of RAM | + | |
| - | + | ||
| - | * A full CPU | + | |
| - | + | ||
| - | Microcontrollers like the Pico have: | + | |
| - | + | ||
| - | * No OS | + | |
| - | + | ||
| - | * Kilobytes of RAM | + | |
| - | + | ||
| - | * Very small processors | + | |
| - | + | ||
| - | MicroPython bridges that gap by giving you a Python‑like experience on hardware that normally only runs C or assembly. | + | |
| - | \\ | + | |
| - | \\ | + | |
| - | === What you can do with MicroPython === | + | |
| - | + | ||
| - | This is where it gets fun. You can: | + | |
| - | + | ||
| - | * Blink LEDs | + | |
| - | + | ||
| - | * Read sesors | + | |
| - | + | ||
| - | * Drive motors | + | |
| - | + | ||
| - | * Control displays | + | |
| - | + | ||
| - | * Build IoT devices | + | |
| - | + | ||
| - | * Make robots | + | |
| - | + | ||
| - | * Read buttons and switches | + | |
| - | + | ||
| - | * Communicate over Wi‑Fi (Pico W) | + | |
| - | + | ||
| - | ---- | + | |
| - | ==== Micro Python Examples ==== | + | |
| - | \\ | + | |
| - | Here are some Micro Python programs for you to try: | + | |
| \\ | \\ | ||
| + | *[[What is Micro Python]]\\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
| Line 90: | Line 25: | ||
| *[[GPIO Controlled LEDs]]\\ | *[[GPIO Controlled LEDs]]\\ | ||
| *[[Traffic Light LEDs using Array]]\\ | *[[Traffic Light LEDs using Array]]\\ | ||
| + | *[[Updated Traffic Lights Using Transistors for Improved LED Brightness]]\\ | ||
| *[[Control an LED Using a Button]]\\ | *[[Control an LED Using a Button]]\\ | ||
| *[[Control an LED using a Webpage]]\\ | *[[Control an LED using a Webpage]]\\ | ||
| + | *[[Using the Pico RUN Button - Simple]]\\ | ||
| *[[Using the Pico RUN Button]]\\ | *[[Using the Pico RUN Button]]\\ | ||
| + | *[[12 NeoPixel LED Strip - Multiple Projects]]\\ | ||
| + | *[[Using Pico with SSD1306 based LCD]]\\ | ||
| + | *[[Connect Pico to Wifi]]\\ | ||
| + | *[[Find Pico MAC Address]]\\ | ||
| + | *[[Check Device I2C Address]]\\ | ||
| \\ | \\ | ||
| Making your Raspberry Pi Pico code run on boot. | Making your Raspberry Pi Pico code run on boot. | ||
| Line 101: | Line 43: | ||
| Full Projects. <color # | Full Projects. <color # | ||
| *[[Project 1 - Coming Soon]]\\ | *[[Project 1 - Coming Soon]]\\ | ||
| + | \\ | ||
| + | \\ | ||
| + | ---- | ||
| + | ==== Micro Python Examples - Waveshare ==== | ||
| + | \\ | ||
| + | The Micro Python examples here will not work with the Raspberry Pi Pico, unless otherwise stated, as we are potentially addressing hardware not available on the Raspberry Pi Pico. These include, but are not limited to: | ||
| + | |||
| + | * USB Type-C: Replaces the standard micro-USB connector. | ||
| + | * Battery Charging Circuitry: Onboard JST connectors and recharge/ | ||
| + | * More Flash Memory: Options with 4MB or 16MB of onboard flash instead of the Pico's 2MB. | ||
| + | * Extra Pins: Extra GPIOs exposed (up to 29 on the Zero, compared to 26 on the Pico). | ||
| + | * Hardware Buttons: Dedicated Reset and BOOT buttons. | ||
| + | * OnBoard Neo Pixel instead of single colour LED | ||
| + | |||
| + | Micro Python code listed here may use some of the above features, so will not work on a Raspberry Pi Pico. | ||
| + | |||
| + | *[[Onboard NeoPixel]]\\ | ||
| + | *[[Traffic Lights]]\\ | ||
| + | |||
| + | |||
| \\ | \\ | ||
| \\ | \\ | ||
| ---- | ---- | ||
micro_python.1784195958.txt.gz · Last modified: by walkeradmin
