esp-jumpstart VS micropython-camera-driver

Think of it as a configuration file. In this case, "board_esp32_devkitc.h" is the configuration for the ESP32 DevKit-C Board. For this board, it is using the GPIO 27 as output. What if you need to build the system for this board and for a different board where the GPIO 27 is already in use or, not even has that GPIO? With a configuration file you just need to pass and argument to the build system and it will use the correct configuration. Without it you'll probably need to clutter you source files with "#ifdef", which would work, but would be worse to maintain, especially if you need to add a third or more boards.

I've downloaded the 1.4MB firmware (https://github.com/lemariva/micropython-camera-driver/blob/master/firmware/micropython_camera_feeeb5ea3_esp32_idf4_4.bin) and flashed it and every time I do, it gives me an infinite loop. Corrupted files. I've tried flashing it from ESPtool in the terminal and also within Thonny, same result. I don't know what I'm doing wrong because the firmware completes flashing without errors. I've also tried the other firmware (https://github.com/lemariva/micropython-camera-driver/blob/master/firmware/micropython_cmake_9fef1c0bd_esp32_idf4.x_ble_camera.bin).

All of these things work fine for me on dev boards. I am using a Camera enabled https://github.com/lemariva/micropython-camera-driver firmware here that comes with Micropython.