Version 0.20

This commit is contained in:
Daniel Beer 2012-08-14 17:24:17 +12:00
parent b9b2c7135f
commit 213c892a00
4 changed files with 44 additions and 16 deletions

View File

@ -1,3 +1,15 @@
Version 0.20 - 14 Aug 2012
* Support for new chips: MSP430F6736, MSP430F2252, MSP430G2403,
MSP430F6435.
* Support for building under Cygwin.
* Support for watchpoints using MSP430.DLL (tilib) driver.
* Support for GoodFET (memory access/programming only).
* Various bug fixes, including many disassembly fixes and an
issue causing FRAM reset-vector corruption.
* Basic C++ demangling support.
* New commands: "fill" and "verify".
* Erase requests are now ignored when using FRAM chips.
Version 0.19 - 3 Mar 2012
* Support for MSP430-JTAG-ISO on platforms other than Linux, via
both serial drivers and raw USB access.

4
README
View File

@ -12,8 +12,8 @@ Features
* Userspace only: no kernel modifications required.
* Works with RF2500, eZ430, FET430UIF (V2 and V3), Launchpad, Chronos,
Olimex MSP430-JTAG-TINY and MSP430-JTAG-ISO programmers. Also
supports the TI flash bootloader.
GoodFET, Olimex MSP430-JTAG-TINY and MSP430-JTAG-ISO programmers.
Also supports the TI flash bootloader.
* Can act as a GDB remote stub (replacement for msp430-gdbproxy)
and/or a GDB client.
* Can single-step, program, run to breakpoint and inspect memory on

View File

@ -1,4 +1,4 @@
.TH mspdebug 1 "3 Mar 2012" "Version 0.19"
.TH mspdebug 1 "14 Aug 2012" "Version 0.20"
.SH NAME
MSPDebug - debugging tool for MSP430 MCUs
.SH SYNOPSIS
@ -6,7 +6,7 @@ MSPDebug - debugging tool for MSP430 MCUs
.SH DESCRIPTION
MSPDebug is a command-line tool designed for debugging and programming
the MSP430 family of MCUs. It supports the eZ430-F2013, eZ430-RF2500,
Launchpad, Chronos, FET430UIF, Olimex MSP430-JTAG-TINY and
Launchpad, Chronos, FET430UIF, GoodFET, Olimex MSP430-JTAG-TINY and
MSP430-JTAG-ISO programming tools, as well as a simulation mode.
When started with appropriate options, MSPDebug will attempt to
@ -501,27 +501,43 @@ byte.
The following chips are supported when using FET-compatible drivers:
.PP
.RS 0
CC430F5133 MSP430F169 MSP430F2370 MSP430F47197 MSP430F5528
CC430F5133 MSP430F2252 MSP430F5342
.RS 0
CC430F5137 MSP430F2012 MSP430F247 MSP430F4784 MSP430F5529
CC430F5137 MSP430F2272 MSP430F5418
.RS 0
CC430F6137 MSP430F2013 MSP430F249 MSP430F5418 MSP430FG4618
CC430F6137 MSP430F2274 MSP430F5437
.RS 0
MSP430AFE253 MSP430F2121 MSP430F2616 MSP430F5437 MSP430FR5739
MSP430AFE253 MSP430F235 MSP430F5437A
.RS 0
MSP430F1121 MSP430F2122 MSP430F2617 MSP430F5437A MSP430G2231
MSP430F1121 MSP430F2370 MSP430F5438
.RS 0
MSP430F1232 MSP430F2131 MSP430F2618 MSP430F5438 MSP430G2252
MSP430F1232 MSP430F2418 MSP430F5438A
.RS 0
MSP430F147 MSP430F2132 MSP430F413 MSP430F5438A MSP430G2452
MSP430F147 MSP430F247 MSP430F5510
.RS 0
MSP430F148 MSP430F2234 MSP430F427 MSP430F5510 MSP430G2553
MSP430F148 MSP430F249 MSP430F5525
.RS 0
MSP430F149 MSP430F2272 MSP430F4270 MSP430F5525
MSP430F149 MSP430F2616 MSP430F5526
.RS 0
MSP430F1611 MSP430F2274 MSP430F449 MSP430F5526
MSP430F1611 MSP430F2617 MSP430F5527
.RS 0
MSP430F1612 MSP430F235 MSP430F47173 MSP430F5527
MSP430F1612 MSP430F2618 MSP430F5528
.RS 0
MSP430F169 MSP430F413 MSP430F5529
.RS 0
MSP430F2012/G2231 MSP430F427 MSP430F6435
.RS 0
MSP430F2013 MSP430F4270 MSP430F6736
.RS 0
MSP430F2121 MSP430F449 MSP430FG4618
.RS 0
MSP430F2122 MSP430F47173 MSP430FR5739
.RS 0
MSP430F2131 MSP430F47197 MSP430G2252
.RS 0
MSP430F2132 MSP430F4784 MSP430G2452
.RS 0
MSP430F2234 MSP430F5329 MSP430G2553/G2403
.SH BINARY FORMATS
The following binary/symbol formats are supported by MSPDebug:

View File

@ -74,7 +74,7 @@ static const struct device_class *const driver_table[] = {
};
static const char *version_text =
"MSPDebug version 0.19 - debugging tool for MSP430 MCUs\n"
"MSPDebug version 0.20 - debugging tool for MSP430 MCUs\n"
"Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>\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 "