Dennis, can you please post your complete project, so that we all can have a look at all of your settings. To do so, use
Creator->File->Create Workspace Bundle (minimal)
and attach the resulting file. Are you using a Cypress Kit? Which one?? Are there any messages when yusing bootloader host program?
There is nothing special about the project, it just uses that standard bootloader components with a slightly modified bootloader interface. This interface read read from a file, and the lines are passed to CyBtldr_ParseRowData.
If I change the bootloader to standard settings (no dual boot), it works fine with small programs. If I try with my main app where the size is 70KB, it flashes with no errors, but when restarting mcu, the bootloader cant find any valid image.
I use the array and row index that CyBtldr_ParseRowData return, is that not correct? or should I do this manual ?
I would suggest to test your "slightly modified bootloader interface" with two smaller bootloadable projects.
Thanks for your reply, finally looked more into this, and it turns out I was a little naive thinking that CyBtldr_ParseRowData did a checksum validation...It did not, and after adding that, it proved that the communication link sometimes corrupted the data. (therefor the small app succeeded, and the large one had bigger risk of failure)
Still confused about the "Golder image" option, since it was possible to destroy app#1, and I would believe it should be protected. This can be done in flash security of cause.
I was also hoping to use the emulated eeprom with an absolute address, but this is also not possible while the dual app mode is active. ('cyelftool.exe' fails with error 1). You think there could be some workaround for this? It is ok for both app#1 and app#2 to share this dedicated area.