Producing TI text files

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Producing TI text files

Wayne Uroda-3
Hello all,

I need to produce a Ti .txt file to use with Ti USB BSL utility.

Caveat - I already have ihex2titext.exe which came with some ancient
version of MSPGCC. The exe file is dated November 2006. The problem with
this version is that it generates one contiguous listing for main code
memory, eg:

@4400
55 42 5c 01 35 d0 08 5a 82 45 92 43 31 40 00 44
3f 40 ac 00 0f 93 08 24 92 42 92 43 5c 01 2f 83
9f 4f f4 c2 00 24 f8 23 3f 40 e6 1e 0f 93 07 24
92 42 92 43 5c 01 1f 83 cf 43 ac 24 f9 23 b2 40
80 5a 5c 01 b0 12 e6 61 b0 12 b0 5e f2 f0 df ff
62 02 f2 d0 20 00 64 02 5f 43 b0 12 e0 63 5f 43
b0 12 fe 63 5f 43 b0 12 1c 64 3e 40 65 00 05 3c
3f 40 07 00 1f 83 fe 23 03 43 3e 53 f9 23 b0 12
20 a2 b0 12 16 90 b0 12 dc a0 b0 12 b2 a7 03 12
03 12 30 12 e4 40 03 12 0c 43 3d 40 64 00 3e 40
f7 ba 3f 40 f6 a3 b0 12 ee 46 31 52 03 12 03 12
30 12 e2 40 03 12 0c 43 3d 40 64 00 3e 40 fe ba
3f 40 84 a1 b0 12 ee 46 31 52 4f 43 b0 12 06 8a
b0 12 46 62 4f 93 19 24 3f 40 06 bb b0 12 ea 58
b0 12 12 8a 3f 40 b0 93 b0 12 0c 8a 3f 40 d0 89
b0 12 e4 93 3f 40 f4 89 b0 12 ee 93 3f 40 fa 89
b0 12 f4 93 b0 12 fa 93 1c 3c 3f 40 1e bb b0 12
ea 58 b0 12 dc 92 4f 93 03 20 5f 43 b0 12 c6 92
3f 40 f2 8f b0 12 14 84 3f 40 ce 8f b0 12 0e 84
3f 40 00 84 b0 12 10 90 b0 12 a0 8f 1f 43 b0 12
ae 82 d2 43 08 24 b0 12 0c 4a 0f 43 32 d0 f0 00
fd 3f 30 40 dc ba 8f 4e 00 00 bf 42 fe ff bf 40
44 44 fc ff bf 40 55 55 fa ff bf 40 66 66 f8 ff
bf 40 77 77 f6 ff bf 40 88 88 f4 ff bf 40 99 99
f2 ff bf 40 aa aa f0 ff bf 40 bb bb ee ff bf 40
cc cc ec ff bf 40 dd dd ea ff bf 40 ee ee e8 ff
8f 4d e6 ff 8f 43 e4 ff 3f 50 e4 ff 30 41 b2 40
00 02 40 03 b2 40 10 00 42 03 82 43 50 03 b2 40
c0 5d 52 03 b2 d0 12 00 40 03 32 c2 03 43 1c 40
dc de 21 4c 3e 41 80 4e 28 de 3f 41 3e 41 3d 41
3c 41 3b 41 3a 41 39 41 38 41 37 41 36 41 35 41
...
Data block continues for total of 2042 lines.


This seems to crash the Ti USB BSL utility (or crash the on chip code which
then causes the utility to crash). When I use a program like Elprotronic to
program this file and then read it back off the chip I get a file which
looks like the following:

