• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 342 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.

MCU-PLUS-SDK-AM243X: Flash driver migration

Dominik Ondra
Prodigy 150 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

Hello Expert,

I am in need of a help regarding custom flash driver. This is a two part question.
We have created our custom flash driver using mcu_plus_sdk_am243x_08_02_00_31
And now we want to migrate the project to mcu_plus_sdk_am243x_08_05_00_24

I see in SDK 8.5. The flash driver is handled via JSON descpriton.
In accordance to SDK 8.2. we have created a source file which functions
as a flash driver. First question is:

Would it be possible to copy already created flash driver (source code as recomened in SDK 8.5.) into the SDK 8.5. and skip the JSON description based driver?

When I run the flash_diag example from SDK 8.5. the app prints out dev. and man. ID just fine and also does correct read-write test. However when continuing to read SFDP goes wrong
and the data seems to be corrupted.
Here is output of the app.




From what I understood the flash_diag should work on any flash that support SFDP. What could be the cause of this ?

Best regards,

Dominik 

  • 0
    Prodigy 150 points

    Also one more question. When trying to import example JSON to try out on the Launchpad, the sysconfig doesnt load anything and
    is tuck in loop on this frame. 

    Do you know what could be causing this Issue ?

    BR,

    Dominik

  • 0 in reply to Dominik Ondra
    TI__Mastermind 26145 points

    Hi ,

    I understand the problem and apologies for the inconvenience but we need to do a deep dive analysis for the same. For now, my suggestion would be to comment the flash open function created by the driver and write a new function of flash open (which refers to the functional code based on previous SDK) and then call out that function.This will surely help you.

    The syscfg you might need to mention the flash sizes. My suggestion would be to fill this data manually if you are facing this issue via *.json.

    Best Regards,
    Aakash