Setting up the Chi.Bio from scratch following the software manual online

[aliceboo]

We have tried to set up a Chi.Bio from scratch, i.e. after reflashing it with the latest debian distro as explained in the software manual.

After flashing the beagle board successfully, and following the instructions in the software manual, we ran bash setup.sh.

Warning messages appeared for the python set up part of the setup.sh script.

After the setup.sh script finished (with various warning messages) the /root/chibio directory didn’t contain any file.

The only way to rescue things at this point was to copy files contained in /home/debian from a factory set up beagle board over in /root/chiobio.

We are not sure if we did anything wrong, however we tried several times following the instructions in the software manual, which resulted in the same outcome after execution of the setup.sh script.

This should probably be investigated, resulting in updates for the github files on https://github.com/HarrisonSteel/ChiBio and in updates to the instructions in the software manual.

Here is the message at the end of the process:

Installed /usr/local/lib/python2.7/dist-packages/Adafruit_BBIO-1.1.1-py2.7-linux -armv7l.egg
Processing dependencies for Adafruit-BBIO==1.1.1
Finished processing dependencies for Adafruit-BBIO==1.1.1
chmod: cannot access ‘cb.sh’: No such file or directory

And here are some warning messages:

source/common.c:668:37: warning: ‘%s’ directive output may be truncated writing up to 49 bytes into a region of size 41 [-Wformat-truncation=]
snprintf(slots, sizeof(slots), “%s/slots”, ctrl_dir);
^~ ~~~~~~~~
In file included from /usr/include/stdio.h:873,
from /usr/include/python2.7/Python.h:33,
from source/common.c:34:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:67:10: note: ‘__builtin___snprint f_chk’ output between 7 and 56 bytes into a destination of size 41
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL – 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
source/common.c: In function ‘device_tree_loaded’:
source/common.c:730:37: warning: ‘%s’ directive output may be truncated writing up to 49 bytes into a region of size 41 [-Wformat-truncation=]
snprintf(slots, sizeof(slots), “%s/slots”, ctrl_dir);
^~ ~~~~~~~~
In file included from /usr/include/stdio.h:873,
from /usr/include/python2.7/Python.h:33,
from source/common.c:34:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:67:10: note: ‘__builtin___snprint f_chk’ output between 7 and 56 bytes into a destination of size 41
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL – 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
source/common.c: In function ‘unload_device_tree’:
source/common.c:780:37: warning: ‘%s’ directive output may be truncated writing up to 49 bytes into a region of size 41 [-Wformat-truncation=]
snprintf(slots, sizeof(slots), “%s/slots”, ctrl_dir);
^~ ~~~~~~~~
In file included from /usr/include/stdio.h:873,
from /usr/include/python2.7/Python.h:33,
from source/common.c:34:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:67:10: note: ‘__builtin___snprint f_chk’ output between 7 and 56 bytes into a destination of size 41
return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL – 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[aliceboo]

During the run of setup.sh, the console output mentioned a problem with a zip file not found: chibio1.zip.

This could be the reason why the setup.sh script doesn’t finish the job properly and why /root/chiobio doesn’t contain any file after setup.sh completes.

[harrison]

As in your other thread, they should come with the setup installed from the factory. However, I think it is in a different directory to where I intended.

Like you said, I think a simple fix to setup.sh might resolve this. I will have a look at what step is going wrong there…

[aliceboo]

Thank you Harry.

Is the operation directory meant to be /home/debian or /root/chibio?

By copying the files over into /root/chibio, we are running this as the operation directory currently.

[harrison]

I personally use /root/chibio, but ultimately it doesnt matter.
In part of that setup.sh script it should set the folder that cloud9 defaults to as root/chibio, hence why I am suggesting that one.

[aliceboo]

Looking at setup.sh, the problem comes from the fact that the file chibio1.zip is missing from /home/debian:

In setup.sh:
…
cd ~/../home/debian
unzip chibio1.zip -d ~/../root/chibio -> fails as chibio1.zip is not available in /home/debian

[harrison]

Yes, that is correct. One of the above commands is also making issues, I believe, because of an update to the underlying Debian operating system.
I have just updated setup.sh on Github, and the software setup instructions. It should now run the setup as intended.

[Author]

Posts