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

Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc.
MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood

GDBproxy comes with ABSOLUTELY NO WARRANTY; for details
use `--warranty' option. This is Open Source software. You are
welcome to redistribute it under certain conditions. Use the
'--copying' option for details.

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.

notice:    msp430-gdbproxy: waiting on TCP port 2000
notice:    msp430-gdbproxy: connected
debug:     msp430: msp430_connect()
debug:     msp430: msp430_current_thread_query()
debug:     msp430: msp430_offsets_query()
debug:     msp430: msp430_set_gen_thread()
debug:     msp430: msp430_read_registers()
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 set device operating frequency (13)
Are you sure the target device is really OK?

..and "lsmod | grep ppdev" produces:

ppdev                   6404   1  (autoclean)
parport                25352   2  (autoclean) [ppdev parport_pc lp]

..and "lsof | grep parport" produces:

msp430-gd 2407 dkoski    3u   CHR       99,0              26956 /dev/parport0
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.

I have also tried ddd and msp430-gdb text mode (not Insight) with the same
outcome.
Regards,
Steve


Reply via email to