Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

A .Net CPU

Posted by timothy on Tue Dec 14, 2004 04:50 AM
from the punctuation-butchers dept.
An anonymous reader writes "Windows for devices has an article about the .Net CPU. The chip is programmed with a subset of the CLR and runs the same software as the SPOT smart watches. Among other things, "[t]he computer module is implemented in the format of a 32-pin "DIP" (dual inline package) chip, allowing the module to conveniently plug into a standard 32-pin DIP socket. In addition, the ".netcpu CPU Module" integrates 4MB of nonvolatile Flash memory (interfaced via an SPI interface on the SoC). It also provides 24 general purpose digital I/O lines, which are multiplexed with other functions including 8 VTU ports, a USB port, two serial ports, and SPI and I2C interfaces." More information about the product can be found at the .netcpu company website."
+ -
story

Related Stories

[+] Goodbye To the SPOT Watch 87 comments
Starturtle sends along an Engadget article on the demise of the Microsoft SPOT Watch. We've discussed related devices a few times in the past; here's a picture of one. "After a long, painful, nearly anonymous ride on the wrists of a select few uber-geeks, Microsoft's finally throwing in the towel on one of its longstanding pet projects: the SPOT watch. The writing's been on the wall for some time; the applications and content available to the watches haven't been updated in ages, and indeed, the entire line of Abacus Smart Watch 2006 models — the only type being recently offered — has been discontinued and out of stock for a few months. For what it's worth, MSN Direct's program manager is quick to note that the underlying technology most certainly isn't going away."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • .Not a .NET CPU (Score:5, Informative)

    by Gopal.V (532678) on Tuesday December 14 2004, @04:56AM (#11079959) Homepage Journal
    It is really just a CPU on which CLR runs , not a real .NET CPU in hardware. (or so the TFA seems to indicate from the diagram). Also of the more convenient peices of the ECMA 335 spec.

    It's an embedded chip which has a CLR on top of it. Nice idea, sorry that Sun thought of it earlier ( The Green Project [java.net]) - Sun seems to be consistently missing the BUS here. They came up with "Network is the computer" and now MS is selling ".NET " :)

    I've seen a couple of stack based engines but by its polymorphic nature .NET bytecode is not suitable for a direct CPU (you could do something like dynamic translation [southern-storm.com.au] like the Crusoe chip had). But then it's still a JIT , right ? :)
    • by Gopal.V (532678) on Tuesday December 14 2004, @06:09AM (#11080154) Homepage Journal
      Yeah, this is very much like ROM Basic [computerhope.com].

      Looks like this idea's been around for god knows how long ... So much for innovation, we seem to be going backwards here ?.

      This is a plug , but I've been working on a .NET CLR which can be trimmed down to around 400k (for a full opcode set, no less !!) for the last 3 years.
      • by Gopal.V (532678) on Tuesday December 14 2004, @07:09AM (#11080309) Homepage Journal
        .NET is a JIT engine , it's designed explicitly for JIT'ing ... It does produce a .exe file which has a main which calls the Mscoree.dll with the current file and starts up the VM using the bytecode data. The EXE part is just bootstrap code , the rest is JIT'd .

        Read this paper [64.233.167.104] about how many hoops you have to go through to get a decent interpreter for .NET. And it blatantly ignores the _Main() x86 native code that's in the .exe files.

          • And the 6809 that ran 6809 machine code.

            Whatdayamean that doesn't count? Programming the 6809 was like programming in a high level language... well, it felt like it, back when the alternative was BASIC. ;-)

  • by rleyton (14248) on Tuesday December 14 2004, @04:57AM (#11079960) Homepage
    They must be very small, but I think I can see them if I look really closely and squint a bit.
  • Parrot (Score:4, Informative)

    by hey (83763) on Tuesday December 14 2004, @05:01AM (#11079972) Journal
    I'm waiting for a Parrot [parrotcode.org] chip.
    Now that would be exciting.
  • by ezelkow1 (693205) on Tuesday December 14 2004, @05:14AM (#11080020)
    this thing seems like an overpriced piece of junk just trying to hawk its .NET and VS support. Most of the microcontrollers out there i have seen can in some way or another be programmed in C and its various forms. 200 dollars just for the cpu seems to be asking a lot when the only advantage i see is that is 4mb of flash, and other MC's can always be expanded to that anyway. Besides the fact that other MC's out there that are cheaper also contain a whole lot more peripherals and features than this one. But maybe thats just me
    • Don't think of it as a product part, think of it more as a BASIC Stamp for people who want something more than a BASIC Stamp can manage.

      BASIC Stamps are good for when you only want to do one, and don't want to lay out a board with crystal, peripherals, etc. Although I have a tendency to do my own boards, I can see that BASIC Stamps are good for some projects.

  • Security ? (Score:2, Insightful)

    by Anonymous Coward
    What happens if someone discover a flaw in the CLR ?
    Do we have to buy another processor ? or flash another CLR ?

    Placing anything on a processor is a *pretty* stupid idea.
    • Re:Security ? (Score:4, Insightful)

      by FrYGuY101 (770432) on Tuesday December 14 2004, @07:08AM (#11080304) Journal
      Question. What happened when the f00f [linuxmafia.com] flaw was discovered for the Pentium?

      Yep, that's right, you had to buy another processor.

      The X86 instruction set isn't somehow immune to flaws.
  • Gee I though Gumsticks were already mainstream... oh.. but of course http://www.oreillynet.com/pub/wlg/4552 [oreillynet.com]

    these thingys aren't from Redmond...

    dang it.. too late...

  • by Anonymous Coward
    Clippy turns you off.
    A drm hardware dream.
  • by david.given (6740) <dg.cowlark@com> on Tuesday December 14 2004, @05:41AM (#11080091) Homepage Journal
    According to the products page on their website:
    • 384K of SRAM, single cycle access
    • 27 MHz ARM7TDMI
    • FBGA chip form
    • ~450,000 instructions per second
    • 4MB non volatile flash
    • 1.8-volt core, 3.3-volt I/O
    • 32768 Hz real-time clock
    • 32-pin pinout, including 24 GPIO ports multiplexed with other functions (8 VTU ports, dual serial ports, SPI, and USB port)
    • SPI and I2C interfaces

    I assume FBGA is a typo for FPGA. This thing sounds suspiciously similar to one of those standard FPGAs with a built-in ARM7 core.

    It actually sounds like quite a nice little embedded system, a kind of grown-up Basic STAMP [parallax.com]. I expect that the .net VM is in ROM; on start-up the FPGA is probably bootstrapped from it. I wonder if it would be possible to replace it with a real operating system?

    • by Pemdas (33265) * on Tuesday December 14 2004, @05:57AM (#11080129) Journal
      I assume FBGA is a typo for FPGA.

      When referring to packaging, FBGA is usually Fine Ball Grid Array. I really doubt it's a typo. From the programmers point of view, the package virtually never significant.

      Overall, this sounds remarkably similar to picoJava [sun.com], which, last I checked, was going nowhere, and for good reason.

      Designing bytecode formats for VMs is not really the same as designing opcodes for microprocessors -- shoehorning hardware that way is painful and generally results in less elegant, more expensive designs.

      OTOH, the bytecodes in question aren't really significantly worse than, say, x86, and look where that is today...

  • Where is the hardware-implemented JVM we've been promised for years and years? Not like this gloified BASIC stamp, running an implementation on the .NET runtime in software, but a real hardware implementation that runs bytecode natively.
  • by nathanh (1214) on Tuesday December 14 2004, @05:46AM (#11080099) Homepage

    Isn't this exactly like the Java CPU that Sun was selling a few years back? And it was simply a close relative of the Lisp processors from the 80s.

    C#, Java. .Net, J2EE. CLR, JVM. .NET CPU, Java CPU. So should we expect Microsoft to simply repeat everything that Sun did with Java? If so, wake me up when they declare they're going to release CLR under an open source license.

    • by sosume (680416) on Tuesday December 14 2004, @05:55AM (#11080125)
      If so, wake me up when they declare they're going to release CLR under an open source license.

      *riiiiiiing* wake up call ... its called Rotor, released by Microsoft a few years ago and it runs on FreeBSD.....
      Well, maybe not your definition of open source (no GPL or BSD license but Shared Source) but remember open != free as in beer
  • by quigonn (80360) on Tuesday December 14 2004, @05:48AM (#11080105) Homepage
    http://www.clifford.at/bfcpu/bfcpu.html This piece of hardware is tres cool, as it implements the _complete_ set of Brainf*ck instructions as native instruction set.
  • Ahnetkpuh? (Score:4, Funny)

    by martin-boundary (547041) on Tuesday December 14 2004, @05:59AM (#11080135)
    Ahnetkpu? Is this an Elder God?
  • That's funny (Score:5, Interesting)

    by le_defaut_tragique (653169) <tragic,flaw&mac,com> on Tuesday December 14 2004, @06:14AM (#11080173)
    Check out the company website, and Google them. I just did and it turns up that this company was founded on Oct10.2k4ce by Mark Phillips. A Google turned up... the company website, the original submission, and a couple other press releases. this is their only product, and they made it in two months.

    Microsoft's only connection with them is that Mark Phillips guy, who, when googled investigatively, appears to have founded A Dot Corporation in Apr.2k3ce and they were involved in... SPOT Watch technology and claim microsoft to be a business partner (spotcorporation.com).

    So is Mark Phillips using his work with microsoft's SPOT developer team to create something to market under a different name? Both companies list only Mark Phillips as founder and, in fact, confirmed employee, although one site listed A Dot as having 24 employees.

    Yeah, so that's funny...
  • by linebackn (131821) on Tuesday December 14 2004, @06:20AM (#11080183)
    It boggles my mind, every time someone comes out with a bytecoded language in order to attempt to achieve hardware independence, someone comes along and creates hardware to execute it! Thus defeating the original purpose.

    Of course people see the need for hardware acceleration because interpreted or even JIT compiled bytecode languages are always going to be slower than precompiled native binaries.
    • Running bytecode will always be somewhat slower than native binary, but Sun has done a good job of getting most of the overhead out of the running code and into the VM startup. Most overhead people experience now with Java isn't from the VM at all but from the constraints Sun puts on the Java language specification (exs. ALL arrays must be bounds-checked, dynamically allocated memory must be garbage collected). C,C++,BASIC,etc. do not have these requirements built into their language specification and the
    • Re:So (Score:3, Insightful)

      Why does it seem scary? What do you imagine the chip will do?

      It's just a CPU for the .net CLR, that's all, in much the same way as Pentiums and Athlons, etc, are CPUs for x86 code. It's not going to prevent you from running Linux, or reach up and take control of your PC and/or spy on you for Bill.
      • a CPU for the .net CLR, that's all, in much the same way as Pentiums and Athlons, etc, are CPUs for x86

        No, it is a CPU for .NET CLR as much as a Gumstix is a CPU for Linux kernel. It's just a VM embedded on firmware, NOT a REAL CPU.

        Btw, the JVM FPGA is a real example of a VM less execution (or more correctly , a native JVM + support libs).
        • No, it is a CPU for .NET CLR as much as a Gumstix is a CPU for Linux kernel. It's just a VM embedded on firmware, NOT a REAL CPU.

          I can only begin to guess what your definition of a CPU is. Anyway, it still isn't going to eat your mother or pull your cats tail. It is just a chip from a vendor you don't like. Move on.

          • Re:So (Score:3, Informative)

            What of things I've read saying that .net will be the default api in windows longhorn?

            As a former DOS programmer, I can tell you that when Microsoft wants to get rid of an API, they're quite good at it. If they want to do it, win32 will be dead before the end of the decade, just like dos.
            • Re:So (Score:5, Insightful)

              by Taladar (717494) on Tuesday December 14 2004, @06:02AM (#11080144)
              It is an entirely different situation.

              They can't just kill backwards compatibility now since it is the one big reason to stay with Windows. Most businesses are evaluating other OS now and if the change to a new Windows version requires rewriting all your programs (I know they will probably implement a compatibility layer but we know how well that worked in the past) then they might just as well rewrite them on Linux (or some other OS that 'lacks' MS Security Features (TM) ).
            • Re:So (Score:3, Interesting)

              So?

              Yes, that'll suck for anyone who's currently working with any API it replaces, but that's progress - technology moves on. Besides, the jobs won't disappear overnight, there are still openings for COBOL programmers, for example (there's even a COBOL binding for .net...)

              I still don't see the big deal. One of the most frequent criticisms I hear on tech sites of Windows is the cruft that's accumulated due to always maintaining backward compatibility. Surely removing that cruft by removing the backward comp
    • Re:So (Score:4, Informative)

      by dan the person (93490) on Tuesday December 14 2004, @06:38AM (#11080235) Homepage Journal
      It's an ARM CPU, not a .NET CPU.

      It loads ".NET Embedded" from firmware.

      This is like saying an iPaq has a WindowsCE CPU.

    • Re:Scary (saracasm) (Score:5, Interesting)

      by kahei (466208) on Tuesday December 14 2004, @05:12AM (#11080014) Homepage

      I'd say that I see more .NET projects starting than any other single platform in my industry, although the lead over Java is slim and obviously there is far more Java already running. I wouldn't say that .NET has reached the 'will be with us forever' point that Java and C have, but it's certainly been very popular with devs and had a number of successful early projects. In the end it will probably stand or fall on the success of Longhorn (which everyone is quite skeptical about). But buy-in has been good.

        • I've seen .Net moving in quite heavily in the manufacturing world. This is one sector that MS has a strong hold on simply because there are so few people that want to sit down and write the hundreds of communications drivers, etc needed to create manufacturing data systems. Or maybe because once you buy a manufacturing system you don't want to switch brands until you get back out of the hole with it :P
          A lot of the products I have seen (both data collection and warehouse-type) are moving to .Net SDK's, and a
    • by the angry liberal (825035) on Tuesday December 14 2004, @05:20AM (#11080037)
      Sorry, Microsoft-- just because you want something to be true doesn't mean that it is.

      Perhaps if you put your troll's club down long enough to take a look at sourceforge, you would notice most of the newer open source applications for Windows are being developed in .NET.

      It won't take over the Internet, but it has been well accepted and is easy to use.

      I wonder though, with all this FUD, if anyone can produce real numbers showing which is in more demand in the workplace: Linux developers vs .NET developers. I'm not talking about which is more 31337, I am talking about which one will find more steady income and have less trouble when they need to change jobs.
      • by shufler (262955) on Tuesday December 14 2004, @05:37AM (#11080079) Homepage
        As you mentioned, newer Windows applications are being written in .NET, and you go on to ponder what the demand is. I don't know of any numbers, but I'd imagine .NET developers would be in all sorts of demand with respect to developing on any Windows platform, after all, .NET is the new API which replaces Win32.

        I agree that there is all sorts of FUD flying around about .NET, and it's pretty sad that it is. I'm not a Microsoft fanboy, but anyone who cannot recognise the Official API of future Windows development is in serious trouble (if they intend on developing future Windows applications, that is). As you said, .NET isn't going to take over the Internet (who said it would in the first place?), but it will take over ALL Windows development.

        All that said, I seem to remember reading about how Microsoft was dropping .NET, however I highly suspect I dreamt it.
      • by benjymous (69893) on Tuesday December 14 2004, @05:49AM (#11080106) Homepage
        Personally as someone who's long developed Windows Win32/MFC code (in C++) and is now moving to C# .NET stuff, I'm finding .NET an absolute doddle.

        let's face it - MFC and Win32 are old and have been cobbled together, seemingly at random over the lifespan of the whole Windows family, meaning nothing feels like it's ever really been designed

        One function returns a colour, another function needs a colour. Oh dear, one uses some kind of int, the other a struct (oh and another some kind of class) - lets bog down our code with lots of conversion functions - Most of the time the sensible obvious approach to a task is the wrong one.

        So far in .NET, whenever I've wanted to do something, I've looked at the classes, thought "How would it be sensible to do this", and 9 times out of 10 it works perfectly
        • Re:Scary (saracasm) (Score:4, Interesting)

          by ceeam (39911) on Tuesday December 14 2004, @06:43AM (#11080252)
          Yes, new things tend to be slick and shiny. Applies to almost everything. When they grow up they become burdened with all kinds of supporting sticks, duct tape and patches. Take PalmOS, take the directories structure on your HDD, take Java, and even when the brightest guys handle it (mod me to hell) - take Python or Unix... Not as easy as it used to be "back in the day".

          .Net (WTF - extremely "ungooglable" name, BTW) is young and peppy... Wait 5-10 years for it to mature though.

      • Although I agree with you that it isn't the case to troll everything that has "microsoft" into it, I think that an high income isn't the first requirement for someone that foreseek freedom of choice and information (why develop Free Software, else?).

        The fact that 85% of the computer world use MS systems doesn't mean that it's the best thing to do. Still, things are (really) slowly changing. Maybe I'll live the day when the market share between MS and *nixes 'll be 50%-50%... and that would mean real compe

    • Re:Scary (saracasm) (Score:5, Interesting)

      by Mant (578427) on Tuesday December 14 2004, @06:07AM (#11080152) Homepage

      I can't imagine .NET is going to take over the Internet, but ASP.NET is a very nice platform for writing web apps. OK they will probably run on IIS, unless you use Mono, but it is a big step up from the scripting languages approach of basically just printing out the web page.

      It gives some nice abstraction to writing web pages, you don't have to worry about hand crafting every bit of HTML that is going out to the browser (although you can if you want or need to), and can deal with the concepts, objects and events.

      .NET does little that is new, Java was doing much of it first, but for writing web apps it is pretty simple and powerful and has good development software. We are moving to it at work because it makes us more productive.

    • Re:Scary (saracasm) (Score:5, Interesting)

      by tarunthegreat2 (761545) on Tuesday December 14 2004, @06:30AM (#11080209)
      Say what you want about .NET (I disagree with u completely BTW), but the IDE KICKS Hardcore BUTT! I have yet to see something better the VS .NET 2003 for development. Quite a few people have bought into .NET and if I have a choice between C++ and C#, I pick C# thanks....but then I was born and raised on C and Java anyway....
    • Re:Scary (saracasm) (Score:4, Interesting)

      by Tim C (15259) on Tuesday December 14 2004, @06:38AM (#11080239)
      Jobserve seems to disagree with you:

      search for ".net", any job type [jobserve.com] - 1629

      search for "c", any job type [jobserve.com] - 1499

      search for "java", any job type [jobserve.com] - 3009

      search for "c++", any job type [jobserve.com] - 2300

      Your comment has too few characters per line (currently 15.6). Guess I'd better explain then that jobserve.com is a major UK-based jobs web site, catering to a large number of industries. While the jobs advertised are mainly in the UK, they also cover parts of Europe, and have a site dedicated to jobs in Australia. How's that slashcode, better?
    • by sosume (680416) on Tuesday December 14 2004, @07:45AM (#11080397)
      Yeah riiiiight have you ever seriously looked at the spec of these 'java chips'? They are not as advanced as Sun may have you believe..

      * No floating point 16-bit int instead of 32 bits.
      * All types (byte, short, char, int and boolean) use 2 bytes,
      though byte and short arrays use 1 byte per element.
      * Only one-dimensional arrays (can use the index to simulate a 2-D array.)
      * Single byte ASCII strings instead of two byte Unicode
      * Only a single thread available, though a timer allows for
      scheduling of multiple tasks. (Plus the VP objects run independently)
      * No interfaces, though sub-classing of an abstract base class is allowed.
      * A subset of the core libraries is available. (Remember also that
      all linked classes must be downloaded with the program and fit into
      the 32kb of memory.)
      * No garbage collection. All objects created will last for the
      duration of the program.

      Compare that to this .NET chip....
      * 384K of SRAM, single cycle access
      * 27 MHz ARM7TDMI
      * FBGA chip form
      * ~450,000 instructions per second
      * 4MB non volatile flash
      * 1.8-volt core, 3.3-volt I/O
      * 32768 Hz real-time clock
      * 32-pin pinout, including 24 GPIO ports multiplexed with other functions (8 VTU ports, dual serial ports, SPI, and USB port)
      * SPI and I2C interfaces

      and its multithreaded, too
      • What you pasted for JVM was the engine specs and for this thing was the CPU/Embedded specs.

        The guys haven't really given out WHAT the "embedded.net" runs - looks like it's about the same as what the embedded JVM runs (not the Java "chip"). It's not a ".NET" chip first off and secondly it's almost the same as those "jvm" embedded (ie 400k sdram for what I have) in features. Multi-threading is not really multi-threading either, it is a kind of co-operative environment.

        It's really not the big badass ".NET" a
      • The aj-100 doesn't seem to have most of the limitations you mention, in particular it has floating point and 32 bit ints.

        Read about it and some other Java chips here [particle.kth.se].