Integrating an Embedded Wizard GUI application on custom hardware requires careful planning and systematic implementation. This article provides a comprehensive guide through the essential steps, from initial hardware assessment to final application deployment.

The first and most critical step is selecting the right Build Environment that matches your custom hardware as closely as possible.

Consider the following criteria when selecting your Build Environment:

Configure the system parameters in the ewconfig.h file according to your hardware specifications. This configuration file contains critical settings that must match your hardware capabilities before any integration work can begin.

The most important configuration areas are Memory Configuration and Display Configuration. Proper configuration of these parameters is essential for stable operation of your GUI application.

For detailed information about all available configuration options and their effects on your specific hardware, refer to Target Configuration.

Adapt the /TargetSpecific/ew_bsp_console.c file to establish a reliable debug console connection:

For microcontroller-based systems, adapt the /TargetSpecific/ew_bsp_system.c file:

For additional information about system integration, refer to Main Loop concepts.

After system initialization is complete and SDRAM timing parameters are properly configured, verify that your memory subsystem is working correctly. Memory issues are among the most common causes of integration problems.

Use a comprehensive SDRAM test that writes incrementing data patterns to consecutive memory addresses and reads them back after exponentially increasing delay times to verify refresh functionality. Put the following code snippet into your ewmain.c file and call the test function just before the initialization of the memory manager:

The incrementing data pattern and exponentially increasing delay times are essential for detecting address line problems and verifying that SDRAM refresh is working correctly.

Adapt the /TargetSpecific/ew_bsp_display.c file for your specific display hardware:

For background information about display integration concepts, see Framebuffer Concepts.

Adapt the /TargetSpecific/ew_bsp_touch.c file for your touch controller:

Reading the raw touch data from the hardware can be implemented either polling-based (checking controller registers) or interrupt-based (using hardware interrupts), depending on your hardware design and performance requirements.

The remaining touch functionality (coordinate mapping, event handling, coordinate transformation) is typically already implemented in the function EwBspTouchGetEvents() in the module ew_bsp_touch.c and may only require minor parameter adjustments. For more details about touch debugging macros, see Target Configuration.

If you want to change from the default operating system (usually FreeRTOS) to a different OS, adapt all functions within the file /TargetSpecific/ew_bsp_os.c to your particular operating system:

Start the integration process with simple test applications rather than complex GUI projects:

Use the /Examples/ScreenOrientation example as your first test:

The ScreenOrientation example demonstrates simple animations and touch response, making it ideal for verifying system tick functionality and touch calibration during hardware integration.

Use the /Examples/ColorFormats example to verify display quality:

The ColorFormats example displays various color gradients and patterns, making it perfect for testing display bit integrity and color format configuration during hardware integration.

Follow these steps with increasing compexity:

Plan your memory layout carefully to ensure optimal performance:

Monitor system performance during integration to ensure optimal operation:

For detailed performance optimization strategies covering hardware architecture, software configuration, and GUI design, see Performance Optimization Guide.

Beyond basic console output, consider additional debugging capabilities:

Implement appropriate power management for your application:

If you encounter problems during integration, check the Error and Warning Codes documentation for detailed error descriptions and solutions. Common integration issues include:

Follow a systematic approach for testing your integration:

By following this systematic approach, you can successfully integrate Embedded Wizard GUI applications on your custom hardware platform while minimizing integration time and avoiding common pitfalls.