You can also consider a hack to sample an Analog value with a digital pin - thought it isn't very fast, and can take a bunch of CPU, and open the potential to burn out the pin or chip, yet, it may give you a simple solution:
http://www.raspberrypi-spy.co.uk/2012/08/reading-analogue-sensors-with-one-gpio-pin/

@Boken-Lin Just got my onion omega today! Wanted to test my oled, but can not find any doc. Hoping for the library soon (today?)

You can also consider a hack to sample an Analog value with a digital pin - thought it isn't very fast, and can take a bunch of CPU, and open the potential to burn out the pin or chip, yet, it may give you a simple solution:
http://www.raspberrypi-spy.co.uk/2012/08/reading-analogue-sensors-with-one-gpio-pin/

Thank you!
I will get on the chromebook setup write-up.

I see that the oled testing is in the latest release https://community.onion.io/topic/198/mega-omega-software-release

Now I just have to get back home to load the new update to try my OLed display - can't wait!

I received my onion kit this week. Very glad to have it!

Sharing my thoughts to date.

I can not test the OLed display, as there does not to be any example code I can load. I would really like just a very simple script that will confirm it turns on.

The OLed I received does not have a stackable header, as shown on the order page. As I do not plan to stack anything over the OLed display, this is not a real problem for me, just a note related to the order page (see attached photo of my OLed unit). Though it does make it challenging to consider adding any wiring to the unit for breadboarding while the OLed is plugged in. However, the flush nature of the OLed would make it fit better in a case.

I was able to set up my onion with only my chromebook. I followed the web instructions, and I was very happy to find it worked. I was pleasantly surprised to find it can do 2 wifi at once, as a client and a server - acting as a bridge in default setup! I would be willing to do a factory reset and document Chromebook setup if that would be a value to you.
I can not install the terminal drivers [without putting my chromebook in developer mode], maybe at some point we can get google to include a terminal driver in the base chromebook code.
I had trouble with SSH on the Chromebook to the Onion. It would not connect. I have successfully used the SSH app to connect to Raspberry PI in the past. Would like pointers on debugging ssh connection challenges.

Looking at the documentation, I learned a tiny bit about the hardware and OS for the Onion. I was also debugging an issue with my home router, an Actiontec, and realized that it was closely related to the Onion! (The squashfs is what made me look twice).

I have successfully used my Onion at home to prove I can connect and work with the terminal. I look forward to seeing more tools and learning more about it.
I brought my Onion into my day job to show off the unit, and I could not connect, or even see the wifi server from the Onion.
Back home, fine. Back in the office, no dice.
There are many wifi access points at my job, which I can only imagine are overwhelming the signal on the onion. Or is it something about not seeing my home network that is keeping it from bringing up its wifi server? Anything I can do to troubleshoot in a noisy wifi environment?
I even tried my wifi analyzed app on my android phone, holding it right over the Onion, and could not see any sign of the Onion wifi. I tried typing in the Wifi SSID, and could not connect.

I wonder how hard it would be to add a standard USB driver on the Onion side so that you could access part of the onion as a flash drive without having to install special drivers?

@Boken-Lin Just got my onion omega today! Wanted to test my oled, but can not find any doc. Hoping for the library soon (today?)