HEX6X problem when converting OUT (size > 0.5 MByte) to HEX

Hi

the problem in the subject line had been reported by one of users
of the group (as far as could b understood from the msg it related
the CCS 3.1)

appreciate if can respond :

(1) when failure indication appear - during conversion time or runtime
(2) i'm using CCS 3.3 Beta 1 - has the above reported problem
re-appeared or known to be resolved yet ?
(3) did someone ever experience the reported problem when converting
a .OUT file to .BIN ?

Tnx, Shuky Persky
------------------------------
email : s...@inter.net.il
cell : +972.50.543-2266 Start a New Thread

Shuky-

> > Hex6x utility has a history/release history separate from CCS, so the CCS
> > version may not matter
> though u r right, such utilities lose their "personality" as they are
> released
> as part of a tools-set package, rarely as standalone util (attempting to say
> never...)

What I meant is that it's likely for a new version of CCS to come out and hex6x.exe
stays the same. When you run hex6x, it has it's own version number -- suggest to go
by that.

> ...there could be different algorithms for .BIN and .HEX that
> may cause the
> problem. that is why i'm looking for any evidence (BTW - not having that
> evidence
> still doesn't mean that there is no problem, but having one will save time
> ...)

Suggest to ask the original poster for his test case parameters. Maybe you can get
his .out file and try the case exactly.

-Jeff

> -----Original Message-----
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Friday, December 01, 2006 1:58 AM
> To: Shuky Persky
> Cc: c...
> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
> HEX
>
> Shuky Persky-
>
> > the problem in the subject line had been reported by one of users
> > of the group (as far as could b understood from the msg it related
> > the CCS 3.1)
> >
> > appreciate if can respond :
> >
> > (1) when failure indication appear - during conversion time or runtime
> > (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
> > re-appeared or known to be resolved yet ?
>
> The previous discussion thread that you mention indicated that hex6x.exe has
> the
> problem. Hex6x utility has a history/release history separate from CCS, so
> the CCS
> version may not matter.
>
> > (3) did someone ever experience the reported problem when converting
> > a .OUT file to .BIN ?
>
> My understanding is it didn't matter what output format (binary or various
> forms of
> hex), the issue is code/data size in the input .out file.
>
> -Jeff Start a New Thread

hi jeff

> What I meant is that it's likely for a new version of CCS to come out and
hex6x.exe
> stays the same. When you run hex6x, it has it's own version number --
suggest to go
> by that.
known and considered as well ("personality" is lost ...)
other point is that HEX6X may be affected by other CCS tools as HEX6X is
using
as input the linker's out put. i think this is a major reason why it SHOULD
BE
tested in the context of the env. rather than refer HEX6X version ...

> Suggest to ask the original poster for his test case parameters. Maybe
you can get
> his .out file and try the case exactly.
u r right ... i can artificially create such file ... trying to save time.
i already applied to TI's support and FAEs. they stiil check. however they
claim
they never encouneterd any customer facing the discussed proble, nor for
.HEX neither
for .BIN file.

tnx, shuky

-----Original Message-----
From: Jeff Brower [mailto:j...@signalogic.com]
Sent: Friday, December 01, 2006 10:39 AM
To: Shuky Persky
Cc: c...
Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
HEX
Shuky-

> > Hex6x utility has a history/release history separate from CCS, so the
CCS
> > version may not matter
> though u r right, such utilities lose their "personality" as they are
> released
> as part of a tools-set package, rarely as standalone util (attempting to
say
> never...)

What I meant is that it's likely for a new version of CCS to come out and
hex6x.exe
stays the same. When you run hex6x, it has it's own version number --
suggest to go
by that.

> ...there could be different algorithms for .BIN and .HEX that
> may cause the
> problem. that is why i'm looking for any evidence (BTW - not having that
> evidence
> still doesn't mean that there is no problem, but having one will save time
> ...)

Suggest to ask the original poster for his test case parameters. Maybe you
can get
his .out file and try the case exactly.

-Jeff

> -----Original Message-----
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Friday, December 01, 2006 1:58 AM
> To: Shuky Persky
> Cc: c...
> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
> HEX
>
> Shuky Persky-
>
> > the problem in the subject line had been reported by one of users
> > of the group (as far as could b understood from the msg it related
> > the CCS 3.1)
> >
> > appreciate if can respond :
> >
> > (1) when failure indication appear - during conversion time or runtime
> > (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
> > re-appeared or known to be resolved yet ?
>
> The previous discussion thread that you mention indicated that hex6x.exe
has
> the
> problem. Hex6x utility has a history/release history separate from CCS,
so
> the CCS
> version may not matter.
>
> > (3) did someone ever experience the reported problem when converting
> > a .OUT file to .BIN ?
>
> My understanding is it didn't matter what output format (binary or various
> forms of
> hex), the issue is code/data size in the input .out file.
>
> -Jeff Start a New Thread

