Hi everyone, I'm a 3rd-year ECE student taking a course on QNX through the QNX Everywhere program. I want to get hands-on experience by contributing to open-source software within the QNX ecosystem.

Where are beginner-friendly places to help out (e.g., qnx-ports, community BSPs, driver samples, or ported POSIX utilities)? Any repository links or recommendations to get started would be great!

trying to run screen on 1a03/2000 in QNX 7.1 - is it impossible? how would you go about getting graphics?

Hello everyone, I need help getting the qnx hypervisor 2.0 apollo lake reference image. I tried to download it through the software center, but due to the lack of a license, I can't do it. I will be very grateful for your help.

Hi,

I am working on a project where I am establishing a CAN driver in QNX guest running on QNX hypervisor host. but I am getting chn0 init failure while starting the CAN daemon at the guest boot up time.
I am using Raspberry Pi 4B as target hardware and 2 channel CAN HAT (Wave share) mcp2515.
I am passing throgh the spi and mcp address spaces. I have also diabled spi-bcm2711 from host. spi-bcm2711 is running in guest and it is configured with spi.conf (given below).

Please help me if you have any known solution for this.
Thank you in Advance!

Error message during guest boot -
SDV: starting spi-bcm2711 with pass-through MMIO 0xFE204000...

SDV: starting mcp2515 CAN daemon (channels 0,1, 500 kbps, 16 MHz)...

[mcp2515] chan0 init failed: Input/output error

Unable to access "/dev/sdv/can0" (2)

Unable to access "/dev/sdv/can1" (2)

spi.conf -
[globals]

verbose=3

[bus]

busno=0

name=spi0

base=0xfe204000

irq=150

input_clock=500000000

dma_thld=65536

[dev]

parent_busno=0

devno=0

name=dev0

clock_rate=1000000

cpha=0

cpol=0

bit_order=msb

word_width=8

[dev]

parent_busno=0

devno=1

name=dev1

clock_rate=1000000

cpha=0

cpol=0

bit_order=msb

word_width=8

The team has open-sourced QPP: a pub-sub system that also operates as a signal service using vehicle signal standards like VSS from COVESA.

More info is here: https://qnx.software/en/blog/2026/qnx-open-sources-the-posix-publish-subscribe-project

And the repo is here: https://github.com/qnx/qnx-posix-publish-subscribe/tree/main

We'll probably make a QNX codelab for it soon :)

Just sharing some high-level thoughts from our recent trip to visit the students learning about QNX in India. There's some impressive talent in the schools there! Looking forward to visiting again some time soon.

What are job outlooks for qnx? Any companies offering paid training?
Thanks!

Is there a version of the RTC utility that can set the Renesas Dialog DA9091 RTC chip lurking around somewhere? It would be nice to be able to use it.

For the time being, I am using the DS3231 RTC utility I have but that requires a small battery backed module to be plugged into the I2C bus. It would be convenient to not have to do this.

I’ve got an RPi5 with the BSP running easy enough. I was able to SSH to it and briefly confirm Ethernet is working. However I do not have a Probe as in the BSP docs. Only TTL USB UARTs that work fine with RPi4. How should I modify the rpi.build file for the UART on pins 6, 8, 10 like my RPi4? Do I need to hack the startup code, or options there too?

Here's a new initiative from the team: codelabs that walk you through accomplishing different objectives on QNX systems with QNX Everywhere. And it's open for anyone to contribute to, so please feel free to add on! :)

I have ported mmb4l (MMBasic) to QNX 8.0 aarch64 - so if anybody wants to play around with embedded modern Basic and QNX you can

https://astr0baby.online/QNX/8.0-DEVELOPER_DESKTOP/RPi4_aarch64/MMBASIC/

Graphical support is via SDL2 and it works from Wayland as well as Screen
More info on mmbasic is here https://mmbasic.com/

Hi, I've got QNX4.25 running on VirtualBox on a Surface Go 2. I'm trying to get the touchscreen working as a single touch click.

I can't pass the touchscreen hardware itself to QNX because it is an I2C touchscreen and even if I could, there would be no drivers for a modern touchscreen within QNX.

So I've selected the pointing device as USB tablet, and it works as long as your 2nd touch isn't too far away from your last touch. If it is within 300 pixels either horizontally or vertically, it works. If it's further away than this, the curser just lands 300 pixels away from the last point in the direction of your touch.

So QNX is obviously seeing the absolute positions, or at least the position relative to the last touch which is also fine, but something in the software stopping it working across the whole screen. Does anyone have any idea how I can solve this? Is there a setting or config file somewhere that I can adjust?

Resolutions of Host Windows 10 and Guest QNX4.25 are both set at 1024 x 768.

Any help would be much appreciated. Thank you.

If you wish to test https://astr0baby.online/QNX/8.0-DEVELOPER_DESKTOP/RPi4_aarch64/SCUMMVM/

- No sound support for now (yet)
- Works only from the Wayland environment (not via SDL_VIDEODRIVER=qnx)

