Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please combine the built spiffs image into the final .bin file #5

Open
pjsg opened this issue Feb 18, 2016 · 5 comments
Open

Please combine the built spiffs image into the final .bin file #5

pjsg opened this issue Feb 18, 2016 · 5 comments

Comments

@pjsg
Copy link

pjsg commented Feb 18, 2016

There is a commit about to be merged into nodemcu-firmware:dev that automates the building of the spiffs image containing files. Could you please add this file into the single .bin file that your build script generates?

-> nodemcu/nodemcu-firmware#1064

@TerryE
Copy link

TerryE commented Feb 19, 2016

Should this be optional or mandatory?

@marcelstoer
Copy link
Owner

@marcelstoer
Copy link
Owner

Will be implemented when nodemcu/nodemcu-firmware#1064 and/or nodemcu/nodemcu-firmware#1164 are merged.

Just to be clear, the aim is to use srec_cat in Dockerfile to combine and pad the .bins so that the SPIFFS image ends up at 0x78000, right? I keep learning new stuff around you guys all the time 😉.

@pjsg
Copy link
Author

pjsg commented Apr 3, 2016

My (not yet a PR) nodemcu/nodemcu-firmware#1164 generates either one or two spiffs image files. One is to fit in a small flash (512k) and the other into a large flash (4M). The problem is that you don't want to flash the small one into a large flash as that limits the amount of free disk space. Flashing the large one takes a long time. I've switched over to the Cesanta flasher: flasher -- you just want the modified esptool.py. This goes significantly faster -- it takes me around 9 seconds to flash a 512k image.

Figuring out what people actually want with regard to this is a challenge.

@mk-pmb
Copy link
Contributor

mk-pmb commented Dec 31, 2019

Any progress on this? Is it still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants