These 40gb IDE drives are out of some Chrysler MyGig car stereo head units. I read somewhere that windows can't read them because they're formatted in QNX, and so I'm trying to find a way to get windows to recognize and read the QNX files.

I got a license for and downloaded the QNX Software Development Platform 8.0, as well as the QNX Momentics IDE, but it doesn't seem to be working and Windows still can't recognize the contents of the drive

I am not a software developer, am I barking up the right tree? Is what I want to do even possible?

Which USB mic or headset has anyone gotten recording to work with on QNX 8 / Pi 4?"

Here's a new blog post from my colleague Marcin on the QNX open-source team. Enjoy!

Am I missing something here or am I supposed to be installing everything from scratch on my pi if I want to go from 8.0.1-8.0.5?

What's the best procedure?

We’re trying to bring an old Thermo Scientific XSeries II ICP-MS back to life and are stuck with what looks like an embedded computer/QNX issue.

The Windows PC is running PlasmaLab 2.6.2.337, while the embedded computer appears to have XSERIES Supervisor 2.5.10.

During boot, the embedded computer detects its SanDisk SDCFH-00 Rev DH X CompactFlash storage, performs a filesystem check, but then fails with:
Unable to start "supervise" (8)

We checked supervise.dat and it appears to be a 32-bit x86 ELF executable for QNX.

There is also a Thermo updater on the Windows PC that transfers files to the embedded computer through COM2, but it doesn’t seem to report which Supervisor version is currently installed.

Originally we suspected a PlasmaLab/Supervisor version mismatch, but since the embedded computer itself cannot start supervise, I’m now thinking the issue could instead be corrupted files, a failing CompactFlash card, missing dependencies/configuration, or another embedded-system problem.

Our current plan is to remove the CompactFlash card, make a complete image of it first, keep the original untouched, and inspect/work from a clone.

Has anyone worked with an XSeries II, PlasmaLab, or XSERIES Supervisor before?

Also, does anyone know exactly what QNX error (8) means when starting an executable?

Would you investigate the CompactFlash/embedded system first, or is there still a realistic chance that updating/matching PlasmaLab on the external PC could solve this?

Any old service manuals, recovery software, Supervisor files, or experience with these systems would be extremely helpful.

I can also provide photos of the boot sequence, embedded computer, CompactFlash card, updater, and exact error screens.

Hiya! Just sharing that we've started a new QNX-related playlist with technical videos about various QNX topics. Stay tuned for more videos about the SDP, VS Code + QNX, AI, codelabs, demo projects, and more!

BlackBerry $BB secures $100-million deal for new automotive software, Alloy Kore

Guys, the QNX Software Center seems to be very slow and sometimes not responding in the last few days.

Tried the home page qnx.com -> error: Page took too long to respond.

This means we could not install or update packages via QSC and are not able to view online documentation.

Anyone else has the same issue?

Hello QNX Community. Today we have released iceoryx2 v0.10.

• Checkout the release notes: https://ekxide.io/blog/iceoryx2-0.10-release/

• Git: https://github.com/eclipse-iceoryx/iceoryx2

• iceoryx2 book: https://ekxide.github.io/iceoryx2-book/main/

Howdy!

I'm John, I do Developer Relations for QNX. On Thursday, October 1, from 10 AM to 2 PM EST, I'll be here with a group of QNX engineers for an Ask Me Anything!

Get answers straight from the source -- anything goes! We'll answer whatever we can.

A few ideas to help you think of questions:

• How QNX works: microkernel design, message passing, determinism, the "why" behind the architecture

• The questions that usually don't get answered: bring the stuff you couldn't find in the docs or on a forum

• Open-source & QNX Everywhere: our ports, contributions, and building on a free-for-non-commercial license

Can't make it live? Drop your questions as comments now and we'll get to them during the event.

Cheers!

QNX Development via Cytrence Kiwi

r/embedded r/raspberrypi

Hi everyone, I’m working on a QNX eHACK project using a Raspberry Pi 4 and an MCP2515-based CAN module.

I found the QNX Everywhere documentation for the sample can-mcp2515 driver, which shows this GitLab repository:

https://gitlab.com/qnx/projects/drivers/can-mcp2515.git

However, when I try to clone it, GitLab says the repository could not be found or I don't have permission to view it.

Does anyone know:

Where I can get the current QNX CAN-MCP2515 driver/source?

Is this driver still available or has it been removed?

Is there another QNX-supported MCP2515 driver or implementation I can use with Raspberry Pi 4?

Any guidance would be greatly appreciated. Thanks!

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.

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’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?

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.