diff options
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 93 |
1 files changed, 93 insertions, 0 deletions
diff --git a/README.md b/README.md new file mode 100644 index 0000000..c31809b --- /dev/null +++ b/README.md | |||
@@ -0,0 +1,93 @@ | |||
1 | meta-eca, the Yocto layer for communication appliances | ||
2 | ====================================================== | ||
3 | |||
4 | This layer's purpose is to add Embedded Connectivity Appliance (ECA) support | ||
5 | when used with Poky packagegroup base. | ||
6 | |||
7 | Please see the MAINTAINERS file for information on contacting the maintainers | ||
8 | of this layer, as well as instructions for submitting patches. | ||
9 | |||
10 | Layer Dependencies | ||
11 | ------------------ | ||
12 | |||
13 | URI: git://git.yoctoproject.org/poky | ||
14 | branch: master | ||
15 | revision: 57e8d56a6b63942b616a1e6dd894fd4ea7b409cf | ||
16 | |||
17 | URI: git://git.openembedded.org/meta-openembedded | ||
18 | branch: master | ||
19 | revision: 0f56bc4e2818a051a511ceb48596cbfa2f51ff3d | ||
20 | |||
21 | Using the above git sha's and master revisions, bitbaking eca-image is | ||
22 | known to work. Using head versions should work also just fine. | ||
23 | |||
24 | |||
25 | Build a QEMU image including ECA components | ||
26 | ------------------------------------------- | ||
27 | |||
28 | You can build a QEMU image including ECA components using the | ||
29 | following steps: | ||
30 | |||
31 | 1. Run the following command: | ||
32 | |||
33 | > $ source poky/oe-init-build-env | ||
34 | |||
35 | 2. Add meta-eca/meta-eca path to COREBASE/build/conf/bblayers.conf file. | ||
36 | |||
37 | 3. Add meta-eca/meta-eca-bsp path to COREBASE/build/conf/bblayers.conf file. | ||
38 | |||
39 | 4. Add meta-openembedded/meta-systemd path to COREBASE/build/conf/bblayers.conf | ||
40 | file. | ||
41 | |||
42 | 5. Add meta-openembedded/meta-oe path to COREBASE/build/conf/bblayers.conf file. | ||
43 | |||
44 | 6. Add meta-openembedded/meta-networking path to | ||
45 | COREBASE/build/conf/bblayers.conf file. | ||
46 | |||
47 | 7. Add meta-openembedded/meta-ruby path to COREBASE/build/conf/bblayers.conf | ||
48 | file. | ||
49 | |||
50 | 8. Set MACHINE ??= "qemux86" in COREBASE/build/conf/local.conf file to build | ||
51 | for an emulated IA-32 instruction-set machine respectively. | ||
52 | |||
53 | 9. Set DISTRO ?= "eca" in COREBASE/build/conf/local.conf file. | ||
54 | If you want a bleeding edge versions of ConnMan, oFono, Bluez5 and Neard, | ||
55 | then you can set the DISTRO to "eca-bleeding" | ||
56 | |||
57 | 10. Mask out bluez4 as we want to use bluez5, set BBMASK in your local.conf file | ||
58 | also ignore ofono recipe as ECA has own one. | ||
59 | BBMASK = "meta/recipes-connectivity/bluez/bluez4*|\ | ||
60 | meta-openembedded/meta-systemd/oe-core/recipes-connectivity/bluez/bluez4*|\ | ||
61 | meta-openembedded/meta-systemd/oe-core/recipes-connectivity/ofono/ofono*" | ||
62 | |||
63 | 11. Optional: In COREBASE/build/conf/local.conf file, you may uncomment | ||
64 | BB_NUMBER_THREADS = "4" and PARALLEL_MAKE = "-j 4" if you build on a | ||
65 | quad-core machine. | ||
66 | |||
67 | 12. Build eca-image | ||
68 | |||
69 | > $ bitbake eca-image | ||
70 | |||
71 | 13. Run the emulator: | ||
72 | |||
73 | > for qemux86: | ||
74 | > $ runqemu qemux86 eca-image | ||
75 | |||
76 | 14. Set the password for root user | ||
77 | The default password for root user is "root". You should change | ||
78 | that to something that only you know. If connecting to the host | ||
79 | using browser (use http://eca.local/ address), the web-ui | ||
80 | forces you to change the root password and it also asks you to | ||
81 | set the username/password for the web management UI. | ||
82 | If connecting to host using ssh, you need to set the root password | ||
83 | manually using "passwd" command. | ||
84 | |||
85 | 15. Connecting to the device | ||
86 | After you have booted the appliance, you can connect to it using | ||
87 | ethernet or wifi. If you have wifi card or usb dongle installed | ||
88 | in appliance, you should see access point called "eca-aabbccddeeff" | ||
89 | (this is just an example) in your wifi scans. | ||
90 | You can connect to that AP, the default passphrase in this case | ||
91 | would be "aabbccddeeff". | ||
92 | Connection can be done either via "ssh root@eca.local" or via | ||
93 | browser http://eca.local | ||