Problem booting Beaglebone Black with LogiBone installed

woody

Hi, I received a new Logibone (R1.5.1). I had no trouble flashing and booting the Debian pre configured image on my BBB.  Next I install the Logibone and again no problem booting into Linux.  I now run
       sudo ./install_logibone.sh

debian@arm:~/logi-tools$ sudo ./install_logibone.sh
[sudo] password for debian:
Err http://repos.rcn-ee.net jessie InRelease
 
Err http://repos.rcn-ee.net jessie Release.gpg
  Could not resolve 'repos.rcn-ee.net'
Err http://ftp.us.debian.org jessie InRelease
 
Err http://ftp.us.debian.org jessie Release.gpg
  Could not resolve 'ftp.us.debian.org'
Settin up cape eeprom ID ...............
Error: Write failed
Error: Write failed
Installing dependencies...............
Installing logi_loader...............
make: Warning: File 'Makefile' has modification time 5439805 s in the future
make: Nothing to be done for 'all'.
make: warning:  Clock skew detected.  Your build may be incomplete.
make: Warning: File 'Makefile' has modification time 5439805 s in the future
install logi_loader /usr/bin
make: warning:  Clock skew detected.  Your build may be incomplete.
Installing python support...............
running build lists... 0%
running build_ext
Traceback (most recent call last):
  File "setup.py", line 1, in <module>
    from distutils.core import setup, Extension
  File "/usr/lib/python2.7/distutils/core.py", line 19, in <module>
    from distutils.dist import Distribution
  File "/usr/lib/python2.7/distutils/dist.py", line 19, in <module>
    from distutils.fancy_getopt import FancyGetopt, translate_longopt
  File "/usr/lib/python2.7/distutils/fancy_getopt.py", line 9, in <module>
    """
Installing logi C library...............
make: Warning: File 'Makefile' has modification time 5439804 s in the future
gcc -shared -o liblogibone.so logibonelib.o
make: *** Deleting file 'liblogibone.so'
Makefile:24: recipe for target 'liblogibone.so' failed
debian@arm:~/logi-tools$

The http://... failures I understand.  There is no network access from the BBB as ip forwarding is not enabled on the host.
Next the write fails to the cape board

After a reboot, I cannot get into Linux, the BBB starts but doesn't complete booting.
If I remove the Logibone then the BBB boots OK.
I already returned one Logibone as being faulty but this replacement board is doing exactly the same thing.
Seems to me the install_logibone.sh script has left some bad state when it failed?

Any help in moving forwards with this appreciated.

jpiat

Hi,

sorry that the process oes not got smooth for you. If you burn one of our pre-configured image to the BBB :
http://valentfx.com/doc/logi-image/logibone/logibone_150429_ubuntu-14.04-console-armhf-2014-08-13.img.zip(updated) 

what you only need to do is to burn the image on a sd-card and boot from it (make sure that the system did not boot from the eMMC). Once booted does not execute the install_logibone script but rather go to logi-tools/init_logibone and execute the init_eeprom.sh script to load the cape eeprom with the cape descriptor. Once dones, reboot the BBB and things should go fine.


The install_logibone script is only useful when creating your own image for the logibone, the pre-configured image has already all the tools installed.

Are yoou running a logi-bone v1 or v2 ?

Regards,

Jonathan Piat

woody

Hi, booting from the uSD card gets me back in, so that's a big relief.
However, loading the cape eeprom still fails:-

sudo ./init_eeprom.sh
Error: Write failed
Error: Write failed

The part ordered from Element14 was a Logibone V2 but the box just says Logibone.  The board itself is marked "LOGI-Bone R1.5.1"

woody

Just looked at the script, it's the two i2cset lines that fail.

jpiat

no worry, the two first line will only work for V1 logibone, it is supposed to fail for v2 logi-bone. After running the script and re-booting, can you load a bitstream ?

woody

Hi, tried the blink led application but no led blinking

root@arm:~/logi-apps/blink_led_app# ./make_demo.sh
bit file size : 340703
FPGA did not answer to prog request, init pin not going high
config success !
Blink LED App *************************************************************************

woody

Hi, problem now seems similar to thread

Problem with running blink test. 'Init pin not going high!'

Although symptom is the same, problem resolution is not as I'm already running the pre-configured Ubuntu image.  I haven't updated anything on this image.  Do I need to for V2 LogiBone?

mjones

The previous linked image was actually for the V1 boards.  I have updated it to the new image which supports the V2 board.  

http://valentfx.com/doc/logi-image/logibone/logibone_150429_ubuntu-14.04-console-armhf-2014-08-13.img.zip

Note that I just updated the wiki for the latest image as well.  The old loader will not work correctly as the GPIO expander has changed.  

I think that only change from the old image to the new image is the updated "~/logi-tools" directory.  You can run "git pull" from this directory to get the latest changes pulled in.  I think that you can then just re-run the logi-tools to setup script to rebuild and install the latest loader.  Double checking now.  @jpiat were there further changes that need to be run?

jpiat

Sorry but appears that i sent the link with the old image for logi-bone, here is the correct link :

http://valentfx.com/doc/logi-image/logibone/logibone_150429_ubuntu-14.04-console-armhf-2014-08-13.img.zip

you don't need to re-run the eeprom initialization script when booting with this one (unless something goes wrong).

jpiat

No further changes for LOGI-Bone, the new install logibone script installs the unified-loader which adapts itself to the board version.

woody

Hi Jonathon, Result !

I went for the updated pre configured image rather than a git pull.  I now have flashing LEDs :-)
The output from the loader is now :-

ubuntu@arm:~/logi-apps/blink_led_app$ logi_loader logibone_r1_blink.bit
Compiled for LOGI-BONE
Board variant is LOGIBONE_R1.5
bit file size : 340703
bitstream loaded, check done led
ubuntu@arm:~/logi-apps/blink_led_app$

Many thanks for your help

jpiat

Great ! You messages you see are the one from the new loader and you can see that your board was identified as a LOGIBONE_R1.5.

Don't hesitate to ask on this forum if you encounter any problem, we will be happy to help.