[MSITETOP]

Summary

• Adds a USB-boot recovery path for failed CC2 cameras that does not require a CH341/SPI programmer: force Ingenic USB boot by shorting flash pins 5–6, dump/repair with thingino-dfu + cc2camera build-image, then verify and re-enumerate as UVC.
• Documents the route in docs/USB-BOOT-RECOVERY.md, links it from the main README and hardware-recovery pages as an optional fallback, and includes a board photo marking flash pins 5 and 6.
• Keeps the external-programmer workflow as the recommended failed-camera recovery path.

Test plan

• Follow docs/USB-BOOT-RECOVERY.md on a supported EF-S7-V1.0.30B / T23 / 8 MiB camera that no longer boots normally
• Confirm shorting flash pins 5–6 at power-up yields a108:c309, then remove the short before DFU read/write
• Confirm three identical 8 MiB dumps, successful cc2camera build-image, DFU --verify, and post-write UVC enumeration (a108:2240)
• Skim README path selection: failed-camera readers are pointed at the programmer route first, USB-boot only as an optional fallback

[phryneas]

This is very cool, but I would not want to document this as the preferred route, but only as a fallback, so this should be more along "if you have an external programmer or can come by one easily, go for X, if you want to try without, read Y".

Same for the rest of the text - I would not want people to build a custom cable and directly hook it up to their laptop without any in-circuit protection that an external programmer usually has as the "recommended path".

[MSITETOP]

Agreed — updated in bde23c1.

USB-boot is now documented only as an optional fallback. The path-selection text and section order put the external-programmer route first as the recommended recovery, and the USB-boot docs warn that a homemade camera-to-USB cable plugged into a laptop lacks the isolation/voltage checks of a CH341-style setup.