Linux To Gain Another Chip Family
An anonymous reader submits "Freescale will unveil the first ColdFire processors ever to include a memory management unit (MMU), and therefore able to run full-scale Linux, this week at the Embedded Processor Forum in San Jose, Calif. The chips cost $17 - $25, and are used mostly in industrial control and factory automation. Simultaneously, Freescale tools subsidiary Metrowerks announced plans to offer Linux development tools for Coldfire chips, which previously had been restricted to running uClinux due to the lack of an MMU."
These chips, distantly related to the 68k motorolas, were once touted as a possible upgrade path for new Amigas in the mid 1990s. Hopefully with these new ones, the more modern AmigaOS4 can be ported to them, and continue the heritage. At the moment the only stock available is AmigaOne G3, G4 and mini-itx PPC boards, which are artificially inflated in price by the apple/ibm/motorola consortium.
I thought I knew which processors were important in the embedded world. What exactly is Coldfire, and why does it matter compare to ARM and Motorola's offerings?
I realise that Yet Another Embedded Processor that can run all of linux is a good thing. I just don't see why that is important, since the difference between embedded and desktop processors has been diminishing sharply.
Huh? Metrowerks produces apple development tools, and they dabble in linux/embedded development tools. I'm pretty sure that Metrowerks is not a freescale subsidary. See for example this PR.
freescale is a subsidiary of motorola, here is homepage for coldfire.
Marge, get me your address book, 4 beers, and my conversation hat.
I added support for ColdFire processors to Linux years ago. This won't be new. It was added to Linus kernels in the 2.5 series, and is fully supported in the 2.6 kernels for all the older ColdFire parts (5206, 5249, 5272, 5282, 5307, 5407). Ofcourse the older parts did not have an MMU.
Look under the arch/m68knommu branch for all the architecture support...
Just as Power begat PowerPC and x86 begat x86-64,
so 680x0 begat ColdFire.
In this case, the instruction set was recoded
to save memory and reduce power consumption.
Given some 680x0 assembly code, you pretty much
have ColdFire assembly code. The mapping from
opcode to binary is different. Most likely there
are a few minor changes beyond that, but not much.
Don't click that link. If you check your status bar, it's "http://www.google.com/url?sa=D&q=http://www.peopl esprimary.com/?n=Sarojin", which redirects to http://www.peoplesprimary.com/?n=Sarojin, not a Google search. The page is nasty
Their shell is an abomination. Their filesystem
is plain old DOS FAT, optionally with an
incompatible long-filename feature. The "mount"
command (function? all the same...) is totally
defective, doing some kind of dumb text substitution
instead of real mount points. Memory support is
terribly limited -- is 32 MB enough for you?
For the cost of VxWorks, you can get a bit of
extra memory for running Linux. You'll also save
on development costs that way.
If you'd really prefer a tiny OS designed for
strict real-time from the start, use eCos.
It's free even.
We looked at VxWorks for our first-ever embedded project. When we found out there was no Perl for VxWorks, nor any chance of ever, ever having Perl on VxWorks, we quickly abandonded VxWorks in favor of Linux.
We've have no problems whatsoever using Linux as an embedded OS. Plus, we get to write much of our code in Perl as well. This is as it should be.
In the course of every project, it will become necessary to shoot the scientists and begin production.
I have *never* found a project where VxWorks was worth the cost! In fact if you look they are loosing market share to Linux. Also the two most commonly used systems are either in-house home rolled things like I use or Linux. Of I'm not writing code for space missions, just medical devices.
Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
They try to fool you into thinking they are. But they aren't. They are an entirely different architecture that uses similar nmeumonics and addressing modes.
Even the hexidecimal encodings of those instructions (i.e. the machine language) is dissimilar from 68K machine language.
ColdFire is a strange product, I moto has been pushing it for some time now. I'm not sure why it is still around.