Shuky Persky-

> the problem in the subject line had been reported by one of users
> of the group (as far as could b understood from the msg it related
> the CCS 3.1)
>
> appreciate if can respond :
>
> (1) when failure indication appear - during conversion time or runtime
> (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
> re-appeared or known to be resolved yet ?

The previous discussion thread that you mention indicated that hex6x.exe has the
problem. Hex6x utility has a history/release history separate from CCS, so the CCS
version may not matter.

> (3) did someone ever experience the reported problem when converting
> a .OUT file to .BIN ?

My understanding is it didn't matter what output format (binary or various forms of
hex), the issue is code/data size in the input .out file.

-Jeff Start a New Thread

hi jeff

> Hex6x utility has a history/release history separate from CCS, so the CCS
> version may not matter
though u r right, such utilities lose their "personality" as they are
released
as part of a tools-set package, rarely as standalone util (attempting to say
never...)

> My understanding is it didn't matter what output format (binary or various
forms of
> hex), the issue is code/data size in the input .out file.
makes sense if u have knowledge about utility internal structure. as i don't
have any
such knowledge there could be different algorithms for .BIN and .HEX that
may cause the
problem. that is why i'm looking for any evidence (BTW - not having that
evidence
still doesn't mean that there is no problem, but having one will save time
...)

many tnx,
shuky

-----Original Message-----
From: Jeff Brower [mailto:j...@signalogic.com]
Sent: Friday, December 01, 2006 1:58 AM
To: Shuky Persky
Cc: c...
Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
HEX
Shuky Persky-

> the problem in the subject line had been reported by one of users
> of the group (as far as could b understood from the msg it related
> the CCS 3.1)
>
> appreciate if can respond :
>
> (1) when failure indication appear - during conversion time or runtime
> (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
> re-appeared or known to be resolved yet ?

The previous discussion thread that you mention indicated that hex6x.exe has
the
problem. Hex6x utility has a history/release history separate from CCS, so
the CCS
version may not matter.

> (3) did someone ever experience the reported problem when converting
> a .OUT file to .BIN ?

My understanding is it didn't matter what output format (binary or various
forms of
hex), the issue is code/data size in the input .out file.

-Jeff Start a New Thread

hi William.

tnx for notifying.

there are 2 lanes we can take :
(1) i can send u a .cmd file that u will need to set the address space
of the generated image. it will create a BIN file using HEX6X
(2) if u still have a contact w/ www.dsignt.de/ - may be u can ask them
if they are aware of any problem w/ HEX6X they know which could
be the reason (or one of them) for developing the DHex6x.exe

appreciate if u can advise which lane u wish to take (may be both)
lane#2 looks a better one if applicable.

tnx, shuky
-----Original Message-----
From: William C Bonner [mailto:w...@wimsworld.com]
Sent: Friday, December 01, 2006 8:01 PM
To: Shuky Persky
Cc: Jeff Brower; Shuky Persky; c...
Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
HEX
I know that this doesn't help very much, but I'm using a program called
DHex6x.exe that is right now conerting a single .out file that is
compiled on my system to 710,349 bytes and gets converted to a single
hex file that is 525,327 bytes.

I'm using a custom board that was originally designed with the help of
http://www.dsignt.de/ so I'm sure it's a custom tool that they built.

I just now tried building a hex file with the hex6x.exe on my system and
did not figure out a way to generate the exact same output.

I am running CCS 3.1.23. When I run the program with the -h option, I
get the following output.

TMS320C6x COFF/Hex Converter v5.1.0
Tools Copyright (c) 1996-2005 Texas Instruments Incorporated

Usage: \CCStudio\C6000\cgtools\bin\hex6x.exe [-options | -h] filename

Options:
-@ Read commands from 'file'
-q Quiet Operation
-e Specify entrypoint address or symbol name
-o Specify output file names
-image Select image mode
-linkerfill Include linker fill sections in images
-zero Zero based addressing
-fill Specify fill value
-romwidth Specify rom width
-memwidth Specify memory width
-datawidth Specify data width
-order Specify data ordering (endianness)
-bootorg Specify origin address or symbol of boot table ROM
-map Specify map file name

Output Format Specification:
-a Output ASCII hex format
-i Output Intel hex format
-m[1|2|3] Output Motorola S hex format
-t Output TI-Tagged hex format
-x Output Extended Tektronix hex format
--ti_txt Output TI-TXT hex format