@4400
55 42 5C 01 35 D0 08 5A 82 45 92 43 31 40 00 44
3F 40 AC 00 0F 93 08 24 92 42 92 43 5C 01 2F 83
9F 4F F4 C2 00 24 F8 23 3F 40 E6 1E 0F 93 07 24
92 42 92 43 5C 01 1F 83 CF 43 AC 24 F9 23 B2 40
80 5A 5C 01 B0 12 E6 61 B0 12 B0 5E F2 F0 DF FF
62 02 F2 D0 20 00 64 02 5F 43 B0 12 E0 63 5F 43
B0 12 FE 63 5F 43 B0 12 1C 64 3E 40 65 00 05 3C
3F 40 07 00 1F 83 FE 23 03 43 3E 53 F9 23 B0 12
20 A2 B0 12 16 90 B0 12 DC A0 B0 12 B2 A7 03 12
03 12 30 12 E4 40 03 12 0C 43 3D 40 64 00 3E 40
F7 BA 3F 40 F6 A3 B0 12 EE 46 31 52 03 12 03 12
30 12 E2 40 03 12 0C 43 3D 40 64 00 3E 40 FE BA
3F 40 84 A1 B0 12 EE 46 31 52 4F 43 B0 12 06 8A
B0 12 46 62 4F 93 19 24 3F 40 06 BB B0 12 EA 58
B0 12 12 8A 3F 40 B0 93 B0 12 0C 8A 3F 40 D0 89
B0 12 E4 93 3F 40 F4 89 B0 12 EE 93 3F 40 FA 89
@4500
B0 12 F4 93 B0 12 FA 93 1C 3C 3F 40 1E BB B0 12
EA 58 B0 12 DC 92 4F 93 03 20 5F 43 B0 12 C6 92
3F 40 F2 8F B0 12 14 84 3F 40 CE 8F B0 12 0E 84
3F 40 00 84 B0 12 10 90 B0 12 A0 8F 1F 43 B0 12
AE 82 D2 43 08 24 B0 12 0C 4A 0F 43 32 D0 F0 00
FD 3F 30 40 DC BA 8F 4E 00 00 BF 42 FE FF BF 40
44 44 FC FF BF 40 55 55 FA FF BF 40 66 66 F8 FF
BF 40 77 77 F6 FF BF 40 88 88 F4 FF BF 40 99 99
F2 FF BF 40 AA AA F0 FF BF 40 BB BB EE FF BF 40
CC CC EC FF BF 40 DD DD EA FF BF 40 EE EE E8 FF
8F 4D E6 FF 8F 43 E4 FF 3F 50 E4 FF 30 41 B2 40
00 02 40 03 B2 40 10 00 42 03 82 43 50 03 B2 40
C0 5D 52 03 B2 D0 12 00 40 03 32 C2 03 43 1C 40
DC DE 21 4C 3E 41 80 4E 28 DE 3F 41 3E 41 3D 41
3C 41 3B 41 3A 41 39 41 38 41 37 41 36 41 35 41
34 41 00 13 1F 43 82 43 40 03 30 41 02 12 32 C2
...
Data blocks continue in groups of 256 bytes per block.

I've checked and it is definitely not the uppercase/lowercase difference
between the two .txt files.
I've also checked and it isn't the last block length/padding (all blocks in
the elprotronic file are 256 bytes long and start on a 256 byte boundary).
I believe it is most likely a bug in Ti's USB BSL utility or in the USB BSL
code on chip which is avoided by breaking the data into 256 byte blocks.

My question: Does there exist a more modern tool for creating Ti text which
might break up the blocks in this manner? My long-term fallback position is
to get the python code from CVS, rework and rebuild it. I'd rather not
since I've never worked with python and don't have a lot of time for this
side project.

Thanks for your advice

- Wayne

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: Producing TI text files

Chris Liechti
Am 31.07.2014 um 03:24 schrieb Wayne Uroda:> Hello all,
 >
 > I need to produce a Ti .txt file to use with Ti USB BSL utility.
 >
 > Caveat - I already have ihex2titext.exe which came with some ancient
 > version of MSPGCC. The exe file is dated November 2006.

the current version is here
https://pypi.python.org/pypi/python-msp430-tools (or here if you want to
look at the source https://launchpad.net/python-msp430-tools/trunk)

