RTOS/PROCESSOR-SDK-AM335X: Problem creating boot SD card

rafal Borkowski

Part Number: PROCESSOR-SDK-AM335X
Other Parts Discussed in Thread: AMIC110, TMDXICE110

Tool/software: TI-RTOS

Hi.

I'm trying to create my sd card. The app file I created following this link:

http://processors.wiki.ti.com/index.php/Processor_SDK_RTOS_BOOT_AM335x/AM437x#Tools_and_Binary_formats

to create the _ti.bin i use this command: C:\ti\pdk_am335x_1_0_7\packages\ti\starterware\tools\ti_image\tiimage.exe 0x80000000 NONE myapp.bin myapp_ti.bin after all I change the name to app. I copied the app file to the build sc card by this script

 sudo [SDK INSTALL DIR]/bin/create-sdcard.sh [SDK INSTALL DIR]/prebuilt-sdcards/[EVM DIR]/sd_card_files/

and I load the card into the BBB. This is what consol shows:

My program didn't start. I tried this solution https://e2e.ti.com/support/development_tools/compiler/f/343/t/669472?tisearch=e2e-sitesearch&keymatch=am335x%20ti%20rtos%20sd%20card%20ti%20bin%20image

over 7 years ago

0 rafal Borkowski over 7 years ago

Intellectual 650 points

I tried the solution I post above but after creating the custom.cmd file I can't build the project

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

the solution posted on the other thread is required only if you are not using GNU GCC compiler for the compilation. Christopher Weber on the other thread was using TI ARM compiler for building code which is not supported in the official TI Processor SDK RTOS hence the need for customization.

Can you confirm that you are using GNU GCC compiler for your application build? does your application use OCMC or SRAM region ? Are you booting an RTOS application or bare-metal application. If you are using one of the PDK examples to boot then notice that at the end of the build the post build steps run the script pdkAppImageCreate.bat so you shouldn`t need to manually generate the app at the end of the build.

Have you tried the debugging steps that we have described here:
processors.wiki.ti.com/.../AM437x

BAsed on your output log, it appears that SBL is booted correctly by the ROM bootloader. HAve you tried to load the symbols from .out of the MLO to see why the BOOT ROM fails.

Regards,
Rahul

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

I'm building my application using the GNU GCC. My application use OCMC and I'm using the PRU-ICSS. I'm booting the RTOS application. I tried to boot it with the created automatically created app and it jumped to the application code but after it consol show that the test was faild. I didn't look into it. I created my own app cos I want to load my application which works fine when i load it via JTAG. I didnt tried to load the symbols from .out. How do I do it?

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

Rafal,

The current version of the SBL is designed to work with application running from DDR. there is a version of the SBL that we introduced to support DDRless usecase where the application from OCMC RAM in the latest release but this was done for AMIC110 Users for running an industrial application without DDR memory. Your usecase will require customization of the SBL code. You can refer to the customization we have done for AMIC110 ICE in the bootloader source by tracing DDRLESS macro in the source.

you can refer to the DDRless build option that loads app into OCMC memory here:
processors.wiki.ti.com/.../AM437x

With more details here:
processors.wiki.ti.com/.../PRU_ICSS_EtherCAT

Note that SBL also runs from OCMC memory so when booting application into DDR memory, you need to make sure that SBL and app memory sections don`t overlap and also that when creating the app, instead of using 0x80000000(DDR start address), you need to use the start address in OCMC memory. Also note OCMC +SRAM on this device is less than 128 KB so make sure that you have room to run both SBL and app from that region.

Regards,
Rahul

The DDRless customization is only done for AMIC110 ICE board users not for beaglebone users.

http://www.ti.com/tool/TMDXICE110

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

I'm sorry I thnik i missunderstod you my program run from DDR 0x80000000 memory but it also use the OCMC memory to strore a buffor. I have also a question maybe this is the problem when I debug via JTAG on the begining of the debug CCS run a gel file do I have to copy the gel file into my app? Maybe everything boot fine but my application are missing the initialization that are in the gel file?

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

Rafal,

As a quick test can you put the buffer in DDR memory and see if that eliminates the booting issue. There may be ways to tell the bootloader not to load the heap section in OCMC to prevent this from occuring but to test this thesis it may be good to first see if moving all code to DDR solves the boot issue.

