A Look at the Ben NanoNote
The command line is something I always want in any computer or gadget I own. For me, it symbolizes ultimate access and control. When I heard about the Ben NanoNote from Qi Hardware and learned it primarily was a command-line device, I knew I had to get one and play with it. It also doesn't hurt that it costs only $99 ($124 after shipping).
Qi Hardware is a firm believer in not only open software, but also open hardware. According to its Web site, its mission is “to promote and encourage the development of copyleft hardware”. As part of this mission, full documentation on the Ben NanoNote is available on the Web site, including circuit-board layouts, schematics and other hardware documentation.
Granted, I probably never will have the tools or expertise to create my own NanoNote from parts, and even if I could, I probably wouldn't be able to do it for less than what it costs to purchase one. But, the documentation is available, and it is under a license that lets me do it if I had the inclination.
Incidentally, “Ben” refers to a Chinese character meaning “origin”, “root” or “beginning”. The idea is that this is the initial or first version of what eventually will be a complete line of NanoNote and other related products.
The Ben NanoNote is built around the JZ4720 366MHz MIPS-compatible processor from Ingenic Semiconductor with a three-inch, 320x240 pixel color TFT LCD (40x15 character in the text console). It has 32MB SDRAM, 2GB NAND Flash memory, one microSDHC slot (SDIO-capable), a 59-key keyboard, a headphone port, a mono speaker and a USB 2.0 Mini port. It is powered by a 3.7V 850mAh Li-ion battery, or it can run off USB power (5V 500mA DC) either by plugging it in to your computer or by using one of the increasingly common USB power adapters (my phone, camera and eBook reader all came with USB power adapters). The Ben NanoNote earns the “nano” part of its name, measuring only 99x75x17.5mm. Including the battery, the Ben NanoNote weighs in at only 126g, which is lighter than my cell phone.
Four days after ordering the Ben NanoNote, it arrived on my doorstep in North Carolina—not bad for coming all the way from Hong Kong. It comes in an attractive black box containing the Ben NanoNote itself, a manual (most of which is devoted to printing the full text of the Creative Commons BY-SA license), a microfiber cleaning cloth, a battery, a USB cable and a little rubber nub for shorting the “USB Boot” pins in the battery compartment.
The build quality is decent with no gaps or loose bits. The keyboard has an okay feel to it, even though it is a bit stiffer than I prefer. And, despite it having the world's smallest spacebar, the layout actually works pretty well for command-line work—except that the dash (-) key is is annoyingly placed.
The sound quality out of the single speaker is tinny and prone to distortion, but it's what I expected. If you must listen to music on the Ben NanoNote, external speakers or headphones are the way to go.
Like many embedded devices, upgrades to the core software are done by flashing the device to the newest firmware. Unlike other handheld devices, which can flash themselves or be flashed by copying some files to the device via USB, the Ben NanoNote needs to start in a special “USB Boot mode” to be upgraded. Full instructions are on the Qi Hardware Wiki, but the basic steps are as follows:
Install the Xburst tools (used for booting the Ben NanoNote over USB).
Download the reflash_ben.sh script from the Qi Hardware Wiki.
Put the Ben NanoNote into USB Boot mode.
Run the reflash_ben.sh script.
Putting the NanoNote into USB Boot mode was harder than I thought it would be. To do this, you need to take out the battery and plug the Ben NanoNote in to your computer (if the screen comes on when you plug it in to your computer, unplug the USB cable briefly and plug it back in; the screen should stay dark). Next, use the little nub that came with the Ben NanoNote (or some other piece of conductive material) to short the two USB Boot pins found in the (now empty) battery compartment. While keeping the pins shorted, and without unplugging the USB cable, you have to press and hold the power button for two seconds. Because the power button is on top and the pins are on the bottom, this was not very easy for me to do. Even worse, the indication that you've succeeded is that nothing happens—when the screen stays dark after holding the power button for two seconds.
After going through the contortions it takes, I would prefer some sort of icon on the screen or even a little indicator light to confirm I am in the proper mode, but for now, that's the process. When in USB Boot mode, the Ben NanoNote is waiting for the usbboot utility (one of the Xburst tools) to give it an image from which to boot.
The final step, running the reflash_ben.sh script, is nicely hands-free. The script automatically fetches the latest firmware (unless you specify a specific version) and then boots and flashes the Ben NanoNote. The main root image is more than 140MB, so downloading may take some time, depending on your Internet connection. Flashing the rootfs also took several minutes. Patience, or a nice snack break, are required for this step.
After flashing my Ben NanoNote, unplugging it and re-inserting the battery, I knew all was well when it booted and I saw the OpenWrt logo, and then the graphical “Desktop” (Figure 5). Although the flash procedure is not overly difficult, it's not ideal, and I hope it improves over time.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
9 hours 3 min ago
- BASH script to log IPs on public web server
13 hours 30 min ago
17 hours 6 min ago
- Reply to comment | Linux Journal
17 hours 38 min ago
- All the articles you talked
20 hours 2 min ago
- All the articles you talked
20 hours 5 min ago
- All the articles you talked
20 hours 6 min ago
1 day 31 min ago
- Keeping track of IP address
1 day 2 hours ago
- Roll your own dynamic dns
1 day 7 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?