Why still FreeRTOS 8.2.0

cherenkov11
Posts: 5
Joined: Fri Jul 07, 2017 5:59 am

Why still FreeRTOS 8.2.0

Postby cherenkov11 » Tue Jul 18, 2017 2:16 am

Investigating the ESP-IDF files in github I realized that the version of FreeRTOS is still 8.2.0, does anyone know if there are any plans to upgrade to version 9.0.0?

User avatar
kolban
Posts: 1683
Joined: Mon Nov 16, 2015 4:43 pm
Location: Texas, USA

Re: Why still FreeRTOS 8.2.0

Postby kolban » Tue Jul 18, 2017 2:32 am

What are the hilights that one would get from a 9.0.0 release?
Free book on ESP32 available here: https://leanpub.com/kolban-ESP32

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: Why still FreeRTOS 8.2.0

Postby WiFive » Tue Jul 18, 2017 2:37 am

Because there were a lot of changes introduced to support dual core SMP so it would be a complex merge.

ESP_Sprite
Posts: 9835
Joined: Thu Nov 26, 2015 4:08 am

Re: Why still FreeRTOS 8.2.0

Postby ESP_Sprite » Tue Jul 18, 2017 6:02 am

As WiFive says. We're not averse to backporting 9.0.0 features to 8.2.0 (and have done that in the past); if you're missing certain features, just put a feature request issue up on our Github.

samsam
Posts: 50
Joined: Sun Jun 04, 2017 5:26 pm

Re: Why still FreeRTOS 8.2.0

Postby samsam » Tue Jul 18, 2017 5:39 pm

What is the story about vTimerSetTimerID? I cant see it in my local esp-idf installation?

And also cant search the forum here if was discussed already, because the search returns some weird result:
The following words in your search query were ignored because they are too common words: vtimersettimerid.
You must specify at least one word to search for. Each word must consist of at least 3 characters and must not contain more than 14 characters excluding wildcards.
Anyway, I think is good feature to have and if was not discussed or rejected already I would put it in the Feature request list?

User avatar
kolban
Posts: 1683
Joined: Mon Nov 16, 2015 4:43 pm
Location: Texas, USA

Re: Why still FreeRTOS 8.2.0

Postby kolban » Tue Jul 18, 2017 5:59 pm

For searching in the forum, a good technique is to use Google as follows.

1. Go to Google.
2. Search on:

site:esp32.com YourPhrase and Keywords Here

This performs a Google search restricted to content in ESP32.com (this forum).
Free book on ESP32 available here: https://leanpub.com/kolban-ESP32

samsam
Posts: 50
Joined: Sun Jun 04, 2017 5:26 pm

Re: Why still FreeRTOS 8.2.0

Postby samsam » Wed Jul 19, 2017 4:21 am

The forum's search engine should be better than Google for the local content as those are not static pages I guess, but some sort of database. Not quite sure how good is Google's bot in indexing dynamic pages ? At least right now (12 hours after my posting, so there should be at least one match - the one I posted), but the result is :

"Your search - vTimerSetTimerID site:esp32.com - did not match any documents

will give some more time the bot to visit the esp32.com and will try again couple days later ;)

ESP_Sprite
Posts: 9835
Joined: Thu Nov 26, 2015 4:08 am

Re: Why still FreeRTOS 8.2.0

Postby ESP_Sprite » Thu Jul 20, 2017 1:38 am

If you have a reason you want this, just open up an issue on Github (or, for more speed and chance of inclusion, port it to esp-idf yourself and make a pull request) and we'll take a look at this.

samsam
Posts: 50
Joined: Sun Jun 04, 2017 5:26 pm

Re: Why still FreeRTOS 8.2.0

Postby samsam » Thu Jul 20, 2017 2:05 am

I already open Feature request on Github, but tried not to make inadvertently spam by checking first if was already discussed (no help so far neither from forum's search nor Google).
I'm pretty newbie to Github, so will need some time to become confident that will not make more harm than good and for sure will go this way in the future ;) just now have some higher priority problems to solve first :(

samsam
Posts: 50
Joined: Sun Jun 04, 2017 5:26 pm

Re: Why still FreeRTOS 8.2.0

Postby samsam » Thu Jul 20, 2017 2:10 am

BTW is there any schedule for current FreeRTOS modules/functions that are included in the esp-idf distrubution, but are marked as "UNTESTED", to be cleared, or also have to post a "Feature request" on Github?

Who is online

Users browsing this forum: No registered users and 76 guests