Re: .NET Micro Framework
- From: Paul Gotch <paulg@xxxxxxxxxxxxxxxxx>
- Date: 15 Feb 2007 21:28:10 +0000 (GMT)
Eric <englere_geo@xxxxxxxxx> wrote:
Yes, I'm guessing the free Express version won't work with it.
Standard Edition required.
I believe that is also the case for the CE platform.
I think they've unified it so you just now need VS 2005 and don't need VS
Embedded which was in effect a previous version of VS retargetted.
I think there is still a separate kernel debugger though.
Notepad, or third-party tools. It comes down to a question of
deployment, and I am guessing that can also be done outside of VS
since they are just using a serial port.
Depends if the they've docmented the protocol spoken to the monitor, MS are
notorious for keeping such things closed so they can change them.
the same here. It shouldn't have the slow klunky feeling that ARM's
Angel monitor had when debugging over a serial port.
Angel was written back in the days of 9600 Kbaud serial ports, it had been
superceeded by JTAG based debugging by the time there was any need to make
it go faster or hide the latency of the serial port.
To me this seems to be a "because we can product" though. To make it go
anywhere they need a huge library of support libraries supporting the
facilities available on common microcontrollers and they need to add JTAG
debugging.
Otherwise it doesn't really provide anything you can't do with existing C
based toolkits from incumbant vendors and it requires oodles more RAM and
faster processors.
Another point is that with the C based tool kits you at least have the
illusion of being able to change tools providers even if in practice it's
very hard, the .NET stuff is essentially single source single toolchain.
-p
--
"Unix is user friendly, it's just picky about who its friends are."
- Anonymous
--------------------------------------------------------------------
.
- Follow-Ups:
- Re: .NET Micro Framework
- From: Eric
- Re: .NET Micro Framework
- References:
- .NET Micro Framework
- From: Jim Granville
- Re: .NET Micro Framework
- From: Ulf Samuelsson
- Re: .NET Micro Framework
- From: Paul Gotch
- Re: .NET Micro Framework
- From: Eric
- .NET Micro Framework
- Prev by Date: Re: How do i create an accurate delay
- Next by Date: Re: Creating RAM faults
- Previous by thread: Re: .NET Micro Framework
- Next by thread: Re: .NET Micro Framework
- Index(es):
Relevant Pages
|