Posts made by Joost Oostdijk

Ok, found at least how to fiddle with the BD Address.

There is a utility specific to this brand of BLE dongles bccmd. In order to change BD Address the following steps need to be taken:

$ hciconfig hci0 -a // check existing bd address
$ bccmd -d hci0 psset bdaddr 04 00 06 05 03 00 02 01 // set new address
$ bccmd -d hci0 warmreset // reset the device
$ /etc/init.d/bluetoothd restart // reset bt deamon
$ hciconfig hci0 -a // should show a different bd address.

To check scan from another device (RPI in my case)

$ sudo hcitool -i hci0 lescan
LE Scan ...
38:01:95:01:5E:41 (unknown)
01:02:03:04:05:06 (unknown) // this is the new bd address.

So solved for now, although I still dont know why the local names are not shown in the scan.

I'm trying to scan for several Onion Omega's that have the BT add-on configured as 'beacon'.

The beacons I configured like:

$ opkg install obluez-libs obluez-utils
$ hciconfig hci0 -a
$ hciconfig hci0 up
$ hciconfig hci0 leadv 3
$ hciconfig hci0 noscan
$ hciconfig hci0 -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
	UP RUNNING
	RX bytes:1182 acl:0 sco:0 events:67 errors:0
	TX bytes:1107 acl:0 sco:0 commands:67 errors:0
	Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
	Link policy: RSWITCH HOLD SNIFF PARK
	Link mode: SLAVE ACCEPT
	Name: 'OnionBLE'
	Class: 0x000000
	Service Classes: Unspecified
	Device Class: Miscellaneous,
	HCI Version: 4.0 (0x6)  Revision: 0x22bb
	LMP Version: 4.0 (0x6)  Subversion: 0x22bb
	Manufacturer: Cambridge Silicon Radio (10)

I also have a raspberry pi (3 with built in BT) from which I scan.

$ sudo hcitool lescan
LE Scan ...
38:01:95:01:5E:41 (unknown)
00:1A:7D:DA:71:13 (unknown)
00:1A:7D:DA:71:13 rpi2

This only shows me 1 of the 2 onion omega with BT add-ons plus the rpi entry for a second RPI that i also configured as 'beacon'.

The question is: what could be the cause of the missing second Onion w BT? They are both configured in the same way so I'd expect them both tho show up.
All devices are in my room (not next to each other). Does somehow the mac address, which is the same for all BT add-ons mess this up? How could I set a name in such a way it gets advertised? (All have their own name set with 'hciconfig hci0 name <unique name>')

Of course I could use 'hcitool lescan --duplicates' in order to not filter them but then I still cannot make a difference as all onions with BT add on seem to be reported as ''00:1A:7D:DA:71:13 (unknown)''

Thanks to anyone who would want to look into this.

@Kit-Bishop After installing/configuring the SDK I now have the following problem:
(put it here for future reference)

vagrant@ubuntu-xenial64-server:~/openwrt/custom/luv$ WITH_LUA_ENGINE=Lua LUA_BUILD_TYPE=System WITH_SHARED_LIBUV=ON BUILD_MODULE=OFF BUILD_SHARED_LIBS=ON STAGING_DIR=/home/vagrant/openwrt/sdk/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir make
cmake -H. -Bbuild -DBUILD_MODULE=OFF -DBUILD_SHARED_LIBS=ON -DWITH_SHARED_LIBUV=ON -DWITH_LUA_ENGINE=Lua -DLUA_BUILD_TYPE=System -DCMAKE_TOOLCHAIN_FILE=~/openwrt/openwrt.cmake  -DWITH_AMALG=OFF
System is unknown to cmake, create:
Platform/AR71xx to use this system, please send your config file to cmake@www.cmake.org so it can be added to cmake
Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please send that file to cmake@www.cmake.org.
-- Could NOT find LIBUV (missing:  LIBUV_LIBRARIES LIBUV_INCLUDE_DIR)
-- Could NOT find Lua (missing:  LUA_LIBRARIES LUA_INCLUDE_DIR)
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
LIBUV_LIBRARIES
    linked by target "luv" in directory /home/vagrant/openwrt/custom/luv

-- Configuring incomplete, errors occurred!
See also "/home/vagrant/openwrt/custom/luv/build/CMakeFiles/CMakeOutput.log".
See also "/home/vagrant/openwrt/custom/luv/build/CMakeFiles/CMakeError.log".
Makefile:37: recipe for target 'build/Makefile' failed
make: *** [build/Makefile] Error 1

