SIMPLELINK-CC13X2-26X2-SDK: APIs for Internal Flash Access

Veena Mohan

Part Number: SIMPLELINK-CC13X2-26X2-SDK
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1

Hi,

I need help in identifying interfaces for internal flash access using the SimpleLink_cc13x2_26x2_sdk.

My development application has an off-chip OAD configuration and hence requires the external flash access as well.

I see that the internal flash access using readFlash and writeFlash interfaces cannot be re-used for internal flash given that the application is using the same for external flash access thru the OAD interfaces.

I intend to use the NVS interfaces, but again am blocked with the NVS Init performing re-initialization during an OAD Open operation.

Can you point me to any example code which accesses both the internal and external flash without much conflicts in the software?

Best Regards,

Veena Mohan.

over 5 years ago

0 J Lindh over 5 years ago

TI__Guru 57865 points

Hi Veena,
Which protocol stack do you use?

0 Veena Mohan over 5 years ago in reply to J Lindh

Prodigy 140 points

Hi Lindh,

I am using the ble5stack within this sdk.

Best Regards,

Veena Mohan

0 Tim C over 5 years ago in reply to Veena Mohan

TI__Mastermind 34660 points

Hello. Are you saying that you want to access the flash(es) for reasons besides OAD? The OAD profile will handle accessing external flash as needed.

0 Veena Mohan over 5 years ago in reply to Tim C

Prodigy 140 points

Hi Tim,

Yes. I want to use the internal flash for reasons other than OAD.

Can you direct me with examples to do the same in an efficient manner.

Best Regards,

Veena Mohan.

0 Tim C over 5 years ago in reply to Veena Mohan

TI__Mastermind 34660 points

I am not aware of any examples that do as you are asking. For dealing with internal flash, I would recommend using the OSAL SNV driver: dev.ti.com/.../flash_memory-cc13x2_26x2.html

0 Veena Mohan over 5 years ago in reply to Tim C

Prodigy 140 points

Hi Tim,

Thanks for your response. I do see the limitations in the link that you have recommended.

Just to be clear, I have currently designed an Internal Flash Access region, outside the NV Region and am using my own driver code to access this region of flash and perform operations.

Do you think with this design, there will be any interference with the stack usage of the Internal Flash?

Also, where can I find the schematics and pin layouts for the Launchpad LAUNCHXL-CC26X2R1?

Best Regards,

Veena Mohan.

0 Tim C over 5 years ago in reply to Veena Mohan

TI__Mastermind 34660 points

Hi. As long as you have set aside space in the linker file for your own flash region, I don't see any issues with this. You can find the schematics here:
dev.ti.com/.../

Other wireless

Other wireless technologies forum

SIMPLELINK-CC13X2-26X2-SDK: APIs for Internal Flash Access