LinX Software Suite v3 Getting Started

Transcription

1 LinX Software Suite v3 Getting Started Product revision: V3.0.2 Document revision: 1.0

2 Contents Revision history Brief Introduction Components and Installation Virtual Box Virtual Development Machine Set-up of the virtual machine Inside the Development Environment Basic Information User and Password Applications and files provided in the virtual machine Creating the first Qt application on CCP VS Create an empty project Connecting to a CCpilot VS Troubleshooting tips if you can t connect Deploy and run on an CCpilot VS Autostart settings on CCpilot device Modify startup scripts Change order of startup Further reading Appendix: Installing LinX Base runtime on CCP VS & VI Download the LinX Base runtime from VM Download an updated LinX Base runtime to your display Revision history P.Görling First Version (VM v3.0) P.Görling First Version (VM v3.0) Glossary Word/Abrevation CrossTecc crc SAP Qt RTE API VDM VM GUI Explanation A set of applications and components... Cyclic redundancy check Software Application Platform Development framework qt.digia.com RunTime Environment Application Programming Interface Virtual Development Machine Virtual Machine Graphical User Interface 2

3 1. Brief Introduction The LinX Software Suite Development Environment is a development tool chain running under Linux running within a virtual machine. This guide provides a guide for installing the virtual machine and getting a first QtQuick application running on a CCpilot device. This guide is based on LinX Software Suite Development Environment v3.0.2 or later. 2. Components and Installation 2.1. Virtual Box In order to be able to execute the virtual machine, the application Virtual Box version 5.0 or higher has to be installed on your local computer 1. Virtual Box is available at: Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and is licensed as Open Source under the GNU General Public License V2 ( 2.0.html). The full documentation about Virtual Box is available online at Please refer to the extensive official troubleshooting guide or our knowledge base if you have trouble when installing or running Virtual Box. For more user info about Virtual Box and how to do interesting things with Virtual Box, see: Virtual Development Machine The virtual development machine (VDM) called LinX Software Suite Development Environment can be downloaded from the download section at: (you need to register on the site in order to access the downloads) Be sure to select the link LinX Software Suite Development Environment v3.0 1 The previous versions of the CrossControl virtual development environments used the VMWare Player which was depreciated with this version. However, if you want to continue to use the older versions of the virtual machines, you need to use VMWare, as the Virtual Box software is not able to run those older environments. 3

4 The picture below shows the download page on the support site. Figure 1: CrossControl support site LinX SW The complete virtual machine is about 14 GB large. Therefore it will be downloaded as a split Zipfile consisting of many smaller files (7-Zip is needed) Set-up of the virtual machine Start the Virtual Box application: Figure 2: Virtual Box GUI 4

5 Under the Machine menu press on Add and open the file LinX Software Suite Development Environment v3.0.x from the VDM archive. The GUI should look like this: Figure 3: Virtual Box with Virtual Development Machine loaded Note: It is possible to have more than one VDM available in Virtual Box. The drawback is that every installed VDM version takes up a lot of the memory on your PC. Review the settings for the VDM and adapt them to your needs. Especially, review the network tab and make sure you get the correct settings for your network. Below is the settings used within CrossControl. Figure 4: Virtual Box with Virtual Development Machine loaded If there are many users of the VM on the same network, it could be wise to generate a new MAC address for your installation of the VM 5

6 Press on to boot up the virtual machine. During the first boot up, you may have to read and accept the software license in order to use the LinX Software Suite Development Environment. 6

7 3. Inside the Development Environment When booting up the development environment you first need to login: Figure 5: Virtual Box startup screen User: Password: ccs default After the login you get to the standard Linux desktop: Figure 6: Development environment desktop 3.1. Basic Information The virtual machine is running a standard Lubuntu You can use all the standard features of Lubuntu, there are no limitations from CrossControl to this environment. You can get further help about lubuntu at: 7

