| | 2 | |
| | 3 | The development environment allows 825 app operation to be simulated. This saves time developing applications and allows for debugging. However, not all aspects of application operation can be simulated. |
| | 4 | |
| | 5 | |
| | 6 | |
| | 7 | |
| | 8 | For 825 simulation when logging into the development environment be sure the desktop graphics type is: |
| | 9 | "Desktop Session: Plasma (Wayland)" |
| | 10 | |
| | 11 | Click the "Toolbar" item "825 simulator for debugging an app" |
| | 12 | |
| | 13 | |
| | 14 | Click "Tools", "Settings…" to configure the simulator. |
| | 15 | |
| | 16 | |
| | 17 | Option card "Details" may be configured. |
| | 18 | |
| | 19 | |
| | 20 | |
| | 21 | Simulation in the development environment is achieved by having a build configuration for each app such as "Debug-ARM825-SIM" that compiles the app with the default GCC compiler in the VM to build the app to run on Intel x86 processor. The lib825ev, and other libraries have corresponding "Debug-ARM825-SIM" build configurations. The build configuration must be setup to link to the appropriate library files. |
| | 22 | |
| | 23 | In case the VM is logged in as Plasma (X11) when starting a simulated app the console message will show: |
| | 24 | |
| | 25 | |
| | 26 | |