December 5, 2023 Haris Turkmanović

Firmware and GUI core functionalities are implemented

Milestone 1MilestonesProject Reports
Firmware and GUI core functionalities are implemented

As mentioned in the previous blog , the first milestone includes the development of core (minimal) firmware and GUI functionalities.

The entirety of the firmware source code created for this milestone can be found in the Firmware/ADFirmware path. Before implementing core functionalities, an important step involved defining a coherent structure for the firmware source code and aligning it with the described firmware architecture. To provide a comprehensive understanding, we will first detail the organization of firmware directories. Subsequently, we will offer a brief overview of the functional blocks integrated into this milestone. Finally, we will guide you through importing, running, and compiling projects within the STM32Cube IDE.

Firmware directory's structure

The complete firmware source code structure is organized as it is presented in Figure 1:

Firmware Top Directory Structure

Within each core directory (CM4 and CM7) is implemented code directory organization to correspond to the overall firmware architecture described here . This organization is illustrated in the following figure:

Firmware Core Directory Structure

Overall firmware architecture that presents blocks implemented within this milestone is illustrated in Figure 3.

Firmware core functionalities

Overall firmware architecture that presents blocks implemented within this milestone is illustrated in Figure 3.

Milestone 1 - Firmware Architecture Overview Development Status

Compile and run acquisition device firmware

STM32Cube IDE is used for code development and the source code located on the GitHub repo is completely adapted to simplify project distribution over different machines that run this tool.

After the complete project is pulled from the project GitHub repo it should be imported within STM32Cube IDE. This is done by clicking on File-> Open Projects From Filesystem as shown in Figure 4.

Import projects menu

After selecting this option, the dialog presented in Figure 5 is opened. Within this dialog, we should press the Directory button and configure the ADFirmware directory path.

Import Projects Menu 1

When the project is successfully imported, it should be available within the STM32Cube IDE project explorer subwindow located on the left side as it is presented in Figure 6.

Project within File Explored subwindow

After the project is successfully imported it is ready to be compiled and run on NUCLEO -H747ZI2 platform. If you have any issues during the compilation process, contact our development team.

The complete GUI source code created for this milestone can be found in the GUI/OpenEPT path. A current version of the GUI application implements only fronted elements with empty backend callback functions. These functions will be implemented within the future milestones. Through this blog, we will first present several windows and dialogs implemented as part of the GUI front end. Subsequently, we will guide you through importing, compiling, and running projects within the Qt Creator.

GUI Windows

The first application version integrates several windows. After the application is started, the main window is opened as presented in Figure 7.

GUI Main Screen

Within the Main application window, from the Menu bar is possible to select Devices->Add device after which a pop-up window is displayed and the user should enter the Acquisition device IP address and port. This Add device dialog is presented in Figure 8.

Add Device Wnd

When the user enters the Device IP address, the Device window appears and presents the device's relevant information. This window is logically divided into three layouts:

The device window layout is presented in Figure 9.

Device Window

The device window presents only basic device configuration. However, it is possible to open the Advance configuration window which provides wider configuration options. This window layout is presented in Figure 10.

Advance Configuration Window

Compile and run application

Compile and run application

In order to run OpenEPT application installation of Qt software is needed. Download of Qt is available in this website - NOTE : in order for Compiler to be compatible with Qt version, MSVC2019 needs to be installed on PC. This can be downloaded here . Version of Qt is 6.2.4 and all additional libraries are following: |--Qt |--Qt 6.2.4 |   |-- MSCV 2019 64-bit |   |-- Sources |   |-- Additional libraries |   |   |--Qt charts |   |   |--Qt image formats |   |   |--Qt websockets |   |--Qt Debug Information Files |--Developer and Designer Tools |--Qt Creator 12.0.0 |--Qt Creator 12.0.0 CDB Debugger Support |--Debugger Tools for Windows |--Qt Installer Framework 4.6 |--CMake 3.27.7 |--Qt Maintenance Tool

Every prerequisite is listed in Figure 11:

QT Maintenance Tool 2
QT Maintenance Tool 2

Project setup is done in Qt Creator in upper toolbar we have Edit -> Preferences and the setup should look like this (for this MSVC2019 is required):

Project setup is done in Qt Creator in upper toolbar we have Edit -> Preferences and the setup should look like this (for this MSVC2019 is required):

Qt Setup

‍

About the author

Haris Turkmanović

Haris Turkmanović

Teaching Assistant

Embedded Software Architect and Project Manager

Since 2018, I have been an employee at the Department of Electronics and Digital Systems, which is part of the Faculty of Electrical Engineering at the University of Belgrade. Beginning in 2019, I also assumed the role of a teaching assistant in the same department while concurrently pursuing my doctoral studies. The main objective of my research revolves around sub-areas of embedded systems. This includes distributed embedded systems, IoT systems, battery-powered embedded systems, and developing optimized software solutions for embedded platforms.

Read more

Related blogs

November 9, 2024The combined testing of hardware and software has been successfully done, completing Milestone 6.
Haris Turkmanović

The combined testing of hardware and software has been successfully done, completing Milestone 6.

Milestone 6 has been one of the most demanding phases of the project to date, primarily focused on testing the hardware and software functionalities developed earlier. It served as a crucial integration point for both components of the proj
June 5, 2024Streamlining Data Flow: Core Software Functionality Completed!
Haris Turkmanović

Streamlining Data Flow: Core Software Functionality Completed!

We have previously announced the PCB design is completed and boards are sent to manufacturing. Fabricated PCB boards have arrived However, while we're all set to begin assembly, some key components are still coming. While we await the arriv
March 3, 2024The acquisition device control and status messages logic have been successfully implemented
Haris Turkmanović

The acquisition device control and status messages logic have been successfully implemented

Control and status message logic represent one of the system's core functionalities. It is responsible for configuring the acquisition device, overseeing its operation, and providing updates on the system's execution status. The Figure 1 il
November 1, 2023Setup development environment, port third parties libraries and create code framework
Haris Turkmanović

Setup development environment, port third parties libraries and create code framework

In the initial phase, our focus lies on configuring all development tools, adapting thirdparty libraries, and effectively establishing the previously outlined architectural frameworks . Our primary objective involves successfully initiating
Read all blogs →