2021-01-31 06:04 PM
2021-01-31 07:01 PM
Put the configuration specific stuff in a structure, store that in a different section of flash than you use for your code. Copy the content in to a RAM side copy. Update that and write back to flash as needed. And recognize this data is missing, and prompt for it during factory programming, or write viable defaults pending new/specific information.
2021-01-31 07:09 PM
I am new to this so I have no experience on how to go about this. The reason there is a .cfg file is because the values can easily be set by someone who does not know anything about code. I am just not sure how the .cfg file would be converted to a .bin file that will be flash loaded to the board.
2021-01-31 07:11 PM
I am new to this so I have no experience on how to go about this. The reason there is a .cfg file is because the values can easily be set by someone who does not know anything about code. I am just not sure how the .cfg file would be converted to a .bin file that will be flash loaded to the board.
PS I meant to reply, but accidentally wrote an answer and can’t delete it lol