search

AferoCE / beetle

Afero Bluetooth daemon
MIT License
0 stars 0 forks source link

About make beetle issue #1

Open Peter-Lin opened 7 years ago

Peter-Lin commented 7 years ago

I tried to "make" in beele-master folder, but I got some error. Makefile:16: /rules.mk: no such file or directory Makefile:30: /package.mk: no such file or directory Makefile:31: /nls.mk: no such file or directory make: *** No rule to make target '/nls.mk'. stop

tastybento commented 7 years ago

Hi Peter,

I'll check into it.

Ben

tastybento commented 7 years ago

Hi Peter - please use autotools

cd pkg autoreconf -i configure make

Peter-Lin commented 7 years ago

/beetle-master/pkg# make make all-recursive make[1] : Entering directory '/beetle-master/pkg' Making all in src make[2] : Entering directory '/beetle-master/pkg/src' gcc -DHAVE_CONFIG_H -I. -I.. -g -02 -MT beetle.o -MD -MP -MF .deps/beetle.Tpo -c -o beetle.o beetle.c **beetle.c:49:24: fatal error: build_info.h: No such file or directory

include "build_info.h"

                                    ^ compilation terminated. Makefile:382 : recipe for target 'beetle.o' failed make[2] : ** [beetle.o] Error 1 make[2] : Leaving directory '/beetle-master/pkg/src' Makefile : 404: recipe for target 'all-recursive' failed make[1] : [all-recursive] Error 1 make[1] : Leaving directory '/beetle-master/pkg' Makefile : 324: recipe for target 'all' failed make : *** [all] Error 2

ranjitsoma13 commented 7 years ago

Hi Peter,

cd beetle/pkg/src ./make-build-info.sh cd .. make

The above instructions should help you build it.

Thanks, Ranjit

tastybento commented 7 years ago

@Peter-Lin Did this work for you? Can we close this issue? Let us know if you need help.

Peter-Lin commented 7 years ago

Could you tell me how to use this tool? thanks.

tastybento commented 7 years ago

Hi Peter - The Beetle commands are here. Beetle is used by our hub software to talk to the Bluetooth stack. It is written to talk to BlueZ. Please port it to talk to Bluedroid. Please have a look at the readme for some basic explanation of the operation.

Peter-Lin commented 7 years ago

Execute the beetle tool: usage -- beetle [options][-p ][-d][-v] -v show version info and exit -i set hci interface (example: hci0) -m {cen|per} set start up mode (central or peripheral) -p <port#> set listen port -d run in background (daemon) It's seem not same as command list.

tastybento commented 7 years ago

I apologize, I didn't understand your question. The "commands" are commands that our hub software (hubby) sends to beetle. What you list is the command line options.

There is no way for you to actually "use" the beetle tool, except to run it. It is only used by hubby. I'll talk to my engineering team tomorrow (Monday) to see what the typical command line options are and if there's anything specific you can do to confirm operation before we provide you with hubby. We are still working on getting hubby to cross compile and run on LE. We hope to get that done this week.

In regards to porting to Bluedroid, have you started that? Do you need a meeting for our engineers to go through the code with you?

tastybento commented 7 years ago

@Peter-Lin Hi Peter - although there is no interactive mode on the command line, it is possible to telnet into Beetle. @afjgeorge is putting together a document to explain how to do that so you can see it working. Please standby.

afjgeorge commented 7 years ago

@Peter-Lin Hi Peter!

Please review the two new documents posted in https://github.com/AferoCE/beetle/tree/master/docs when you get a chance. They're some simple diagnostic procedures you can use to ensure that beetle is able to communicate over BTLE. The device test doc uses one beetle instance talking to an Afero device, and the connection test doc is a more thorough test of beetle's functionality but it requires two instances of beetle on two separate hosts and exercises both hub mode and peripheral mode in the software. Please let me know if you have any questions!