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.
Tool/software:
The SBL OSPI example project
mcu_plus_sdk_am263px_09_02_00_56\examples\drivers\boot\sbl_ospi\am263px-cc
... in SDK:
mcu_plus_sdk_am263px_09_02_00_56
... uses Lockstep in the BOOTLOADER driver configuration.
See:
Questions:
1)
Is this the project used to build the prebuilt image in:
mcu_plus_sdk_am263px_09_02_00_56\tools\boot\sbl_prebuilt\am263px-cc
2)
What is the reason for the Lockstep configuration?
Is this the project used to build the prebuilt image in:
mcu_plus_sdk_am263px_09_02_00_56\tools\boot\sbl_prebuilt\am263px-cc
Hi Scott, that is correct conclusion, as a part of post build step the built binary is copied to the prebuilt folder
2)
What is the reason for the Lockstep configuration?
No particular reason, just one of the option that can be selected.
Hi Nilabh,
3)
I use OSPI SBL while running the cores in "standalone" mode (cores running different executables) without noticing problems.
If "Lockstep" is selected, for the BOOTLOADER parameters:
R5FSS0 Operating Mode
R5FSS1 Operating Mode
... does this mean that the cores are expected to execute om lockstep mode?
4)
I want to use:
mcu_plus_sdk_am263px_09_02_00_56\examples\drivers\boot\sbl_ospi\am263px-cc
... as the a starting point for a OSPI SBL.
My cores will be running different executables. Is it important to use "standalone" mode for BOOTLOADER parameters:
R5FSS0 Operating Mode
R5FSS1 Operating Mode
... ?
Regards,
Tollman
I use OSPI SBL while running the cores in "standalone" mode (cores running different executables) without noticing problems.
If "Lockstep" is selected, for the BOOTLOADER parameters:
R5FSS0 Operating Mode
R5FSS1 Operating Mode
... does this mean that the cores are expected to execute om lockstep mode?
Hi Tollman,
This is not very clear to me. Do you see any issue with cores running in non-lockstep mode?
I want to use:
mcu_plus_sdk_am263px_09_02_00_56\examples\drivers\boot\sbl_ospi\am263px-cc
... as the a starting point for a OSPI SBL.
My cores will be running different executables. Is it important to use "standalone" mode for BOOTLOADER parameters:
R5FSS0 Operating Mode
R5FSS1 Operating Mode
... ?
This would be a choice. Can you explain your bootloader design a bit, so I comment better here?
Again
Hi Nilabh,
Regarding:
" Do you see any issue with cores running in non-lockstep mode?"
I'm not having a problem, but the configuration of:
R5FSS0 Operating Mode
R5FSS1 Operating Mode
... in the Bootloader SysConfig seems like it may either be wrong or irrelevant.
I think, since my cores are not using lockstep, I may change the configuration to be "standalone".
Please let me know if that is a good approach.
Regards,
Tollman
... in the Bootloader SysConfig seems like it may either be wrong or irrelevant.
Hi Tollman except IPC we do not use Standalone in any other example, so we tend to keep the two cores in lock step.
I think, since my cores are not using lockstep, I may change the configuration to be "standalone".
Please let me know if that is a good approach.
Yes it is a good approach if you need standalone alone mode for your application. As i mentioned before it is a application level consideration.