Other Parts Discussed in Thread: CC2642R
Does 2642 support A/B partition startup?
If it supports A and B partitions, where should I modify them?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Does 2642 support A/B partition startup?
If it supports A and B partitions, where should I modify them?
Hi Alex,
I interpret your question as "Can BLE5-Stack support having two equivalent application images stored inside the flash memory?" If this is the case then it is possible but not enabled by default. You would need to modify the BLE project's command linker file (among other dependencies) to only allocate half of the available Flash for one image, and program the on-chip BIM as a dual-image configuration to pick between the two images during startup. Please note that this is not supported for the existing OAD examples as they use a persistent application for on-chip updates.
Regards,
Ryan
hi
A and B partitions. Initially, the two images are the same. For subsequent upgrades, if the current partition is A, the A partition process will flush the new image into B, write it successfully, restart and switch to B. If an exception occurs, the A partition will continue to be used, similar to a backup mechanism.
So this is possible, but it is not enabled by default. You need to modify the command linker file (and other dependencies) of the BLE project to allocate only half of the available Flash for one image
Can you provide a detailed description? Or refer to those?
Appeal: What can I refer to when using SPI to upgrade partitions (non OAD)?
As explained in the OAD section of the BLE5-Stack User's Guide, on-chip OAD uses a BLE persistent image to accomplish on-chip updates. Thus the feature requested exists outside of the available TI examples and developers will need to further investigate BLE5 dual image solutions independently. Since the CC2642R does not have enough flash memory to store two equivalent BLE images, a device with a larger memory footprint such as the CC2652R7 will be required to accomplish this feature. You can refer to the differences in project configurations from the CC2652R7 Zigbee on-chip OAD example, which does use a dual image setup.
SPI communication is an available interface for the ROM bootloader, as can be reviewed from SWRA466 or Chapter 10 of the TRM.
Regards,
Ryan
After calculation, if the generated Bin is controlled within 150K, it is applicable,
How to generate HEX for projects under Dome, such as simple_peripheral/simple_central/multirole, and how to set the starting address?
Can you please clarify what is meant by "Dome"? The hex output is generated by BLE projects from the Post-build steps from Project Properties -> CCS Build -> Steps window. The starting address is determined by the command linker file (*.cmd), refer to FLASH_START.
Regards,
Ryan