Channels ▼

Al Williams

Dr. Dobb's Bloggers

Stupid Beagle Tricks, Part II

October 02, 2012

I've been working more with the BeagleBone, and I've found that it takes a little different mindset to develop with a tiny Linux system instead of a traditional microcontroller. I wrote about this back in June but I wanted to share a few other tips on Beagle development. Many of these tips will probably also apply to other small Linux boards like the Raspberry Pi or the Olimex OLinuXino (Micro and Maxi; sorry Tsevan, that's a terrible name).

My favorite trick of all is near the end of my entry from June: Use sshfs to mount the BeagleBone's file system as a local disk. Then you can use any of your normal tools on your desktop machine. I don't use Windows much, but if you do, you might try the Windows version, which seems to work, although with some quirks. I suppose you could also install Samba (just run opkg install samba from a prompt running on the BeagleBone).

One reason I really like that trick is that I can use my beloved emacs easily to edit files. However, you can install emacs on the board itself. For some reason, it doesn't show up on the Angstrom's opkg package manager, but there is a way to get a working version from an older Angstrom distribution (I found the information about this here).

You can look up the details, but the short instructions are:

opkg install liblockfile_1.06-r1.6_armv7a.ipk emacs_22.3-r1.6_armv7a.ipk

That same website suggests installing xinetd and swat if you want to use Samba, by the way.

It is certainly pleasant doing simple tasks with Linux tools. You can only wonder how much lower Linux modules can go in price and at what point that will start to erode some of the market for traditional microcontrollers. If I had to create a high-volume or hard real-time system, I'm still going to lean towards a microcontroller, but for a lot of non-demanding control applications there is going to be a price where the Linux environment will win my vote over a dedicated microcontroller.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.