From 4a298cdb3b286eb7f6b3c1739308dfc9b30d4298 Mon Sep 17 00:00:00 2001 From: Daniel Beer Date: Tue, 23 Mar 2010 16:43:12 +1300 Subject: [PATCH] Version 0.6 --- main.c | 7 +++++-- mspdebug.man | 19 ++++++++----------- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/main.c b/main.c index 9edffaa..15bdb31 100644 --- a/main.c +++ b/main.c @@ -470,6 +470,7 @@ static int cmd_run(char **arg) { char *bp_text = get_arg(arg); int bp_addr; + device_status_t status; if (bp_text) { if (stab_parse(bp_text, &bp_addr) < 0) { @@ -491,7 +492,9 @@ static int cmd_run(char **arg) printf("Running."); printf(" Press Ctrl+C to interrupt...\n"); - msp430_dev->wait(1); + status = msp430_dev->wait(1); + if (status == DEVICE_STATUS_INTR) + printf("\n"); if (msp430_dev->control(DEVICE_CTL_HALT) < 0) return -1; @@ -988,7 +991,7 @@ int main(int argc, char **argv) int mode = 0; puts( -"MSPDebug version 0.5 - debugging tool for MSP430 MCUs\n" +"MSPDebug version 0.6 - debugging tool for MSP430 MCUs\n" "Copyright (C) 2009, 2010 Daniel Beer \n" "This is free software; see the source for copying conditions. There is NO\n" "warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n"); diff --git a/mspdebug.man b/mspdebug.man index a1cebb5..ca68d30 100644 --- a/mspdebug.man +++ b/mspdebug.man @@ -1,4 +1,4 @@ -.TH mspdebug 1 "20 Mar 2010" "Version 0.5" +.TH mspdebug 1 "20 Mar 2010" "Version 0.6" .SH NAME MSPDebug - debugging tool for MSP430 MCUs .SH SYNOPSIS @@ -132,6 +132,9 @@ corresponding to printable bytes, and . for non-printing characters. Write a sequence of bytes at the given memory address. The address given may be an address expression. Bytes values are two-digit hexadecimal numbers separated by spaces. + +Unless used in the simulation mode, this command can only be used for +programming flash memory. .IP "nosyms" Clear all symbols from the symbol table. Symbols may be reloaded with the \fBsyms\fR command. @@ -223,16 +226,6 @@ complete. If you see a message like the following after connecting: Please report it, as well as the model of the device you are using. -Some firmware versions of the FET430UIF are not supported. If you -encounter a version which doesn't work, you should try to extract -the firmware using the command: - -.B mspdebug -B \fIdevice\fP 'hexout 0x2500 0xdb00 firmware.hex' - -Please send the HEX file, along with the firmware version. The -firmware version is reported in the transcript when connecting -with the \fB-u\fR option. - Firmware version 20107000 is known to work with MSPDebug, and you can update your FET to this version using the proprietary \fBmsp430\-gdbproxy\fR program: @@ -242,6 +235,10 @@ update your FET to this version using the proprietary This command updates the FET firmware using the same bootloader supported by MSPDebug's \fB\-B\fR option. However, as mentioned above, MSPDebug does not support erase or programming in this mode. + +When using the GDB remote stub in simulation and an IO read request +occurs, any request to interrupt from GDB will not be acknowledged +until the IO request is either completed or aborted. .SH COPYRIGHT Copyright (C) 2009, 2010 Daniel Beer