diff --git a/Sming/Libraries/FatIFS b/Sming/Libraries/FatIFS
index 4def3ea474..56360c2662 160000
--- a/Sming/Libraries/FatIFS
+++ b/Sming/Libraries/FatIFS
@@ -1 +1 @@
-Subproject commit 4def3ea474a800d9c9458e62b73b8d45575f8fee
+Subproject commit 56360c26623b57e7c03de225d6b3141e181a37f7
diff --git a/docs/source/information/flash.rst b/docs/source/information/flash.rst
index e999b304ac..e835bc0282 100644
--- a/docs/source/information/flash.rst
+++ b/docs/source/information/flash.rst
@@ -8,13 +8,15 @@ Introduction
 
 ESP8266 flash memory sizes vary from 512Kbytes on the ESP-01 up to 4Mbytes on the ESP12F.
 Up to 16MBytes are supported for custom designs.
+Rp2040 has similar support, and the Esp32 has enhanced VMM (Virtual Memory Management) hardware.
 
 Sming version 4.3 introduced partition tables to support multiple architectures,
 different hardware variants and custom flash layouts without restriction.
+It is binary compatible with the Esp32 IDF partition tables but with a consistent API across all architectures.
 
 See :ref:`hardware_config` for details.
 
-A typical layout for a 4MByte device might look like this:
+A typical layout for a 4MByte Esp8266 device might look like this:
 
    =======  ===============   ====   =========================  ===================================================                                
    Address  Config variable   Size   Source filename            Description            
@@ -51,13 +53,14 @@ A typical layout for a 4MByte device might look like this:
    3FC000                     4      esp_init_data_default.bin  PHY configuration data            
    3FD000                     12     blank.bin                  System parameter area
    =======  ===============   ====   =========================  ===================================================            
-   
+
+The actual layout in use can be seen by running ``make map``.
 
 
 Speed and caching
 -----------------
 
-Flash memory on the ESP8266 is accessed via an external SPI bus, so reading it takes about 12x
+Flash memory is accessed via an external SPI bus, so reading it takes about 12x
 longer than reading from internal RAM. To mitigate this, some of the internal RAM is used to
 cache data. Part of this is managed in hardware, which means if the data required is already in
 the cache then there is no difference in speed. In general, then, frequently accessed data is read
diff --git a/docs/source/information/memory.rst b/docs/source/information/memory.rst
index 675881c379..4b6d5d151c 100644
--- a/docs/source/information/memory.rst
+++ b/docs/source/information/memory.rst
@@ -1,6 +1,8 @@
 Memory
 ======
 
+This section refers to the ESP8266 but is applicable to all device architectures.
+
 Map
 ---
 
@@ -10,7 +12,7 @@ You can find a map for the ESP8266 memory layout in the `Wiki <https://github.co
 Memory Types
 ------------
 
-The ESP8266 has several types of memory, and it is important to have a basic apprecation of what they
+There are several types of memory, and it is important to have a basic apprecation of what they
 are and how they're used.
 
 DRAM
@@ -68,30 +70,36 @@ directly from Flash memory on hardware reset.
 BIOS
 ~~~~
 
-The ESP8266 and ESP32 are far more complex, and most of the low-level initialisation
-happens in the ROM code. The ROM essentially contains the systems BIOS, with various
+Most of the low-level initialisation happens in the ROM code.
+The ROM essentially contains the systems BIOS, with various
 low-level routines which may be used instead of accessing hardware directly. It is
 also responsible for setting up memory caching.
 
 Runtime libraries
 ~~~~~~~~~~~~~~~~~
 
-Control is passed to runtime libraries provided by Espressif, stored in Flash memory.
-Both ROM and runtime code are closed-source and not generally available for inspection,
+For Espressif devices, control is passed to the SDK runtime libraries, stored in Flash memory.
+The ROM and some runtime code are closed-source and not generally available for inspection,
 though disassemblies do exist.
 
 Boot loader
 ~~~~~~~~~~~
 
-The first point we really see what's going on is in the bootloader (rBoot).
+The first point we really see what's going on is in the bootloader.
+
+This is :component:`rboot` for the Esp8266; the Esp32 bootloader is part of the SDK.
 The bootloader identifies the correct program image (as there can be more than one),
-loads the starting portion into IRAM and jumps there. It also configures the caching
-mechanism so that the correct program image is  loaded.
-You can find more details about this in the :component:`rboot` documentation.
+
+The Rp2040 bootloader is more basic as it only supports booting one image.
+
+In all cases, the bootloader loads the starting portion of the program image into IRAM and jumps there.
+It also configures the caching mechanism so that the correct program image is loaded.
 
 Memory initialisation
 ~~~~~~~~~~~~~~~~~~~~~
 
+This is done by startup code in the SDK before passing control to Sming.
+
 Code is copied from flash into IRAM, and *const* data copied into DRAM.
 Also static and global variable values are initialised from tables stored in flash.
 Static and global variables without an initialised value are initialised to 0.
@@ -99,7 +107,29 @@ Static and global variables without an initialised value are initialised to 0.
 Sming initialisation
 ~~~~~~~~~~~~~~~~~~~~
 
-{todo}.
+This varies between architectures but involves the following general tasks:
+
+Initialize hardware
+   e.g. system clocks, timers, RTC
+
+Invoke C++ initializers
+   static/global constructors get called.
+   We only need to do this for the Esp8266, the SDK handles it for other architectures.
+
+Load partition table
+   Reads partition information from flash into RAM.
+   - ESP32: we get called from the SDK which does this independently
+   - Esp8266: we need to tell SDK about various partitions
+   - Rp2040: the SDK no concept of partition tables
+
+Initialise networking
+   If enabled.
+
+Invoke the application's ``init`` function
+
+Enter the main run loop
+   Interaction with SDK to ensure that registered software timers and queued tasks
+   are executed, and the watchdog timer serviced.
 
 
 .. toctree::