AM625: mcu+ build errors for sbl

Munan Xu

Part Number: AM625

Tool/software:

Hello,

I'm compiling the SBL examples on windows and I'm running into a similar issue as the referenced post where it looks like the makefile can't find some object files to link the sbl together:

 Linking: am62x:r5fss0-0:nortos:ti-arm-clang sbl_emmc_linux_stage1.release.out ...
tiarmclang: error: no such file or directory: 'obj/release/ti_drivers_config.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_drivers_open_close.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_board_config.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_board_open_close.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_dpl_config.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_pinmux_config.obj'
tiarmclang: error: no such file or directory: 'obj/release/ti_power_clock_config.obj'
make[2]: *** [sbl_emmc_linux_stage1.release.out] Error 1
make[1]: *** [sbl] Error 2
make: *** [sbl] Error 2

I'm on the latest 10.01 MCU plus SDK for AM62 and have installed the dependencies described in the getting started guide. I also tried to specifically build the sbl stage 2 that the python flash loader script requires for the AM62-SK, but that build also fails.

How do you resolve this build error?

Munan

7 months ago

0 Munan Xu 7 months ago

TI__Expert 4950 points

Also for reference I am building on Windows, it seems that the build steps in Linux work just fine...

One other point of feedback, is that for an out of box experience, it should not be required to have to build the sbl. It's one thing to run a script to flash the SBL onto OSPI, it's entirely another to have customers go through a build process for the entire SDK and examples to just get something up and running on the device...

Munan

0 Nitika Verma 7 months ago in reply to Munan Xu

TI__Expert 7385 points

Hi Munan,

I have assigned your query to our domain expert, please allow them some time to get back to you.

Regards,

Nitika

+1 Prashant Shivhare 7 months ago in reply to Nitika Verma

TI__Guru 71451 points

Hello,

What is the gmake version you have on your Windows system?

Please see the following related issue:

e2e.ti.com/.../4749765

Regards,

Prashant

0 Munan Xu 7 months ago in reply to Prashant Shivhare

TI__Expert 4950 points

Hey Prashant,

I see, I am also using gmake 3.8.1 downloaded from gnu.org.

I'll give the gmake with CCS a try, but if it's a know issue it should be noted in the documentation to use to specific CCS version or a version number that addresses this issue.

Munan

0 Munan Xu 7 months ago in reply to Munan Xu

TI__Expert 4950 points

Or what I ended up doing is just defining the MAKE command in the imports.mak

Munan

0 Prashant Shivhare 7 months ago in reply to Munan Xu

TI__Guru 71451 points

Hi Munan,

Munan Xu said:
I'll give the gmake with CCS a try, but if it's a know issue it should be noted in the documentation to use to specific CCS version or a version number that addresses this issue.

The documentation does have a section for setting up make command in Windows:

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/10_01_00_33/exports/docs/api_guide_am62x/MAKEFILE_BUILD_PAGE.html#autotoc_md199

Regards,

Prashant

0 Munan Xu 7 months ago in reply to Prashant Shivhare

TI__Expert 4950 points

Hey Prashant,

Thanks for pointing that out, I'm saying for ease of use, we already detect if we're running on windows, ccs is a documented requirement, so I think it makes sense to just define your gmake path in the makefile or imports.mak since this way the customer never needs to think about doing this since this step is very easy to miss.

It's like if there's a guaranteed way to prevent a problem from happening why wouldn't we do it because otherwise it leads to more support questions and frustrated users :)

Just my 2 cents, but again appreciate the help here!

Munan

0 Prashant Shivhare 7 months ago in reply to Munan Xu

TI__Guru 71451 points

Munan Xu said:
It's like if there's a guaranteed way to prevent a problem from happening why wouldn't we do it because otherwise it leads to more support questions and frustrated users :)

I definitely agree. I will convey the suggestion to the SDK team.

Thanks!

Processors

Processors forum

AM625: mcu+ build errors for sbl