Whither XS-ARM? Forth and Back

After returning from Europe 10 days ago, I’ve been thrashing around for a sense of direction.  When I posed the question, on the server-devel list, of what sort of integration of my changed code to shoot for as I continued XS-ARM debugging, I got somewhat demoralized.  Daniel Drake pointed out, I think correctly, that supporting more than one distribution of XS was a substantial commitment, not to be taken lightly.

I had also been wondering how to relate to all the different ARM devices.  Most of them use Uboot, in some form or other.  But what might work for a pogo plug might not work for Tonido plug, etc. in terms of creating installation media.

So I started working on the Arduino battery monitor idea, and decided to put the ARM project on hold.

4 turns = more sensitive

I build up a current probe, using a hall effect sensor, and wrote the code to accumulate charge and discharge information and display it on an LCD display.  Since the LCD shield I was using had 5 push buttons, I wrote code to calibrate and zero the current probe, and store the new calibration values in the eeprom of the Arduino.

Then I came across Scott Ananian’s blog about a $5 arduino board he had designed using Eagle computer aided design tools.  A really low cost arduino sounds exciting to me.  Maybe I could do an Eagle CAD project for the battery monitor, and create a shield to go along with his main board.

$27 sensor – not robust enough

There’s no real substitute for experience.  The current sensor, from honewell, turned out to have a very fragile circuit board attached to the electrical terminals.  Fortunately, I had purchased 2 sensors, and was able to improve the design, to account for this fact, when I  used the second one.

Sorry it’s so dark

There’s a potted current sensor, ($18), that is mechanically much more robust. But at this point I’m focusing my attention on an op amp solution, which I built up 2 months ago. All of the parts for this approach may cost two dollars or so.

ARM project may be back on front burner

I got email from Andrew and Sridhar at OLPC-Australia.  It turns out that they are interested in using the XO-1.75 as a School Server.  I’m very excited about collaborating with them, and can imagine some form of consolidation and integration path with XS Boston in the long run.  In the mean time it helps to have someone on the ground to focus my efforts, and collaborate with.

An an aside, I noticed that pre-release XO code 12.1.0 uses systemd for start up.  This suggests to me that in the longer time frame, the Trimslice start up problems are strategic and need to be solved.

Advertisements

About George Hunt

Retired electrical engineer and programmer, enthusiastic about OLPC as a vehicle for gathering together volunteerism, mine and so many others', for helping education in developing countries.
This entry was posted in Uncategorized. Bookmark the permalink.

One Response to Whither XS-ARM? Forth and Back

  1. Peter says:

    The uboot issues on generic ARM hardware are being worked upon. You’ll see the start of that work appearing with Fedora 18 where various devices will be supported with anaconda (the Fedora installer system which covers both GUI and kickstart installs) so I suspect that might be a good first target. With it we should support at least PandaBoard/BeagleBoard/Trimslice devices and maybe even more.

    systemd is certainly strategic. OLPC uses Fedora or CentOS as it’s base and you just have to look at the Fedora roadmap to see the direction the OS side of things will go. I’m happy to help where possible

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s