- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a CCG3PA workspace. For some reason, when I program my chip with the main project, which i assume is the bootloader + app, nothing happens. The application does not boot, which i have confirmed with placing LED or debug line toggles in main.
On the other hand, the second project in the workspace, the noboot project, works fine. I can program the chip and everything works.
Granted, I do not need the bootloader feature but I want to fix any misconfigurations now while i have the chance. Perhaps I am misunderstanding the hex file that is generated by the main project and it is not the bootloader combined with the application....
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can I please know if you ae using the CCG3PA firmware available in the power sdk directly or made some changes. If yes, please do share the modifications carried out.
"Perhaps I am misunderstanding the hex file that is generated by the main project and it is not the bootloader combined with the application...."
Main firmware: This is the main firmware project for the application. This application is
designed to work on top of the bootloader pre-programmed on the CCG3PA device.
noboot: The main firmware project does not support runtime debugging through the SWD interface. The noboot.cydsn is a version of the same firmware application, which does not depend on the bootloader. This firmware overwrites the complete device flash and expects that the device will be programmed through SWD.
You can also refer these threads, 1 and 2 which is a similar issue.
Regards,
Abhilash P
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can I please know if you ae using the CCG3PA firmware available in the power sdk directly or made some changes. If yes, please do share the modifications carried out.
"Perhaps I am misunderstanding the hex file that is generated by the main project and it is not the bootloader combined with the application...."
Main firmware: This is the main firmware project for the application. This application is
designed to work on top of the bootloader pre-programmed on the CCG3PA device.
noboot: The main firmware project does not support runtime debugging through the SWD interface. The noboot.cydsn is a version of the same firmware application, which does not depend on the bootloader. This firmware overwrites the complete device flash and expects that the device will be programmed through SWD.
You can also refer these threads, 1 and 2 which is a similar issue.
Regards,
Abhilash P
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a custom project based on the CCG3PA FW but the functionality of the stack is unmodified.
This application is designed to work on top of the bootloader pre-programmed on the CCG3PA device.
This might be my problem. Is the bootloader a ROM bootloader or is it programmed into Flash, such as with one of the included binaries, such as CYPD3175-24LQXQ_cc_src_boot_3_1_2_1484_0_0_0_pa.hex? If that is the case, then that would explain why the application doesn't boot... there is no bootloader programmed!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
CCG3PA has a 64-KB flash memory that is designated to store a bootloader, the firmware binary along with the corresponding configuration table. The flash memory map for the device is shown below,
Regards,
Abhilash P