AM2432: SDK 8.5.0.24 OSPI Multipartition bootloader can't set the M4 clock

Hi Scott Leibelt,

Let me try this example on my local setup and get back to you with this by end of the day.

Best Regards,
Aakash

Hi Scott Leibelt,

I tried the same on my end and it worked on the same release tag.

Are you using this default_sbl_ospi_multi_partition.cfg file or a different *.cfg file ?

Attached the file below -

/cfs-file/__key/communityserver-discussions-components-files/908/default_5F00_sbl_5F00_ospi_5F00_multi_5F00_partition.cfg 

Best Regards,
Aakash

Hi Akash,

I'm using the default_sbl_ospi_multi_partiton.cfg file with different paths to the ipc examples.  I'm using version 8.05.00.24 of the SDK which, when I build the examples, apparently uses a different version of DMSC firmware.  In your screenshot, the DMSC firmware version is "8.4.7.-- v08.04.07 (Jolly Jellyfi", however, when I build the examples using SDK 8.05.00.24, the DMSC version I see is "8.5.3 -- v08.05.03 (Chill Capybar".

Here is what I see on my terminal:

Starting OSPI Multi-Partition Bootloader ...

DMSC Firmware Version 8.5.3--v08.05.03 (Chill Capybar
DMSC Firmware revision 0x8
DMSC ABI revision 3.1

INFO: Bootloader_runCpu:155: CPU r5f1-0  is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU r5f1-1 is initialized to 800000000 Hz !!!
ERROR: Bootloader_socCpuSetClock:559: CPU clock set for 400000000 Hz failed for m4f0-0
Some tests have failed!!

Hi Scott Leibelt,

I have replicated the issue with the latest .

Scott Leibelt said:

DMSC Firmware Version 8.5.3--v08.05.03 (Chill Capybar

Let me work on the same. I will try to come back on this by 23rd January.

Best Regards,
Aakash