Yes, something seems to be wrong. Difficult to tell what, can you share the projects, Bootloader and Bootloadable? Use Creator -> File-> Create workspace bundle (minimal) and upload the resulting .zip.
from time to time I get a spurious interrupt and execution gets stuck in the Cm3Start.c::CY_ISR(IntDefaultHandler) This is mostly caused by a clobbered stack or bad pointer handling leading to accessing non-existing memory etc.
Thank you for your reply. I'll try to create a simpler project that exhibits this behavior (my app is pretty complex) and post the project so that yo can take a look.
It will take few days until then, I have to finish something else meanwhile.
While trying to create a simple version of a custom bootloader and application I've run into another issue:
The PSoC Creator 4 "Flash Security" has all the rows grayed out, so I cannot change them.
The comment at the top of the .cydr screen says:
"This can only be set in the referenced bootloader project. Bootloadable projects inherit the value from the associated bootloader"
And the build fails with the message:
"ADD: fit.M0013: error: Invalid flash security level. The last flash row in 'Bootloader/Bootloadable' and last two rows in 'Multi App Bootloader/Bootloadable' projects must be writable by the CPU (U, F, or R) since it is used for application metadata."
But this project is for a regular application, I don't have any "Bootloadable" component in the project, or at least I don't see it (although I might have played with it at some time).
Probably some file/setting remained hidden in there and no matter what clean up procedure I've tried, no success.
Is there anything I can try other that re-creating the project?
Thank you for any suggestion.
Your bootloader's flash security settings seem to lead to a conflict. Again: Post the workspace containing the bootloader and bootloadable projects.
I've attached the workspace containing 2 simple projects: test_app and test_boot (the bootloader is custom, not based on the PSoc Creator Bootloader module).
Hopefully it has all the needed files.
Basically the test_boot waits for a command and then launches the application - this is where my problems are, the application when launched like that does not run properly.
I wanted to create a single hex from both but I did not succeed.
When I wanted to add a "Bootloadable" component to the test_app (the only way I have found to mention the custom bootloader hex dependency) I ran into all sorts of other issues.
Is there a way to create a single hex file from these 2 projects in the workspace so that I can download both the app and the bootloader the same time?
If not, I'll think of creating a "merge" tool and I can post the resulting hex, if needed.
Thanks for your help.
Please share the bootloader project as well to recreate the issue.