: Friday, 20 September 2013 10:05 a.m.
To: William Swanson
Cc: Jesse Frey; GCC for MSP430 - http://mspgcc.sf.net; and...@aratika.co.nz
Subject: Re: [Mspgcc-users] msp430-gdbproxy loses connection with target
Yeah, this is pretty far from mspgcc, but still on topic for MSP430.
There are three
On Thu, Sep 19, 2013 at 12:44 PM, Jesse Frey jmf...@alaska.edu wrote:
When I need to read a timer asynchronously do three consecutive reads and do
a bitwize majority function on them.
Not to take this thread too far off-topic, but that approach doesn't
work. For example, say your middle reading
Yeah, this is pretty far from mspgcc, but still on topic for MSP430.
There are three timer read solutions I use in BSP430, depending on the
relative speed of the clocks:
* If the clock source is synchronous to mclk, just read the counter.
* If it's asynchronous and is significantly slower, read
Subject: Re: [Mspgcc-users] msp430-gdbproxy loses connection with target
have you verified that the board is getting the voltage that you think it
should be?
On Mon, Sep 2, 2013 at 3:38 PM, Andrew McLaren and...@aratika.co.nz
wrote:
On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew
...@gmail.com] On Behalf Of Peter Bigot
Sent: Wednesday, 18 September 2013 10:15 p.m.
To: and...@aratika.co.nz
Cc: Eric Decker; GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] msp430-gdbproxy loses connection with target
MSP430FG4618 erratum TB18: MOV to TBCTL may clear TBR.
http
.
To: and...@aratika.co.nz
Cc: Daniel Beer; GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] msp430-gdbproxy loses connection with target
have you verified that the board is getting the voltage that you think it
should be?
On Mon, Sep 2, 2013 at 3:38 PM, Andrew McLaren and...@aratika.co.nz wrote
On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew McLaren wrote:
It would have been easy if the problem had been gdbproxy,
but no such
luck. Now that mspdebug is running, I'm seeing exactly the same
scenario here. The messages are a tad different, but I
think they are
saying the
have you verified that the board is getting the voltage that you think it
should be?
On Mon, Sep 2, 2013 at 3:38 PM, Andrew McLaren and...@aratika.co.nz wrote:
On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew McLaren wrote:
It would have been easy if the problem had been gdbproxy,
but
It would have been easy if the problem had been gdbproxy, but no such luck.
Now that mspdebug is running, I'm seeing exactly the same scenario here. The
messages are a tad different, but I think they are saying the same thing.
Everything works fine until mspdebug reports...
fet: FET returned
On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew McLaren wrote:
It would have been easy if the problem had been gdbproxy, but no such luck.
Now that mspdebug is running, I'm seeing exactly the same scenario here. The
messages are a tad different, but I think they are saying the same thing.
is there some reason you are using msp430-gdbproxy rather than mspdebug?
msp430-gdbproxy has been deprecated for many years now.
current devlopment is occuring on mspdebug.
it is a superset of msp430-gdbproxy.
On Sat, Aug 24, 2013 at 6:16 PM, Andrew McLaren and...@aratika.co.nzwrote:
I've
No reason at all except maybe laziness. I did have a play with mspdebug a
few years back, and from memory had some issues with the target processor I
was using. gdbproxy worked, so I've stayed with that ever since. There is
always enough work in the code itself, so if the environment works I just
12 matches
Mail list logo