1 of 1 people found this helpful
I tried Bootloading by creating a Bootloader project in PSoC Creator 3.3 and an Bootloadable Application in PSoC Creator 4.2. While creating the Bootloadable application I made sure that I use the same version of the Bootloadable component that was being used in the PSoC Creator 3.3. I added the hex and elf files from the old Bootloader project as dependencies in the Bootloadable component in PSoC Creator 4.2.
The Bootloading happened successfully and my application project was working as expected.
Thus, It is possible to build the application in 4.2 and in the Bootloadable component to link it to the old Bootloader.hex and Bootloader.elf from 3.3 env and this should not cause any issue.
As mentioned by you the .cyacd files in both the cases were not the exact match. But there are a number of factors due to which the contents (data) of the .cyacd file might change, this in turn will change the checksum at the end of each row.
Please refer to the following KBA for more details on the format of .cyacd file: Format of .cyacd File for PSoC® 3 or PSoC 5LP Bootloader - KBA216138
Please let me know if this helps.
It was helpful.