• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 96 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Using NVS driver (external)

Mateusz Foks
Prodigy 130 points
Other Parts Discussed in Thread: SYSCONFIG

Hello all,

i've few questions about using NVS driver with external flash memory.

In our project we are doing OTA firmware upgrade with use of external flash memory.

As far is i know on the launch-xl board there is mounted MX25R8035F chip, which has 1M byte of memory.

For now we can do OTA without any issues. I'm only wondering why in examples in syscfg NVS region is set to 0x256000? It is much more than 1MB.

Is this correct value?

Other thing is we want to use bigger external flash chip (4MB) in our target hardware.

We want then to divide this memory into two blocks. One block (1MB) will be used for OTA purposes and on the second one

we want to store some audio samples, that will be played after trigger.

Do you think will we be able to play short audio (which means reading data from external flash) simultaneously with doing OTA (which means writing/reading data from the same chip)?

Audio player should have higher priority access to the SPI, So i am little afraid if some timeouts during OTA will occure... (We are using now example implementation of OTA client).

regards,

mf

  • +1
    TI__Guru**** 202126 points

    Hello mf,

    I am not sure why the SysConfig NVS External Flash configuration is as such, but please note that flash_interface.h of source\ti\common\cc26xx\flash_interface uses the correct value of 0x100000 for EFL_FLASH_SIZE which should be referenced by the OTA code.  You can modify the SysConfig setting accordingly if desired.  It is possible to substitute a larger external flash device and will be able to divide the external memory into separate sections.  There are concerns with the bandwidth required by the audio player alongside an OTA update.  You will be able to delay the OTA Image Block Transfer Requests until you've properly stored the previous block after waiting for the audio segment to finish accessing the external flash, but this will result in further elongating the OTA process.  I am  not aware of any instance where this has been attempted before, but it is possible given the update is allowed to go slowly.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 130 points

    Hello Ryan,

    Thanks for answer. It's good to know that this should be possible.

    Regards,

    mf