-->
Page 1 of 2

Only flashing user code instead of whole firmware?

PostPosted: Fri Mar 04, 2016 12:46 am
by GigAHerZ
Hi all!

I started to wonder, if it's possible to somehow set up a project in a way that it creates different bin files and not all of them are required to be flashed on chip all the time.

Flashing the whole firmware is somewhat slow. At the same time, i usually only change my user code and the firmware is pretty static.

So is it somehow possible to update the make file in a way that i don't always have to flash the whole firmware, when i only change the user code?

Thank you!

Re: Only flashing user code instead of whole firmware?

PostPosted: Fri Mar 04, 2016 11:15 am
by xtal
nodeMCU - YES
Arduino - I don't know , but some burners allow sections to be burnt, so maybe?

Re: Only flashing user code instead of whole firmware?

PostPosted: Sat Mar 05, 2016 12:48 am
by GigAHerZ
xtal wrote:nodeMCU - YES
Arduino - I don't know , but some burners allow sections to be burnt, so maybe?


Well, nodeMCU is interpreting LUA language.

But i'm more interested in pure C/C++ solutions. Not even arduino.
Sections can be burnt separately, it is already done by default to some extent. (0x0000 and 0x4000 if i remember correctly)

Biggest question is how to prepare the code and "make" file so eventually i have separate bin file only for user code (possibly some kind of split of 0x4000 bin file) which can be flashed without other bin files that contain the basic, "static" firmware, that doesn't usually change?

Re: Only flashing user code instead of whole firmware?

PostPosted: Thu Mar 10, 2016 8:45 pm
by isti37
Nodemcu, I don't think you gain any advantage with pure C/C++ unless you want to do some math, however you can always compile nodemcu with native c code and use the functions in lua.