8 Sooner or later you will need to use the Linux shell through a terminal window. Open it by clicking on the button in the lower left corner and select System Tools LXTerminal : Figure 7: Select the Terminal icon Or use the keyboard combination (shortcut): Ctrl + ALT + T A guide for using the shell can be found at wikibooks.org. You can change the keyboard layout by right-clicking on the panel frame and then selecting: Add/Remove Panel Items Panel frame Figure 8: Select Panel Preferences In the popup window, press + Add and select Keyboard Layout Handler and press + Add.. Figure 9: Select Panel Preferences 8

9 Right-click on the language-switch button in the lower right corner of the screen and select Keyboard settings... : Figure 10: Select Panel Preferences 3.2. User and Password In the virtual machine you will login with the default user account ccs. This account is the default root account (used for sudo access) User: ccs Password: default 3.3. Applications and files provided in the virtual machine Open your personal Home folder by clicking the button File Manager PCManFM in the start menu: Figure 11: Places menu Inside your Home folder, you can find a folder qt which contains a folder MyProjects which is the default location for new development projects Pre-installed applications Qt Framework and Qt Creator DataEngine Pre-Installed files and resources The folder /opt contains further resources for development and deployment and other additional files: /opt/bin: pre-compiled SAP binaries /opt/vs and /opt/vi2: contains all binaries compiled for the VS/VI2 ARM platform /opt/mtcc/db: Firebird database storage folder 9

10 /opt/mtcc/images: Image resources for Qt components and widgets /opt/mtcc/include: all include files for compiling Qt applications /opt/mtcc/symbols: vector based, partly ISO-conform symbols /opt/packages: /opt/qt-5.7.1: /opt/vboxguestadditions : /opt/vi2: contains all binaries compiled for the VI2 ARM platform /opt/vs: contains all binaries compiled for the VS ARM platform 10

11 4. Creating the first Qt application on CCP VS In this chapter you can find a step-by-step guide for creating a simple Qt-application and download and run it on a CCpilot VS Create an empty project Start the Qt Creator by either double-clicking the Qt Creator icon on the desktop. Figure 12: Qt Creator icon on desktop After the Qt Creator has started, press on the button Projects from the File menu. (You can also press either Ctrl-N to shortcut to the New File or Project dialog.) Figure 13: QtCreator welcome dialog 11

12 In the appearing dialog, choose New Project, if you want start with an empty project, or Open Project, if you want to continue working in an existing project. Figure 14: QtCreator projects dialog In this section we choose New Project and in the appearing dialog, we choose CrossControl Project on the left side and QtQuick2 in the right list. Figure 15: New Project dialogue Press Choose..., and enter a name for the project in the next dialog and check that the folder: /home/ccs/qt/myprojects Or change the location to where you want to store your Qt application projects. 12

13 Then press on Next > to continue. On the next page, you can select the target s screen resolution and screen orientation. The CCpilot VI2 has 320x240 pixel displays; the CCpilot VS has 1280x800 pixel displays. Figure 16: Application Information The screen resolution for CCP VS should be set to: 1280x800 The orientation of the screen has four options: - Default - 90 Clockwise - Upside down - 90 Counter-clockwise Then press on Next > to continue. The next window will present you with all the Kits available in the virtual machine. They contain pre-configured settings for the different platforms. As we are going to run a Qt5-application on a CCpilot VS, choose both the CCpilot ARM (VS) Qt and the Virtual Development Qt and press Next > and then Finish. Figure 17: Kit Selection 13

14 A project will be created with a few lines of QML-code: Figure 18: Template project We are using a generic template for both Qt 5.6 and 5.7.1, depending on the selected build-kit. There are some differences between the kits, but the project will use the correct build-kit. You can update the project-file (.pro) and remove the reference to the kit that s not used. You can directly execute the application in the Virtual Machine. Click on the Kit -button in the bottom left corner of your screen and select Virtual Development Qt Figure 19: Kit selection shortcut Press on Run in the Build -menu, F5 or Ctrl-R: Figure 20: Run command 14

15 Or press on the green Run -Arrow in the lower left corner to start the application. The application will compile and start up, looking like this: Figure 21: Template project running in virtual machine Congratulations, you have just created your first QtQuick / QML application! Press the Exit button to return to QtCreator Connecting to a CCpilot VS Be sure to have the CCpilot connected to both power and an Ethernet port which is accessible from your PC (the CCpilot uses DHCP by default, connecting the CCpilot to your PC directly will not work). The Standard GUI on the CCpilot will show its IP-Address in the lower right corner: Figure 22: IP address showing on the CCpilot Startup Launcher GUI 15

