AM2434: SBL_OSPI

Hi Eli,

Eli Mordel said:

I've created hello_world.hs_fs which I load with sbl_uniflash then I use sbl_ospi. It loads and runs after power-up.

Does the hello world program execute as expected?

Eli Mordel said:

I've creates my_app.hs_fs - using the same sbl , after power up it loads to DDR and MSRAM but crashes to abort handler .

At which exact point your application is going into an abort handler?

Is there a particular instruction that causes this issue?

How are you creating this custom image, are there any changes to linker/makefile for this, what other changes are there?

Hi,

I'd like to emphasize that when I load my_app with XDS debugger - it works fine !

Thanks,

Eli Mordel

Hi Meet Thakar !

Thank you for helping me.

I'm creating my.hs_fs with exact the same post build script I'm using for hello_world , which runs as expected.

I see in sbl that I get to a point of emitting "wfi".

Then I attach CCS with the XDS and I see I'm in one of abort handlers - sometimes "undefined handler".

How I proceed ? Is there a way to be sure the M3 jumped to my_app ?

Thanks,

Regards,

Eli Mordel  

Are you using a TI EVM or a custom board?

Eli Mordel said:

I'd like to emphasize that when I load my_app with XDS debugger - it works fine !

Does it mean that when you use SBL NULL and then load the program from CCS it works, but the same program doesn't work if you try to boot it via SBL OSPI?

Could you please share the SBL logs with me.

Hi Meet Thakar,

I'm using my board with am2434 . 
I've adjusted for new DDR and Flash and verified that all works with the XDS.

I also see that the hello_world example app is running well completely unchanged !

Please advice to how to proceed .

Thanks,

Regards,

Eli 

Hi,

I've noticed that I land on _c_int00 but then the _system_pre_init is corrupted (writes to a non existing memory)

and thus I never get into __TI_auto_init instead I crash into an abort handler.

Please explain in which stage does this code gets into the MSRAM ?

Where this code exist in the my_app.hs_fs ?   (I'd like to view the file - check if it's there)

Thanks,

Regards,

Eli

Hi Eli,

You can find it in the boot_armv7r.c file: https://github.com/TexasInstruments/mcupsdk-core/blob/next/source/kernel/nortos/dpl/r5/boot_armv7r.c#L41 

Could you share your entire application project as a zip file with me, if possible?

Best Regards,

Meet.

Hi,

I'm working with the AM2434ALV and using all 4 R5F cores (R5FSS0-0, R5FSS0-1, R5FSS1-0, R5FSS1-1).

Up until now, I’ve been relying on the SysConfig instance embedded within each CCS project — as provided in TI’s examples. This works, but I realize that this approach doesn’t allow SysConfig to be aware of which specific core (0-0, 0-1, 1-0, 1-1) each project is targeting.

I’ve now noticed that there is also a standalone SysConfig tool (external to CCS), which does allow selecting the target core explicitly.

Could you please clarify:

• Which SysConfig path is recommended for multicore AM243x development?

• Should I move to using the standalone SysConfig tool for proper per-core configuration (e.g., peripheral instance ownership, interrupt routing)?

• Is there a way to make the CCS-integrated SysConfig aware of the specific core number?

Thanks,

Eli

Hi Meet,

Where would I see the answer - in this forum ?

Thanks,

Best Regards,

Eli 

Please check the link I shared in my previous response.