Up and coming changes

Yup this is what I posted on mine.   Close enough.  You should include networking as a required start btw.  The remote_fs probably isn't so important but I like to make sure that is up too.

#!/bin/sh

### BEGIN INIT INFO
# Provides:          xap
# Required-Start:       $remote_fs $syslog $networking
# Required-Stop:        $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      1
# Short-Description: xAP HAH system
# Description:       xAP Home automation hub
### END INIT INFO
#
# /etc/init.d/xap start [component...]
# /etc/init.d/xap stop [component...]

What think is happening is that because the IP address is obtained via DHCP.  This part of the init script is ASYNC and eth0 isn't ready before the xAP sub-system is trying to start up using it.

root@beaglebone:/var/log# more xap-hub.log
xAP HUB
Copyright (C) DBzoo, 2008-2014

[crt][init.c:113:discoverBroadcastNetwork] errno 99 (Cannot assign requested address)
[crt][init.c:113:discoverBroadcastNetwork] Unable to query capabilities of interface eth0

I am going to switch to a static IP (how it currently looks)

root@beaglebone:/var/lib/connman/ethernet_00183193c84d_cable# cat settings
[ethernet_00183193c84d_cable]
Name=Wired
Modified=2014-02-05T10:12:06.005549Z
IPv4.method=dhcp
IPv6.method=auto
IPv6.privacy=disabled
IPv4.DHCP.LastAddress=192.168.1.100

I will modify this to be STATIC anyway that will make it easier to find.
What is odd is that kloned starts up just fine its all the xap app that are failing.

http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/

[ethernet_00183193c84d_cable]
Name=Wired
Modified=2014-02-06T08:35:43.519891Z
IPv4.method=manual
IPv6.method=auto
IPv6.privacy=disabled
IPv4.DHCP.LastAddress=192.168.1.100
Nameservers=192.168.1.20;
IPv4.netmask_prefixlen=24
IPv4.local_address=192.168.1.100
IPv4.gateway=192.168.1.1

Nope - same issue.  WTF.    Is this some latent bug?   Digging.....

Brett

Mark,

I don't have an /etc/network directory let alone an interfaces file inside it.
Are you stil on Angstrom v2012.05 ?

As an experiment I built an systemd enabled xap-hub.
Although it still does not startup correct it does however now stay alive when I log out.
So its a minor step forward.

I also played around with dependencies.  I built an xap-hub.ipk and an xaplib2.ipk when I install the hub it noticed the dependency and opkg automatically downloaded the library too.   So that's kind of neat to get working.

connman is a stinking pile of shit.  Its trying to be too smart for its own damn good.
I have one interface just bring it up FFS and stop rooting around with looking for wifi and all the other crap I don't even have.   It also screws with my /etc/resolv.conf and I can't get that sorted at all.   What a crock connman is.  A half baked steam pile.

As Gary said it just works on the PI.  That is how things should be.

I'm going to rework this code that is playing up in the xaplib2.so library.
At the same time I'm going to have it default to using the first network interface that it can find if none is supplied with (-i <nic) option.  That will help with defaulting too.

Brett

