LAUNCHXL-CC26X2R1: Modify oad_onchip project replacement persistent_app

Alex Zhang

Purpose: Divide the flash into two parts: A: 0-160k, B: 160k-320k, A partition flushing (oad_onchip) project, B partition copying (oad_onchip) project, replacing the original (persistent app), and specifying the starting address 160k.

Adding (OAD_IMG_A=1) and (OAD_IMG_B=1) to two projects still failed. How can I modify them?

over 2 years ago

0 Jan over 2 years ago

TI__Mastermind 43500 points

Hi Alex,

Thank you for reaching out to us. We will look into this and get back to you as soon as possible. In the meantime, can you specify which SDK is being used for this as well as what the end goal is for splitting the flash into two parts?

Best Regards,

Jan

0 Alex Zhang over 2 years ago in reply to Jan

TI__Intellectual 1305 points

SDK:simplelink_cc13xx_cc26xx_sdk_7_10_00_98

CCS:Code Composer Studio 12.2.0

Jan said:
what the end goal is for splitting the flash into two parts?

Create A and B partitions.

0 Clément over 2 years ago in reply to Alex Zhang

TI__Guru** 101490 points

Hi Alex,

First of all, we do not provide the exact configuration you are asking for. It will require a few tuning on your side.

Here a few elements I can think of. Please share your progress so we can continue providing you some inputs:

- I would recommend verifying the feasibility of fitting the OAD enabled image in ~156kB of Flash (this is to account for the BIM).

- The linker command file has to be modified to account for the new memory layout.

- The BIM project has to be modified to ensure you are taking into account the memory layout newly set up

- You may have to implement a small system to tell the BIM which image should be used. It might be as simple as writing a "magic" number in Flash or more advanced according to your system requirements.

I hope this will help,

Best regards,

0 Alex Zhang over 2 years ago in reply to Clément

TI__Intellectual 1305 points

How is the linker command file modified?
I modified the persistent_app CMD (IMG_A_FLASH_START is 0x00028000).
The result is that 28000 has only header information, 0x28000+Hdr to 38000 is 0xff

0 Clément over 2 years ago in reply to Alex Zhang

TI__Guru** 101490 points

Hi Alex,

Can you specify which linker command file(s) you have modified?

Also, can you specify whether the screenshot you have provided is for the image built or if it is obtained after the completion of the OAD process?

Best regards,

0 Alex Zhang over 2 years ago in reply to Clément

TI__Intellectual 1305 points

Because the BIM project does not contain ICALL. Which interface should be used by "osal_snv_write" and "NVS_write" to read and write Flash?

0 Alex Zhang over 2 years ago in reply to Alex Zhang

TI__Intellectual 1305 points

and what's the different in "osal_snv_write" and "NVS_write" ?

0 Alex Zhang over 2 years ago in reply to Clément

TI__Intellectual 1305 points

Clément said:
Can you specify which linker command file(s) you have modified?

Modify the (#define IMG_A_FLASH_START 0x00038000 -> 0x00028000) of "cc13x2_cc26x2_app_tirtos7.cmd" in the persistent_app project. After compilation, the HEX file generated by Unflash burning was used, and Flash Programmer 2 was used to read the FLASH distribution in the chip, finding that only the header information of the mirror was shifted to 0x00028000

+1 Clément over 2 years ago in reply to Alex Zhang

TI__Guru** 101490 points

Hi,

Alex Zhang said:
Because the BIM project does not contain ICALL. Which interface should be used by "osal_snv_write" and "NVS_write" to read and write Flash?

You should use the NVS driver, you can refer to the example <SDK>\examples\nortos\CC26X2R1_LAUNCHXL\drivers\nvsinternal

Alex Zhang said:
and what's the different in "osal_snv_write" and "NVS_write" ?

osal_snv is an over-layer for NVS. PLease refer to https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/7.10.00.98/exports/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory-cc13xx_cc26xx.html#flash

Alex Zhang said:
Modify the (#define IMG_A_FLASH_START 0x00038000 -> 0x00028000) of "cc13x2_cc26x2_app_tirtos7.cmd" in the persistent_app project

I guess all the linker command files from all the projects involved should be updated (including simple_peripheral_oad_onchip).

As mentioned initially, the changes you are making have not been tested by TI and we can only provide limited support for those. As the initial question has been answered, and the discussion is now about other topics, I am closing the thread.

Thank you for your comprehension.

Best regards,

0 Alex Zhang over 2 years ago in reply to Clément

TI__Intellectual 1305 points

thank you

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC26X2R1: Modify oad_onchip project replacement persistent_app