This commit moves the definitions of UNAME_* above the initial check
of the OS environment variable. Previously, UNAME_O would not be set
in the case where OS is Windows_NT. Builds would incorrectly use Windows
OS_LIBS and OS_CFLAGS in a Cygwin build environment. The tree now builds
cleanly with Cygwin's libusb-1.0 and libreadline development packages
installed.
Using Cygwin's serial port mappings for MSP-FET430UIF:
$ mspdebug -d /dev/ttyS1 uif
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.
Trying to open /dev/ttyS1 at 460800 bps...
Initializing FET...
FET protocol version is 20408002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0x0580
Code start address: 0x5c00
Code size : 262144 byte = 256 kb
RAM start address: 0x1c00
RAM end address: 0x5bff
RAM size : 16384 byte = 16 kb
Device: MSP430F5438A
Number of breakpoints: 8
fet: FET returned NAK
warning: device does not support power profiling
Chip ID data:
ver_id: 8005
ver_sub_id: 0000
revision: 13
fab: 55
self: 5555
config: 13
Device: MSP430F5438A
[...]
The "regs" command indicates when the PC is sitting on an enabled
breakpoint. The simulator emits debug output when a watchpoint is
triggered by a simulated instruction.
We now have entirely separate channels for each direction of
communication between the producer and consumer, rather than having the
two sides share a single state machine.
The Olimex JTAG adapter occasionally emits an extra 0xff before sending
its reply to the C_INITIALIZE message. A small change to the FET packet
parser works around this.
Problem and original solution reported by Yingwei Li <ysulyw@gmail.com>.
Entry added for chip ID 0x0382 (MSP430F5255)
Flash/RAM Memory layout and EEM debugging facilities have been set
according to device data-sheet. (msg28_data, msg29_data,
MSP430_STORED_INFO entries)
Flags and Parameters in msg2b_data copied from MSP430F5437A - couldn't
find any documentation on those. msg29_params copied from MSP430F5437A
- couldn't find any documentation on those
Chip detection, flashing and single step debugging with gdb tested with
MSP430F5255 using olimex-v1 hw-debugger
Signed-off-by: Jan Willeke <willeke@smartmote.de>
John Pitney
Daniel Beer
Tamas TEVESZ
Derald D. Woods
David Siroky
zcsahok
Ingo van Lil
Eric Price
Peter Bägel (DF5EQ)
Jan Willeke