This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/RM48L930: Is TI-RTOS supported on Hercules RM48Lx30 family uCs?

Part Number: RM48L930

Tool/software: TI-RTOS

Support Path: /Product/Help with Device Selection/

Hello,

A newbie question:  is TI-RTOS (or some version of DSP/BIOS) supported on the Hercules RM48Lx30 family uCs?  If so, what is the most recent version that supports the RM48Lx30?  Also, can you point me to a sample RTOS-enabled project for the Hercules RM48 HDK dev board?

thank you,

Keith

  • I am not a TI support person, just a client. The RM48L930 is likely supported by HalCoGen. It would likely mean that supported versions of FreeRTOS could be available simply by using HalCoGen with selected options.
  • Thanks for your feedback, I do see the FreeRTOS target in HALCoGen. But I would like to use TI-RTOS if available. Why would it not be available on Hercules ICs?
  • I do not know for sure that it is not available. The RM48L930 is a class of safety controller. Using established tools is easier when trying to have the product validated by safety critical review organizations. If you just want to build something for fun on your desk, then TI-RTOS might be a neat experiment. If you want to claim safety compliance, then HalCoGen and other standardized (well established) approaches would be for the best. Making it easier to be validated by external agencies.
  • Hello Keith,

    TI-RTOS does not support the Hercules products.

    As Neil has pointed out, we include a Free RTOS example in Halcogen. Other than the fact that it is free, the Free RTOS OS is very similar to SafeRTOS which is why we have included it in Halcogen so there can be a natural migration to a safety compliant RTOS.

    I want to add some detail and explanation to clarify some points made by Neil regarding use of established tools. Dependent on the safety standards to which you are going to apply, there will be standard specific requirements for qualifying any software used in the project and any tool used that can have a direct impact on the safety of the system. TI offers our Halcogen tool for the generation of the HW abstraction layer of the code. We also offer a SafeTI Diagnostic library and for automotive applications, we offer an MCAL which is similar to the HAL but compliant with the AUTOSAR standards. The key for all of these tools is to be able to provide evidence to the assessor of your project to demonstrate compliance to the safety standard required for your application.

    Our software/drivers were developed according to a process that was certified to ISO26262 and IEC61508. This does not mean our software is certified, but it does mean that we can provide evidence to show compliance to those standards and that can be used as part of the qualification of the SW for use in your project. This evidence is generated using our Compliance Support Packages which, in the case of the HAL and SafeTI Diagnostic Library SW, includes a limited license for the LDRA tool and a Test Automation Unit (TAU) that can be used to regression test the generated/supplied SW in your development environment.

    Note that there are limits to what the evidence and the software can be used for. For example, we do not comply with DO178b standards for SW so any requirement for this type of compliance would require significant work to make the code compliant to that standard.

    Finally to get back to the topic of the RTOS, this is a complex entity and beyond the scope of our efforts as the RTOS' that support Hercules such as SafeRTOS, Micrium, Sciopta, etc. are all 3rd party tools that carry with them their own targeted certification requirements.

    I hope this clears up any questions about available software and why there are limitations to which can be used to support the Hercules family of MCUs.
  • Chuck, thanks for your detailed explanation!