- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
it there a plan to support also MQX RTOS in WICED SDK (beside FreeRTOS and ThreadX)?
Thank you, Klemen
Solved! Go to Solution.
- Labels:
-
SPI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, it's not marketing gimmick. We've had feedbacks from customers who completed the exercise in mere 1 or 2-man days. The duration obviously varies and really depends to the individual, but porting a new RTOS is commonly done and clearly defined API helps a huge deal.
If you're using WICED-SDK-2.4.1, take a look at the following files and directories for clues:
<WICED-SDK>/include/wiced_rtos.h - contains WICED-level RTOS API declaration
<WICED-SDK>/Wiced/WWD/include/RTOS/wwd_rtos_interface.h - contains WWD-level RTOS API declaration
<WICED-SDK>/Wiced/RTOS/ThreadX
<WICED-SDK>/Wiced/RTOS/FreeRTOS
Note that ThreadX is only bundled with NetX or NetX Duo while FreeRTOS is bundled with LwIP. I'm not sure with LwIP already has support MQX though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, there's no short-term plan to add support for MQX RTOS a the moment.
WICED SDK has clearly-defined RTOS abstraction API which makes effort of adding a new RTOS support easier. You're welcome to contribute to the code base if you're will spend the porting effort
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Gerdiman
Your comment:
"WICED SDK has clearly-defined RTOS abstraction API which makes effort of adding a new RTOS support easier"
sounds like a marketing line, but realistically probably a lot've work?
- How many hours would you consider this task to be?
Can you possibly provide some guidelines / a short checklist of what needs to be taken care of-/potential gotchas,etc when porting the underlying RTOS from ThreadX to MQX...?
Thanks
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, it's not marketing gimmick. We've had feedbacks from customers who completed the exercise in mere 1 or 2-man days. The duration obviously varies and really depends to the individual, but porting a new RTOS is commonly done and clearly defined API helps a huge deal.
If you're using WICED-SDK-2.4.1, take a look at the following files and directories for clues:
<WICED-SDK>/include/wiced_rtos.h - contains WICED-level RTOS API declaration
<WICED-SDK>/Wiced/WWD/include/RTOS/wwd_rtos_interface.h - contains WWD-level RTOS API declaration
<WICED-SDK>/Wiced/RTOS/ThreadX
<WICED-SDK>/Wiced/RTOS/FreeRTOS
Note that ThreadX is only bundled with NetX or NetX Duo while FreeRTOS is bundled with LwIP. I'm not sure with LwIP already has support MQX though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Comment on LwIP…. MQX has its own TCP/IP stack implementation called RTCS. No need for LwIP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the info