On Mon, 22 Mar 2004 07:43:58 +0800 Steve Underwood <ste...@coppice.org> wrote:
> Hi David, > > David Koski wrote: > > >I can run Insite on either Windows or Linux (two different hardware) to > >successfully connect to and run programs via msp430-gdbproxy.exe for Windows. > >But running msp430-gdbproxy on Linux fails. The debug messages are: > > > ># msp430-gdbproxy --debug msp430 <snip> > >debug: msp430: msp430_open() > >info: msp430: Target device is a 'MSP430F11x1' (type 2) > > > > > This means gdbproxy is communicating with your target OK. It cannot > determine the device type unless the JTAG interface is functional. <snip> > Are you sure the target device is really OK? Yes, the target device (a brand new OLIMEX MSP430-P-1121) works using a windows host for msp430-gdbproxy. I can erase, run, etc. no problem. <snip> > As I said before, this is looking in the wrong area. The parallel port > must be functional. However, it might be worth looking in your BIOS, and > making sure the parallel port is set to the basic SPP mode - not ECP or > EPP. On some motherboards using ECP or EPP modes breaks some tools like > gdbproxy. On other motherboard is doesn't matter. We have never really > figured out the problem, but it may be dues to changes in the port timing. Okay, I changed the parallel port in the BIOS to "Normal". Still no joy. I am assuming "Normal" (Award BIOS) is SPP. ECP and EPP are separate options. (I have tried them all before). But the outcome is the same: <snip> debug: msp430: msp430_write_mem(0xF000, ptr, 0) debug: msp430: msp430_write_mem(0xF000, ptr, 39) error: msp430: Could not preserve/restore device memory (12) debug: msp430: msp430_write_mem(0xF000, ptr, 39) error: msp430: Could not preserve/restore device memory (12) Do you suppose it would help to build the kernel with ppdev built-in instead as a module? David Koski david.nosp...@kosmosisland.com !.nospham
