TMS320C6657: how can i make btbl file from out.

Hi,

The engineer responsible is currently out of office. Please expect 1 day delay in response.

Regards,
Sivadeep

Hi Eric,

Can you share the content of "convert_hex.rmd" file?

Regards,

Betsy Varughese

Hello TI team,

I am trying to generate a NOR flash boot image for the TMS320C6657. I used a batch file called elf2HBin.bat to create a .bin file from my .out file, but the board does not boot from NOR flash with this file.

set C6000_CG_DIR="C:\ti\ccsv5\tools\compiler\c6000"
set TOOL_DIR="..\..\..\..\..\..\"
set TARGET=6657
set ENDIAN=little
set PATH=%PATH%;%SystemRoot%\system32;%SystemRoot%;

@echo off

echo C6000_CG_DIR set as: %C6000_CG_DIR%
echo TARGET set as: %TARGET%
echo IBL_ROOT_DIR set as : %IBL_ROOT_DIR%

echo Converting .out to HEX ...
if %ENDIAN% == little (
hex6x -order L convert_hex.rmd boot.out
) else (
hex6x -order M convert_hex.rmd boot.out
)

Bttbl2Hfile boot.btbl boot.h boot.bin

hfile2array boot.h APP1_Code.h bootCode

make_imageIBL.exe boot.out boot.img

Regards,

Eric

Hi Eric,

I was on leave yesterday. I will look into this and update you shortly.

Regards,

Betsy Varughese

Hello Betsy,

boot.out
-map boot.map
-a
-image
-zero
-order L
-memwidth 16
-romwidth 16
-boot
-e _c_int00

ROMS
{
ROM1: org = 0x80000000, length = 0x20000, memwidth = 16, romwidth = 16
files = { boot.btbl }
}

It is my using rmd file.

Regards,

Eric

Hi Betsy,


RA_TYPE_C_v0_01.out
-map RA_TYPE_C_v0_01.map
-a
-image
-zero
-order L
-memwidth 8
-romwidth 16
-boot
-bootorg 0x70000900
-bootsection .boot_load 0x70000000

ROMS
{
FLASH: org = 0x70000000, len = 0x20000, romwidth = 16, files = {C_v0_01.hex}
}


It is my rmd file for single core0 of DSP useage.

Regards,

Eric

can  i use single source to target dual Core(Multi core) usage on the TMS320C6657?

Hi Eric,

I hope you are trying without IBL.

Regards,

Betsy Varughese

Hello Betsy,

Yes. I didn't use ibl.

RA_TYPE_C_v0_01.out
-map RA_TYPE_C_v0_01.map
-a
-image
-zero
-order L
-memwidth 8
-romwidth 16
-boot
-bootorg 0x70000900
-bootsection .boot_load 0x70000000

ROMS
{
FLASH: org = 0x70000000, len = 0x20000, romwidth = 16, files = {RA_TYPE_C_v0_01.hex}
}

This process generates an App_Code.h file from a single-core .out file, and it works as expected.

set C6000_CG_DIR="C:\ti\ccsv5\tools\compiler\c6000"
set TOOL_DIR="..\..\..\..\..\..\"
set TARGET=6657
set ENDIAN=little
set PATH=%PATH%;%SystemRoot%\system32;%SystemRoot%;

@echo off

echo C6000_CG_DIR set as: %C6000_CG_DIR%
echo TARGET set as: %TARGET%
echo IBL_ROOT_DIR set as : %IBL_ROOT_DIR%

echo Converting .out to HEX ...
if %ENDIAN% == little (
hex6x -order L convert_hex.rmd boot.out
) else (
hex6x -order M convert_hex.rmd boot.out
)

hex2h.exe boot.btbl boot2h.h

Bttbl2Hfile boot.btbl boot.h boot.bin

hfile2array boot.h APP1_Code.h bootCode

make_imageIBL.exe boot.out boot.img

-a
-boot
-e _c_int00

ROMS
{
ROM1: org = 0x80000000, length = 0x20000, memwidth = 32, romwidth = 32
files = { boot.btbl }
}

This section describes how to generate dual-core .out files (from a single source), and then convert them into .bin and boot2h.h files for flash boot.

Regards,

Eric

Hi Eric,

Just mentioning below the steps we need to follow to generate the .btbl:

