Merge branch 'main' into update_win11_docs

Author: Erol444

docs/source/components/bootloader.rst

@@ -3,52 +3,83 @@
 Bootloader
 ==========
 
-DepthAI bootloader is a small program which **handles the booting process**, either by **booting the flashed application**,
-or by **initializing the OAK PoE camera** so DepthAI API can connect to it.
+DepthAI bootloader is a small program which handles the booting process, either by **booting the flashed application** (see :ref:`Standalone mode`),
+or by **initializing the OAK PoE camera** so DepthAI API can connect to it. OAK PoE cameras already come with bootloader flashed at the factory.
 
-To be able to run in :ref:`Standalone mode`, the Depthai bootloader must be first flashed to the devices flash.
-This step is required only once.
-
-Once the device has the bootloader flashed, it will perform the same as before. Running pipelines with a host
-connected doesn't require any changes.
-
-Suggested workflow is to perform as much of development as possible with the host connected as the
-iteration cycle is greatly improved.
+Bootloader is part of the ``depthai`` library, so to eg. flash the newest bootloader, you should use the newest ``depthai`` library.
 
 Device Manager
 ##############
 
-``device_manager.py`` is a Python helper that interfaces with device :ref:`Bootloader` and bootloader configuration.
+``device_manager.py`` is a Python script that interfaces with device :ref:`Bootloader` and bootloader configuration.
 It can be found at `depthai-python/utilities <https://github.com/luxonis/depthai-python/tree/main/utilities>`__.
 
-.. image:: https://user-images.githubusercontent.com/18037362/171629704-0f78f31a-1778-4338-8ac0-bdfb0d2d593f.png
+.. image:: https://github.com/luxonis/depthai-python/assets/18037362/b2f067d8-8b4b-4158-9342-ea0dfbe0caf6
 
-Device Manager Usage
---------------------
+About Device
+------------
 
-**About device tab** - Select a camera to see its metadata - like MxID, flashed bootloader version, device state etc.
+Allows you to select the device you want to connect to, and you see metadata of connected device.
 
 * First we have to select the device we want to connect (boot) to, you can select that using:
 
   * **Dropdown** which contains found device MX Ids. Dropdown will only get updated when starting the app.
   * **Specify IP** button if your OAK PoE camera isn't in the same LAN.
   * **Search** feature - a new window will show that has a table with all available cameras (either via USB port or on LAN - OAK PoEs), their MxId, name, and status. Clicking on a table row will select that device and boot to it.
-* ``Flash newest Bootloader`` button will flash the ``newest bootloader`` to the device. You can select AUTO, USB or NETWORK bootloader.
 
-  * **AUTO** will select the connection type of bootloader with which the camera is currently connected to. If you are connected via USB (doing factory reset) to an OAK PoE camera, you shouldn't select AUTO, as it will flash USB bootloader.
-  * **USB** bootloader will try to boot the application that is stored on flash memory. If it can't find flashed application, it will just behave as normal USB OAK - so it will wait until a host computer initializes the application.
-  * **NETWORK** bootloader is used by the OAK PoE cameras, and is flashed at the factory. It handles network initialization so the OAK PoE cameras can be booted through the LAN.
-* ``Factory reset`` will erase the whole flash content and re-flash it with only the USB or NETWORK bootloader. Flashed application (pipeline, assets) and bootloader configurations will be lost.
-* ``Boot into USB recovery mode`` will force eg. OAK PoE camera to be available through the USB connector, even if its boot pins are set to PoE booting. It is mostly used by our firmware developers.
+Configuration settings
+----------------------
 
-**Configuration settings tab** - After you select a device that has bootloader flashed, you can also configure bootloader
-configuration.
+After you select a device that has bootloader flashed, you can also configure bootloader configuration.
 
 - If the device has **NETWORK bootloader flashed**, you will be able to set its static/dynamic IP/mask/gateway, DNS, MAC, etc.
 - If the device has **USB bootloader flashed**, you will be able to set its USB max speed and USB timeout.
 
-After setting some values, you have to click on the ``Flash configuration`` button. You can also flash a :ref:`DAP`,
-or clear the bootloader config.
+After setting some values, you have to click on the ``Flash configuration`` button. You can also ``Clear configuration``, or ``View configuration`` (its JSON).
+
+.. figure:: https://github.com/luxonis/depthai-python/assets/18037362/4bced0ab-92fa-4a73-986f-4a3ba8848940
+
+  When flashing static IP, make sure to also set the gateway/mask
+
+Applications settings
+---------------------
+
+Useful when dealing with :ref:`Standalone mode` applications.
+
+- **Flash application**: Select DepthAI Application Package (``.dap``) you want to flash the device. Below is a code snippet that showcases how to create the dap file.
+- **Remove application**: Removes/clears the flashed application from the device
+- **Open device streaming application**: Starts streaming frames from all connected cameras on the device.
+
+.. code-block:: python
+
+  import depthai as dai
+  pipeline = dai.Pipeline()
+  # ... add nodes to pipeline
+  dai.DeviceBootloader.saveDepthaiApplicationPackage(
+      './file.dap', # Where to save the .dap file
+      pipeline, # My pipeline
+      compress=True, # Compress the FW and assets. In my case, it went from 24MB -> 9.5MB
+      applicationName='myAppName' # Optional, so you know which app is flashed afterwards
+    )
+
+Danger Zone
+-----------
+
+.. warning::
+
+    This section can potentially soft-brick your device, so be careful when using it.
+
+To prevent soft-bricking, OAK devices (since 2023) have factory bootloader and user bootloader. If user flashes a corrupted user bootloader, it will fallback to using factory bootloader. When updating bootloader,
+Device Manager will try to flash the user bootloader first, if flashed (factory) bootloader supports it. If it's not possible, it will flash the factory bootloader.
+
+* **Update Bootloader** button will flash the newest bootloader to the device. You can select AUTO, USB or NETWORK bootloader.
+
+  * AUTO will select the connection type of bootloader with which the camera is currently connected to. If you are connected via USB (doing factory reset) to an OAK PoE camera, you shouldn't select AUTO, as it will flash USB bootloader.
+  * USB bootloader will try to boot the application that is stored on flash memory. If it can't find flashed application, it will just behave as normal USB OAK - so it will wait until a host computer initializes the application.
+  * NETWORK bootloader is used by the OAK PoE cameras, and is flashed at the factory. It handles network initialization so the OAK PoE cameras can be booted through the LAN.
+* **Flash Factory Bootloader**: If you want to flash the factory bootloader, you can use this button. It will flash the factory bootloader, even if the user bootloader is already flashed.
+* **Factory reset** will erase the whole flash content and re-flash it with only the USB or NETWORK bootloader. Flashed application (pipeline, assets) and bootloader configurations will be lost.
+* **Boot into USB recovery mode** will force eg. OAK PoE camera to be available through the USB connector, even if its boot pins are set to PoE booting. It is mostly used by our firmware developers.
 
 Boot switches
 #############