ihex2titext does not exist in that form anymore, instead there is
msp430.memory.convert.

running the tool from source (assuming a basic python 2.7 installation
from python.org is installed on system):

python -m msp430.memory.convert <input.any> -f titext -o <output.txt>

(you could also omit -f as titext is the default)
in case of a binary distribution, the call is slightly different:

msp430-tool.exe convert ...


 > The problem with
 > this version is that it generates one contiguous listing for main code
 > memory,
[...]
> This seems to crash the Ti USB BSL utility (or crash the on chip
> code  which
> then causes the utility to crash). When I use a program like  Elprotronic to
> program this file and then read it back off the chip I get a file
> which looks like the following:
[...]
 > Data blocks continue in groups of 256 bytes per block.

my current tool still outputs one large blob. but it would be easy to
change that.

> I've checked and it is definitely not the uppercase/lowercase
> difference between the two .txt files. I've also checked and it isn't
> the last block length/padding (all  blocks in
> the elprotronic file are 256 bytes long and start on a 256 byte
> boundary). I believe it is most likely a bug in Ti's USB BSL utility
> or in theUSB BSL
> code on chip which is avoided by breaking the data into 256 byte
> blocks.

i do not use their tool, i've always used my own msp430-bsl (which is
included in the project linked above)

> My question: Does there exist a more modern tool for creating Ti
> text  which
> might break up the blocks in this manner? My long-term fallback
position is
> to get the python code from CVS, rework and rebuild it. I'd rather
> not since I've never worked with python and don't have a lot of time
> for this side project.



------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: Producing TI text files

Adam Ford
Check out this example Makefile

https://github.com/uctools/msp430-template/blob/master/Makefile

Using srec_cat to generate the txt file.  Specify -TITXT
After than run unix2dos on the output file to use the proper CR/LF stuff.

# TI TXT file
$(OUTDIR)/%.txt: $(OUTDIR)/%.hex
        $(MAKETXT) -O $@ -TITXT $< -I
        $(UNIX2DOS) $(OUTDIR)/$(TARGET).txt





On Thu, Jul 31, 2014 at 9:05 AM, Chris Liechti <[hidden email]> wrote:

> Am 31.07.2014 um 03:24 schrieb Wayne Uroda:> Hello all,
>  >
>  > I need to produce a Ti .txt file to use with Ti USB BSL utility.
>  >
>  > Caveat - I already have ihex2titext.exe which came with some ancient
>  > version of MSPGCC. The exe file is dated November 2006.
>
> the current version is here
> https://pypi.python.org/pypi/python-msp430-tools (or here if you want to
> look at the source https://launchpad.net/python-msp430-tools/trunk)
>
> ihex2titext does not exist in that form anymore, instead there is
> msp430.memory.convert.
>
> running the tool from source (assuming a basic python 2.7 installation
> from python.org is installed on system):
>
> python -m msp430.memory.convert <input.any> -f titext -o <output.txt>
>
> (you could also omit -f as titext is the default)
> in case of a binary distribution, the call is slightly different:
>
> msp430-tool.exe convert ...
>
>
>  > The problem with
>  > this version is that it generates one contiguous listing for main code
>  > memory,
> [...]
> > This seems to crash the Ti USB BSL utility (or crash the on chip
> > code  which
> > then causes the utility to crash). When I use a program like
>  Elprotronic to
> > program this file and then read it back off the chip I get a file
> > which looks like the following:
> [...]
>  > Data blocks continue in groups of 256 bytes per block.
>
> my current tool still outputs one large blob. but it would be easy to
> change that.
>
> > I've checked and it is definitely not the uppercase/lowercase
> > difference between the two .txt files. I've also checked and it isn't
> > the last block length/padding (all  blocks in
> > the elprotronic file are 256 bytes long and start on a 256 byte
> > boundary). I believe it is most likely a bug in Ti's USB BSL utility
> > or in theUSB BSL
> > code on chip which is avoided by breaking the data into 256 byte
> > blocks.
>
> i do not use their tool, i've always used my own msp430-bsl (which is
> included in the project linked above)
>
> > My question: Does there exist a more modern tool for creating Ti
> > text  which
> > might break up the blocks in this manner? My long-term fallback
> position is
> > to get the python code from CVS, rework and rebuild it. I'd rather
> > not since I've never worked with python and don't have a lot of time
> > for this side project.
>
>
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> Mspgcc-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|