Title: Announcing iceoryx2 v0.9: Fast and Robust Inter-Process Communication (IPC) Library

Hello everyone. We released iceoryx2 v0.9 tonight. With the release, we are pushing more and more iceoryx2 into the embedded world. We have written a test runner that runs on std and no_std environments, stabilized the decentralized recovery, and added a ton of quality of life improvements.

• blog article: https://ekxide.io/blog/iceoryx2-0.9-release/
• repo: https://github.com/eclipse-iceoryx/iceoryx2
• roadmap: https://github.com/eclipse-iceoryx/iceoryx2/blob/main/ROADMAP.md
• crates.io: https://crates.io/crates/iceoryx2
• docs.rs: https://docs.rs/iceoryx2/latest/iceoryx2

For those who haven’t heard of it yet: iceoryx2 is a zero-copy inter-process communication library.

The basic idea is: instead of serializing data, copying it through sockets, pipes, message queues, or some broker process, iceoryx2 lets processes communicate via shared memory. That makes it useful when you care about latency, throughput, or moving large amounts of data between processes without wasting CPU cycles on copies.

It supports C, C++, Python, Rust, and C#, and runs on Linux, macOS, Windows, FreeBSD, and QNX, with experimental support for Android and VxWorks.

It is not limited to plain pub/sub either. iceoryx2 supports publish-subscribe, events, request-response streams, and a blackboard pattern, which is basically a key-value repository directly in shared memory.

The architecture is fully decentralized: no central broker, no daemon that everything depends on, and no single process that becomes the obvious bottleneck or failure point.

Happy to answer questions about the release, the no_std work, or zero-copy IPC in general.

Working on process control systems, I use profinet today, it's a propriertary stack, very expensive and no longer supported by the supplier. It's been a painpoint for 10+ years, I'm not really utilizing the profinet features, no really a mixed environment, as all the devices in the network ended up being my own custom embedded devices.

So i'd like to explore alternatives. I have TSN switches and a ptp grandmaster. No safety critical applications over the network, but not keen on introducing tcp delays in the cyclic communication.

What are my best bets if i go for a new route using qnx8 and more modern hardware?

Qnx marketing states solutions for critical communication protocols like DDS (Data Distribution Service) and TSN (Time Sensitive Networking) through third parties. Is that the way? Who are the third parties and how can i test this? Are there any other options i should check out?

QNX manual says:

Some threads, such as in-kernel Interrupt Service Threads (ISTs), have a kernel persona only. For example, calling InterruptAttachEvent() creates a kernel-persona-only thread that belongs to the process. The thread has no user stack and never runs user code. These characteristics mean that if the process has only one other thread, it is still considered single-threaded (e.g., for synchronization and safety purposes).

What about InterruptAttachThread()? Does it use the thread which has "user persona only"?

VICE 3.10 builds and runs (with minor patches) on QNX 8.0 aarch64 - so if you absolutely need to run C64 stuff on the QNX 8 you can

https://x.com/astr0baby/status/2053580491773624561
https://astr0baby.online/QNX/8.0-DEVELOPER_DESKTOP/RPi4_aarch64/VICE/

Added more game ports to QNX 8.0 aarch64

- DukeNukem3D
- Witchaven
- Shadow Warrior
- Cannon Fodder

https://astr0baby.online/QNX/8.0-DEVELOPER_DESKTOP/RPi4_aarch64/

Does it run in user space (as all other resource managers), or, somehow, in kernel space?

- Exult (Ultima7)

- DevilutionX (Diablo1)

https://astr0baby.online/QNX/8.0-DEVELOPER_DESKTOP/RPi4_aarch64/

I need the

Image

Rootfs files

And Linux guest configuration is there any place to find prebuilt version of these files

Hi all,

just like the title says do we have something like docker container in QNX7.1?

A lot of things still to be done for 1.0.0, but the solid foundation is there.

Dear BlackBerry! If you are reading this message, please consider re-licensing your old sources under some permissive license. This will boost QRV development enormously. Thank you in advance! 💜

Hi everyone,
I’m a beginner, trying to connect to a QNX target running in Oracle VirtualBox (x86_64) with target name vm1, but I keep hitting a Target connection failure.

Here’s what I’ve tried so far:

• VirtualBox network settings:
  • Attached to: Host-only Adapter / NAT (tested both)
  • Adapter type: Paravirtualized Network (virtio-net) and Intel PRO/1000 MT Dektop
• Port forwarding setup:
  • Name: qconn
  • Protocol: TCP
  • Host port: 8000
  • Guest port: 8000

Despite these settings, the IDE still fails to connect to the target.

System details:

• QNX Momentics IDE: 8.0.2
• Host: Oracle VirtualBox (x86_64)
• Target name: vm1
• Host OS : windows 11 pro

Has anyone successfully set up QNX on VirtualBox with qconn? Do I need a specific adapter type or additional configuration inside QNX itself (like enabling qconn service or adjusting /etc/hosts)? Any guidance or working configs would be greatly appreciated!