Tizen Platform Practice Part 3. Project. SKKU Embedded Software Lab.

Transcription

1 1 Tizen Platform Practice Part 3. Project

2 Contents 2 Part 1. Overview Tizen Platform & Kernel Overview Development System Overview Appendix: Tizen Source Code Management Part 2. Setting Tizen Development System Setting Tizen SD-card Setting Part 3. Project Building a Tizen Platform Project Example Tizen Projects Remote Key Framework Appendix: Hello Tizen Service Appendix: Tizen Project FAQ

3 3 Part 3-A. Building a Tizen Platform Project

4 Tizen Platform Project Build Process (1/2) 4 Assume that Tizen is running on target board Example: build and install package A

5 Tizen Platform Project Build Process (2/2) 5 1. Clone the Source Code of a Tizen Project Download source code of a Tizen project from Tizen review server. 2. Build the Tizen Project Build the source code of the project with GBS, and make package files(*.rpm). 3. Install the Packages Install the package files(*.rpm) to the target board with SDB.

6 Required Files in Repository (1/2) 6 Tizen project repository requires following files Red files are required at least. AUTHORS: Author list LICENSE: License information CMakeLists.txt: cmake configuration file about this directory s build <project-name>.manifest: SMACK manifest file packaging <project-name>.manifest: SMACK manifest file <project-name>.spec: RPM package specification file <sub-directory 1> CMakeLists.txt include Header files src Source code files <sub-directory 2>, <sub-directory 3>,

7 Required Files in Repository (2/2) 7 ex. Remote Key Framework Service Project (Link) AUTHORS: Author list LICENSE: License information CMakeLists.txt: cmake configuration file about this directory s build remote-key-framework.manifest: SMACK manifest file packaging remote-key-framework.manifest: SMACK manifest file remote-key-framework.spec: RPM package specification file remote-key-framework.service: systemd service configuration file server CMakeLists.txt include common.h: Common header file src main.cpp: Main source code common.cpp: Source code of dlog connector

8 Clone the Source Code of Tizen Project (1/2) 8 1. Log in Tizen review server (review.tizen.org) 2. Enter into Projects List 3. Find a repository that you want to clone Caution: Packages in Tizen 2.3 and 3.0 are managed in different way, so multiple packages will be displayed on the result. 4. Clone the repository 1. $ git clone ssh://username@review.tizen.org:29418/project-name

9 Clone the Source Code of Tizen Project (2/2) 9 Tizen project source code has several branches by release version. 5. Check branches 1. $ git branch --remote ex. origin/1.0_post origin/2.0alpha origin/head -> origin/master origin/master origin/tizen_2.0 origin/tizen_2.1 origin/tizen_2.2 origin/tizen_ Change branch to target release version 1. $ git checkout <target branch> ex. git checkout origin/tizen_2.3

10 Build the Tizen Project (1/3) 10 Build the most recent version in Git repository In default, GBS builds the source code of most recent version. 1. Move to the directory of repository. 2. $ gbs build -A armv7l -A <architecture type>: i586, x86_64, armv7l

11 Build the Tizen Project (2/3) 11 Build the working directory Use it in the case of building the source code in work. 1. Move to the directory of repository. 2. $ gbs build -A armv7l --include-all --include-all: option for building working directory

12 Build the Tizen Project (3/3) 12 GBS downloads dependent packages from Tizen download server on demand. ex. wrt(web Runtime) package depends on ewebkit2(webkitefl) package, so ewebkit2 is downloaded when building wrt. Other GBS Options --threads <# of threads>: the number of build threads --clean: initializes the GBS build root --exclude=<packages>: the list of packages to be excluded Build Result(Package Files; *.rpm) The name of package file is dependent on the project s RPM spec. Typically package file is named as package_name-version.arch.rpm. ex. remote-key-framework armv7l.rpm Located in: ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/

13 Install the Packages (1/2) 13 Install package files(*.rpm) on target board Send package files to target board through SDB Install the packages by RPM tool

14 Install the Packages (2/2) Connect to ODROID-U3 via USB How to check connection: $ sdb devices Caution: If you are using VMWare, check the connection of removable device 2. Enter to SDB root mode 1. $ sdb root on 3. Send package file to target board through SDB 1. $ sdb push <package file> / 4. Install the package 1. $ sdb shell rpm -ivh --nodeps --force <package file> 5. Reboot your target board 1. $ sdb shell sync; sdb shell reboot -f

15 15 Part 3-B. Example Tizen Projects More Projects:

16 Project 1: Remote Sensor Framework 16 Remote Sensor Virtualization Remote sensor를 internal sensor로가상화 Sensor Framework 수정 (Tizen 2.2) Sensor 플러그인과 sensor 서버사이에 middle layer 생성 Need to understand sensor framework Github repository:

17 Project 2: Remote Camera Framework 17 Remote Camera Virtualization Remote camera를가상화 Remote camera를연결하고제어하는 API 제공 App에서는 remote camera data( 사진 ) 를파일형태로 read 가능. Need to understand multimedia framework Github repository:

18 Project 3: App Relay 18 Seamless Cross-device Application Application의작업을 seamless 하게전달가능한 service 구현 Music player application 수정 음악재생작업을옮길수있는 seamless music player application 구현 Need to understand network framework Github repository:

19 Project 4: App Prefetch 19 Prefetch application data for fast application launch Profiling system calls in VFS Register profile results at App Info. DB AUL daemon prefetches data Need to understand application framework 19

20 Project 5: Chameleon Display 20 Change the display color according to the weather condition Get temperature and humidity information from Oduino device Develop sensor plug-in for Oduino humidity and temperature sensor Adjust display color Need to understand on UI & graphics framework 20

21 Project 6: Battery Usage Info. 21 Tizen has no service on Per-app battery usage information Profile runtime, CPU time and I/O time (storage, network) Service daemon collects power consumption information from system server, devman(device manager) and power manager Need to understand the interface between platform and kernel (device manager service, HAL, etc.) 21

22 22 Part 3-C. Remote Key Framework

23 Prerequisites Install Tizen development environment. Already covered in 1st day 1. Install git, repo, gbs and mic. 2. Register Tizen developer ID. 3. Do review server configuration. 4. Make GBS configuration file. (~/.gbs.conf) 2. Kernel source code Required for building virtual key kernel module 3. Resolve troubles of Tizen on ODROID-U3. Already covered in last week

24 Motivation 24 No home key, back key and menu key in ODROID- U3 & ODROID-VU.?

25 Concept 25 A framework to control Tizen device through remote Android smartphones.

26 Requirements 26 Wireless connection between Android device and Tizen device Bluetooth and RFCOMM protocols Bluetooth frameworks in Tizen and Android Virtual key input event on Tizen device Virtual input device driver is required Background process Register a Tizen service on Systemd

27 Design 27 Virtual Input Device Driver (Kernel Module) If a command come from service, it creates an input event. Server Service (Tizen Framework Service) Connection with Android device via Bluetooth Client (Android Application) UI and connection with Tizen device via Bluetooth Android Phone Client Application Framework Bluetooth/ RFCOMM Message ODROID-U3 (Tizen) Applications Framework Server Service X11 & EFL Kernel Kernel Virtual Input Device Driver evdev

28 Download Source Code Download Source Code 아래사이트에들어가서 Download ZIP 으로소스코드다운로드 VM 으로복사 압축풀기 ervice 3. ient

29 Virtual Input Device Driver 29 Host driver Connected to evdev(event device driver) In this project, make a new host driver for making virtual key events. evdev Sends events to udev udev Sends device events to xinput xinput (in X server) Sends events to X clients

30 Virtual Input Device Driver 30 Receive commands from Server Service Make key input events via evdev Those events will be delivered to apps. virtual input device driver evdev xinput(in X server) EFL Application Android Phone Client Application Framework Bluetooth/ RFCOMM Message ODROID-U3 (Tizen) Applications Framework Server Service X11 & EFL Kernel Kernel Virtual Input Device Driver evdev

31 Virtual Input Device Driver: Order Initialize device driver homekey_init() Register input device on evdev sysfs 에 entry 등록 (/sys/bus/platform/devices/homekey/coordinates) 2. Handling sysfs entry events Server service 가 sysfs entry file 에대한 write command 수행 sysfs entry file 에대한 write command 가 device driver 의 homekey_click() 함수호출

32 Virtual Input Device Driver 32 Source Code 원본위치 Source Code Files virtual_homekey.c Main source code load-virtual-homekey.service Systemd service description file Makefile Makefile for building kernel module build.sh Build Script Xmodmap Xinput keymap file

33 Virtual Input Device Driver 33 Edit virtual_homekey.c $ cd virtual_inputdevice $ gedit virtual_homekey.c static ssize_t homekey_click() Make an input event static struct attribute *homekey_attrs[] sysfs attribute entry (/sys/bus/platform/devices/homekey/coordinates) static struct attribute_group homekey_attr_group sysfs group entry (/sys/bus/platform/devices/homekey/) static int init homekey_init() Initialize device driver static void exit homekey_exit() Unregister the input device and remove sysfs entry

34 virtual_homekey.c 34 homekey_init() Initialize device driver Register a platform device Register a sysfs entry Allocate an input device data structure Set an keymap entry Register an input device to evdev

35 virtual_homekey.c 35 coordinate entry file registered on sysfs calls homekey_click() function /sys/bus/platform/devices/homekey/coordinates /sys/bus/platform/devices/homekey

36 virtual_homekey.c 36 homekey_click() Make and synchronize an input event 남는 keycode 값을담은 input event을발생시킴 KEY_XFER, KEY_PROG1, KEY_PROG2 Make an virtual input event Synchronize the input event

37 virtual_homekey.c 37 homekey_exit() Unregister the input device and remove sysfs entry Unregister the input device from evdev Unregister the platform device Remove the homekey entry from sysfs Set module init & exit functions

38 Virtual Input Device Driver 38 Makefile Build kernel module Build Input cross compiler & kernel path $./build.sh Kernel path Cross compiler path

39 Virtual Input Device Driver 39 Install At first, connect your ODROID target to host PC. Ensure SDB connection $ sdb devices Turn on root mode $ sdb root on Push kernel module & service file $ sdb push virtual_homekey.ko /data/ $ sdb push load-virtual-homekey.service /usr/lib/systemd/system

40 Virtual Input Device Driver 40 Install (Cont d) Make load-virtual-homekey service run on boot $ sdb shell ln -s /usr/lib/systemd/system/load-virtualhomekey.service /usr/lib/systemd/system/graphical.target.wants/ Reboot ODROID target $ sync $ reboot -f

41 Xmodmap (1/5) 41 Xmodmap Kernel input event X input event map 설정하는유틸리티 Virtual input event 와 Tizen 의 home, back, menu key 와연결시필요 Tizen 의 x11-xserver-utils 프로젝트에포함되어있으나, 2.3 부터는기본적으로빌드되지않도록바뀜 1. x11-xserver-utils 다운로드 1. $ git clone xserver-utils

42 Xmodmap (2/5) Xmodmap 를빌드대상에포함하도록변경 1. $ cd x11-xserver-utils 2. $ vi packaging/xorg-x11-xserver-utils.spec 빨간색글씨부분추가 # Line 45 %define DEF_SUBDIRS xkill xrandr xrdb xset xmodmap # Line 139 %{_libdir}/systemd/user/core-efl.target.wants/xrdb.service %{_bindir}/xmodmap

43 Xmodmap (3/5) 빌드및설치 1. $ gbs build -A armv7l --include-all 2. $ cd ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/ 3. $ sdb push xorg-x11-server-utils armv7l.rpm / 4. $ sdb shell rpm -ivh --nodeps --force /xorg-x11-server-utils armv7l.rpm

44 Xmodmap (4/5) 44 Configuration file Virtual input event 와 Tizen 의 home, back, menu key 와연결 KEY_XFER(=155) home key(xf86send) KEY_PROG1(=156) back key(xf86phone) KEY_PROG2 (=157) menu key(xf86stop)

45 Xmodmap (5/5) Install configuration file 1. $ sdb root on 2. $ sdb push./xmodmap /etc/x11/xmodmap 3. $ sdb shell sync 5. Reboot target device 1. $ sdb reboot -f

46 Virtual Key Event Test 46 SDB 내에서아래명령을실행하면키동작이일어남 Menu key $ echo 1 > /sys/bus/platform/devices/homekey/coordinates Home key $ echo 11 > /sys/bus/platform/devices/homekey/coordinates Back key $ echo 111 > /sys/bus/platform/devices/homekey/coordinates

47 Server Service 47 Source Code 원본위치 Source Code Files CMakeLists.txt: cmake configuration file about this directory s build packaging remote-key-framework.spec: RPM package specification file remote-key-framework.service: systemd service description file server CMakeLists.txt: cmake configuration file about this directory s build include src main.cpp: Main source code

48 Server Service 48 Android phone 의 client app 으로부터 Bluetooth 메시지전송받음 Bluetooth 연결유지역할도담당해야함 Virtual input device driver 의 sysfs entry file 에명령을내림 Android Phone Client Application Framework Bluetooth/ RFCOMM Message ODROID-U3 (Tizen) Applications Framework Server Service X11 & EFL Kernel Kernel Virtual Input Device Driver evdev

49 Server Service: 작동순서 Initialization rkf_initialize_bluetooth() Bluetooth 장치를초기화하고 event handler 설정 2. Listening Connection rkf_listen_connection() & rkf_finalize_bluetooth() target device 가 Bluetooth 로연결되기를기다림 3. Handling Bluetooth Events Glib main loop 이동작하며 Bluetooth event 받음 Received data event, Socket connection status changed event, Bluetooth State changed event,

50 Server Service 50 server/src/main.cpp Main source code of the service Glib event loop handles Bluetooth events rkf_initialize_bluetooth() Initialize Bluetooth adapter and set event handlers rkf_finalize_bluetooth_socket() & rkf_finalize_bluetooth() Cleanup Bluetooth connection rkf_listen_connection() Wait until target device is connected through Bluetooth Handles Bluetooth events rkf_received_data_cb() rkf_socket_connection_state_changed_cb() rkf_state_changed_cb() timeout_func_cb() main() Main function, calls initialization routine and event loop

51 server/src/main.cpp 51 main() Calls initialization routine and event loop Initialize glib main loop Initialize Bluetooth adapter and set event handlers Wait until target device is connected through Bluetooth After connection is done, enter the Glib main loop. It will receive and handle Bluetooth events Cleanup Bluetooth connection

52 server/src/main.cpp 52 rkf_initialize_bluetooth() Initialize Bluetooth adapter and set event handlers Initialize Bluetooth adapter Get Bluetooth adapter state Ensure Bluetooth device is enabled If Bluetooth device is disabled, issue enable Bluetooth command. Then, wait until Bluetooth is enabled or timeout is expired.

53 server/src/main.cpp 53 rkf_initialize_bluetooth() (Cont d) Initialize Bluetooth adapter and set event handlers Set Bluetooth device visible always by other Bluetooth devices

54 server/src/main.cpp 54 rkf_initialize_bluetooth() (Cont d) Initialize Bluetooth adapter and set event handlers Create Bluetooth/RFCOMM socket and get its file descriptor Register Bluetooth event handlers Connection state changed event Socket data received event

55 server/src/main.cpp 55 rkf_listen_connection() Wait until target device is connected through Bluetooth

56 server/src/main.cpp 56 rkf_received_data_cb() Handler of socket data received event Received message: menu, home, back Make an input event by sysfs entry /sys/bus/platform/devices/homekey/coordinates

57 server/src/main.cpp 57 rkf_connection_state_changed_cb() Handler of Bluetooth connection state changed event If Bluetooth connection is disconnected, it exits Glib main loop

58 server/src/main.cpp 58 rkf_state_changed_cb() Handler of Bluetooth adapter state changed event This handler is registered only if Bluetooth adapter is disabled. If Bluetooth adapter becomes enabled, stop waiting this event anymore.

59 server/src/main.cpp 59 rkf_finalize_bluetooth_socket() & rkf_finalize_bluetooth() Cleanup Bluetooth socket and adapter

60 Server Service 60 Build Requisites packaging/remote-key-framework.spec CMakeLists.txt packaging/cmakelists.txt Build Order 1. gbs build: build and make rpm package as specified in *.spec 2. cmake: make Makefile as specified in CMakeLists.txt 3. make: build project as specified in Makefile

61 packaging/remote-key-framework.spec 61 Systemd service description file Basic descriptions of the package List of required packages

62 packaging/remote-key-framework.spec 62 Systemd service description file (Cont d) When gbs build command is issued, %prep, %build, %install, %post scripts will run in order

63 packaging/remote-key-framework.spec 63 Systemd service description file (Cont d) RPM package includes file list in %files Service binary file /usr/bin/rkf_server Systemd service description files /usr/lib/systemd/system/remote-key-framework.service /usr/lib/systemd/system/graphical.target.wants/remote-keyframework.service License description file /usr/share/license/remote-key-framework

64 Server Service 64 CMakeLists.txt Cmake configuration file about root directory s build Set sub-directories to be built Environment value will be used by CMakeLists.txt in subdirectory. PREFIX, EXEC_PREFIX, LIBDIR, INCLUDEDIR,

65 Server Service 65 server/cmakelists.txt Cmake configuration file about this directory s build List of Packages to be used by linker Set compiler flags for additional packages Set directories of headers to be included Set source codes Set loader flags Set compiler flags and make binary

66 Server Service 66 packaging/remote-key-framework.service Systemd service description file After: units that should run before this service Command to be executed Restart if the service is terminated in 1 second This unit will be executed at graphical.target stage in boot time

67 Server Service: Build 사전작업 67 Github 에서 zip 으로다운로드했기때문에, git repository 를먼저초기화해야함 1. $ git init 2. $ git add --all 3. $ git commit -m Initial commit

68 Server Service: Build 68 Build *.spec file is required for gbs build Build the working directory $ gbs build -A armv7l --include-all Build the most recent version in Git repository $ gbs build -A armv7l

69 Server Service: Install 69 Install the package Package files are located in: ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/ Send package files to target board through SDB Install the packages by RPM tool

70 Server Service: Install Connect to ODROID-U3 via USB How to check connection: $ sdb devices Caution: If you are using VMWare, check the connection of removable device 2. Enter to SDB root mode $ sdb root on 3. Send package file to target board through SDB $ cd ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/ $ sdb push remote-key-framework armv7l.rpm / 4. Install the package $ sdb shell rpm -ivh --nodeps --force remote-key-framework armv7l.rpm 5. Reboot your target board $ adb shell sync; sdb shell reboot -f

71 Bluetooth Pairing 71 Tizen 과 Android 간 Bluetooth 연결 Android phone 검색을허용 해당 phone 과 bluetooth 연결 Android mobile Tizen Odroid-U3

72 Client 72 Tizen 장치에키입력명령을내리는 Android App 소스코드도제공됨 설치하기 1. 설정앱 보안 알수없는소스 체크 2. client/android-client/bin/remotekeyclient.apk 를 Android 장치에넣어서설치

73 Client 73 화면구성 Control Buttons (Device 목록갱신, Bluetooth ON/OFF) Bluetooth 로 Pairing 된 Device 목록 ( 미리 설정 앱에서대상장치와 Bluetooth Pairing 이끝나있어야함 ) Key Buttons (Menu key, Home key, Back key)

74 사용하기 ODROID와 Bluetooth Pairing 2. Client Application 실행 3. Update 버튼클릭 4. 목록에서대상 device 선택 5. 키입력가능

75 75 Appendix: Hello Tizen Service

76 Appendix: Hello Tizen Service 76 Minimum code of Tizen service Glib event loop for service lifecycle Timeout event occurs in one minute after startup Other events can be added for other purposes Service is launched on startup

77 Appendix: Required Files in Repository 77 Tizen project repository requires following files Red files are required at least. AUTHORS: Author list LICENSE: License information CMakeLists.txt: cmake configuration file about this directory s build <project-name>.manifest: SMACK manifest file packaging <project-name>.manifest: SMACK manifest file <project-name>.spec: RPM package specification file <sub-directory 1> CMakeLists.txt include Header files src Source code files <sub-directory 2>, <sub-directory 3>,

78 Appendix: Download Service 78 Download Source Code from Github(Link) $ git clone AUTHORS: Author list LICENSE: License information CMakeLists.txt: cmake configuration file about this directory s build hello-tizen-service.manifest: SMACK manifest file packaging hello-tizen-service.manifest: SMACK manifest file hello-tizen-service.spec: RPM package specification file hello-tizen-service.service: systemd service configuration file server CMakeLists.txt include common.h: Common header file src main.cpp: Main source code common.cpp: Source code of dlog connector

79 Appendix: Build Service Package 79 Build *.spec file is required for gbs build Build the working directory $ gbs build -A armv7l --include-all Build the most recent version in Git repository $ gbs build -A armv7l

80 Appendix: Install Service Package 80 Install the package Package files are located in: ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/ Send package files to target board through SDB Install the packages by RPM tool

81 Appendix: Install Service Package Connect to ODROID-U3 via USB How to check connection: $ sdb devices Caution: If you are using VMWare, check the connection of removable device 2. Enter to SDB root mode $ sdb root on 3. Send package file to target board through SDB $ cd ~/GBS-ROOT/local/repos/tizen2.3/armv7l/RPMS/ $ sdb push hello-tizen-service armv7l.rpm / 4. Install the package $ sdb shell rpm -ivh --nodeps --force hello-tizen-service armv7l.rpm 5. Reboot your target board $ adb shell sync; sdb shell reboot -f

82 82 Appendix: Tizen Project FAQ

83 Appendix: Locale error in build phase 83 Problem GBS can run on only English Ubuntu. If you use Ubuntu in other language, GBS could not be work. Solution Run below commands before run GBS. $ export LANGUAGE=en_US.UTF-8 $ export LANG=en_US.UTF-8 $ export LC_ALL=en_US.UTF-8 $ locale-gen en_us.utf-8 $ dpkg-reconfigure locales

84 Appendix: GBS Trouble-shooting (1/2) 84 When build error is occured, refer to the error log. Example info: *** Build Status Summary *** === the following packages failed to build due to rpmbuild issue (1) === xf86-video-exynos: /home/user/gbs- ROOT/local/repos/tizen2.3/armv7l/logs/fail/xf86-video-exynos /log.txt You can find the problem on the error log. /home/user/gbs-root/local/repos/tizen2.3/armv7l/ logs/fail/xf86-video-exynos /log.txt [ 139s] error: db4 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch [ 139s] error: cannot open Packages index using db4 - (-30971) [ 139s] error: cannot open Packages database in /var/lib/rpm [ 139s] error: db4 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch [ 139s] error: cannot open Packages database in /var/lib/rpm

85 Appendix: GBS Trouble-shooting (2/2) RPM DB4 error /home/user/gbs-root/local/repos/tizen2.3/armv7l/ logs/fail/xf86-video-exynos /log.txt [ 139s] error: db4 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch [ 139s] error: cannot open Packages index using db4 - (-30971) [ 139s] error: cannot open Packages database in /var/lib/rpm [ 139s] error: db4 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch [ 139s] error: cannot open Packages database in /var/lib/rpm Problem: temporary files in BUILD-ROOT are in conflict each other. Solution: Add --clean flag on GBS. gbs build -A armv7l --include-all --clean build.sh