Made HOWTO a tiny bit better.

Documentation/HOWTO-change-firmware-and-compile-it_MeesElectronics.md

@@ -158,7 +158,20 @@ The new code:
           }
       };
 
-A lot of the abilities of the board is defined here. Most of it is self explanatory. In a future update of this document it will be beter explained. For now, the above values should be good enough to get you started.
+A lot of the abilities of the board is defined here. Most of it is self explanatory. The above values should be good enough to get you started.
+
+|Name|What does it do|
+|----|-------|
+|IS_ESP32S3|Is the board an ESP32 S3|
+|HAS_DISPLAY| Has the board a display|
+|HAS_BLUETOOTH| Has the board Bluetooth|
+|HAS_BLE|Has the board Bluetooth LE|
+|HAS_PMU|Unknown yet|
+|HAS_CONSOLE|RNode Bootstrap Console|
+|HAS_EEPROM|All ESP32 have EEPROM|
+|INTERFACE_COUNT|Unknown, set to 1|
+|HAS_NP|Has the board a NeoPixel|
+|EXTERNAL_LEDS|Has the board external LEDs|
 
 The SPI bus is defined in the structs `interfaces`, `interface_cfg` and `interface_pins`. The comments in the code explain it well enough, I think. When the value of `interface_cfg[0]` is set to *false*, we can define all the IO pins in the struct `interface_pins`. The numbers are the GPIO numbers of the ESP32 S3. So 10 means GPIO10. If the value is set to -1 the pin is not used. For example, the SX1278 transceiver doesn't have a busy pin, so it is set to -1.