Update docs

Author: ThomasFarstrike

docs/os-development/compiling.md

@@ -12,29 +12,19 @@
 
     <pre>
     ```
-    ./scripts/build_mpos.sh <target system> <build type (prod or dev)> [optional target device]
+    ./scripts/build_mpos.sh <target system>
     ```
     </pre>
 
     **Target systems**: `esp32`, `unix` (= Linux) and `macOS`
     
-    **Build types**:
-
-    - A `prod` build includes the complete filesystem that's "frozen" into the build, so it's fast and all ready to go but the files in /lib and /builtin will be read-only.
-    - A `dev` build comes without a filesystem, so it's perfect for power users that want to work on MicroPythonOS internals. There's a simple script that will copy all the necessary files over later, and these will be writeable.
-
-    _Note_: for unix and macOS systems, only `dev` has been tested. The `prod` builds might have issues but should be made to work soon.
-
-    **Target devices**: `waveshare-esp32-s3-touch-lcd-2` or `fri3d-2024`
-    
     **Examples**:
 
     <pre>
     ```
-    ./scripts/build_mpos.sh esp32 prod fri3d-2024
-    ./scripts/build_mpos.sh esp32 dev waveshare-esp32-s3-touch-lcd-2
-    ./scripts/build_mpos.sh esp32 unix dev
-    ./scripts/build_mpos.sh esp32 macOS dev
+    ./scripts/build_mpos.sh esp32
+    ./scripts/build_mpos.sh unix
+    ./scripts/build_mpos.sh macOS
     ```
     </pre>
 

docs/os-development/installing-on-esp32.md

@@ -4,19 +4,20 @@ But if you need to install a version that's not available there, or you built yo
 
 1. **Get the firmware**
 
-    - Download a release binary (e.g., `MicroPythonOS_fri3d-2024_prod_0.2.1.bin`, `MicroPythonOS_waveshare-esp32-s3-touch-lcd-2_prod_0.2.1.bin`, etc.)
+    - Download a release binary (e.g., `MicroPythonOS_esp32_0.5.0.bin`)
     - Or build your own [on MacOS](macos.md) or [Linux](linux.md)
 
 2. **Put the ESP32 in Bootloader Mode**
 
     If you're already in MicroPythonOS: go to Settings - Restart to Bootloader - Bootloader - Save.
 