16 To open the options menu in QtCreator, choose Tools Options from the menu bar: Figure 23: Options menu item To set up the IP-address of your unit, click on Devices in the left column, and choose the CCpilot ARM Device in the drop-down field at the top of the window. Enter the IP address of your unit in the Host name field: Figure 24: Devices window of the QtCreator 16

17 Press on the Test button on the right side to the test connection: Figure 25: SSH connection test Close the window by pressing Ok 4.3. Troubleshooting tips if you can t connect 1. Make sure that you can connect from Windows to your CCpilot by opening the start menu and run the command cmd (just press the windows-key and enter the letters c m d and press enter): Figure 26: Windows run window This should bring up a console window. Enter the command ping and the ip-address of the CCpilot and press enter. The output should look like this: Figure 27: Ping in the Windows console window If not, check the Ethernet connection between your PC and the CCpilot. Ask your local IT support for help if not sure how to do this. 2. If you can connect to the CCpilot from windows, check if you can access it from a console window in the virtual machine by opening a console and entering the same ping command as above (press Ctrl-C to cancel): Figure 28: Ping in the Linux console window If this does not work, check the Ethernet configuration of the virtual machine. Refer to the Virtual Box manual for further help. 3. Make sure you have activated the network connection from the virtual machine. If the network symbol looks like in the picture below. Click on it and activate it. Figure 29: If you see this symbol, click it and activate network 17

18 5. Deploy and run on an CCpilot VS Click on the Projects -tab on the left side of the Qt Creator screen: The precondition for this process is the availability of the LinX Base runtime on the display. See chapter 0 for instructions on how to install the runtime. Figure 30: Available Project options in QtCreator Check the compiler settings by clicking on Manage Kits button at the top. The list of the available kits should look like this: Figure 31: The available Kits in the Build & Run settings Press the tab Compilers and make sure that the settings look like this: 18

19 Figure 32: Settings for cross-compiler Close the dialogue by pressing Ok Select the HW unit and select the Run settings: Figure 33: The Kit and Run selection in the project settings Deployment settings: - Note the remote directory, where the application will be stored on the CCP VS - Add Remote path... to: /opt Figure 34: The Deployment settings in the Run settings Run settings: - No additional settings necessary! 19

20 Figure 35: Run settings Run Environment settings: - Add the following variable: XDG_RUNTIME_DIR Figure 36: Add environment variable in Run settings After changing from the kit from Virtual Development Qt (X86-compiler) to CCpilot ARM (VS) Qt (ARM-compiler), you need to rebuild the project. Choose Rebuild all from the Build menu: Remember to always do a rebuild all when switching targets! Figure 37: Rebuild All menu item Press on the run button. 20

21 The application will be compiled and deployed to the CCP VS. The application should start on the target device. If the following error message appears in the QtCreator: Failed to create display (Permission denied) Application finished with exit code 1. To solve this, you must do the following from a terminal in the CCP VS unit: sudo chmod -R 777 /var/run/user/root/ But when restarting the unit, this setting will be lost and you would have to do it again. You must close the application by pressing the Exit button before you can deploy a new version to the display. After closing the application, the application window might stay on the screen because there might be no other application running anymore which updates the screen buffer. Congratulations, you have now started your first QtQuick/QML application on a CCP VS! 21

22 6. Autostart settings on CCpilot device All CCpilot display devices come preinstalled with an application, CCSettings (cclauncher), which automatically starts during boot. This is a Qt5 application located in the device folder: /usr/bin/cclauncher This application holds a few setting and test tools together with current assigned IP Address. [CC Settings Touch CC Video ] [Terminal Rotate Shutdown] 6.1. Modify startup scripts In Linux the startup procedure looks thru a couple of files to decide what application, drivers and scripts to start and in what order. In following directory of the device, we find the following scripts: cd /opt/etc/init.d ls -al These two files are installed during installation of packages. The CCSettings application cclauncher is the default startup application. This start script can be found in folder - /etc/init.d: The cclauncher script can be used if you want to create an auto-script for your own application. Just copy the script to folder /opt/etc/init.d and rename it to something that reminds you of the actual project. Open the script (with e.g. nano) and change the name cclauncher to you project. Remember to add the folder-path to where the application is stored! If we would have your own QML Qt5 application starting up during boot instead of the default CCSettings, follow the steps below. To stop the cclauncher GUI from auto-starting (the CCSettings application), go to the folder rc5.d and change the links: cd /opt/etc/rc5.d sudo ln sf /dev/null S10CClauncher 22

23 sudo ln sf../init.d/<your appl script> Make sure that your application startup script is executeable : sudo chmod +x <your appl script> Restart your device (# reboot) and your application should show up on the display Change order of startup The applications starts in a timed order during boot and this is controlled by symbolic links in folder /opt/etc/rc5.d Follow these steps to change the order of your startup application (if needed). cd /opt/etc/rc5.d ls al These are symbolic links pointing to the actual startup-scripts in /opt/etc/init.d. For example if we look at S25Start_codesys-deploy.sh you can see it points to:../init.d/ S25Start_codesys-deploy.sh To change it to start after Data Engine during boot rename the link to e.g. S50Start-codesys-deploy.sh mv S25codesys_deploy.sh S50codesys-deploy.sh Now our application in CODESYS application will start after Data Engine (starting at S50). 23

24 7. Further reading We recommend the following resources for further reading: The official Qt documentation at qt-project.org Qt5 Cadaques - A Book about Qt5 Linux Guide at wikibooks.org And of course the Knowledge Base at the CrossControl support site. 24

25 8. Appendix: Installing LinX Base runtime on CCP VS & VI2 When you order a product with LinX Base (UX Designer and Data Engine) the required runtime will be pre-installed. If you still need to download this runtime package manually, because a new version has been released, follow the steps below Download the LinX Base runtime from VM In the 3.0.x version of the VM, the LinX Base runtime is already pre-installed in this environment and ready to be deployed to the target. To install on target: 1. Move to the following folder: # cd /opt/<target>/targetinstallation (target = VS or VI2) 2. Run the script: #./DEPLOY.sh <target IP address> The output during installation: 25

26 8.2. Download an updated LinX Base runtime to your display As the LinX Base runtime is included in the VM installation, you will only be able to use this section when there is a new version of the LinX Base runtime available Get new version from CC support site In the virtual machine, open the Firefox web browser and navigate to the CrossControl support site. You need to log in to the support site to get access to downloads etc. If you don t have a login, start by register a user to the support site. Under Product Information > Software > LinX > LinX Software Suite 3 select and download the installation file for your display from the section LinX-Base runtimes 2. You can see the download progress in the top right corner of the window. Wait for the download to be completed. By default, the files get downloaded to the folder Downloads in your home folder Transfer the runtime installation file to the CCpilot In the virtual machine, open a terminal window (see chapter 3.1). Change to the download folder by entering # cd Downloads Make sure that you know the IP address of your CCpilot (see chapter 4.2). Enter the following command in the terminal window, replacing LinX-Base-XXX.run with the proper filename of the file you just downloaded and #.#.#.# with the IP address of the CCpilot: # scp LinX-Base-XXX.run root@#.#.#.#:/opt Write yes if you get asked Are you sure you want to continue connecting (yes/no)? When asked for the password, enter the root-password suseroot Install the runtime on the CCpilot While still in the terminal window, enter: # ssh root@#.#.#.# where #.#.#.# is the IP address of your CCpilot. If root login is not permitted, use the login: ccs and default When logged in with the root-password suseroot, make sure that the.run file is executable before starting (if logged in with ccs, you may have to use sudo before commnds): # cd /opt # chmod +x #./LinX-Base-XXX.run 2 You need to be registered and logged in on the support site in order to access the downloads. 26

27 Don t forget to replace LinX-Base-XXX.run with the filename of the installation file. The runtime installation takes around one minute and will finish by listing the installed packages. Reboot the unit by writing: # reboot 27