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 <cliec...@gmx.net> 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
> Mspgcc-users@lists.sourceforge.net
> 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
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
