QNX integration Q&A

[antonkri]

Please put your questions regarding QNX integration & usage in S-CORE project here:

1. Does QNX Everywhere also provide Safety Manuals and can we use them in S-CORE projects to reference QNX AoUs in our requirements?
2. Does QNX SDP 8.0 include support for a qualified rust toolchain?
3. Will QNX Everywhere also include QNX 7.1 eventually? It would be nice to have the ability to provide ports for QNX 7.1 in the open source.
4. What are the prerequisites for using QNX Everywhere for internal S-CORE development?
5. How will AI tooling, accelerator, ... support be integrated in QNX?

[MarkSchmitt]

6. There is still no full support for a Rust QNX 8.0 target, this is a blocker right now. Any plans on helping the rust lang project to get the support in? ( see https://doc.rust-lang.org/rustc/platform-support/nto-qnx.html for current status)

More questions, specifically for 2:
2.1. Will blackberry allow for rust QNX targets to be distributed by anyone (so they can be built and distributed like any other target)
2.2. Will blackberry in the future help the Rust lang project, that new QNX releases will also have rust support at release date? Right now, we still don't have full support for QNX 8.0!

[JohnAtQNX]

Hi @MarkSchmitt!

6. There is still no full support for a Rust QNX 8.0 target, this is a blocker right now. Any plans on helping the rust lang project to get the support in? ( see https://doc.rust-lang.org/rustc/platform-support/nto-qnx.html for current status)

See my top-level comment in response to Anton and also the additional context below, but in short: the QNX team plans to release a pre-built compiler this year and is evaluating our approach to upstreaming QNX target support.

More questions, specifically for 2:
2.1. Will blackberry allow for rust QNX targets to be distributed by anyone (so they can be built and distributed like any other target)

If QNX decides to help upstream Rust support, so I would think use of that code and the resulting builds would be governed by the license(s) on the rust-lang repository. But if I'm misunderstanding the question or can address a more specific use case, let me know.

2.2. Will blackberry in the future help the Rust lang project, that new QNX releases will also have rust support at release date? Right now, we still don't have full support for QNX 8.0!

We're starting to formulate our long-term maintenance model and evaluating how best to contribute over time. Rust support is important to QNX and we’re dedicating time to formulate a long-term plan here.

[JohnAtQNX]

Howdy! Just for full transparency, I edited my response above to be more clear about our current status with Rust. TL;DR: the QNX team plans to release a pre-built compiler this year and is still evaluating our approach to upstreaming QNX target support.

[TomFleischmann]

The License S-CORE aims to develop safety software according to ASIL-B requirements and should still not fall under number 4.2.5 of the QNX non-commercial license.

[JohnAtQNX]

Hi folks! I'm John from QNX -- I work on Developer Relations for the QNX Everywhere initiative. I'm happy to answer any questions you have. (And sorry for the delay, this just came across my desk.)

I'll put other answer in-line, but responnding first to @antonkri:

1. Does QNX Everywhere also provide Safety Manuals and can we use them in S-CORE projects to reference QNX AoUs in our requirements?

No, safety manuals are not included. These are provided to customers of the QNX OS for Safety and QNX Hypervisor for Safety products.

2. Does QNX SDP 8.0 include support for a qualified rust toolchain?

Not at this time, though it's a priority for our teams. QNX is aiming to release a pre-built ‘QNX experimental’ Rust compiler before the end of this year.

3. Will QNX Everywhere also include QNX 7.1 eventually? It would be nice to have the ability to provide ports for QNX 7.1 in the open source.

This isn't planned, no. The QNX Everywhere initiative is future-focused, helping to steer QNX into new areas. In general, projects released as part of the QNX Everywhere initiative will not apply to previous product releases. QNX is open to discussing specific situations though, such as porting specific projects or providing community support for something specific.

4. What are the prerequisites for using QNX Everywhere for internal S-CORE development?

Anyone can access the non-commercial QNX license released as part of the QNX Everywhere initiative. This license enables access to the QNX Software Development Platform, which will give you what you need to develop for QNX in a non-commercial & prototyping capacity. If you need more detail here or if I misunderstood the question, please let me know!

5. How will AI tooling, accelerator, ... support be integrated in QNX?

QNX has a task force dedicated to this today, and we're listening to how folks are using and want to use AI tooling in their embedded workflows. We're very open to learning about how you would like to leverage AI tools for development with QNX -- please share your feedback on this with me!

Cheers!