Re: [threadx-dev] ThreadX - Feature extension plans

[hmnews@xxxxxxxxxxx]

Just wondering, when in this list the term "ThreadX" is used in relation 
to safety certifications and compliance with FS standards, would that 
also include NetXDuo, USBX and FileX? Or are these repos excluded from 
those certs.

Frédéric Desbiens via threadx-dev wrote on 19/07/2024 10:50 PM:
> Hi Mike.
>
> I appreciate your support for Eclipse ThreadX. Glad to have you as a user.
>
> The Foundation intends to certify ThreadX 6.4.1, the latest release, 
> against the same standards for which 6.1.x has been certified. These 
> include IEC 61508 and ISO 26262. We will also maintain our UL 
> certifications for home appliances.
>
> You wrote:
>
>     /Would it be that users of the RTOS as they incorporate new features
>     would be expected to re-certify these changes, or will the
>     certification be kept up to date in some other way?/
>
>
> The exact cadence for future certifications has yet to be decided. 
> Ultimately, it will come down to the capacity of the project's 
> committers and the funding we will get from selling our certification 
> documentation. Naturally, any new features added inside the scope of 
> what is currently certified will require recertification. Expanding the 
> scope of the certification will also impact this.
>
> I appreciate you took the time to share your thoughts with us.
>
> Best Regards,
>
> *Frédéric DESBIENS*
>
> *Senior Manager — Embedded and IoT | **Eclipse Foundation*
>
> Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx 
> <mailto:fdesbiens@xxxxxxxxxxxxxxxxxxxxx>
>
>
>
>
> On Thu, 18 Jul 2024 at 14:46, Bill Lamie via threadx-dev 
> <threadx-dev@xxxxxxxxxxx <mailto:threadx-dev@xxxxxxxxxxx>> wrote:
>
>     Hi Mike,____
>
>     __ __
>
>     First, thank you for being a loyal TheadX customer! ____
>
>     __ __
>
>     On the certification front, each new version of ThreadX must be
>     recertified.  The last certified version was from several years
>     back.  I don’t know the roadmap for any new certifications.____
>
>     __ __
>
>     As for the feature request, I believe you might be interested in
>     ThreadX Modules:____
>
>     __ __
>
>     https://github.com/eclipse-threadx/rtos-docs/blob/main/rtos-docs/threadx-modules/chapter1.md____
>
>     https://github.com/eclipse-threadx/threadx/tree/master/common_modules____
>
>     https://github.com/eclipse-threadx/threadx/tree/master/ports_module____
>
>     __ __
>
>     A Module is separately built (compiled/linked) application code
>     containing one or more threads. It can be loaded dynamically or
>     reside in place. Since it has its own distinct address space
>     (instruction and data), memory protection (MMU or MPU) can be used
>     to isolate its access from the rest of the application. There is
>     also some time-domain protection by limiting the priority of threads
>     running in the context of a module.____
>
>     __ __
>
>     I hope this helps!____
>
>     __ __
>
>     Best regards,____
>
>     __ __
>
>     Bill____
>
>     __ __
>
>     __ __
>
>     *From:*threadx-dev <threadx-dev-bounces@xxxxxxxxxxx
>     <mailto:threadx-dev-bounces@xxxxxxxxxxx>> *On Behalf Of *Skinner,
>     Mike (UK1Y) via threadx-dev
>     *Sent:* Thursday, July 18, 2024 2:13 AM
>     *To:* threadx-dev@xxxxxxxxxxx <mailto:threadx-dev@xxxxxxxxxxx>
>     *Cc:* Skinner, Mike (UK1Y) <Mike.Skinner@xxxxxxxxxxxxx>
>     *Subject:* [threadx-dev] ThreadX - Feature extension plans____
>
>     __ __
>
>     Hello everyone,____
>
>     __ __
>
>     First post here but a long time user of ThreadX. Interesting news
>     that ThreadX is being brought into the open source community. I am
>     still reading through the announcements and related documentation
>     but I am interested in understanding how the Functional safety
>     certification will be maintained and at what frequency, and who will
>     bear the costs for this?____
>
>     __ __
>
>     Would it be that users of the RTOS as they incorporate new features
>     would be expected to re-certify these changes, or will the
>     certification be kept up to date in some other way?____
>
>     __ __
>
>     My apologies for being greedy but I also had a further question on
>     any future features that may be being considered. I know from my
>     previous experience with ThreadX that there were ongoing efforts to
>     provide a “thread isolation” module such that it was guaranteed (and
>     more importantly assessed and certified to be the case!) that the
>     resources or any errors etc in one thread would not have any effect
>     on other threads. This would allow, in functional safety terms,
>     “functionally safe” code to run in one (or more threads) and for
>     “non safe” code to run on another thread without danger of
>     interference to the safe code even while operating on the same MCU.
>     Is there any ongoing development effort to provide this feature and
>     certify it?____
>
>     __ __
>
>     Thank you for your consideration and I am excited to see what the
>     future brings!____
>
>     Mike____
>
>     __ __
>
>     *Mike Skinner*____
>
>     Senior Advanced Embedded Engineer
>     *Honeywell*| PMC____
>
>     Office: +44 1202 645556
>
>     Mike.Skinner@xxxxxxxxxxxxx <mailto:Mike.Skinner@xxxxxxxxxxxxx>____
>
>     HoneywellAnalytics.com <http://www.honeywellanalytics.com/>____
>
>     ____
>
>     This email, its content and any files transmitted with it are
>     intended solely for the addressee(s), are confidential, subject to
>     copyright and may be legally privileged and/or confidential. If you
>     are not the intended recipient please delete and contact the sender
>     on the telephone number shown above or via email return. Unless
>     expressly stated otherwise, and subject to the disclaimer below,
>     this email does not form part of a legally binding contract or
>     agreement between the recipient and City Technology Limited.
>     (Registered no. 1326515 (England)).  Registered Office: Honeywell
>     House, Skimped Hill Lane, Bracknell, Berkshire, RG12 1EB, England.
>     E-mail cannot be guaranteed to be secure, error free or free from
>     viruses. Neither the sending company nor its group of companies
>     accepts any liability whatsoever for any loss or damage which may be
>     caused as a result of the transmission of this message by e-mail. If
>     verification is required, please request a hard copy version.  Any
>     opinions or recommendations expressed herein are solely those of the
>     author.____
>
>     __ __
>
>     _______________________________________________
>     threadx-dev mailing list
>     threadx-dev@xxxxxxxxxxx <mailto:threadx-dev@xxxxxxxxxxx>
>     To unsubscribe from this list, visit https://accounts.eclipse.org
>
>
>
> _______________________________________________
> threadx-dev mailing list
> threadx-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://accounts.eclipse.org