// You can use Hex conversion utility
1. Create a Hex conversion command file (.cmd/.rmd)
2. Run the hex utility using the created .cmd/.rmd and .out file
3. The "step :2" will generate a .btbl 
4. Burn the .btbl to flash.

Added a note here for reference.

Regards,

Betsy Varughese

Hi Eric,

eric rk said:

This process generates an App_Code.h file from a single-core .out file, and it works as expected.

Just to confirm, you mean that with this, you are able to flash without any issues, Is that correct?

eric rk said:

This section describes how to generate dual-core .out files (from a single source), and then convert them into .bin and boot2h.h files for flash boot.

I'm checking in detail and will get back to you.

Regards,

Betsy Varughese

Hi Eric,

eric rk said:

boot.out
-map boot.map
-a
-image
-zero
-order L
-memwidth 16
-romwidth 16
-boot
-e _c_int00

ROMS
{
ROM1: org = 0x80000000, length = 0x20000, memwidth = 16, romwidth = 16
files = { boot.btbl }
}

It is my using rmd file.

Can you try replace -image with -btbl, and check?

Regards,

Betsy Varughese

Hello Betsy,




I did change to try rmd file but it has errors.

Regards,

Eric

Hi Eric,

Which version of hex6x version?

Regards,

Betsy Varughese

Hello Betsy,


I'm using the hex6x of ti-cgt-c6000_8.3.5.


Regards,

Eric

Hi Eric,

Betsy Varughese said:

Which version of hex6x version?

Then it will support. No worries.

eric rk said:

Can you try to add -btbl option after -boot?

Regards,

Betsy Varughese

Hello Betsy,

I tried to modify this file, but it still has errors.

Regards,

Eric

Hi Eric,

Let me check on this and get back to you.

Regards,

Betsy Varughese

Hi Eric,

Can you please do me a favor? From the error log, it looks like you are using TI CGT version 8.3.5. Just to confirm that the correct hex utility from the same toolchain path is being used (and not from a different PATH), could you please check the following in the command prompt:

1. where hex6x

2. hex6x -version

Regards,

Betsy Varughese

Hello Betsy,


It is the correct hex6x file. I copied it to my working folder.

Regards,

Eric

Hi Eric,

Can you update the .bat file with -boot -btbl option ?

Regards,

Betsy Varughese

Hi Eric,

Betsy Varughese said:

1. where hex6x

2. hex6x -version

if possible, can you share the screenshot?

Regards,

Betsy Varughese

Hello Betsy,

Is it correct?

Regards,

Eric

Hi Eric,

Thanks alot.

I checked the helper function for this version, and it only supports the image option. That’s the reason you’re getting an invalid error when using the btbl option. Let me check on the other possibilites and let you know.

Regards,

Betsy Varughese

Hi Eric,

Can you give it a try:

boot.out
-map boot.map
-a
-image
-zero
-order L
-memwidth 16
-romwidth 16
-boot
-e _c_int00

ROMS
{
ROM1: org = 0x70000000, length = 0x20000, memwidth = 16, romwidth = 16
files = { boot.bin }
}

Regards,

Betsy Varughese

Hi Eric,

I believe the error is occurring because the .bat file hasn't been updated accordingly.

Just to get more clarity on this, are you able to generate the file using the .rmd provided below? Could you please also confirm the offset used here is correct?

eric rk said:

boot.out
-map boot.map
-a
-image
-zero
-order L
-memwidth 16
-romwidth 16
-boot
-e _c_int00

ROMS
{
ROM1: org = 0x80000000, length = 0x20000, memwidth = 16, romwidth = 16
files = { boot.btbl }
}

Regards,

Betsy Varughese

hello betsy,

i did try it.

Regards,

Eric

Hello betsy,

How can i use the iBL in this situation?

Regards,

Eric

Hi Eric,

I am attaching the previous E2E post here (Thread related to length mismatch issue in btbl),

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1173142/tms320c6678-the-length-of-the-section-in-the-btbl-file-does-not-match-the-length-of-the-section-shown-in-the-map-file,

We've also included a few FAQ links inside. Could you please confirm if this addresses your concern?

Regards,

Betsy Varughese

Hi Eric,

it has some error.

Regards,

Eric

Hi Eric, 

Can you check and let me know.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1173142/tms320c6678-the-length-of-the-section-in-the-btbl-file-does-not-match-the-length-of-the-section-shown-in-the-map-file

Regards,

Betsy Varughese