-    Otherwise, physically keep the "BOOT" (sometimes labeled "START") button pressed while briefly pressing the "RESET" button.
+    Otherwise, physically keep the "BOOT" (sometimes labeled "START") button pressed while powering up the board.
+    This is explained in more detail at [the webinstaller](https://install.micropythonos.com/)
 
 3. **Flash the firmware**
 
     ```
-    ~/.espressif/python_env/idf5.2_py3.9_env/bin/python -m esptool --chip esp32s3 write_flash 0x0 firmware_file.bin
+    ~/.espressif/python_env/idf5.2_py3.9_env/bin/python -m esptool --chip esp32s3 write_flash 0 firmware_file.bin
     ```
 
     Add the `--erase-all` option if you want to erase the entire flash memory, so that no old files or apps will remain.
@@ -33,36 +34,30 @@ But if you need to install a version that's not available there, or you built yo
     lvgl_micropython/lib/micropython/tools/mpremote/mpremote.py
     ```
 
-5. **Populate the filesystem** (only for "dev" builds)
+5. **Populate the filesystem** (only for development)
 
-    The "dev" builds come without a filesystem so you probably want to copy:
+    In development, you probably want to override the "frozen" libraries and apps that are compiled in, and replace them with source files, which you can edit.
 
-    - the whole internal_filesystem/ folder, including main.py
-    - the appropriate device-specific internal_filesystem/boot*.py file to /boot.py on the device
-    
     There's a convenient script that will do this for you.
     
     Usage:
 
     <pre>
     ```
-    ./scripts/install.sh <target device>
+    ./scripts/install.sh
     ```
     </pre>
     
-    **Target devices**: waveshare-esp32-s3-touch-lcd-2 or fri3d-2024
 
-    Examples:
+    Example:
 
     <pre>
     ```
-    ./scripts/install.sh fri3d-2024
-    ./scripts/install.sh waveshare-esp32-s3-touch-lcd-2
+    ./scripts/install.sh
     ```
     </pre>
 
 
 ## Notes
 
-- A "dev" build without frozen files is quite a bit slower when starting apps because all the libraries need to be compiled at runtime.
 - Ensure your ESP32 is compatible (see [Supported Hardware](../getting-started/supported-hardware.md)). If it's not, then you might need the [Porting Guide](../os-development/porting-guide.md).

docs/os-development/porting-guide.md

@@ -10,23 +10,26 @@ If you prefer to have the porting work done for you and you're open to making a
 
 ## What to write
 
-By design, the only device-specific code for MicroPythonOS is found in the ```internal_filesystem/boot*.py``` files.
+By design, the only device-specific code for MicroPythonOS is found in the ```internal_filesystem/lib/mpos/board/<boardname>.py``` files.
+
 
 ## Steps to port to a new device
 
 1. Compile [lvgl_micropython](https://github.com/lvgl-micropython/lvgl_micropython) for the new device.
 
 	The goal is to have it boot and show a MicroPython REPL shell on the serial line.
 
-	Take a look at our [build_mpos.sh](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/scripts/build_mpos.sh) script. A "dev" build (without any "frozen" filesystem) is preferred as this will still change a lot.
+	Take a look at our [build_mpos.sh](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/scripts/build_mpos.sh) script.
 
 	Also go over the [official lvgl_micropython documentation](https://github.com/lvgl-micropython/lvgl_micropython/blob/main/README.md) for porting instructions. If you're in luck, your device is already listed in the esp32 BOARD list. Otherwise use a generic one like `BOARD=ESP32_GENERIC` with `BOARD_VARIANT=SPIRAM` or `BOARD=ESP32_GENERIC_S3` with `BOARD_VARIANT=SPIRAM_OCT` if it has an SPIRAM.
 
 2. Figure out how to initialize the display for the new device
 
-    Use the MicroPython REPL shell on the serial port to type or paste (CTRL-E) MicroPython code.
+    Use the MicroPython REPL shell on the serial port to type or paste (CTRL-E) MicroPython code manually at first to see what works.
 
-    Check out how it's done for the [Waveshare 2 inch Touch Screen](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/boot.py) and for the [Fri3d Camp 2024 Badge](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/boot_fri3d-2024.py). You essentially need to set the correct pins to which the display is connected (like `LCD_SCLK`, `LCD_MOSI`, `LCD_MOSI` etc.) and also set the resolution of the display (`TFT_HOR_RES`, `TFT_VER_RE`S).
+    Take a look at [```waveshare_esp32_s3_touch_lcd_2.py```](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/lib/mpos/board/waveshare_esp32_s3_touch_lcd_2.py) or [```fri3d_2024.py```](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/lib/mpos/board/fri3d-2024.py).
+
+    You essentially need to set the correct pins to which the display is connected (like `LCD_SCLK`, `LCD_MOSI`, `LCD_MOSI` etc.) and also set the resolution of the display (`TFT_HOR_RES`, `TFT_VER_RE`S).
 
     After a failed attempt, reset the device to make sure the hardware is in a known initial state again.
 
@@ -47,17 +50,16 @@ By design, the only device-specific code for MicroPythonOS is found in the ```in
     ```
     </pre>
 
-3. Put the initialization code in a custom boot_...py file for your device
+3. Put the initialization code in a custom ```<boardname>.py``` file for your device
 
-4. Copy the custom boot_...py file and the generic MicroPythonOS files to your device (see [install.sh](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/scripts/install.sh)
+4. Copy the custom ```<boardname>.py``` file and the generic MicroPythonOS files to your device (see [install.sh](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/scripts/install.sh)
 
-    After reset, your custom boot_...py file should initialize the display and then MicroPythonOS should start, run the launcher, which shows the icons etc.
+    After reset, your custom ```<boardname>.py``` file should initialize the display and then MicroPythonOS should start, run the launcher, which shows the icons etc.
 
 5. Add more hardware support
 
-    If your device has a touch screen, check out how it's initialized for the [Waveshare 2 inch Touch Screen](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/boot.py).
-    If it has buttons for input, check out the KeyPad code for the [Fri3d Camp 2024 Badge](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/boot_fri3d-2024.py).
+    If your device has a touch screen, check out how it's initialized for the [Waveshare 2 inch Touch Screen](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/lib/mpos/board/waveshare_esp32_s3_touch_lcd_2.py). If it has buttons for input, check out the KeyPad code for the [Fri3d Camp 2024 Badge](https://github.com/MicroPythonOS/MicroPythonOS/blob/main/internal_filesystem/lib/mpos/board/fri3d-2024.py).
 
     Now you should be able to control the device, connect to WiFi and install more apps from the AppStore.
 
-    This would be a good time to create a pull-request to merge your boot_...py file into the main codebase so the support becomes official!
+    This would be a good time to create a pull-request to merge your ```<boardname>.py``` file into the main codebase so the support becomes official!