For now the workaround is just to wait until the network is up and then a couple of seconds after detecting it for good measure.  By doing a network check and not a "always sleep" the script remains responsive when called on the command line or if the network is instantly up like it is on the PI (or perhaps later angstrom distro's).  Its a hack but it works.
See /etc/init.d/xap and the 'checkNetwork' function.

I've push 0.5 of the HAH distribution .ipk up with my latest changes including this hack.
Just a reminder that you can install the HAH onto your BB with like this:

# cat /etc/opkg/hah.conf
src/gz hah http://homeautomationhub.com/feeds/ipkg/eglibc/armv7a

# opkg update
# opkg install hah

Mark you will see a single location MYDEV that you need to change to wlan0 to get this wireless lan enabled.  You migh also need to hack with the checkNetwork script and wait on wlan0 if that is doing the same tricks on you.

One thing that I found useful for testing on a reboot is to set in the /etc/init.d/xap script.
MYDEV="-d 6"
When the init script runs everything is started in debug mode!
Now that the interfaces enumerate you can see what is going on and if they are there or not.

Brett

Mark,

I think you ended up sorting out your problems for yourself - I was a little confused at the end of reply as to whether you still had a problem or not.

The changes I made to output the interfaces definately helps debug these sorts of problem thou..  Which is good that was the intent.

You wrote -> "If I START xap after the BB has booted the xap-hub process runs but still not after a reboot."

For wlan0 you need to wait for this to startup by modifying the checkNetwork{} function so the xap startup does not get ahead of itself.  Wait for WLAN0 to be UP before allowing the xap processes to start up.

If xap-hub if it can't bind to port 3639, that is its the first xap process up, then it will fail (by design).

If you are not waiting for the network to fully start up as xap-hub is being started first, if the network is not quite ready, it will fail (as you are discovering).   However as the other processes are starting the network might become ready so you end up with things like xap-serial, plugboard later on starting but not connected into a hub so they won't be able to receive xAP packets.  (Well the 1st one as its grab port 3639 but nothing else will be able to).

Brett

Cool.

I have a jeenode attached to mine now so I know: xap-hub, xap-serial and plugboard are happy.

What is neat is the the livebox is caching the xAPBSC.event with xapCacheWebserverApplet.lua with simple set of filters.

local vfs = {
   filter={
      xap.Filter{["xap-header"] = {
                    source="dbzoo.livebox.Controller:1wire.*",
                    class="xAPBSC.event" }
              },
      xap.Filter{["xap-header"] = {
                    source="dbzoo.*.jeenode:>",   -- Any jeenode attached to any HOST
                    class="xAPBSC.event" }
              },
   },
   data={}
}

So I get this web page from my livebox on port 8080 (served by the LUA web server)

Cached xap-header source keys

• dbzoo.nanode.jeenode:5.temp
• dbzoo.nanode.jeenode:3.temp
• dbzoo.nanode.jeenode:4.temp
• dbzoo.nanode.jeenode:5.moved
• dbzoo.nanode.jeenode:3.lobat
• dbzoo.nanode.jeenode:2.light
• dbzoo.nanode.jeenode:7.temp
• dbzoo.nanode.jeenode:4.lobat
• dbzoo.livebox.Controller:1wire.1
• dbzoo.beaglebone.jeenode:1.temp
• dbzoo.nanode.jeenode:5.lobat
• dbzoo.nanode.jeenode:5.light
• dbzoo.nanode.jeenode:3.light
• dbzoo.nanode.jeenode:7.lobat
• dbzoo.nanode.jeenode:4.light
• dbzoo.nanode.jeenode:2.temp
• dbzoo.nanode.jeenode:7.humi
• dbzoo.beaglebone.jeenode:1.light
• dbzoo.nanode.jeenode:2.lobat

Which is then polled by my CACTI logging system to produce nice graphs.  The SHED node is the beagle bone feed.  Its a large shed 6m x 9m x 3m  (w x l x h)
It getting a little warm in there today  :)

The spikey comms temperature is because I have another LUA script that monitors the temperature and turns on an exhaust fan when it gets too hot in there.  So when it kicks in the temp drops rapidly and then it heats back up again.

I have downloaded the latest Angstrom distro so I will check that out too.

Brett

One step back.
I updated to the lastest angstrom distro and now I get a kernel crash when I boot up with my jeenode attached.  :(

Detaching loopback /dev/loop0.
All loop devices detached.
Detaching DM devices.
All DM devices detached.
[   98.928239] (NULL device *): gadget not registered.
[   98.948135] Power down.
[   98.954053] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
[   98.954053]
[   98.963667] [<c001051d>] (unwind_backtrace+0x1/0x8c) from [<c036c641>] (panic+0x55/0x14c)
[   98.972241] [<c036c641>] (panic+0x55/0x14c) from [<c002ec8f>] (do_exit+0x2ef/0x5dc)
[   98.980268] [<c002ec8f>] (do_exit+0x2ef/0x5dc) from [<c0036983>] (sys_reboot+0xb5/0x126)
[   98.988747] [<c0036983>] (sys_reboot+0xb5/0x126) from [<c000c641>] (ret_fast_syscall+0x1/0x46)

The good - there is a fix for this.
The other good - I installed the new distro on another micro SD card just in case I need to switch back.

https://github.com/beagleboard/kernel/issues/26

The bad - you have to build your own distro as its not released with this bug fix yet.
And on that note I'm going to back to v2012.05

Mark let me know if you run into this.  Have you attached a jeenode yet?
Brett

A kernel panic is never "normal" - that's what we call a bug.

UPDATE:  310.11 - As part of the BB porting work I've pushed another livebox release.
This includes a couple of changes
  * The xap-hub won't appear as dbzoo.hub.linux-x.x.x  instead it will be inline with all the others for the host.    dbzoo.'hostname'.hub
  * There is no need to add -i br0 when you start them up on the livebox, they will figure it out for themselves which interface is active and can be used.

Look mum, no -i br0 !

  142 root      1032 S    /usr/bin/xap-hub
  145 root      1080 S    /usr/bin/xap-xively
  146 root      1072 S    /usr/bin/xap-livebox -s /dev/ttyS0
  148 root      1460 S    /usr/bin/iServer
  151 root      1460 S    /usr/bin/iServer
  152 root      1460 S    /usr/bin/iServer

I think this will be my final beta before I push 311.  To put a stick in the sand.

Brett

I have upgraded my beagle to unbuntu and have built a "portable" distribution that compiles everything up.  Just having a few issues with kloned, which I'm going to deprecate when moving from the livebox, but I'd like to get it working as a starter.

Once I get a clean build I'll check this lot in to a 'portable' branch.  This should "just compile" on the PI too.  I'm doing this all native no cross compiling this time if it works for me, it should work for you too.

Out of this "sysroot" that is built the next step is to automate the packaging.  Once this framework stuff is in place I can look at rewriting a new web UI.

Brett

Mark / Gary,

I have some testing for you.  You'll need to be running Ubuntu on your Bone / PI.
@Gary there is no need to swap cards as the build will not install anything its simply lays out the created files in a sysroot.   The purpose of the test is to verify the build works for you like it does for me.
@Mark I used a .img from here http://elinux.org/BeagleBoardUbuntu with my windows box to write the SD card.

How to proceed.  You don't need to be root and its best you aren't.

svn checkout http://livebox-hah.googlecode.com/svn/branches/portable
cd portable

In there you will find a README that details what additional build packages you should have installed just run the apt-get to check you have them all.

After you have installed those type "make" and sit back.  When its done all the binaries will be in build/sysroot.
On my beagle bone: 9m 30sec

This portable distribution built just as easily on my x86_64 linux machine too.
On my linux box it built in: 40sec.

This should allow folk to compile the code on whatever platform they desire, assuming you can resolve the dependencies, most distro's have those dev packages available even on my aging old Centos 5 box.

UPDATE:

I just finishing doing a raspberry PI build running pidora and it built just fine.

The intial pre-requisites are a little different from a ubuntu distro so I'll list them here:

Install subversion and friends.    

 yum install subversion libxml2-devel libcurl-devel openssl-devel

Install development environment tools.

yum groupinstall "Development Tools" --skip-broken

The Pidora distro has some issues with dependencies so skip the broken rpm's they aren't needed anyway.

Get the portable build

svn checkout http://livebox-hah.googlecode.com/svn/branches/portable
cd portable
make

On Derek's Raspberry PI it took: 15m 50sec

NOTE: There are not installation scripts nor startup scripts in this portable branch yet so even thou the binaries all build you won't be able to "start it up" and use it. YET.

I've added the target "bb-package" that will build a .deb file that you can install on the beaglebone running ubuntu to set the HAH system up.   IT just works !

Gary you'll need clone this a little for the PI and adjust the 'control' file for the PI architecture after that it should be good.   OR you can wait for Derek to rebuild his PI with a Ubuntu distro so I can figure this out.   Derek if you wouldn't mind rebuilding with Ubuntu instead of Pidora your PI  :)

Brett

Gary you said,

tried: sudo make
then sudo make bb-package
then sudo dpkg -i build/*.deb

The correct steps are:

make
make bb-package
sudo dpkg -i build/*.deb

Only the installation needs to be done as root everything you can do as a normal user.

Yes there is quite a bit more work to be done this was an ALPHA release of the portable branch and I've yet to set many of the binaries up and verify their behaviour.   Gary you are on the leading edge of development here so expect some issues having said that it did seem to go relatively smoothly for you. Intereresting that you did not require any modification to the bb-package target for installation on the PI.   That's good to know I will adjust the directory layout then to be a little more architecture agnostic.  If you shutdown the apache server on port 80 kloned should just work too.  Or you can adjust kloned's port in the /etc/kloned.conf file to something else.

Anway this looks to be progress.. Thx for testing.

UPDATE:
To get yourself back to a clean environment you will need to clean as root as the output has already been created as the root user.
sudo make clean
After that you should be able to "make" and "make clean" as a normal user, I try not to be root more than I need to be.

Brett

AS part of my "the hah hardware should not be directly on your PI/Beagle" philosophy.
I've already built and tested as standalone xAP compliance ethernet tethered devices/sketches.

• URF TX - http://livebox-hah.googlecode.com/svn/trunk/userapps/arduino/EthURF/
• Relays - http://www.dbzoo.com/livebox/ethrelay & http://www.dbzoo.com/livebox/hah_hahnode/outputnode

The other functions on the PCB are

• 1wire, well the jeenodes can do that, and if you really want you can put one your HAHCentral.
• I2C/PPE -  nobody is using it even thou it very cool.
• An LCD display -  I could built an xAP compliance LCD display for remote use.  Would be neat.
• 4x Inputs - can build a jeenode for that if you wish.

So you see everything that the HAH hardware does can already be replaced.  Thus its not needed as a single unit.

Brett