Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://www.openembedded.org" rel="nofollow noreferrer">OpenEmbedded</a> is a good place to go to get started. A lot of embedded products use ARM and other processors, so cross-compiling is a big deal. <a href="http://buildroot.uclibc.org/" rel="nofollow noreferrer">Buildroot</a> is another resource for building custom linux kernels for small systems.</p> <p>You can also find lots of manufacturers with Single Board Computers (SBCs) that have tools to do what you want - do a google search for "SBC Linux" and you should have a gold mine.</p> <p><a href="http://linuxdevices.com/" rel="nofollow noreferrer">LinuxDevices</a> keeps a pulse on the linux embedded community and you should find several good articles there that lead you to products or software to help you.</p> <p>Debian has an embedded build, but I haven't explored that.</p> <p>There are several books on <a href="http://www.linuxdevices.com/articles/AT2969812114.html" rel="nofollow noreferrer">embedded linux</a> available if you want to go that route.</p> <p>The GPS receiver simply connects to a serial or USB port, and present an NMEA stream of data, which you can parse with GPSD and several programs can access it through GPSD. It's a very simple text based format.</p> <p>I've used regular PC motherboards, and Atmel AT91 processors for embedded systems (with GPS, cellular, etc). There's a lot of information out there right now, and it's not expensive to get into. If I were to start a new project, I'd look at the AVR32 processors from Atmel - they are very hobbyist friendly, and provide a lot of community support for linux on the AVR32 architecture. They provide free GCC compilers and significant framework and examples if you want to go the OS-less route and have a single program running on the processer as well.</p> <p>Good luck!</p> <p>-Adam</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.
    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