Quickstart. with F&S Development Machine Fedora 23. Version 1.2 ( )

Transcription

1 Quickstart with F&S Development Machine Fedora 23 Version 1.2 ( ) F&S Elektronik Systeme GmbH Untere Waldplätze 23 D Stuttgart Germany Phone: +49(0) Fax: +49(0)

2 Table of Contents 1 Welcome 1 2 Import the Appliance 2 3 Using the Virtual Machine U-Boot Login Directory Structure TFTP Server NFS Server Keyboard Layout Guest Addition Compile in just 3 steps Buildroot, Kernel, Device Tree U-Boot... 8 Qt Development Introduction Create a Root File System SSH Settings in Qt Creator Running the Application Debugging Demo Application U-Boot Settings...13 Appendix 14 List of Figures...14 List of Tables...14 Listings Important Notice...15

3 Welcome 1 Welcome Hello and Welcome to F&S Development Machine Fedora 23! What s it all about? F&S Development Machine Fedora 23 is a VirtualBox Appliance based on Fedora 23 provided by F&S. It contains the installed Board Support Packages for fsimx6, fsimx6sx and fsimx6ul. The F&S toolchain is installed, the source code is extracted and ready to run. System packages that are needed are installed too. Besides that it contains a configured environment for Qt Development. Qt Creator is installed with a cross-compile/debug kit using the F&S toolchain and a configured deployment strategy. Why should I use it? Because it saves time. A lot of configuration is already done. Compilation has been tested and is working out of the box. Missing packages are installed etc.. Just a few points that belong to your decision can t be done beforehand. For example if you want to have your favorite IDE. By default Qt Creator, vim, emacs, and gedit are preinstalled. Besides that we try to keep the image as small as possible. When should I not use it? There are just two cases not to use this virtual machine. First when you are going for a native development machine. Second when you absolutely want to go with your favorite distribution and it s not Fedora. 1

4 Import the Appliance 2 Import the Appliance Let s import our new virtual machine. If you haven t downloaded yet log in at our website and download F_S Development Machine - Fedora 23 V1.2.ova. Open your VirtualBox Manager and click: File Import Appliance Figure 1: Import the Appliance Select your downloaded F_S Development Machine - Fedora 23 V1.2.ova file in the dialog and click next. 2

5 Import the Appliance Figure 2: Choose the *.ova file When you have done this you can see all the details of the virtual machine like name, version and the hardware configuration. First check if the hardware settings for CPU and RAM correspond to your needs and to the performance of your host machine. Second you can adjust the name if you have imported an appliance with this name before or if you want to use another name. 3

6 Import the Appliance Figure 3: Adjust appliance settings Now there is nothing left except for clicking on Import. Depending on your machine it will take about 10 minutes. 4

7 Using the Virtual Machine 3 Using the Virtual Machine 3.1 U-Boot After importing start your virtual machine by selecting it on the left and clicking on Show. Figure 4: Boot your VM 3.2 Login After boot you will be asked for the login. Use the user developer and log in with password developer. Figure 5: Login in with password developer 5

8 Using the Virtual Machine 3.3 Directory Structure The fsimx6, fsimx6sx and fsimx6ul releases are located in the home directory of developer. There you will find, documentation, binaries, source code etc.. The source code is extracted to a folder called build. Links to the releases are on the desktop too. If you want to build a root file system on imx6 go to /home/developer/fsimx6v3.0/build/buildroot fsimx6-v3.0. The kernel should also be build from this directory via Buildroot not in the separate linux directory. Handling of kernel modules is much easier when compiling via Buildroot. In the home directory there is a folder buildroot_dl_packages. All packages downloaded by Buildroot are stored there. When providing the virtual machine all packages that are needed for the default configuration have been downloaded already. 6

9 Using the Virtual Machine 3.4 TFTP Server There is a TFTP Server that starts automatically when booting. Simply lay your files in the /tftpboot/ folder. 3.5 NFS Server An NFS Server is starting automatically when booting. It uses the directories /download and /rootfs. You can put your files there or mount a root file system image as loop back device. Please consult the First Steps manual for detailed information. 3.6 Keyboard Layout You can change your keyboard layout in the top panel on the right. By default it says en here. 3.7 Guest Addition The Guest Addition is already installed on the virtual machine. Features like shared folder or a shared clipboard can be activated in the settings when the virtual machine is not running. 3.8 Compile in just 3 steps What about compiling a kernel and root file system or U-Boot for your module in just 3 steps? Here is how it is done: Buildroot, Kernel, Device Tree 1. Open a terminal by clicking the terminal icon in the top panel. 2. Change directory to the Buildroot directory for your desired processor architecture. E.g. for imx6ul we type: cd fsimx6ul-v2.0/build/buildroot fsimx6ul-v2.0/ 3. Now we will create a.config (e.g. standard defconfig) and start the compilation. The steps in brackets are optional: make fsimx6ul_std_defconfig (make menuconfig) (make linux-menuconfig) make //apply standard defconfig for fsimx6ul //customize Buildroot configuration //customize kernel configuration //build 7

10 Using the Virtual Machine U-Boot 1. Open a terminal by clicking the terminal icon in the top panel. 2. Change directory to the U-Boot directory for your desired processor architecture. E.g for imx6ul we type: cd fsimx6ul-v2.0/build/u-boot fsimx6ul-v2.0/ 3. Now we will create a.config and start the compilation: make fsimx6ul_config make 8 //apply config for fsimx6ul //build

