Your project didn't build in my environment. There was a missing unused file I removed and I had to insert the "BLE" path into compiler's include directories.
I removed all generated files and re-built both projects which included to set location of .hex and .elf files anew.
>>Could not test if working. There are 3 warnings which you should remove before testing!
OK, I cleaned up all three warnings, deleted the generated source, copied the BLE api anew, built both projects again (ran mk.bat in between), and tried again. Same result.
It builds without error (and without warnings now), loads to the evaluation kit, and nothing happens. No debug messages, no blinking LEDs, no BLE advertisement.
Now if I simply point the bootloadable object back at the old .hex and .elf files and clean/build the bootloadable project, everything works great.
I decided to try another thing: Since I still have gcc 4.9.3 on my computer, I set that compiler up as "ARM_GCC_Generic" and set it as the active compiler. Rebuilt both projects (modified mk.bat accordingly and re-ran it in between as well). First I get the missing BLE path that you mentioned, which I fixed. Then re-ran again and I get "The command 'cyelftool.exe' failed with exit code '1'".
workspace attached again.
I'm still stumped on this one...
1 of 1 people found this helpful
When you cannot get any help here try to get in contact with Cypress directly: At top of Cypress Home page select "Design support -> Create a Support Case" and ask your question. You will be helped by a Cypress engineer.Best provide all information: Workspace bundle, Creator version, OS version, PCB or Kit type.
Did you find a solution for this? It sounds like the same problem I'm facing. Your code is running but is probably hitting the general exception handler. I have modified the gen exception handler in my project indicate a solid red LED so I can easily tell what's happening.
The times I've encountered this are when there is some kind of issue between the bootloader and bootloadable projects.
I've noticed that in creator 4.1 and 4.2 (after the compiler update) that "mk.bat" used in the previous versions to create the linker script so the bootloadable project can refer to bootloader calls isn't included. The earlier mk.bat refers directly to the earlier compiler; changing this doesn't seem to help.
Frankly I've been underwhelmed by the lack of answer from Cypress, either through my FAE contact or through a trouble ticket here. The root question (to me at least) is "why isn't mk.bat included anymore? Is this a mistake, or has it been deprecated, and if it has been depcreated, where is that documented?" I may have missed something in the release notes but shouldn't this also be included in the bootloader/bootloadable datasheet?
Sorry for the slow reply. I never really found the solution. I got past it by wiping out my bootloader project and re-creating the bootloader again from scratch.