uCsimm News
The uClinux guys have
announced that they are finished testing the uCsimm and are now taking
pre-orders. For US$175, you get a SIMM-sized unit with a 16MHz
Dragonball processor (the very one used in the Palm Pilots), 2MB of
Flash, 8MB of RAM, and integrated 10baseT. Since it can apparently drive a
QVGA LCD, I guess it might be good for my fridge? :) uClinux is
Linux without an MMU and more info can be found at the uClinux.org site.
This thing is awesome. I can't wait until they ship, I've placed an order for 2 of them for instant prototype work on some things I've been meaning to work on for years.
The fact that it has built-in ethernet is a *major* plus, in my opinion.
Imagine a small terminal that you can plug into your network and get statistics, information from around your network, instantly.
You don't need your PC to be up and running, you just have this small device sitting on a pedestal on your desk with a 320x200 screen, scrolling information from your network, displaying bar graphs of system activity, etc.
Since it runs Linux, we could build a minimal web server for it, so that you can administer it by sticking it on the network and pointing your browser at it.
I'm going to build something like this when I get my prototype uCSimm boards, and I think I will call it the GeekClock. It'll have a few modes:
Clock mode (dial/digital face, etc)
Netmon interface - display stats from various netmon packages on your different machines.
News scroller - slashdot headlines on your desk!
IRC interface - see who is in your favourite #channel!
etc.
Sort of like a dedicated push client... imho the problem with the whole push phenomenon a few years back was that it required your PC not do much else - if you can have it on your desk and just look at it now and then as you work, it seems to me that this is a better way of doing it.
And since it'll be an Open Source project, we can make the GeekClock totally rock! Got a module you want to write, simply dl the code, add it, and away we go.
This way I can finally turn off all the stuff that runs in the background on my main systems, and I don't need to interrupt what I'm doing to keep an eye on things - the GeekClock stands on its pedestal on my desk, telling me whats going on with my network.
That's just one idea.
Another idea I had was to add a MIDI interface to it, and use it as a MIDI protocol analyzer - since I write music software for a living, this would be useful to me.
I guess the point is that there are a whole bunch of things that I could do with a uCSimm when I get one, and I can't wait!
If anyone is interested in the GeekClock project, don't hesitate to mail me. I'd sure like to colaborate with other people that are interested in putting this nifty device to use...
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
>4004, 8008, 8080, 8088, 8086, 80186, 80286
^
4040
The 8088 is an 8086 with an 8 bit bus, so even though it's less powerful (seems to me the hit was about 30%), it probably comes after the 8086 in the sequence
Go pull an old intel catalgo, or something else with details. The 4004 and 8008 had very little in common. The 8008 had general memory addressing (14 bits), while the 4004 adressed memory *chips*, with a different address space for RAM and ROM. Both were meant for what we'd now call embedded applications (they weren't meant to be desktops), but it was possible to build a general purpose machine around the 8008. The 4004 tended to end up in cash registers and calculators.
The 4 bit and 8 bit lines were just plain different. The 4040 was an enhanced 4004, and the 8080 a (much) enhanced 8008. But the 4040 was real, and they sold them. If it wasn't so deeply buried in my basement, I'd pull my old intel parts catalog to give you the citations for it.
Dallas Semiconductor (the folks who make the Java ring) have a product called TINI that puts ethernet and Java into this form factor. (They're working on a single-chip version.)
--
Brent J. Nordquist N0BJN
compared to other micro boards used for robotics:
pros
- low power ussage when idle
- lots of ram (for the size)
- good number of io/ports. good for controlling servo motors and reading digital sensors.
- fairly fast. Probably good enough to do some image processing.
- ethernet useful for fast experimentation in tethered mode.
- nice environment to work in (linux!)
cons
- Needs at least one A/D converter.
- Wireless Ethernet would be more useful. Autonomous robots aren't going to be able to use plain ethernet.
-- Virtual Windows Project
It is kind of hard to put PalmOS, QNX and WinCE in the same boat. Yes, you could use each with a GUI, but each has very different design goals. QNX is realtime first, with a GUI second. PalmOS was built on top of Kadak's AMX (realtime first, GUI later). PalmOS added the GUI we know and love. WinCE is just gooey :-). Seriously, WinCE is GUI (really look-and-feel) first, realtime a distant second.
I don't know much about the PalmOS, but QNX DOES use the MMU, at least on the x86 version. For years, that was one of the big selling points of the OS. Same with WinCE.
I don't know that much about the Dragonball, but other 68k machines (I know, not quite the same) had user/supervisor modes that one could use to at least keep an application from crashing the OS.
Its remember the firt days of Altair computer,
whe you order by mail your kit, and after some
hardwork with your soldering iron you got a box with some keys, and you need to setup every assembler instruction without any error using that keys to boot from a paper tape.
And the legend tells that our "friend" Bill started their company hacking a basic for the Altair using computer time paid by us in the university.
Malba Thaan
(excuse my poor knowledge of english)