See the User's guide for additional information
and target specific options.

Shuky Persky wrote:
> hi jeff
>> What I meant is that it's likely for a new version of CCS to come out and
>>
> hex6x.exe
>
>> stays the same. When you run hex6x, it has it's own version number --
>>
> suggest to go
>
>> by that.
>>
> known and considered as well ("personality" is lost ...)
> other point is that HEX6X may be affected by other CCS tools as HEX6X is
> using
> as input the linker's out put. i think this is a major reason why it
SHOULD
> BE
> tested in the context of the env. rather than refer HEX6X version ...
>> Suggest to ask the original poster for his test case parameters. Maybe
>>
> you can get
>
>> his .out file and try the case exactly.
>>
> u r right ... i can artificially create such file ... trying to save time.
> i already applied to TI's support and FAEs. they stiil check. however they
> claim
> they never encouneterd any customer facing the discussed proble, nor for
> .HEX neither
> for .BIN file.
>
> tnx, shuky
>
> -----Original Message-----
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Friday, December 01, 2006 10:39 AM
> To: Shuky Persky
> Cc: c...
> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
> HEX
> Shuky-
>>> Hex6x utility has a history/release history separate from CCS, so the
>>>
> CCS
>
>>> version may not matter
>>>
>> though u r right, such utilities lose their "personality" as they are
>> released
>> as part of a tools-set package, rarely as standalone util (attempting to
>>
> say
>
>> never...)
>> What I meant is that it's likely for a new version of CCS to come out and
> hex6x.exe
> stays the same. When you run hex6x, it has it's own version number --
> suggest to go
> by that.
>> ...there could be different algorithms for .BIN and .HEX that
>> may cause the
>> problem. that is why i'm looking for any evidence (BTW - not having that
>> evidence
>> still doesn't mean that there is no problem, but having one will save
time
>> ...)
>> Suggest to ask the original poster for his test case parameters. Maybe
you
> can get
> his .out file and try the case exactly.
>
> -Jeff
>> -----Original Message-----
>> From: Jeff Brower [mailto:j...@signalogic.com]
>> Sent: Friday, December 01, 2006 1:58 AM
>> To: Shuky Persky
>> Cc: c...
>> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte)
to
>> HEX
>>
>> Shuky Persky-
>>> the problem in the subject line had been reported by one of users
>>> of the group (as far as could b understood from the msg it related
>>> the CCS 3.1)
>>>
>>> appreciate if can respond :
>>>
>>> (1) when failure indication appear - during conversion time or runtime
>>> (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
>>> re-appeared or known to be resolved yet ?
>>>
>> The previous discussion thread that you mention indicated that hex6x.exe
>>
> has
>
>> the
>> problem. Hex6x utility has a history/release history separate from CCS,
>>
> so
>
>> the CCS
>> version may not matter.
>>> (3) did someone ever experience the reported problem when converting
>>> a .OUT file to .BIN ?
>>>
>> My understanding is it didn't matter what output format (binary or
various
>> forms of
>> hex), the issue is code/data size in the input .out file.
>>
>> -Jeff
>> Start a New Thread

I know that this doesn't help very much, but I'm using a program called
DHex6x.exe that is right now conerting a single .out file that is
compiled on my system to 710,349 bytes and gets converted to a single
hex file that is 525,327 bytes.

I'm using a custom board that was originally designed with the help of
http://www.dsignt.de/ so I'm sure it's a custom tool that they built.

I just now tried building a hex file with the hex6x.exe on my system and
did not figure out a way to generate the exact same output.

I am running CCS 3.1.23. When I run the program with the -h option, I
get the following output.

TMS320C6x COFF/Hex Converter v5.1.0
Tools Copyright (c) 1996-2005 Texas Instruments Incorporated

Usage: \CCStudio\C6000\cgtools\bin\hex6x.exe [-options | -h] filename

Options:
-@ Read commands from 'file'
-q Quiet Operation
-e Specify entrypoint address or symbol name
-o Specify output file names
-image Select image mode
-linkerfill Include linker fill sections in images
-zero Zero based addressing
-fill Specify fill value
-romwidth Specify rom width
-memwidth Specify memory width
-datawidth Specify data width
-order Specify data ordering (endianness)
-bootorg Specify origin address or symbol of boot table ROM
-map Specify map file name

Output Format Specification:
-a Output ASCII hex format
-i Output Intel hex format
-m[1|2|3] Output Motorola S hex format
-t Output TI-Tagged hex format
-x Output Extended Tektronix hex format
--ti_txt Output TI-TXT hex format

