Hi Carles,
Carles Perello wrote:
Hi
I tried the last version of gdbproxy,
./msp430-gdbproxy --port=2000 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_Initialize()
About to init '/dev/parport0'
inited '/dev/parport0'
debug: MSP430_Configure()
debug: MSP430_VCC(3000)
debug: MSP430_Identify()
info: msp430: Target device is a 'MSP430F147' (type 5)
debug: MSP430_Configure()
notice: msp430-gdbproxy: waiting on TCP port 2000
when I launch msp430-gdb version 5.1.1:
debug: MSP430_Registers(READ)
debug: MSP430_Registers(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: command '657261736520616c6c'
debug: command 'erase all'
debug: executing target dependant command 'erase'
debug: MSP430_Memory(WRITE)
error: msp430: Could not write device memory (7)
debug: MSP430_Memory(WRITE)
error: msp430: Could not write device memory (7)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
debug: MSP430_Memory(READ)
... never stops
my gdb script looks
ta remote 192.168.1.126:2000
set remoteaddresssize 16
set remotetimeout 999999
set download-write-size 512
set remote memory-write-packet-size 512
set remote memory-write-packet-size fixed
set remote memory-read-packet-size 512
set remote memory-read-packet-size fixed
mon erase all
lo test
Is that happening every time, or erratically? I don't an F147 board
handy to try this. However, I have been programming an F149 board
without problems. Are you sure the Vcc is high enough? A low Vcc is the
commonest reason for memory write problems. I have no idea why endless
reads might occur.
Regards,
Steve
