Realize the message queue method of vxworks and qt communication

Abstract

The invention relates to a message queue method for realizing communication between VxWorks and Qt. The method is suitable for mixed development of VxWorks and Qt and comprises the steps of: S1, declaring and establishing a message queue in a VxWorks task; S2, establishing a plurality of Qt sub threads in a Qt main thread and declaring the message queue outside the Qt sub threads; and S3, carrying out communication between the Qt sub threads and corresponding VxWorks tasks respectively through a message queue mechanism. Synchronization of the VxWorks tasks and the Qt sub threads is realized through a VxWorks message queue blocking reception mechanism, so that the atomic operation for message queue data during task or sub thread read and write process is ensured, and task deadlock is avoided.

Description

technical field [0001] The invention relates to the field of embedded development, in particular to a message queue method for realizing communication between VxWorks and Qt. Background technique [0002] Qt is a cross-platform C++ graphical user interface application framework developed by Nokia. It provides application developers with all the functionality needed to create state-of-the-art graphical user interfaces. And Qt is fully object-oriented, easy to expand, and allows real component programming; using software developed with Qt, the same code can be compiled and run on any supported platform without modifying the source code. [0003] The VxWorks operating system is an embedded real-time operating system (RTOS) designed and developed by WindRiver Corporation of the United States in 1983, and it is a key component of the embedded development environment. VxWorks operating system occupies a place in the field of embedded real-time operating system because of its goo...

AI Technical Summary

Problems solved by technology

However, when multiple VxWorks tasks or Qt sub-threads read and write the same piece of shared memory, the integrity of the data will be destroyed due to the asynchrony between the tasks or sub-threads, resulting in errors in reading and writing data.

If the critical area or mutual exclusion protection is implemented for the shared memory data, although the integrity of the data is guaranteed when reading and writing, it will cause task priority inversion under certain conditions, and even task deadlock, so that the real-time performance of the system will be affected. influences

Images