UPDATE [Dec 23]: After a couple of days' success with the
Overo, it is time to give it a name: Tivovy.
Mon Dec 21 2015
Unboxing
1200> My gumstix kit arrived sometime before noon today. Kaspar
somehow missed the UPS truck and I just happened to look out the
window to see the package sitting in the rain at the end of the
driveway. The box had been sealed in a plastic bag and was not
wet.
The original photos are 2MB.
First mistake: I should have taken a close-up photo of the Tobi
board before mounting the COM. I still need to deduce the BoM for the
Tobi board. To remove the COM with the spacers installed, first
gently pry up the COM board just enough to disengage the snap connectors,
then squeeze the spacers from the bottom of the Tobi and push them up
through the Tobi to release the COM. Obviously, the whole procedure
should be performed as few times as possible (ideally never).
The first step is to mount the Overo COM onto the Tobi board. Make
sure to install the small, white, plastic spacers first. The snap-in
connectors are offset to one end of the COM so that the silkscreen
outline of the COM on the Tobi board lets me know how to orient the
COM. Settle the COM onto the spacers, making sure all four are poking
through the alignment holes. Press firmly and evenly on both ends of
the COM and it will snap into place. There will be an audible click as
each of the two connectors mate. The COM can be removed, but the
connectors have a limited lifetime that is measured in tens of cycles,
not thousands.
There should be a version of Linux already programmed into the NAND
flash, so I should be able to connect a USB cable to the debug port
and boot up. First I need to hunt down a gumstix AC/DC power
adapter...
12:30> The gumstix boots up just fine...
gumstix_first_boot:
U-Boot SPL 2014.10 (Feb 25 2015 - 07:02:26)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
corrected bitflip 2731
U-Boot 2014.10 (Feb 25 2015 - 07:02:26)
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 1024 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
Board revision: 4
Direct connection on mmc2
No EEPROM on expansion board
Die ID #7bd000029ff800000156083e0402900f
Net: smc911x-0
Warning: smc911x-0 using MAC address from net device
Hit any key to stop autoboot: 1 0
Card did not respond to voltage select!
Card did not respond to voltage select!
Booting from nand ...
NAND read: device 0 offset 0x280000, size 0x800000
8388608 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Booting from nand with DTS...
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI: attached mtd1 (name "mtd=4", size 1013 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 512 (aligned 512), data offset: 2048
UBI: good PEBs: 8108, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1143547297
UBI: available PEBs: 0, total reserved PEBs: 8108, PEBs reserved for bad PEB handling: 160
Loading file '/boot/omap3-overo-storm-tobi.dtb' to addr 0x88000000 with size 65848 (0x00010138)...
Done
Loading file '/boot/zImage' to addr 0x82000000 with size 4768136 (0x0048c188)...
Done
Kernel image @ 0x82000000 [ 0x000000 - 0x48c188 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffec000, end 8ffff137 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
...
[ 45.555847] Bluetooth: HCI UART driver ver 2.2
[ 45.560760] Bluetooth: HCI H4 protocol initialized
[ 45.565795] Bluetooth: HCI BCSP protocol initialized
[ 45.571136] Bluetooth: HCILL protocol initialized
[ 45.993499] Bluetooth: RFCOMM TTY layer initialized
[ 45.998870] Bluetooth: RFCOMM socket layer initialized
[ 46.004394] Bluetooth: RFCOMM ver 1.11
Poky (Yocto Project Reference Distro) 1.7.1 overo ttyO2
overo login: root
root@overo:~# ls -l
total 0
root@overo:~# uname -a
Linux overo 3.17.8-custom #1 SMP Wed Feb 25 04:05:20 PST 2015 armv7l GNU/Linux
root@overo:~#
The linux kernel is version 3.17.8, which is more recent than the
3.2 I am using on the BLIS project. This is a good thing, it means I
should be able to use kernel threads instead of Xenomai.
Next steps:
Configure ethernet
I did not have the ethernet cable plugged in during boot, and when I
used ifup eth0 linux complained that
/etc/network/interfaces did not exist. This system is using systemd,
which (I think) does not use the interfaces file. I found a
note
about a version mismatch in the scripts. I typed "dhclient" and the
ethernet was working, although it is possible that it had started
working on its own before I typed the command. I need to repeat the
experiment to be sure. The goods news is that I am able to ping
www.google.com. When I rebooted with the ethernet plugged in,
everything just worked.
Create a new Ubuntu VM for the gumstix build environment. I
could reuse the Nirvana VM, but I don't want to risk
contaminating either the BLIS or IronStorm environments, and I want to
document the complete process from start to finish.
Download the current Yocto bootstrap from gumstix.
Build the stock Overo boot disk.
Boot from my own boot disk.
Compile and run HelloWorld.
Create a new git repo for the project.
Extract the omap3-isp.ko source files to an out-of-tree
environment.
Rebuild omap3-isp.ko, install, and run it.
WebV7 (C)2018 nlited | Rendered by tikope in 46.691ms | 3.15.231.17
