Simulating 825 Gen2 App Operation

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.

For 825 simulation when logging into the development environment be sure the desktop graphics type is:

"Desktop Session: Plasma (Wayland)"

Click the "Toolbar" item "825 simulator for debugging an app"

Click "Tools", "Settings…" to configure the simulator.

Option card "Details" may be configured.

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.

1. Right-click on the project in Eclipse and select "Build Configurations", "Manage..."
2. Click "New..." and type for the "Name:" input "Debug-ARM825-SIM". Selected "Copy settings from "Existing configuration - Debug-ARM825". Click "OK".
3. There is now a duplicated build configuration. We will change this configuration to compile for the virtual machine simulation.
4. Right-click on the project and select "Properties...", Select "Settings". Make sure the "Configuration" is selected as "Debug-ARM825-SIM" and click the "Tool Settings" tab.
5. Some projects might have "Cross Settings" under "Tool Settings". If so change the "Prefix" to blank "". If the "Cross Settings" is in the project the following steps 6-9 may then be skipped.
6. Select "GCC C++ Compiler". Change the "Command:" to "g++". This changes the compiler to compile for PC architecture.
7. Select "GCC C++ Linker". Change the "Command:" to "g++". This changes the linker to link the project for the PC architecture. Linking is the process of combining the already compiled code modules and libraries to create the executable.

8. In some cases the project may also have a "GCC C Compiler". If so change the command to "gcc".
9. In some cases the project may also have a "GCC Assembler". If so change the command to "as".
10. Click "Apply".
11. Go back to "Tool Settings" and under "GCC C++ Compiler" select "Include paths". Click the green plus icon to add paths. Add the paths "/usr/include/freetype2", "/usr/include/pixman-1" If there is a "GCC C Compiler" section also add these paths to the includes there.
12. Under the "GCC C++ Linker" select "Libraries".
13. Under "Library search path". Edit existing library paths as appropriate. For example change "${workspace_loc:/lib825ev/Debug-ARM825}" to "${workspace_loc:/lib825ev/Debug-ARM825-SIM}"
14. Under "GCC C++ Compiler" select "Preprocessor". Click the green plus icon to add symbols. Add "ARM64=1" and "SIM825=1". These are used for conditional compilation. If there is also a "GCC C Compiler" section select "Preprocessor under that and also add these symbols there.
15. Click "Apply and Close".

In case the VM is logged in as Plasma (X11) when starting a simulated app the console message will show:

The simulator running with a legacy mode app may appear similar to:

The simulator running with new style app may appear similar to:

Simulator Project Settings Reference

Debug-ARM825-SIM build configuration

Compiler and Linker

If the properties sheet has "Cross Settings" section set:

Prefix: <blank>

Tool Settings	Command
Cross G++ Compiler	g++
Cross GCC Compiler 1	gcc
Cross G++ Linker	g++
Cross GCC Assembler 1	as

₁ "Cross GCC Compiler" and "Cross GCC Assembler" items may not be present in all projects.

If the properties sheet does not have "Cross Settings" section:

Tool Settings	Command
GCC C++ Compiler	g++
GCC C Compiler 1	gcc
GCC C++ Linker	g++
GCC Assembler 1	as

₁ "GCC C Compiler" and "GCC Assembler" items may not be present in all projects.

Preprocessor

Defined symbols	Description
DEBUG
ARM64=1
SIM825=1

Includes

Includes	Description
"${workspace_loc:/lib825ev/inc}" 1	Main 825 library
"${workspace_loc:/lib825lang/inc}" 2	825 Multi language
"${workspace_loc:/lib825sql/inc}" 3	825 SQLite
/usr/include/freetype2
/usr/include/pixman-1/
/usr/include/gstreamer-1.0/
/usr/include/glib-2.0/
/usr/lib64/glib-2.0/include
/usr/include/cairo
/usr/include/mysql

₁ Older apps may use 825 instead of 825ev. In this case change the include to: "${workspace_loc:/lib825/inc}"

₂ 825lang is used for newer 825 Gen2 apps. This is not needed for recompile of Legacy 825 apps.

₃ Older recompiled apps may instead use sql3_7_9. To use sql3_7_9 library change include path "${workspace_loc:/libsql3_7_9/inc}".

Libraries

Library	Description
825ev 1	Main 825 library
825lang 2	825 Multi language
825sql 3	825 SQLite
sqlite3 3	825 SQLite
${UI_LIBS}
${CAIRO_SIM_LIBS}
${GLIB_LIBS}
${PRT_SIM_LIBS} 4	(PRT_SIM_LIBS new 2025-03-05)

₁ Older apps may use 825 instead of 825ev.

₂ 825lang is used for newer 825 Gen2 apps. This is not needed for recompile of Legacy 825 apps.

₃ For newer apps it is preferred to use 825sql and sqlite3 for dynamically linked SQLite shared object that is already on 825 Gen2. Older recompiled apps may instead use sql3_7_9 which is statically linked.

₄ If VM is not updated to have PRT_SIM_LIBS environment variable instead use individual lines: cups, json-c, esmtp, ssl, crypto

Library search path
${workspace_loc:/lib825ev/Debug-ARM825-SIM} 1
${workspace_loc:/lib825lang/Debug-ARM825-SIM} 2
${workspace_loc:/lib825sql/Debug-ARM825-SIM} 3

₁ If the older lib825 is used change search path to "${workspace_loc:/lib825/Debug-ARM825-SIM}".

₂ The lib825lang search path is not needed if not using lib825lang.

₃ If sql3_7_9 library is used change search path to "${workspace_loc:/libsql3_7_9/Debug-ARM825-SIM}".