Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The main problems with using the Linux kernel to replace microcontroller systems is driving the devices you are interfacing with. For this you may have to write drivers. I would say <strong>stick with C</strong> as the language because you are going to want to keep the user-space as clean as possible. Look into the <strong>uclibc</strong> library for a leaner C standard library.</p> <p><a href="http://www.uclibc.org/" rel="noreferrer">http://www.uclibc.org/</a></p> <p>You may also find <strong>busybox</strong> useful. This provides many userspace utilities as a single binary.</p> <p><a href="http://www.busybox.net/" rel="noreferrer">http://www.busybox.net/</a></p> <p>Then it is simply a matter of booting from some storage to a live system and running some controlling logic through init that interfaces with your hardware. If need be you can access the live system and run the busybox utilities. Really, the only difference is that the userspace is much leaner than in a normal distribution and you will be working 'closer' to the kernel in terms of objectives.</p> <p>Also look into realtime linux.</p> <p><a href="http://www.realtimelinuxfoundation.org/" rel="noreferrer">http://www.realtimelinuxfoundation.org/</a></p> <p>If you need some formal promise of task completion. I suspect the hardest bit will be booting/persistent storage and interfacing with your hardware if it is exotic. If you are unfamiliar with Linux booting then </p> <p><a href="http://www.cromwell-intl.com/unix/linux-boot.html" rel="noreferrer">http://www.cromwell-intl.com/unix/linux-boot.html</a></p> <p>Might help.</p> <p>In short, if you have not developed at a deep level for Linux, built your own distro, or have kernel experience then <strong>you might find the programming hard-going</strong>.</p> <p><a href="http://www.linuxdevices.com/" rel="noreferrer">http://www.linuxdevices.com/</a> Might also help</p> <p><strong>Good Luck</strong> </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload