TMDS64EVM: A program that can wait time within SBL OSPI

Kiyomasa Imaizumi

Intellectual 830 points

Part Number: TMDS64EVM

Tool/software:

Hello TI support team.

I am using SBL OSPI to start up the CA53 and CR5.

I understand that the CA53 starts the user application with Bootloader_runCpu,

and then CR5 starts with Bootloader_runSelfCpu.

CA53 initializes peripherals on startup.

CR5 also initializes peripherals when it starts up.

Since I don't want the initializations to be simultaneous,

I want the CR5 user application to start after the CA53 peripheral initialization is complete.

I would like to insert a wait time between CA53's runCpu and CR5's runSelfCpu.

By the way, in SBL, TIMER8 has a clock setting of 1 ms.

If the TIMER8 setting is changed when the CA53 user application is launched,

the TIMER8 setting will be overwritten when the CA53 runs the CPU.

If SBL OSPI inserts a wait process using TIMER8 between CA53's runCpu and runSelfCpu,

it is expected that it will not work correctly.

Is the only way to wait for processing between CA53's runCpu and CR5's runSelfCpu to be inserted a nop?

For example, please let me know if there are any processes such as wait_us or wait_ms that do not depend on the TIMER.

Best regards,

Kiyomasa Imaizumi.

29 days ago

0 Meet Thakar 29 days ago

TI__Genius 13865 points

Hi Kiyomasa,

You can also use IPC from A53 to R5, to indicate that peripheral initialization in A53 is complete and R5 can now start executing the application.

0 Kiyomasa Imaizumi 29 days ago in reply to Meet Thakar

Intellectual 830 points

Hello Meet Thakar.

Thank you for your reply.

I understand that waiting with IPC is one solution.
I would like to know how to wait with SBL
rather than waiting on the user application side.

Best regards,

Kiyomasa Imaizumi.

0 Meet Thakar 29 days ago in reply to Kiyomasa Imaizumi

TI__Genius 13865 points

Kiyomasa Imaizumi said:
I would like to know how to wait with SBL

You can add the code for the IPC in the SBL as well, and wait for the message before running Bootloader_runSelfCpu.

0 Kiyomasa Imaizumi 26 days ago in reply to Meet Thakar

Intellectual 830 points

Hello Meet Thakar.

I thought about adding an IPC to SBL to wait for the CA53 to start up.
However, since the SDK versions used by SBL and CA53 are different,
I would prefer not to use peripherals from different versions if possible.
Also, IPC is already used in the CA53 and CR5 user applications.
Even if IPC were used, I think there would be inconvenience because TIMER8 is used for semaphore timeouts.
Therefore, I think it will be necessary to wait for a time in SBL alone.

Best regards,
Kiyomasa Imaizumi.

0 Meet Thakar 25 days ago in reply to Kiyomasa Imaizumi

TI__Genius 13865 points

Hi Kiyomasa,

Another option would be to poll on an address from SBL, you can right 1 to this particular address or any other value from A53 core, which indicates that the peripheral initialization for A53 is done and from SBL you can poll this address to confirm if A53's initialization is complete before moving forward. You can consider this instead of just adding some random delay.

Best Regards,
Meet.

0 Kiyomasa Imaizumi 23 days ago in reply to Meet Thakar

Intellectual 830 points

Hello Meet Thakar.

Thank you for your suggestion.

For example, when CA53 starts up, some data is written to the memory area on MSRAM that can be shared by CA53 and SBL, and SBL reads it and recognizes that CA53 has started up?

Best regards,

Kiyomasa Imaizumi.

+1 Meet Thakar 23 days ago in reply to Kiyomasa Imaizumi

TI__Genius 13865 points

Yes, correct.

Processors

Processors forum

TMDS64EVM: A program that can wait time within SBL OSPI