Update flasher stubs and bootloaders

[jessebraham]

@SergioGasquez if you could please verify you're able to flash and run applications to each chip you have access to, that'd be very much appreciated! Should work fine, but we just need to be sure.

(I realize a few of the stubs don't actually have any changes other than number formatting, but I just copy-pasted all of them 😁)

[SergioGasquez]

I did test the following features in all the chips but ESP32-C6:

espflash

• Flash (espflash flash --monitor)
  • ESP32
  • ESP32-C2
  • ESP32-C3
  • ESP32-H2
  • ESP32-S2
  • ESP32-S3
• Monitor (espflash monitor)
  • ESP32
  • ESP32-C2
  • ESP32-C3
  • ESP32-H2
  • ESP32-S2
  • ESP32-S3
• Board Info (espflash board-info)
  • ESP32
  • ESP32-C2
  • ESP32-C3
  • ESP32-H2
  • ESP32-S2
  • ESP32-S3
• Save Image (espflash save-image)
  • ESP32
  • ESP32-C2
  • ESP32-C3
  • ESP32-H2
  • ESP32-S2
  • ESP32-S3

cargo-espflash

• Flash (cargo espflash flash --monitor)
  • ESP32
  • ESP32-C2
  • ESP32-C3
  • ESP32-H2
  • ESP32-S2
  • ESP32-S3

Errors

ESP32-C2 is failing with:

E (106) boot_comm: Image requires chip rev <= v1.99, but chip is v2.0
E (113) boot: Factory app partition is not bootable
E (119) boot: No bootable app partitions in the partition table

Rebuilding the bootloader with the following config (Develop on ESP32-C2 v2.0 (Preview)), solves the issue

Here is the working bootloader in case its useful: esp32c2-bootloader.zip

[jessebraham]

Thanks for testing, I've updated the C2's bootloader so we should be good to go. C6 works fine.