Hello,
I made a similar post on the e-embedded yahoo group. I know that ucLinux was
ported to
the AT91.
I would like to know how much of an operating system is actually on a limited
flash
storage space of a MCU? Do I get a login, with file storage a graphical X server
with KDE or
GNOME somehow stripped down and swapped in and out of a multi MB storage
device?
What kind of I/O would one typically use (graphics module screen, hard disk,
kyb,
ethernet) and how much work is needed to make the peripherals work?
Thanks,
Frank
ucLinux on MCUs
Started by ●March 4, 2007
Reply by ●March 4, 20072007-03-04
--- In A..., "Frank"
wrote:
>
> Hello,
> I made a similar post on the e-embedded yahoo group. I know that
ucLinux was ported to
> the AT91.
>
> I would like to know how much of an operating system is actually
on a limited flash
> storage space of a MCU? Do I get a login, with file storage a
graphical X server with KDE or
> GNOME somehow stripped down and swapped in and out of a multi MB
storage device?
Resources, resources, resources...
Your system will be limited by how much RAM and flash you have
available.
There are many AT91xxx parts, some of which can support multiple MB
of RAM and flash. You can run uclinux on those.
Forget it for AT91SAM7512 or smaller.
Reading uclinux.org is a good start. I would disagree with the claim
that it is the world's most portable OS. Sure you can run it on ARM,
but not on all ARM-based parts.
>
> What kind of I/O would one typically use (graphics module screen,
hard disk, kyb,
> ethernet) and how much work is needed to make the peripherals work?
You are obviuosly limited by the peripherals. No display == no KDE
(well I guess you possibly could over X windows).
You are also limited by RAM, Flash & CPU. Trying to run X on a small
underpowered system is no fun.
Many SBCs only use console-type interfaces over a serial port or
ethernet/wifi.
It really depends on what you are trying to achieve. Sometimes a web-
server interface might be the most appropriate.
Some SBCs will use hard disks, but most will use either nfs or flash.
wrote:
>
> Hello,
> I made a similar post on the e-embedded yahoo group. I know that
ucLinux was ported to
> the AT91.
>
> I would like to know how much of an operating system is actually
on a limited flash
> storage space of a MCU? Do I get a login, with file storage a
graphical X server with KDE or
> GNOME somehow stripped down and swapped in and out of a multi MB
storage device?
Resources, resources, resources...
Your system will be limited by how much RAM and flash you have
available.
There are many AT91xxx parts, some of which can support multiple MB
of RAM and flash. You can run uclinux on those.
Forget it for AT91SAM7512 or smaller.
Reading uclinux.org is a good start. I would disagree with the claim
that it is the world's most portable OS. Sure you can run it on ARM,
but not on all ARM-based parts.
>
> What kind of I/O would one typically use (graphics module screen,
hard disk, kyb,
> ethernet) and how much work is needed to make the peripherals work?
You are obviuosly limited by the peripherals. No display == no KDE
(well I guess you possibly could over X windows).
You are also limited by RAM, Flash & CPU. Trying to run X on a small
underpowered system is no fun.
Many SBCs only use console-type interfaces over a serial port or
ethernet/wifi.
It really depends on what you are trying to achieve. Sometimes a web-
server interface might be the most appropriate.
Some SBCs will use hard disks, but most will use either nfs or flash.
