Ditto for me.  I have started using rproxy with gdb about a week ago, and
have begun using pyjtag for downloads, for the same reason, and with pretty
much the same results.

I frequently need to run pyjtag 5 to 10 times before I get a good verify.
Some hex files seem to be more sensitive to the problem than others, and
often a change of a byte or two in a string will have a very noticeable
impact on the download success rate.

I'm guessing that it may be related to the speed of the host (1.6 GHz.
Linux).  Interestingly, I have another system (1.2 GHz.) that will not even
connect using rproxy under Linux, but it does work under Cygwin.

Walt Spicker
Salient Systems, Inc
4330 Tuller Road
Dublin, Ohio 43017
Tel 614 792-5800
Fax 614 792 5888



----- Original Message -----
From: "David Brown" <da...@westcontrol.com>
To: <mspgcc-users@lists.sourceforge.net>
Sent: Wednesday, December 11, 2002 5:42 AM
Subject: [Mspgcc-users] Problems loading new code to the target


> Hi,
>
> I now use pyjtag and gdb regularly.  Mostly I call pyjtag directly as part
> of my "make", since it burns the chip far faster than downloading via gdb
> (any ideas as to why that might be the case?).  It works well together,
and
> I can happily leave rproxy running even while using pyjtag.
>
> However, sometimes the code will not verify - I get verify errors from
> pyjtag, and if I try to use gdb to download, I get "Remote failure reply:
> E00".  I don't know how much of the code has actually been burnt
properly -
> the reset vector certainly isn't.  I can, however, download the same hex
> file using C-Spy (I'm on W2K here).  If I make any sort of change in the
> code, and recompile, then I generally have no problem burning the new
> version.  I can find no patern as to what works and what fails - my guess
is
> that there is a bug that hits for some particular checksum value, since it
> is apparently random whether my code has the problem or not, but is
entirely
> consistant for a given hex file.
>
> I can email over a couple of hex files - one that works, and one that
> fails - if it helps.
>
> I am using the TI FET, with an MSP430F149.
>
> Thanks for any ideas,
>
> David Brown
> Norway.
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>


Reply via email to