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.

TDA4VM: why ospi need be closed befor write ospi after read ospi for sbl

Part Number: TDA4VM

 Dear Expert,

Now I find for sbl, when write ospi, if ospi has been read after init, ospi need to be close and then open. If I hadn't done it,when write ospi, it will report an error.

How can I write ospi after read? Why is this the case?

Thank you.

  • Hi,

    By default there are no write use case in SBL. Can you please share at what point are you writing to the OSPI in SBL and please share the changes that you have done to write to the SBL?

    Regards,
    Parth

  • Hi,

    Before function SBL_MulticoreImageParse, I shall write to OSPI, as shown in the figure below:

    In function SBL_OSPIBootImage, I call the function ota_update_manager. In function ota_update_manager, I shall read ospi, and then may call below function. In below function, I will do ospiinit before write ospi because if I do not close ospi then open ospi, writing to ospi will be failed.

    In function ota_save_ota_flag_data, I will write data to OSPI by SBL_ospiFlashWrite function that written by me. The function is below:

    The changes I done are above. 

    Thank you!

  • Hi,

    Apologies for delay in response.
    Is this issue still open?

    If yes, can you please share the following details:

    1) At what address you are writing the data?
    2) Are you able to write the data properly if you do ospi init before writing?

    Regards,
    Parth

  • Hi

    This issue is still open.

    1)I write data befor function SBL_MulticoreImageParse in function SBL_OSPIBootImage in SBL, and before function AppSetup in function Boot_App in mcu can boot.

    I write data in norflash address 0x3CE0000.

    2)Yes. And I find just close and then open ospi before writing also is ok.

    Thank you

  • Hello, The engineer (Parth) responsible is currently out of office for till Jan 28th.

    Please expect the response from him next week once he is back.

    Thanks.