11 Qt Development 4 Qt Development 4.1 Introduction The virtual machine comes with a preconfigured Qt Creator environment. First you ll find a cross-compile/debug kit based on the F&S toolchain. It is called FS Cross Compile Kit for ARM. Second there is a project with a small demo application called QT_Test_App using the preconfigured environment. Nevertheless a few things have to be configured: A root file system prepared for debugging configuration on that root file system Paths and addresses in Qt Creator The Explanation in this chapter is more general. If there are some basics that are not faced here and are not clear please have a look at the First Steps documentation. 4.2 Create a Root File System At the moment there is just a qt5_defconfig for fsimx6. This will change in the next release. To give you an idea our qt5_defconfig contains lots of qt5 packages and no XServer. This is important because Qt doesn t like to have an XServer next to it. For remote debugging a few additional packages need to be activated: Target packages -> Development Tools -> ctest (activates cmake) Target packages -> Interpreter languages and scripting -> python Target packages -> Debugging, profiling and benchmark > gdb -> full debugger Target packages -> Debugging, profiling and benchmark > gdb -> Python support (Toolchain -> Build Cross gdb for the host -> Python support After that we have to reconfigure the host-gdb package to face the python changes: make host-gdb-reconfigure Otherwise it will say, that no python support is available. After compiling we can write the rootfs image to the module. 9

12 Qt Development 4.3 SSH SSH is needed for deployment and remote debugging. In this example we will setup ssh with a simple configuration using the root user. Make sure that the date is set correctly on your module otherwise we will get trouble with certificates (e.g type: date " :50"). Here is what we do: udhcpc (e.g. got ) mount -o remount,rw / passwd (set password root for user root) vi /etc/ssh/sshd_config Port 22 AdressFamily any ListenAddress PermitRootLogin yes A more detailed explanation: Fetch an ip address. Mount the root partition read/write able. That is important for deployment later on too. Set a root password. In Qt Creator it has been set to root. In the next step edit sshd_config e.g. with vi. The settings written below the vi command must be activated (no # at the beginning of the ine) or initially written by yourself. Now we can start the server: /etc/init.d/s50sshd start And test it from the computer with: ssh root@ Settings in Qt Creator Start Qt Creator and open QT_Test_App. This project was configured for fsimx6 platform so we need to correct some paths. Additionally we need to check network settings and ssh connection. First make sure that you have already build your root file system because it contains tools we need. Click on Tools Options On the left there is a tab called Devices. The configured device represents the F&S module. Check the connection settings e.g. IP address and user name / password that will be used for the SSH connection. With click on Test Qt Creator will try to establish an ssh connection. It must show: Connecting to host... Checking kernel version... Linux F+S armv7l 10

13 Qt Development Checking if specified ports are available... All specified ports are available. Device test finished successfully. Now click on Build & Run on the left. Go through the tabs Cmake, Debuggers, Qt Versions and Kit. In every tab we need to check and maybe adjust the paths of the manually added tools. Mostly they are labeled with...for ARM. The targets of the paths must exist (root file system was build) and point to the correct platform. It can happen that you open the QT_Test_App project the first time and it shows an error: Figure 6: First start of QT_Test_App This is the case when the root file system hasn t been build. The project expects an available qmake tool as the project file says but can t find it. Close Qt Creator, build a root file system and open the project again. 11

14 Qt Development 4.5 Running the Application After these steps we can run the application. The following steps should happen: The application compiles It is copied due to the custom deployment strategy to /tftpboot/ Qt Creator starts an ssh connection and downloads the binary via TFTP to the board. The QT_Test_App will be started on the module. It shows an empty window on a connected display. 4.6 Debugging By clicking on the debugging symbol Qt Creator starts a gdbserver on the module via ssh and establishes a connection. Figure 7: Debugging with Qt Creator 4.7 Demo Application If you want to create your own application later on there is one important detail. Qt Creator must know that it should deploy a binary to the module and where it should be deployed. Therefore you need to tell this in the Qt Creator Project file (*.pro). The following lines had been added in the *.pro file for QT_Test_App: linux-* { target.path = /root INSTALLS += target } 12

15 Qt Development 4.8 U-Boot Settings To keep the configuration effort small after a reboot settings like static IP address or an rw mount of the root file system can be set in U-Boot. 13

16 Appendix 5 Appendix List of Figures Figure 1: Import the Appliance...2 Figure 2: Choose the *.ova file...3 Figure 3: Adjust appliance settings...4 Figure 4: Boot your VM... 5 Figure 5: Login in with password developer...5 Figure 6: First start of QT_Test_App...11 Figure 7: Debugging with Qt Creator...12 List of Tables Listings 14

17 Appendix Important Notice The information in this publication has been carefully checked and is believed to be entirely accurate at the time of publication. F&S Elektronik Systeme assumes no responsibility, however, for possible errors or omissions, or for any consequences resulting from the use of the information contained in this documentation. F&S Elektronik Systeme reserves the right to make changes in its products or product specifications or product documentation with the intent to improve function or design at any time and without notice and is not required to update this documentation to reflect such changes. F&S Elektronik Systeme makes no warranty or guarantee regarding the suitability of its products for any particular purpose, nor does F&S Elektronik Systeme assume any liability arising out of the documentation or use of any product and specifically disclaims any and all liability, including without limitation any consequential or incidental damages. Products are not designed, intended, or authorised for use as components in systems intended for applications intended to support or sustain life, or for any other application in which the failure of the product from F&S Elektronik Systeme could create a situation where personal injury or death may occur. Should the Buyer purchase or use a F&S Elektronik Systeme product for any such unintended or unauthorised application, the Buyer shall indemnify and hold F&S Elektronik Systeme and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, expenses, and reasonable attorney fees arising out of, either directly or indirectly, any claim of personal injury or death that may be associated with such unintended or unauthorised use, even if such claim alleges that F&S Elektronik Systeme was negligent regarding the design or manufacture of said product. 15