I figured out my issue. I was linking the bootloadable component to the wrong hex file. I was linking it to the application hex file when I should have linked it to the launcher hex file. Obviously, this makes sense since the launcher needs to know where the bootloadable applications are in flash.
My next question is:
- How do I flash the application on the chip?
In the single/dual application bootloader cases, you first flash your bootloader application onto the chip and then you use that bootloader to flash the application on the chip via the communication interface.
In the case of the combination-launcher project, there is no stand-alone bootloader. It is just a launcher. How does the launcher get flashed? How does the combination project get flashed? If you flash the launcher first, then you have no way to flash another image without erasing the launcher. If you flash the combination project first then can you flash the launcher? That feels strange...
1 of 1 people found this helpful
Normal and bootloader project hex files contain code and data bytes for just that project. Whereas, Bootloadable.hex files are different in that they contain code and data bytes for the bootloadable and the associated bootloader project. When you program Bootloadable.hex file; both projects are programmed in at the same time. You can follow these steps to program both combination application and get started;
(1) Program Combination_Application1.hex file which contains both launcher and combination application 1. Later, bootload the Combination_Application2.cyacd and device flash would contain launcher, Combination_Application1 and Combination_Application2.
(2) You can merge both combination applications (Combination_Application1.hex and Combination_Application2.hex) and program the device. Please go through Combine Dual-application Bootloadable Hex Files for Production Programming– KBA224390
Thank you! This is good information.