GitHubBecome a leader in the IoT community!
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
Step 1 of 5
CREATE YOUR PROFILE *Required
Step 2 of 5
WHAT BRINGS YOU TO DEVHEADS? *Choose 1 or more
Connect & collaborate 🤝with other tech professionals
Learn & Grow 📚
Contribute Experience & Expertise 🔧
Step 3 of 5
WHAT'S YOUR INTEREST OR EXPERTISE? *Choose 1 or more
Hardware Design 💡
Embedded Software 💻
Edge Networking ⚡
Step 4 of 5
Personalize your profile
Step 5 of 5
Read & agree to our COMMUNITY RULES
- We want this server to be a welcoming space! Treat everyone with respect. Absolutely no harassment, witch hunting, sexism, racism, or hate speech will be tolerated.
- If you see something against the rules or something that makes you feel unsafe, let staff know by messaging @admin in the "support-tickets" tab in the Live DevChat menu.
- No age-restricted, obscene or NSFW content. This includes text, images, or links featuring nudity, sex, hard violence, or other graphically disturbing content.
- No spam. This includes DMing fellow members.
- You must be over the age of 18 years old to participate in our community.
- You agree to our Terms of Service (https://www.devheads.io/terms-of-service/) and Privacy Policy (https://www.devheads.io/privacy-policy)
By clicking "Finish", you have read and agreed to the our Terms of Service and Privacy Policy.
specially for those basic apis
download the freertos book from freertos.org
It has a complete breakdown of all the features and helps yiu get started from scratch. That way you will be able to use it it in many contexts.
Yu can also check the official FreeRTOS website’s API reference page. Its easy to quickly look up individual functions and examples
There are even some demo projects provided in FreeRTOS, they will show how the basic APIs like task creation, delays, and how semaphores work in real applications
also atomic keywords provides thread safety in FreeRTOS too or we have to use MUTEX?
mutual exclusion isn’t really the same as atomicity. You woll use atomic keywords when you want an operation to be done all at once or none at all. Something like a database transaction. And you will use mutexes when you need to share but only one user of the resource at a time
I know that but atomicity can prevent the abnormal behaviour of a variable if multiple task want to access it
like prevent context switching in between an operation of a atomic variable
When when you want atomicity for a single variable or one flag you can use the atomic keywords. context switching really applies when you have a longer operation that you dont want interrupted. Whereas atomic is for simpler data types
CONTRIBUTE TO THIS THREAD