Other Parts Discussed in Thread: UNIFLASH
I am attempting to automate the build process for our software
currently the build system generates a .out file that can be loaded onto our device using CCS or uniflash
I have managed to create a standalone command line package using uniflash & would now like to take it one step further - to generate the standalone package using the build system.
I have tried taking a package created by uniflash & editing the various filenames & paths (the name of our .out file contains the version number & so continuously changes)
this appeared to work initially, but I then tried creating a new version that didn't clear the Flash memory - it starts to work & then fails with a flash verification failure during the download to the board.
My reason for not wanting to erase the flash is that I am making use of a NVS (non volatile store) and don't want that store overwritten every time we load a new build.
- So is there a way of protecting the NVS, or do i need to create the standalone package using the 'don't erase flash' option ?
- is there a way of generating a standalone command line package from the command line?