Re: Producing TI text files

Wayne Uroda-3
Thank you I will look into both solutions :)

- Wayne

On 01/08/2014, at 22:25, Adam Ford <[hidden email]> wrote:

> Check out this example Makefile
>
> https://github.com/uctools/msp430-template/blob/master/Makefile
>
> Using srec_cat to generate the txt file.  Specify -TITXT
> After than run unix2dos on the output file to use the proper CR/LF stuff.
>
> # TI TXT file
> $(OUTDIR)/%.txt: $(OUTDIR)/%.hex
>    $(MAKETXT) -O $@ -TITXT $< -I
>    $(UNIX2DOS) $(OUTDIR)/$(TARGET).txt
>
>
>
>
>
> On Thu, Jul 31, 2014 at 9:05 AM, Chris Liechti <[hidden email]> wrote:
>
>> Am 31.07.2014 um 03:24 schrieb Wayne Uroda:> Hello all,
>>>
>>> I need to produce a Ti .txt file to use with Ti USB BSL utility.
>>>
>>> Caveat - I already have ihex2titext.exe which came with some ancient
>>> version of MSPGCC. The exe file is dated November 2006.
>>
>> the current version is here
>> https://pypi.python.org/pypi/python-msp430-tools (or here if you want to
>> look at the source https://launchpad.net/python-msp430-tools/trunk)
>>
>> ihex2titext does not exist in that form anymore, instead there is
>> msp430.memory.convert.
>>
>> running the tool from source (assuming a basic python 2.7 installation
>> from python.org is installed on system):
>>
>> python -m msp430.memory.convert <input.any> -f titext -o <output.txt>
>>
>> (you could also omit -f as titext is the default)
>> in case of a binary distribution, the call is slightly different:
>>
>> msp430-tool.exe convert ...
>>
>>
>>> The problem with
>>> this version is that it generates one contiguous listing for main code
>>> memory,
>> [...]
>>> This seems to crash the Ti USB BSL utility (or crash the on chip
>>> code  which
>>> then causes the utility to crash). When I use a program like
>> Elprotronic to
>>> program this file and then read it back off the chip I get a file
>>> which looks like the following:
>> [...]
>>> Data blocks continue in groups of 256 bytes per block.
>>
>> my current tool still outputs one large blob. but it would be easy to
>> change that.
>>
>>> I've checked and it is definitely not the uppercase/lowercase
>>> difference between the two .txt files. I've also checked and it isn't
>>> the last block length/padding (all  blocks in
>>> the elprotronic file are 256 bytes long and start on a 256 byte
>>> boundary). I believe it is most likely a bug in Ti's USB BSL utility
>>> or in theUSB BSL
>>> code on chip which is avoided by breaking the data into 256 byte
>>> blocks.
>>
>> i do not use their tool, i've always used my own msp430-bsl (which is
>> included in the project linked above)
>>
>>> My question: Does there exist a more modern tool for creating Ti
>>> text  which
>>> might break up the blocks in this manner? My long-term fallback
>> position is
>>> to get the python code from CVS, rework and rebuild it. I'd rather
>>> not since I've never worked with python and don't have a lot of time
>>> for this side project.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Infragistics Professional
>> Build stunning WinForms apps today!
>> Reboot your WinForms applications with our WinForms controls.
>> Build a bridge from your legacy apps to the future.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Mspgcc-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Mspgcc-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users