>>From this are you building the new Bootloadable project with new Bootloader or Old Bootloader?
I am building the bootloadable project with new bootloader.
To be more clear about the scenario -
Lets say I built the bootloadable and the bootloader with bootloader application version changed from default 0x0000 to 0x1111.
Now when I program the bootloader on the product that we are building, and install the bootloadable .cyacd, I get the bootloader version return as 0x1111. All fine till now.
But when I install only the .cyacd file (lets say accidently) without programming the new bootloader (with version 0x1111) and try to retrieve the bootloader version from our C++ program through the bootloadable, I still get 0x1111. This is actually false information because the bootloader version on the product is still 0x0000 because it was not programmed (lets say accidently).
When you upload the new bootloadable the program overwrites the metadata with the bootloader version with which the bootloader is built.
I have attached the image from the .cyacd file where the bootloader app version is present.
Is there a way to avoid writing only that part of the metadata? Anything we can do/ a setting/ code so that the bootloadable does not write the bootloader app version part of the metadata at least if not the whole metadata section?
I am thinking of using the "Checksum exclude section size" feature