Regards,
Rahul

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

Ok I moved the buffer to DDR memory and it didn't solve my issue. What else can I try maybe I need to change the MLO file cos I'm using the default bootloader?

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

I create the default sd card and this is what I got I see the program went further but failed runnig test. I created the sd card from folder /rebuilt-sdcards/evmam335x/sd_card_files/

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

I tried to use a sample project which I found under MyExampleProjects\UART_BasicExample_bbbAM335x_armExampleProject I used the already generated app file. After inserting the sd card I end up on the Jumping to StarterWare Application... as shown on the first printscreen I think the problem is not my application but something with the generated app file. I use this command to generate the _ti.bin do I do i right? Do I use 0x80000000 as a proper image load address?
C:\ti\pdk_am335x_1_0_9\packages\ti\starterware\tools\ti_image\tiimage.exe 0x80000000 NONE C:\ti\pdk_am335x_1_0_9\packages\MyExampleProjects\UART_BasicExample_bbbAM335x_armExampleProject\Debug\app.bin C:\ti\pdk_am335x_1_0_9\packages\MyExampleProjects\UART_BasicExample_bbbAM335x_armExampleProject\Debug\app_ti.bin

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

Maybe I have to generate diffrent MLO bootloader?

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

I tried to create a new MLO file but I run into errors (Błąd 2 means error 2 I have polish windows). It looks like the make file is old. First time I run the gmake bootlioader it couldn't find the c:/ti/ccsv6/utils/cygwins/mkdir it is searching in old CCS veriosn now I have version 7. I change it but i run into more errors.

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

On this printscreen it looks like it is looking for the qspi_flash.c but I don't have it in the folder I dont know why it isnt there

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

Ok I did a mistake now I changed mcspi to mmcsd but it didn't help

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

You are not using the correct steps to build the bootloader.

you need to setup the SDK build environment as described in Getting started guide and then invoke the build for the bootloader. On windows platform the makefile based build uses gmake.

Try the following steps:

1. set SDK_INSTALL_PATH= <Path to where you have installed SDK> Default assumes C:\ti

2. cd pdk_am335x_1_x_x\packages\ti\starterware

3. gmake bootloader BUILDCFG=boot BOOTMODE=mmcsd PLATFORM=am335x-evm PROFILE=debug -s KW_BUILD=no

Hope this helps.

Regards,

Rahul

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

I install everything in default path c:\ti I did it specialy to not set the sdk_install paths on my own.

0 rafal Borkowski over 7 years ago in reply to rafal Borkowski

Intellectual 650 points

Didn't solve my problem

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

DId you try gmake instead of the Cygwin make.exe that you are trying to use. I have just tried this instructions and this seems to work seamlessly. Also, try without the ENABLE_PRU option as this is used only for specific industrial boot use cases.

Regards,

Rahul

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

This is what i get when i run gmake:

'gmake' is not recognized as an internal or external command,
operable program or batch file.

I'll try to run it under linux maybe it's gonna work.

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

This indicates to me that your SDK build environment is not setup correctly. The gmake utility is available in the C:\ti\xdctools_3_50_03_33_core
and every Processor SDK RTOS release is validated on Windows and Linux so this is definitely either corruption in your environment or issue with your setup script.

0 Rahul Prabhu over 7 years ago in reply to Rahul Prabhu

TI__Guru** 116770 points

Can you post a screenshot after your run the setup.bat script to show how the paths are detected in your environment.

0 rafal Borkowski over 7 years ago in reply to Rahul Prabhu

Intellectual 650 points

0 Rahul Prabhu over 7 years ago in reply to rafal Borkowski

TI__Guru** 116770 points

As you can see, there is bunch of errors at the start of the script that indicates that path2dos utility is not in your environment. this utility should be located at xdctools_3_50_03_33_core\packages\xdc\services\io\release

you have most likely a corrupted install of the xdctools on your machine that is causing this issue. After you run the script, the path that I indicated above should be added to your Windows %PATH% variable. If this is not the case or if the path2dos doesn`t exist then you may need to re-install the SDK and ensure that the utility is part of the install.

Regards,
Rahul