Compiler/PROCESSOR-SDK-AM335X: Creating binary file for SD card

Rahul,
Thanks for your reply, however it is still not working... All my steps are below, but in nutshell I was already following the steps you provided links to, and not having success.

As a reminder, I do have these boot loader steps working for projects built with the GCC compiler, but our company enterprise wide tool is the TI compiler, so I need to built and test my units in that environment.

And, I am also able to get a failure just using a newly created project that just blinks the LED using the TI compiler.  Works from JTAG, but doesn't bootload.  So that is a tiny example which still fails.

First, I know the MLO bootloader works, as it is successfully used to load projects written in GCC. So I have not changed it (does it need to be changed for TI projects?).  It came from the sd_card.img.gz after unpacking the image to the SD card (the file is date 6/25/17 and is 83,028 bytes).

Also, I routinely open the "app" file in a binary editor to confirm that the header is correctly pre-pended to the file, as performed by "tiimage.exe".

And I have executed the arm-none-eabi-objcopy, tiimage, mkhex4bin and others,... following the  tiobj2bin.bat as well as pdkAppImageCreate.bat, in an attempt to manually execute the processes, and just to confirm what is happening.

I consulted the page:
processors.wiki.ti.com/.../AM437x
However, the app is relatively small (261K), so I don't think it is an issue with size. But to confirm, I checked the output linker.cmd file.  I see that  MEMORY  ... defines SRAM_LO, SRAM_HI, OCMC_RAM, and DDR, the SECTIONS  only use DDR. So everything is in DDR at address 0x8000000+

This isn't a "long time to load" problem, as I have waited plenty of time (minutes) and it never comes up.  And to repeat, this failure also occurs with a small LED flash demo program (93k in size)

------ Here is the long version of my steps ------

It's actually much longer considering the other permutations I have tried.  But I don't want to waste too much time telling you all the things I've tried. 

(I just now tried these again to confirm):
I tried just using the

${TI_PDK_INSTALL_DIR}/packages/pdkAppImageCreate.bat

and it gave me a failure... which I expected (since I am not linking to any PDK tools, that environment is not set ).

/packages/pdkAppImageCreate.bat /packages C:/ti/ccsv7/tools/compiler/ti-cgt-arm_17.9.0.STS C:/Users/scott/workspace_v7/RNDIS_NDK/Release RNDIS_NDK AM335x arm
makefile:355: recipe for target 'post-build' failed
'csv7' is not recognized as an internal or external command,
operable program or batch file.
gmake[2]: [post-build] Error 1 (ignored)

So I went straight to a command prompt to do it manually. I also modified the batch file to turn echo on and changed the forward slashes to back slashes, just to make sure Microsoft Windows wasn't going to complain.

And it can't find the tool

'C:\ti\ccsv7\tools\compiler\ti-cgt-arm_17.9.0.STS/bin/arm-none-eabi-objcopy' is not recognized as an internal or external command,

Again, expected, because the tool is a GCC tool. So I searched and found two of them, and altered the command line to point to the newer one located in: C:\ti\ccsv7\tools\compiler\gcc-arm-none-eabi-6-2017-q1-update\bin

Then I got this WARNING:

C:\ti\ccsv7\tools\compiler\gcc-arm-none-eabi-6-2017-q1-update\bin\arm-none-eabi-objcopy: RNDIS_NDK.out: warning: sh_link not set for section `.ARM.exidx'

I'm not sure about it, because I am not deeply familiar with the ELF formatting. But it moved to the next step.

It also failed on "tiimage", also not a surprise, so I fixed that path as well.  No big issue there.

And I finally got a "bin" file and an "app". I manually verified the correct values in the "TI header", so I am confident that "tiimage.exe" is executing properly.
I loaded it, and got nothing. But I didn't expect to, as the entry address was set to 0x80000000. So I changed it to the value that was listed in the MAP file: 0x80390d30
I deleted the "bin" and "app" and re-ran the script, but this "app" still doesn't work.

Next I changed the "arm-none-eabi-objcopy" to use the other location I found in C:\ti\gcc-arm-none-eabi-4_9-2015q3.  I dn=on't know if there is any significant difference.

I got the same warning, and got the same bin and app file. But that didn't work either.

in the end, my manual execution of the script looks like this:

C:\ti\pdk_am335x_1_0_7\packages\pdkAppImageCreate.bat C:\ti\pdk_am335x_1_0_7\packages C:\ti\gcc-arm-none-eabi-4_9-2015q3 C:\Users\scott\workspace_v7\RNDIS_NDK\Release RNDIS_NDK AM335x arm

Something I noticed that is interesting is that the start of the app file has the 8 byte header, followed by static TEXT, see the screen shot below.  So I know I can't use 0x80000000 as the entry point, because that isn't executable code at the beginning.  Doesn't that mean one of the steps, like "arm-none-eabi-objcopy.exe" is moving the actual entry point?   If so, where do I find out it's been moved to?

Or how am I supposed to put some kind of "jump" instruction at location 0x00 to jump to the "_c_int00" entry point, when the SYS/BIOS config is doing everything under the covers and out of my control?

I am thinking the solution to this is some modification to the linker script to change the order of the sections... but I don't know what.

I hope this helps explain what I'm doing, and helps us figure out how to make this work with the TI compiler environment.

While I haven't done this with the Sitara device, I have done this with other devices. The key here is that you cannot use the "Debug" toolbar button as that will, as you point out, replace the program already in memory. 

The "Debug" toolbar button accomplishes a number of steps:

• Builds the active project.
• Launches a debug configuration (.ccxml) and switches to the Debug perspective
• Connects to the Target processor
• Loads the program code from the active project

To connect with a program that is already resident on the target board, you need to do each of these steps independently. In the case where the program is already resident, you shouldn't need to rebuild it, so we'll skip that step.

1. Open the "Target Configurations" window (View->Target Configurations)
2. In the "Edit" perspective, find your .ccml file in the Target Config window and right-click to "Launch Selected Configuration"
   • At this point, you should be in the "Debug" perspective
3. Connect to your target (Run->Connect Target)
   • At this point, you should be connected to your target board
4. You don't want to load your program, but you will probably want to load the debug symbols from your program
   • Run->Load->Load Symbols... and then select your executable file from your project

Hopefully, this will get you started.

-Scott

Scott, Rahul,

None of this is working...

1.  I tried to create a Target config and open it.  It seemed to work, until I did a "connect to target"  It tells me the device is held in reset.

WHAT??  It's a bare board, even the EEMC has been erased.  The board is dead until I load it with something.  There are no connectors hanging off of it except for the JTAG.  Where does it think it's being HELD in a reset condition?

But, with my project open, it downloads and runs my "Blink LED" test program.  So why will it REFUSE to let me connect to the device with this one-off target config file??

So I can forget trying to attach to the MLO bootloader or to my code.  However, as I said when I started this, the whole thing works when built in GNU, except I have to manually change the entry point to match what the map files told me it was.  Therefore, I conclude that the MLO is working just fine.

2.  I tried to follow the link Rahul provided:

processors.wiki.ti.com/.../Accessing_c_int00

There is a statement "To place the .text symbol at an explicit address, add a custom linker command (.cmd) file to your project"...  Really?  Named what?  Where?  I just created a CUSTOM.CMD file, and it made NO DIFFERENCE in my output.  The map file is completely unchanged whether the file is there or not.

If it would tell me something substantially less vague, this actually might solve my problem.  Then again, it might not.  I tried to manually assign the _c_init00 to location 0x8000000, and the linked said it wouldn't fit.  Duh.  I need a "jump to _c_int00" instruction there.  Not the whole entry point.  With Sys/Bios doing everything behind my back, I have no idea how this would be done.

-CSW

Scott, Rahul,

Update... but it's still broken. 

But I did manage to get it to connect and load...  The problem was I didn't highlight the A8 core when I selected "Connect".  It apparently thought I wanted to connect to the M3 core.  (when I debug a project the FIRST time, it asks me which core.  Then it remembers.  I imported the same "ccxml" file from a project, but it didn't know I wanted to connect to the A8.  WHY??  Why doesn't it know which core to use from the "ccxml" when it remember for my project.  Truly VERY annoying.  But I digress...)

Okay, step ONE.  A brutally simply "Flash the LED" program works when written in GNU, but doesn't work when written in TI compiler. Identical code.

The GNU version has a map file that says:

 .c_int00       0x80000000       0xb4 C:\ti\bios_6_46_05_55\packages\gnu\targets\arm\rtsv7A\lib\boot.aa8fg(boot.oa8fg)
                0x80000000                _c_int00

So, we can see that the entry point is at the beginning of the memory location, where we would expect.  On the other hand, the TI version map files says:

OUTPUT FILE NAME:   <TI_BLinkTest.out>
ENTRY POINT SYMBOL: "_c_int00"  address: 80008698

So, we can see it does't match.  And I know of no way to FORCE it to match.  The Sys/Bios is providing this stuff...

So, put the GNU version of APP on the SD card, along with the "bootloader_boot_mmcsd_a8host_debug_ti.bin"  which I renamed to MLO. 

I inserted the CD card, then I connected the JTAG, loaded the "bootloader_boot_mmcsd_a8host_debug.out" loader, which should match the MLO of the code.  Stopped at the beginning, loaded the "sbl_main.c" file, and was able to step through the bootloader.  So, that is all good.  It loaded the "APP" and read the TI header, loaded the program to address 0x8000000 as expected.  All works.

I repeated this with the APP set to the entry point of 0x80008698  because that is what the map file tells me. And it did load the image, and I could see the address of 0x80008698. But, here's the problem.  The MLO is assuming the the entry point and the base address ARE THE SAME.  Well, that will NEVER work.

Here's the code from the MLO  sbl_mmcsd.c, line 221:

        pDestAddr = (uint8_t *)imageHdr.load_addr;
        *pEntryPoint = imageHdr.load_addr;
    }

So, how am I supposed to set an entry point for the "_c_int00" location that is DIFFERENT from the destination address?  Because that is what the TI version of the tools did to me!

Or... how am I supposed to tell the TI version of the compiler tools to place the "_c_int00" function (or it's equivalent BL instruction) at the location 0x80000000 to match the load address??  I'll be happy to just add a miniature assembler code with a BL instruction, if I could tell the build system where to place it.  But alas, the Sys/Bios doesn't let me do that that I can find.

Rahul Prabhu said:

Chris,

For this mechanism to work, your load address and entry point needs to align. My recommendation is still to use the guidance provided in the wiki but modify this to match your linker output
processors.wiki.ti.com/.../Accessing_c_int00

Rahul,

I've read this. And I've tried it,  But this doesn't provide me enough information... "add a custom linker command (.cmd) file to your project "

WHAT linker cmd file??   I will repeat:  The Sys/Bios build environment ERASES AND REWRITES the build scripts.  So how am I supposed to put in my own??

I just arbitrarily created a "command.cmd" file, and just tossed it into the project.  There was no difference.

Rahul Prabhu said:

that guidance seems to be provided for DSP/C28x devices where the entry point is .text:_c_int00. since you are using TI ARM compiler and your entry point is being placed in section .c_int00. Try and use the following syntax that is provided by the TI ARM compiler team here and let us know if you still see this issues.
e2e.ti.com/.../2209073

Per one of the replies, it clearly DOES NOT SAY where to stick that piece of text.  So I just added it to the CFG script:

 I added ".c_int00 { boot.aea8f<boot.oea8f>(.text) } : load > 0x80000000, run > 0x80000000" to the script.  And of course the XDC barfed all over it.

js: "C:/Users/scott/workspace_v7/TI_BLinkTest/app.cfg", line 1: Compilation produced 1 syntax errors.
js: "./package/cfg/app_pea8fnv.cfg", line 195: Compilation produced 1 syntax errors. (C:/Users/scott/workspace_v7/TI_BLinkTest/app.cfg#1)
gmake.exe: *** [package/cfg/app_pea8fnv.xdl] Error 1

So my question remains:  How do I coerce the build environment to set these values to what I want, when it doing all this stuff behind my back, and under the covers?

I know WHERE the load and entry point needs to be.  I know WHAT ADDRESS the entry point needs to be. I know WHAT SYMBOL needs to be set to that address.  I know what SECTION NAME needs to be set to that address...  How do I do it when XDC and Sys/BIOS are running everything behind my back and don't let me control it?  

Chris,

The syntax from the other E2E needs to be added in the custom.cmd file that you had added to your project and not in the .cfg file. The .cmd file will not be used by the XDC tools. It will only be consumed by the TI ARM Linker utility when it is making the decision of placing symbols.

Regards,
Rahul

Rahul,

Can you spell this out??  All I am doing it throwing random changes because nothing is specific.

In my "custom.cmd" file:

.c_int00 { boot.aea8f<boot.oea8f>(.text) } : load > 0x80000000, run > 0x80000000

Error:

<Linking>
"../custom.cmd", line 1: error #10008-D: cannot find file ".c_int00"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of "{"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of ":"
error #10010: errors encountered during linking; "TI_BLinkTest.out" not built

Then I changed the label:

._c_int00 { boot.aea8f<boot.oea8f>(.text) } : load > 0x80000000, run > 0x80000000

Error:

<Linking>
"../custom.cmd", line 1: error #10008-D: cannot find file "._c_int00"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of "{"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of ":"
error #10010: errors encountered during linking; "TI_BLinkTest.out" not built

And again, change the label:

_c_int00 { boot.aea8f<boot.oea8f>(.text) } : load > 0x80000000, run > 0x80000000

Still:

<Linking>
"../custom.cmd", line 1: error #10008-D: cannot find file "_c_int00"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of "{"
"../custom.cmd", line 1: error #10021-D: expecting filename, option, MEMORY, or SECTIONS instead of ":"
error #10010: errors encountered during linking; "TI_BLinkTest.out" not built

Okay... enough of this...  lets try making a "linker" looking script:

 SECTIONS {
   .text:c_int00 > 0x80000000
 }

No error, but the entry point is still 0x80008698.  Tried "._c_int00"  "_c_int00"  etc...  

Try sticking that text from the E2E posing inside a "section"

 SECTIONS {
   .text:.c_int00 { boot.aea8f<boot.oea8f>(.text) } : load > 0x80000000, run > 0x80000000
 }

Nope. Error:

<Linking>
"../custom.cmd", line 2: error #10008-D: cannot find file "boot.aea8f"
"../custom.cmd", line 2: error #10026-D: expecting output section, GROUP, or UNION instead of ":"
"../custom.cmd", line 2: warning #10068-D: no matching section
error #10010: errors encountered during linking; "TI_BLinkTest.out" not built

( boot.aea8f is the startup entry generated by XDC??  But not in this case.  So what is it in this case?  And where is that documented?)

So I tried removing that file, and using "_c_int00"  "._c_int00"  ".c_int00"  ".c_int00"...

SECTIONS {
   .text:c_int00  : load > 0x80000000, run > 0x80000000
}

No build errors, but the entry point in the map file is STILL

OUTPUT FILE NAME:   <TI_BLinkTest.out>
ENTRY POINT SYMBOL: "_c_int00"  address: 80008698

It is not working.