Help getting started with BBB and LOGI Bone

TySkby

Hi,

I'm having a bit of confusion when it comes to getting everything set up here.  It's possible that I have actually done everything right, but the User Manual ad Quick Start Guide fr the LOGI Bone have left me scratching my head.  So I'm wondering if one of you fine community members can tell me whether I'm on the right track (and if not, what am I doing wrong?).  Here goes...

Here are my steps to get to where I am:

1.  Prepared an 8GB SD card with the image from the Quick Start Guide (here: http://valentfx.com/doc/logi-image/logibone/logibone_150429_ubuntu-14.04-console-armhf-2014-08-13.img.zip)
2. Attached the LOGI Bone to the BBB.  Seems nice and tight.
3. Connect an ethernet cable to my router and the BBB.
4. With no power to the BBB, insert the SD card
5. Hold down the boot button on the BBB and plug in power to the BBB
6. After 30 seconds or so, I connect my laptop (running Ubuntu) to the BBB via USB.
7. SSH into the BBB: ssh ubuntu@192.168.7.2 using temppwd at the password prompt
8. cd ~/logi-tools
9. sudo ./install_logibone.sh and get this output:
   ubuntu@arm:~/logi-tools$ sudo ./install_logibone.sh 
   [sudo] password for ubuntu:
   Ign http://ports.ubuntu.com trusty InRelease       
   Get:1 http://repos.rcn-ee.net trusty InRelease [3,028 B]
   Ign http://ports.ubuntu.com trusty-updates InRelease 
   Err http://repos.rcn-ee.net trusty InRelease         
   
   Hit http://ports.ubuntu.com trusty Release.gpg
   Hit http://ports.ubuntu.com trusty-updates Release.gpg
   Hit http://ports.ubuntu.com trusty Release
   Hit http://ports.ubuntu.com trusty-updates Release
   Hit http://ports.ubuntu.com trusty/main armhf Packages
   Hit http://ports.ubuntu.com trusty/universe armhf Packages
   Hit http://ports.ubuntu.com trusty/multiverse armhf Packages
   Get:2 http://ports.ubuntu.com trusty/main Translation-en [943 kB]
   Get:3 http://ports.ubuntu.com trusty/multiverse Translation-en [123 kB]
   Get:4 http://ports.ubuntu.com trusty/universe Translation-en [5,063 kB]
   Hit http://ports.ubuntu.com trusty-updates/main armhf Packages                 
   Hit http://ports.ubuntu.com trusty-updates/universe armhf Packages             
   Hit http://ports.ubuntu.com trusty-updates/multiverse armhf Packages           
   Get:5 http://ports.ubuntu.com trusty-updates/main Translation-en [352 kB]      
   Get:6 http://ports.ubuntu.com trusty-updates/multiverse Translation-en [6,294 B]
   Get:7 http://ports.ubuntu.com trusty-updates/universe Translation-en [203 kB]  
   Ign http://ports.ubuntu.com trusty/main Translation-en_US                      
   Ign http://ports.ubuntu.com trusty/multiverse Translation-en_US                
   Ign http://ports.ubuntu.com trusty/universe Translation-en_US                  
   Fetched 6,693 kB in 8s (761 kB/s)                                              
   Reading package lists... Done
   W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repos.rcn-ee.net trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D284E608A4C46402
   
   W: Failed to fetch http://repos.rcn-ee.net/ubuntu/dists/trusty/InRelease
   
   W: Some index files failed to download. They have been ignored, or old ones used instead.
   Settin up cape eeprom ID ...............
   Installing dependencies...............
   Reading package lists... Done
   Building dependency tree       
   Reading state information... Done
   gcc is already the newest version.
   make is already the newest version.
   git is already the newest version.
   0 upgraded, 0 newly installed, 0 to remove and 122 not upgraded.
   Installing logi_loader...............
   gcc  -DLOGIBONE -o logi_loader logi_loader.c i2c_loader.c bit_bang_loader.c
   install logi_loader /usr/bin
   Installing python support...............
   Reading package lists... Done
   Building dependency tree       
   Reading state information... Done
   python-dev is already the newest version.
   0 upgraded, 0 newly installed, 0 to remove and 122 not upgraded.
   running build
   running build_ext
   running install
   running build
   running build_ext
   running install_lib
   running install_egg_info
   Removing /usr/local/lib/python2.7/dist-packages/PackageName-1.0.egg-info
   Writing /usr/local/lib/python2.7/dist-packages/PackageName-1.0.egg-info
   Installing logi C library...............
   gcc -shared -o liblogibone.so logibonelib.o
   mv liblogibone.so /usr/lib/liblogi.so
   cp logilib.h /usr/include
10. Then I power off the board.

This is the point where I feel a bit stuck... 

From here on out, when I want use the LOGI Bone and BBB together, do I have to boot from the SD card, or does the above process modify the existing (Wheezy) installation? Basically, at this point, I'm wondering what is installed, and where?  Can I re-purpose the SD card for something else, or do I need to keep it forever plugged into the SD card slot?  Furthermore, will I be able to use the LOGI Bone from the existing Wheezy installation on the BBB, or should I plan on always booting from the SD card if I want to use the LOGI Bone?

Thanks very much!

-Ty

PS- A bit of background: The LOGI Bone is the next step in a project I've been building with my brother- essentially we have the BBB programmed to react to various events that happen over the course of a (NFL) football game.  The next logical step was to add a "scoreboard" of sorts, which is where the LOGI Bone comes in.  We're feeling "stuck" here because we're not sure if we need to take our existing code and reinstall it onto the BBB while its running the Ubuntu 14.04 OS from the SD card, or if we're supposed to keep on going with the existing Debian installation.

We'll be sure to post the results of our project in the "User Projects Discussion" section when we're done!

mjones

Hi @TySkby

Thanks for dropping by.  Sorry for the confusion.  

The LOGI bone primarily uses GPMC as the communication port between the FPGA and the BBB.  On the BBB the GPMC port shares the same pins as the EMMC (BBB flash).  Thus in order to  use GPMC with the LOGI Bone the EMMC must be disabled, which requires the SD card to be used to load linux.  When running the "install_logi.sh" the device tree overlay setting are writting to the eeprom on the LOGI-Bone, which disable the EMMC when the LOGI Bone is connected to the BBB. 

Therefore, it is best if you boot from the LOGI Image using SD card if you want to use the default FPGA/BBB drivers.  Though you can use SPI to communicated between FPGA/BBB as is done with the LOGI Pi, but would need to modify the current LBone drivers.

Here is information as to what is on the LOGI image and what the "install.sh" script does

http://valentfx.com/wiki/index.php?title=LOGI_Bone_User_Manual#What_is_on_the_image

http://valentfx.com/wiki/index.php?title=LOGI_Bone_User_Manual#What_.22install_logibone.sh.22_does

Does this answer your question?

Sounds like a cool project - good luck!

TySkby

Awesome, thanks for the quick, helpful response!  That's everything we needed to know to move forward.

Best,

Ty