On Thu, Aug 16, 2012 at 10:22:51PM +0200, Hardy Griech wrote:
> may I make some minor code "donations"?
>
> For me "hexout" does not have enough features, because I'm using a "big"
> MSP430. Therefor I need correct address extensions. My implementation
> of hexout looks like this:
...
> It als
On 16.08.2012 21:43, Daniel Beer wrote:
:
> I don't have gcc-3 set up, but are you able to find the definition of
> WINAPI anywhere in the Cygwin-included header files? I'm surprised that
> this is apparently defined, but not correctly.
Hi Daniel,
WINAPI is defined as __stdcall in windef.h which
Hi Daniel,
may I make some minor code "donations"?
For me "hexout" does not have enough features, because I'm using a "big"
MSP430. Therefor I need correct address extensions. My implementation
of hexout looks like this:
int cmd_hexout(char **arg)
{
char *off_text = get_arg(arg);
On Thu, Aug 16, 2012 at 01:00:01PM +0200, Hardy Griech wrote:
> One more thing with tilib:
>
>
> hardy:~/workspace.37/mspdebug> ./mspdebug tilib -d COM12
> MSPDebug version 0.20 - debugging tool for MSP430 MCUs
> :
> (mspdebug) setbreak 0xa800
> Set breakpoint 0
> (mspdebug) delbreak
> Clearing
On Thu, Aug 16, 2012 at 09:46:55AM +0200, Hardy Griech wrote:
> On 14.08.2012 23:00, Daniel Beer wrote:
> :
> >> One "funny" remark from my side: mspdebug would have been compilable out
> >> of the box under cygwin, if I'd used the "correct" compiler: gcc-4
> >> (4.5.3) produces invalid (?) code wh
One more thing with tilib:
hardy:~/workspace.37/mspdebug> ./mspdebug tilib -d COM12
MSPDebug version 0.20 - debugging tool for MSP430 MCUs
:
(mspdebug) setbreak 0xa800
Set breakpoint 0
(mspdebug) delbreak
Clearing all breakpoints...
(mspdebug) run
tilib: MSP430_EEM_SetBreakpoint: Invalid paramet
On 14.08.2012 23:00, Daniel Beer wrote:
:
>> One "funny" remark from my side: mspdebug would have been compilable out
>> of the box under cygwin, if I'd used the "correct" compiler: gcc-4
>> (4.5.3) produces invalid (?) code which makes mspdebug crash with
>> segmentation fault (with gdb one can se
On Tue, Aug 14, 2012 at 10:35:39PM +0200, Hardy Griech wrote:
> Hey, that came just in time!
>
> One "funny" remark from my side: mspdebug would have been compilable out
> of the box under cygwin, if I'd used the "correct" compiler: gcc-4
> (4.5.3) produces invalid (?) code which makes mspdebug
Hey, that came just in time!
One "funny" remark from my side: mspdebug would have been compilable out
of the box under cygwin, if I'd used the "correct" compiler: gcc-4
(4.5.3) produces invalid (?) code which makes mspdebug crash with
segmentation fault (with gdb one can see that "device" is ch
MSPDebug version 0.20 is available from:
http://mspdebug.sourceforge.net/download.html
Significant changes in this version are:
* Support for new chips: MSP430F6736, MSP430F2252, MSP430G2403,
MSP430F6435.
* Support for building under Cygwin.
* Support for watchpoints using
10 matches
Mail list logo