See the User's guide for additional information
and target specific options.

Shuky Persky wrote:
> hi jeff
>
>
>> What I meant is that it's likely for a new version of CCS to come out and
>>
> hex6x.exe
>
>> stays the same. When you run hex6x, it has it's own version number --
>>
> suggest to go
>
>> by that.
>>
> known and considered as well ("personality" is lost ...)
> other point is that HEX6X may be affected by other CCS tools as HEX6X is
> using
> as input the linker's out put. i think this is a major reason why it SHOULD
> BE
> tested in the context of the env. rather than refer HEX6X version ...
>
>
>> Suggest to ask the original poster for his test case parameters. Maybe
>>
> you can get
>
>> his .out file and try the case exactly.
>>
> u r right ... i can artificially create such file ... trying to save time.
> i already applied to TI's support and FAEs. they stiil check. however they
> claim
> they never encouneterd any customer facing the discussed proble, nor for
> .HEX neither
> for .BIN file.
>
> tnx, shuky
>
> -----Original Message-----
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Friday, December 01, 2006 10:39 AM
> To: Shuky Persky
> Cc: c...
> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
> HEX
> Shuky-
>
>
>>> Hex6x utility has a history/release history separate from CCS, so the
>>>
> CCS
>
>>> version may not matter
>>>
>> though u r right, such utilities lose their "personality" as they are
>> released
>> as part of a tools-set package, rarely as standalone util (attempting to
>>
> say
>
>> never...)
>>
>
> What I meant is that it's likely for a new version of CCS to come out and
> hex6x.exe
> stays the same. When you run hex6x, it has it's own version number --
> suggest to go
> by that.
>
>
>> ...there could be different algorithms for .BIN and .HEX that
>> may cause the
>> problem. that is why i'm looking for any evidence (BTW - not having that
>> evidence
>> still doesn't mean that there is no problem, but having one will save time
>> ...)
>>
>
> Suggest to ask the original poster for his test case parameters. Maybe you
> can get
> his .out file and try the case exactly.
>
> -Jeff
>
>
>> -----Original Message-----
>> From: Jeff Brower [mailto:j...@signalogic.com]
>> Sent: Friday, December 01, 2006 1:58 AM
>> To: Shuky Persky
>> Cc: c...
>> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
>> HEX
>>
>> Shuky Persky-
>>
>>
>>> the problem in the subject line had been reported by one of users
>>> of the group (as far as could b understood from the msg it related
>>> the CCS 3.1)
>>>
>>> appreciate if can respond :
>>>
>>> (1) when failure indication appear - during conversion time or runtime
>>> (2) i'm using CCS 3.3 Beta 1 - has the above reported problem
>>> re-appeared or known to be resolved yet ?
>>>
>> The previous discussion thread that you mention indicated that hex6x.exe
>>
> has
>
>> the
>> problem. Hex6x utility has a history/release history separate from CCS,
>>
> so
>
>> the CCS
>> version may not matter.
>>
>>
>>> (3) did someone ever experience the reported problem when converting
>>> a .OUT file to .BIN ?
>>>
>> My understanding is it didn't matter what output format (binary or various
>> forms of
>> hex), the issue is code/data size in the input .out file.
>>
>> -Jeff
>>
>
> Start a New Thread

I have no contact with the dsignt.de group, so option number two is out.
If you want to send me somethign to compare outputs, I should be able to
do that. The only options I have in the DHex6x program are the
Destination flash address and the SBSRAM configuration (for full DSP
speed or half DSP speed.)

I'm leaving for the weekend early, in about 20 minutes, so the next
you'll hear from me will probably be Monday, unless I find a good free
wireless hotspot in the airport. (unlikely in SEA.)

Here's the output it generated when I ran it just now on my program.

D.Hex6x Rev. 1.2
Configuration File: -

COFF File: C:\Documents and Settings\wim\My
Documents\ss\Model501\Model501x\Release\Model501x.out

converting C:\Documents and Settings\wim\My
Documents\ss\Model501\Model501x\Release\Model501x.out to Intel-Hex

current settings:

Program Entry Address : 0x800AEB80 (specified in COFF)
Destination in Flash Memory: 0x00010000
SBSRAM at half DSP clock

$BRID - initialised, but not allocated
.debug_frame - initialised, but not allocated
.debug_abbrev - initialised, but not allocated
.debug_info - initialised, but not allocated
.debug_line - initialised, but not allocated
.stack - uninitialised
.iram - uninitialised
.l2ram - initialised --> Hex File ( 1120 Bytes)
.cio - uninitialised
.switch - initialised --> Hex File ( 132 Bytes)
.pinit - initialised --> Hex File ( 12 Bytes)
.data - uninitialised
.bss - uninitialised
.far:1 - uninitialised
.far:2 - uninitialised
.text:1 - initialised --> Hex File ( 52704 Bytes)
.text:2 - initialised --> Hex File (153216 Bytes)
.cinit - initialised --> Hex File ( 5684 Bytes)
.const - initialised --> Hex File ( 5256 Bytes)
.sysmem - uninitialised

Intel-Hex File Model501x.hex generated successfully

Shuky Persky wrote:
> hi William.
>
> tnx for notifying.
>
> there are 2 lanes we can take :
> (1) i can send u a .cmd file that u will need to set the address space
> of the generated image. it will create a BIN file using HEX6X
> (2) if u still have a contact w/ www.dsignt.de/ - may be u can ask them
> if they are aware of any problem w/ HEX6X they know which could
> be the reason (or one of them) for developing the DHex6x.exe
>
> appreciate if u can advise which lane u wish to take (may be both)
> lane#2 looks a better one if applicable.
> Start a New Thread

Shuky-

> > ... - not asking him first is wasting time, not saving it.
> makes sense, but u know he is not the only one around.
> may some others
> have any experience/understanding on that issue as well.

TI should know, but they don't -- or at least one FAE group somewhere may know, but
others don't (doesn't surprise me). On the C6x group, there's a lot of sharp DSP
persons, including people who work with the latest TI tools and beta releases (like
Bhooshan Iyer), and they didn't know about the bug prior to Suresh's posts.

You could try comp.dsp group, but my guess is they wouldn't know as the discussions
tend more towards DSP theory and algorithm problem solving and less on TI tools.

Who else are you going to ask besides the person who found it? You know other places
to try, then please let everyone know. Thanks.

> btw -where are u located - US ?

Dallas, Texas.

-Jeff

> -----Original Message-----
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Friday, December 01, 2006 4:04 PM
> To: Shuky Persky
> Cc: Shuky Persky; c...
> Subject: Re: [c6x] HEX6X problem when converting OUT (size > 0.5 MByte) to
> HEX
>
> Shuky-
>
> > > Suggest to ask the original poster for his test case parameters. Maybe
> > you can get
> > > his .out file and try the case exactly.
> > u r right ... i can artificially create such file ... trying to save time.
> >
> > i already applied to TI's support and FAEs. they stiil check. however they
> > claim
> > they never encouneterd any customer facing the discussed proble, nor for
> > .HEX neither for .BIN file.
>
> And you believe that? Below is the last post I could find from Suresh
> Kirthi. Ask
> him for the TI case number then go back to the hotline. Suresh already
> spent a lot
> of time on this -- not asking him first is wasting time, not saving it.
>
> -Jeff
>
> -------- Original Message --------
> Subject: Re: [c6x] Re: BOOT LOADER
> Date: Tue, 14 Nov 2006 08:10:39 -0800 (PST)
> From: suresh kirthi
> To: suresh kirthi ,Jeff Brower
>
> CC: c...
>
> Jeff & 6x group,
> I spoke to TI they have accepted that hex converter (hex6x) of TI seem to
> have some
> limitation that it cannot convert *.out greater than 512KB to hex properly
> (rather
> it overwrites ).
>
> be aware of this when burning your application on flash.
>
> thank you,
> suresh kirthi
> kolkata Start a New Thread

Shuky-

> > Suggest to ask the original poster for his test case parameters. Maybe
> you can get
> > his .out file and try the case exactly.
> u r right ... i can artificially create such file ... trying to save time.
>
> i already applied to TI's support and FAEs. they stiil check. however they
> claim
> they never encouneterd any customer facing the discussed proble, nor for
> .HEX neither for .BIN file.

And you believe that? Below is the last post I could find from Suresh Kirthi. Ask
him for the TI case number then go back to the hotline. Suresh already spent a lot
of time on this -- not asking him first is wasting time, not saving it.

-Jeff
-------- Original Message --------
Subject: Re: [c6x] Re: BOOT LOADER
Date: Tue, 14 Nov 2006 08:10:39 -0800 (PST)
From: suresh kirthi
To: suresh kirthi ,Jeff Brower
CC: c...

Jeff & 6x group,
I spoke to TI they have accepted that hex converter (hex6x) of TI seem to have some
limitation that it cannot convert *.out greater than 512KB to hex properly (rather
it overwrites ).

be aware of this when burning your application on flash.

thank you,
suresh kirthi
kolkata Start a New Thread