Helio Vogel <[email protected]> writes:
> Call me dumb, but I'm having some basic problems...
>
I ran into the same ones! As usual with open source projects, the contents
comes first, and the documentation comes later! :-)
If ever :-) :-)
The primary software writers for this project are concentrating on getting
things working - which is surely the way to go. However, below are some of my
comments on how to get started with gdb/JTAG on linux:
> 1) I can't find gdbproxy, where do I get it? The links I found are
> broken, that's why I reverted to rproxy
>
I asked this a few days back. Hopefully Steve Underwood (or Chris Liechti or
someone) will fix that soon.
> 2) When I run rproxy (rproxy-linux-20021030) it complains that libHIL.so
> is missing. I saw a post mentioning HIL.c, but I can't find that
> either.
>
It's in mspgcc/jtag/hardware_access under CVS.
Go to that directory and type 'make'. Then copy libHIL.so to /usr/local/lib
(or wherever you like to keep such things).
Next you run rproxy as a daemon. It listens to some specified well-known-port,
and you need to know that port number so you can tell gdb who to speak to.
A possible problem:
I was out of action for days trying to find why I didn't have a usable/workable
/dev/parport0. The answer is there (but doesn't exactly stand out) in the
README.txt in mspgcc/jtag/hardware_access.
You need the 'ppdev' device driver, but to get one (if you've not already got
one) you must select the option "Parallel port user-mode device drivers"
in the kernel setup menu and recompile and reinstall the kernel. This might
not trouble people running stock RedHat/Debian/Mandrake kernels, but it did
for me because I'm running a custom kernel.
The option is in the 'Character Devices' submenu of the kernel config tool.
You can't use the ppdev driver if the parallel port in question is already
busy being doing something else (like being used as a printer port for
instance).
I had to shut down the 'lpd' printer system on my system.
> 3) insight is compiled with the msp430 as target, but what are the
> proper settings? Target, baud, (anything else)? I'm assuming the port
> is /dev/parport0
>
> After this is all nice and dandy, how does it work together? I come
> from dev. using the HCS12, and this is a different beast.
> Any help would be appreciated :)
>
I'm confused now. According to Sourceforge, 'Insight' is a Virtual Reality
visualization tool for financial data!
I expected you to want to run gdb!
If so, then the suggestion on the 'mspgcc - tools' page is to add the following
to your ~/.gdbinit
set remoteaddresssize 64
set remotetimeout 999999
They don't mention the vital line:
target remote localhost:4110 (or whatever well known port you've got rproxy
listening to.)
Confusing:
the 'target' command can take 'msp430' instead of 'remote' as its 1st arg,
but even Chris Liechti didn't know what *that* did back in November when
I last emailed him on the subject!
--------------------------------
Despite everyone telling me that this is the way to go, I've still not
yet actually got gdb to upload and run a program for me :-(
The interface just seems to hang for about 30 seconds then time-out with an
error message. Other messages from gdbproxy do however show that it can
see the FET module on the parallel port, and recognises my 'F149 device
plugged into it.
Rumours abound that supply voltage to the msp340 is critical. I'll be
investigating ASAP.
--
Steve Hosgood |
[email protected] | "A good plan today is better
Phone: +44 1792 203707 + ask for Steve | than a perfect plan tomorrow"
Fax: +44 70922 70944 | - Conrad Brean
--------------------------------------------+
http://tallyho.bc.nu/~steve | ( from the film "Wag the Dog" )
