CCS/LAUNCHXL-CC1352P: Adding resource files to the build image for later reading

Hi,

I sent it to a concerned engineer. We will get back to you ASAP. Please bear with us.

Thanks,

PM

Thanks,

has there been progress on this?

Hello Taylor,

Apologize for the delay!

Taylor Ramirez said:

I have been able to read and write files to and from the flash using both NVS and SPIFFS...

Have you been able to write to the internal Flash (on CC1352 device) or external SPI Flash using NVS and SPIFFS?

Taylor Ramirez said:

but what I need to do is place the file into the flash

Do you want to place it in internal Flash or external flash?

Using the nvs TI-Driver you can write to both internal flash (on CC1352 device) and external Flash. The examples "nvsinternal" and "nvsexternal" (in the folder ./examples/rtos/CC1352P_2_LAUNCHXL/drivers) demonstrate how to use the nvs driver to write to internal and external flash.

Hope this information helps!

Regards,

Sai

I have been able to read and write both internal and external flash.

It does not matter if internal or external the main goal is to be able to build an image which when flashed to the device contains this resource file in it, with the other code which would already be there.

The issue is more to do with actually building an image than reading from/writing to it with the TiRT-OS

So far I've not found a solution to do this with any TI tools on Linux or Windows.

This covers how to go about preparing a firmware over the air update but really does not cover how to put an extra file into that binary. 

I'm thinking there might not be any real good way to do this over possibly manually editing the linker scripts or some form of manual binary manipulation.

I would assume the image would look something like this

.cinit

.init_array

.ccfg

.data

.bss

.vtable

.stack

.text

.location in flash which contains the file

Maybe this is overthought and doing a simple concatenation of the generated image and the file I need to put in the image would give the intended result.

Hi Taylor,

This additional binary file, does it contain data only, or will it contain executable code?

Regards,
Fredrik

The binary file will only be data related no executable code of any kind.

That seems like a valid approach, do you happen to know of any examples doing this type of thing?

Thanks 

Hi Taylor,

We do not have any examples for exactly what I proposed. 

An alternative method would be to replicate how the SensorController FW image is stored in flash. You can find examples here: dev.ti.com/.../node

Regards,
Fredrik

Okay, both these ideas results in what I am looking for.

Thanks