OMAP-L137: Porting TI-RTOS to FreeRTOS

Hello 
We regret the late response on this. Unfortunately OMAPL137 is now considered a legacy device with non new software/ collateral investment from past several years. There is no Free RTOS port available for the OMAPL1x/C67x family of devices. 

Hi Mukul,

Thank you, no worries. It is the hardware used for the current project. What do you mean by legacy? Is it TI  no longer produces the OMAP-137 hardware at all?  or is it the TI-RTOS that is legacy and there is no support for the TI-RTOS (which is what I was informed)? On the TI website it shows that we can still buy the hardware part and it is still advertised (i.e., https://www.ti.com/product/OMAP-L137/part-details/OMAPL137DZKBD4).  What did you mean?

TI-RTOS is what is running now on the OMAP-137 DSP hardware we have in the system now. I understand that there is no freeRTOS port now, only TI-RTOS. 

- Can FreeRTOS be ported and can it be run on the DSP (C67x) of the OMAP137? Or is there a feature on the DSP that would not allow another rtos like freeRTOS to run successfully on the DSP the way TI-RTOS does?

- Is it possible to get the DSP's TI-RTOS source code port and any additional documentation on the DSP to support the platform ourselves at the RTOS level? When I installed the BIOS, I did not see the source code files of the TI RTOS install and only saw some source code of drivers.  Since TI-RTOS is legacy and no longer supported, can we get the source code for the TI-RTOS port in the bios version we are using to this DSP from TI (by signing an NDA or whatever)?

Thank you again.

Hi Makul,

Thank you. I can explain why the persistence if this is helpful to discuss with your team to help. The reason we ask is it is your platform is implemented in a medical device and with the FDA's (US Government) new cybersecurity rules this year is the FDA (US Government agency) it was discovered, will reject the submission (will not allow us to sell our product with your system) if the software is not supported (like your case of the BIOS DSP that you stopped supporting but you have not made the code available) and the engineering company making the submission like ours does not have the source code to prove to the Government that if an issue arose later, we would have the ability to fix it in the code. Do you see what I mean?

Thank you we will check the links above and see if that has what we are using from your DSP BIOS and C6000 libs.

i.e., Our application included header files from your solution that included i.e., clk.h, c64.h, sem.h, ecm.h, tsk.h, hwi.h, exc.h, mbx.h, mem.h, swi.h  and log.h (in the include directory) but we cannot show the FDA we have the corresponding C code files today -- and that is the root problem and why this is urgent. Any version TI can supply will be helpful of code corresponding to the header files that we can show the FDA is helpful, even if I have to do some clean up.  We are using bios version 5_42_0_7 (the header files are in packages->ti>bios->include). We can sign whatever NDA your team needs if you can track down the code corresponding to these header files or whatever versions you can find, so we can make the FDA submission for our medical device and have it approved. With no FreeRTOS  option already available that would allow a quick port to save the submission, is why you checking internally with your team on this is so helpful.

Thank you again for checking on your side, and I will browse through the links above in meantime.  Thank you again for taking the time. 

Thanks for the background. I will ask around internally , if anything is available.

Hi Mukul,  Thank you so much. Just to update you, we tried building the sysbios-master code you sent link for and downloaded using attached bios.mk we configured for the OMAP-137/C6000. But it errors out as shown below but there were also no instructions that came with it for what combo of tools to use to build it. The download came with a ->packages->ti>bios directory, but the code in include header files were different then what is in 5_42_0_07 include header files of the same name.

We also downloaded your latest version off of your website 6_76_03_28  (in case it was the version we had used to design this device that came with no code, but a later one would have the code) but  the install included no ->packages->ti>bios directory  and tried building with same make file for the OMAP137, but it fails also though in a different way but also no details on combo of tools used to get it to build. Same bios.mak. But installation there is no ->packages->ti>bios directory like there is in 5_42_0_07 directory so no lib and no include directory to interface with. Should a Bios directory be created upon installation or is it generated by the 'gmake -f bios.mak' command?

The version we are using 5_42_0_07 has no build.mk or source files when we installed it (but it has a bios directory with the include header files). If would be helpful to get 5_42_0_07 with the source files and build.mk tree.

The other versions like above you suggested came with build.mk ands source files  do not compile successfully for our OMAP137/C674 platform for the version of compiler and xdc tools we are using for 5_42_0_07 and one has no bios directory (where should the  ->packages->ti>bios have come from? generated somehow or should it have been part of installation?) and the other had bios directory but header file code interface is different then 5_42_0_07's (which is Ok if I have to update the application code to new APIs for functions, if it can build and work). 

We will wait to hear if you/team can just get us any building version that can run on OMAP-137/C674 DSP that we can demonstrate that builds for this hardware and works for this part to the FDA.(i.e., is there only a specific co'smbination of specific version of bios with specific version of xdc tools with specific  version of C6000 compiler that would result in a successful  'gmake -f bios.mak' command for the OMAP137/C674)  We cannot just show the FDA (Government) source code, we have to prove that it builds and we linked it into our CCS project, etc.  If your team located 5_52_0_07 with its source tree like the other ones and associated build.mk set up, that would be very helpful or any other combination that would work. Thank you again for your attention to this urgent matter for our company. 

bios.zip

Thank you Mukul. I will start downloading other versions and see while you are working to track down 5_42_0_07.  Thank you again.

Hi Mukul Good news, I was able to get the BIOS 5 based application code ported over to both SYS/BIOS 6 (that is the install where we have full code and can rebuild) and Freertos on the DSP (with a lot of effort LOL)  to the OMAP-137 with your links so we will try to port now from TI-RTOS to FreeRTOS using the driver code source in your links to spring board from to complete the submission. If you have other customers in the same situation as us and need to switch to Freertos, please feel free to give them my contact info on here and I can help explain to them how to get it working with FreeRTOS. Thank you again for all your great support.  

Hi Mukul, Thank you. Yes you are right. LOL. Yes please feel free to contact me anytime. Thank you again.