Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Once everything is running, it is mainly linux programming. If you start with an eval board, I guess you have already a lot of tools. Anyway, you might find the following links useful.</p> <p>Toolchain : cross-compilation. You can go the easy way, ie download a pre built toolchain from <a href="http://www.codesourcery.com/" rel="noreferrer">code sourcery</a>. Or you can go the hard way, and build your own toolchain. The hard way is however made easier if you use the right tool. <a href="http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool" rel="noreferrer">Croostool-ng</a> is sucha project with a very reactive mailing list.</p> <p>Kernel : well, arm architecture has been in mainline for a while, however, if you have some ARM specific question, you should definitly ask them <a href="http://www.arm.linux.org.uk/mailinglists/" rel="noreferrer">there</a> </p> <p>Userspace : Once the kernel is booting, you need a userspace to run, ie some filesystem, shell, C library, init process etc ... To build such tools, there are many options. One is to do everything yourself. You start with busybox, and then continue with the various tools you need. Or you can go with automated and configurable tools. My preference goes to <a href="http://www.pengutronix.de/software/ptxdist/index_en.html" rel="noreferrer">ptxdist</a>, because it has the right complexity level (for my use). Another options is <a href="http://buildroot.uclibc.org/" rel="noreferrer">buildroot</a> which I don't know. And if you feel you need something more powerful maybe you can take a look at <a href="http://wiki.openembedded.net/index.php/Getting_Started" rel="noreferrer">OpenEmbedded</a>.</p> <p>I came across som books related to embedded development, but it was more like documented scripts. Building a complete embedded system is hard, and I think you will find more infos in the tools and mailing list than in books.</p>
 

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