I am sure it is just setting those missing variables, but I have no clue where to find them from.
I changed the cmake file into:

# this one is important
SET(CMAKE_SYSTEM_NAME AR7xxx)
#this one not so much
SET(CMAKE_SYSTEM_VERSION 1)

# specify the cross compiler
SET(CMAKE_C_COMPILER   /home/vagrant/openwrt/sdk/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-gcc)
SET(CMAKE_CXX_COMPILER /home/vagrant/openwrt/sdk/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-g++)

# where is the target environment
SET(CMAKE_FIND_ROOT_PATH  /home/vagrant/openwrt/sdk/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/target/linux/ar71xx)

# search for programs in the build host directories
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
# for libraries and headers in the target directories
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

@Kit-Bishop dropped you an email.

@Kit-Bishop Thanks for your help. I guess it might help me out to have a toolchain version that includes Lua.
What probably would help me even more is to also figure out what I do not understand about the toolchain.

I assumed that if the lua package is under the packages dir of the toolchain that I could somehow link to it, but yeah assumptions,

The luv repository is the one from where I got the source. I was trying to build against lua not luajit.

Thank you for your time!

I am looking into using a small footprint solution to use libuv on the Omega with either Python or Lua as the 'interface' to it.

OpenWRT on the Omega seems to support libuv out of the box.

root@Omega-1E13:~# opkg list | grep libuv
libuv - 1.4.2-1

But I am struggling with cross compiling libraries such as pyuv or luv

I setup the cross compile environment on a linux VM and tried to compile a package (not the whole image) according to the tutorial to no avail. Does anyone have experience cross compiling e.g pyuv or any other external package? Maybe the tutorial could be updated with an example of how to create external packages?

I'm trying to cross compile luv with the help of the cross compile tutorial. I set the environment up on a virtual machine and git cloned the luv repo to ~/openwrt/custom/luv directory on this VM.

Then I added a openwrt.cmake file with this content (as building this repo depends on cmake)

# this one is important
SET(CMAKE_SYSTEM_NAME AR7xxx)
#this one not so much
SET(CMAKE_SYSTEM_VERSION 1)

# specify the cross compiler
SET(CMAKE_C_COMPILER   /home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-gcc)
SET(CMAKE_CXX_COMPILER /home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-g++)

# where is the target environment
SET(CMAKE_FIND_ROOT_PATH  /home/vagrant/openwrt/target/linux/ar71xx)

# search for programs in the build host directories
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
# for libraries and headers in the target directories
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

and in order to source the previous settings to cmake I added this line to the luv repos Makefile

-DCMAKE_TOOLCHAIN_FILE=~/openwrt/openwrt.cmake \

I run make as follows (I intend to install lua and libuv separately (these can be simply installed with opkg) so the make flags are intended to link to the deps)

$ WITH_LUA_ENGINE=Lua LUA_BUILD_TYPE=System WITH_SHARED_LIBUV=ON BUILD_MODULE=OFF BUILD_SHARED_LIBS=ON STAGING_DIR=./staging_dir make

this however results in :

cmake --build build --config Debug
make[1]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[2]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
[ 92%] Built target uv
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
[ 96%] Building C object CMakeFiles/luv.dir/src/luv.c.obj
In file included from /home/vagrant/openwrt/custom/luv/src/luv.c:18:0:
/home/vagrant/openwrt/custom/luv/src/luv.h:19:17: fatal error: lua.h: No such file or directory
 #include <lua.h>
                 ^
compilation terminated.
CMakeFiles/luv.dir/build.make:62: recipe for target 'CMakeFiles/luv.dir/src/luv.c.obj' failed
make[3]: *** [CMakeFiles/luv.dir/src/luv.c.obj] Error 1
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/luv.dir/all' failed
make[2]: *** [CMakeFiles/luv.dir/all] Error 2
make[2]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
Makefile:127: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
Makefile:40: recipe for target 'luv' failed
make: *** [luv] Error 2

How can I make sure lua is available in the cross compile environment? I am quite new to openwrt, lua and cross compiling in general so I might be missing something obvious.

Cool, thanks for that. I was wondering if it is possible and feasible to add websocket support to this setup.

Or might there be a way to add websocket support to the uhttp deamon. This is running the oem onion Web console AFAIK. Would it make any sense to look into making uhttp somehow support websockets and simple lua scripts?

Or, can ubus be used to push system events into a page?