You are here

Different binary output on PSoC Creator 3.3 SP2 | Cypress Semiconductor

Different binary output on PSoC Creator 3.3 SP2

Summary: 1 Reply, Latest post by HIMA on 01 Nov 2016 11:24 PM PDT
Verified Answers: 1
Last post
Log in to post new comments.
cjoachim_1597296's picture
User
75 posts

(I use Git as revision system)

I implemented a (upgradable stack) bootloader for my application at commit A. Since then, the bootloader code has not been altered, but the application code has changed and is now at commit B. But between A and B, I upgraded PSoC Creator from 3.3 to 3.3SP2. If I now try to build the code in commit A on 3.3SP2, it generates completely different .hex and .cyacd files even though the source code is the same.

I suspect, but have not tried, that .cyacd files build on 3.3SP2 are not compatible with devices having a bootloader buildt with the older 3.3. I though I just could install PSoC Creator 3.3 parallell with PSoC Creator 3.3SP2, but that was not possible. Any sugguestions on how to proceed?

 

HIMA's picture
Cypress Employee
203 posts

Hello,

Do you have the bootloader.hex file from PSoC Creator 3.3 stored as golden image? In that case you use that. Else, you will need to install the older Creator in another machine and obtain the .hex file.

Also please have a look at this post:http://www.cypress.com/forum/proc-ble/ota-projects-update.

Thanks,

Hima

Log in to post new comments.