• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 348 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2652R: External flash writing(MX25R8035F)

Mohamed Aslam
Intellectual 310 points

Part Number: CC2652R

Hi all,
I am working on simple peripheral off chip OAD project. For my application, I want to store lot of data in external flash. So I want to know the address range (start and end address) which is used by the simple peripheral off chip OAD project to store BIM image /other data into external flash.

By knowing this, I can store my application data into external flash area which is not used by the simple peripheral off chip OAD project.

Regards,
Aslam

  • 0
    TI__Mastermind 38535 points

    Hi Aslam,

    This will depend on the size of the incoming image that's sent via OAD. I would recommend placing your application data at the end of the available memory to minimize the possibility of overwriting, and maybe even including some error checking to ensure your two pages don't overwrite one another. You can find a lot of the code for this in oadImgBlockWrite in OAD/oad.c

    Best,

    Nate

  • 0 in reply to Nathan Block
    Intellectual 310 points

    Dear Nate,

              We are going to store up to 16mb data in external flash. So we cant place our application data at the end available memory. So, we want to know the exact memory location allocated in external flash to store incoming image that's sent via OAD in the simple peripheral off chip OAD project. Please help us on this.

    Regards,

    Aslam

  • +1 in reply to Mohamed Aslam
    TI__Mastermind 38535 points

    Hi Aslam,

    If you look at our documentation here, you can see that the amount of space allocated in the external memory device for the incoming image is allocated dynamically, so it can take up as much or as little space as required. If you're worried about overwriting the OAD image with the data you want to store in flash, I'd recommend implementing software to prevent your data and OAD image from overwriting one another, perhaps a counter or a maximum memory size.

    Best,

    Nate