Yes, I tried 4800 up to 115200.
I tried two different versions of mspdebug.
$ mspdebug --v
MSPDebug version 0.23 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2015 Daniel Beer <dlb...@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.
$ mspdebug --v
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 Daniel Beer <dlb...@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.
And naken_asm
naken_asm - by Michael Kohn
Joe Davisson
CPU: MSP430, MSP430X, 65xx, 65816, 680x, 68HC08, 680x0, 805x
ARM, AVR8, dsPIC, MIPS, STM8, THUMB, TMS1000, TMS1100
TMS9900, Z80
Web: http://www.mikekohn.net/
Email: m...@mikekohn.net
Version: January 07, 2015
This is my output from make:
$ make
mspdebug rf2500 "prog lp-2553.hex "
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 Daniel Beer <dlb...@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.
Trying to open interface 1 on 016
Initializing FET...
FET protocol version is 30394216
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0x2553
Code start address: 0xc000
Code size : 16384 byte = 16 kb
RAM start address: 0x200
RAM end address: 0x3ff
RAM size : 512 byte = 0 kb
Device: MSP430G2xx3
Number of breakpoints: 2
fet: FET returned NAK
warning: device does not support power profiling
Chip ID data: 25 53
Erasing...
Programming...
Writing 72 bytes at 0200...
Writing 258 bytes at 0280...
Writing 60 bytes at 1080...
Writing 4096 bytes at e000...
Writing 3730 bytes at f000...
Writing 32 bytes at ffe0...
Done, 8248 bytes total
On Mon, Sep 21, 2015 at 3:43 PM, Andreas Wagner <
andreas.wag...@lowfatcomputing.org> wrote:
> Hi cadar,
>
> Did you try other baud rates with the "-s" option?
>
> Regards,
> Andreas
>
> On Mon, Sep 21, 2015 at 8:39 AM cadar <cadar...@gmail.com> wrote:
>
> > Hi,
> >
> > I can not connect to my MSP430 launchpad using Amforth-6.0 with
> > amforth-shell.
> >
> > All I get is,
> > "E=Input character not echoed."
> >
> > Exact same setup worked for 5.8 and 5.9. (OSX 10.10)
> >
> > Anyone got it working on MSP430?
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Amforth-devel mailing list for http://amforth.sf.net/
> > Amforth-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
> >
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amforth-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
------------------------------------------------------------------------------
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel
