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.

TMS570LC4357: The VxWorks support on TMS570LC4357

Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMS570LS3137, , HALCOGEN, TMS570LS3137-EP

Dear Experts

Are the operating systems listed in below website the only choice that we have?

www.ti.com/.../tools-software.page

Do we have VxWorks and RTEMS support in Hercules?

If not, is there any 3rd party who can provide the service?

Thanks for your comment.

  • Hello, Jefferey,

    The currently supported operating systems are listed on this page: www.ti.com/.../tools_software.page

    Please refer to this thread about VxWorks and RTEM:
    e2e.ti.com/.../241104

    Regards,
    QJ
  • As you ask for RTEMS support as well, then older TMS570LS3137 / TMS570LS31 HDK is fully supported by RTEMS 4.11 release and mainline GIT code base.

    BSP directory

    git.rtems.org/.../tms570

    BSP README

    git.rtems.org/.../README

    RTEMS application image can be configured as standalone (tms570ls3137_hdk) with included hardware initialization TMS570_USE_HWINIT_STARTUP=1 when it starts from Flash address 0 and runs required peripherals setup and self-tests or chip initialization can be left on the loader. As part of other project ( rtime.felk.cvut.cz/.../ ), we have implemented automotive XCP protocol over ETHERNET loader.

    There is interest to enhance RTEMS TMS570 BSP to support TMS570LC4357 as well but it has low priority on my enthusiast wishes/work list. As for my our university department, it has even lower chance to be allowed by our head to invest my or others time to work on such project if there is no funding or contract.

    May it be some GSoC or other project/company can help. The BSP code should be well prepared for extension, pin multiplexer support is implemented to be TMS570LC4357 compatible and I have generated required define files as well. I have not committed them to the RTEMS mainline yet, because there are more TMS570LC4357 pieces missing and without these pieces and option to test (or some company commitment for this work) it only makes RTEMS less consistent.

    Preparing RTEMS TMS570LC4357 support with external loader, HW setup should be even more straightforward.

    Some problem is generation of registers definitions header files conforming to RTEMS style. We have tools for that but until now we have used tedious work to parse manuals in PDF format because direct use of Ti's XML registers definitions files from HalCoGen or debugger has not been declared by Ti as GPL compliant option.

    If you have interest contact me directly or over RTEMS project mailing-list.

    Best wishes,

    Pavel Pisa

    PS: I think that TMS570LC4357 and TMS570LS3137-EP are in pefect match with RTEMS and its target areas and I am surprised that Ti does not care much about that even when informed in the past. I have more question from space (RTEMS is one of a few ESA and NASA target OSes) and aerospace industry for this target but when chip manufacturer is not interested then support backed by enthusiasts free time only cannot be proposed for such projects.