summaryrefslogtreecommitdiffstatshomepage
path: root/esp8266/scripts/flashbdev.py
Commit message (Collapse)AuthorAge
* esp8266/scripts/flashbdev: Use all available Flash for filesystem.Paul Sokolovsky2016-04-26
| | | | | | All Flash sans firmware at the beginning and 16K SDK param block at the end is used for filesystem (and that's calculated depending on the Flash size).
* esp8266/scripts/flashbdev: Correct bootloader flash size to match real size.Paul Sokolovsky2016-04-20
| | | | | | | | | Flash size as seen by vendor SDK doesn't depend on real size, but rather on a particular value in firmware header, as put there by flash tool. That means it's user responsibility to know what flash size a particular device has, and specify correct parameters during flashing. That's not end user friendly however, so we try to make it "flash and play" by detecting real size vs from-header size mismatch, and correct the header accordingly.
* esp8266/scripts/flashbdev: Disable debug output/checks.Paul Sokolovsky2016-04-20
|
* esp8266/scripts: Don't try to create filesystem on 512KB devices or less.Paul Sokolovsky2016-04-18
| | | | There's no space for it.
* esp8266/scripts/flashbdev: Use all available space in 1MB FlashROM for FS.Paul Sokolovsky2016-04-18
|
* esp8266: Add Python modules for initial configuration.Paul Sokolovsky2016-04-12
Main entry point is _boot.py which checks whether FAT FS in flash mountable, and if so, mounts it. Otherwise, it checks if flash is empty, and if so, performs initial module setup: makes FAT FS, configures default AP name, etc. As a last option, if flash is not empty, and could not be mounted, it means filesystem corruption, and warning message with instructions is printed in an infinite loop.