शैडोइंग अभ्यास: Introduction to RTOS Part 1 - What is a Real-Time Operating System (RTOS)? | Digi-Key Electronics - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

हर मोड पूरी स्क्रीन का अभ्यास कक्ष खोलता है।

119 वाक्य

यदि वाक्य बहुत छोटे या लंबे हों, तो समायोजित करने के लिए Edit पर क्लिक करें।

A real-time operating system, or RTOS, is very much like any other operating system with a few important differences.

Over the next few videos, I'd like to talk about those differences and how to get started using free RTOS.

We'll go over tasks, threads, prioritization, memory management, and intertask communication.

Let's get started.

An operating system is a piece of software that runs on a computer or microcontroller that accomplishes a number of important functions.

First, it is in charge of scheduling background tasks and user applications.

In most operating systems, dozens of background processes are executing at the same time,

and you probably have several applications open on your phone or computer right now.

The operating system figures out how to give slices of time to each of these processes

so that everything appears to be happening concurrently.

Second, it manages a number of virtual resources like files, libraries, and folders, allowing applications and processes to access them when needed.

Third, they can manage or provide device drivers for your system.

These drivers allow the system to read and write from an external disk, respond to keyboard and mouse input or draw graphics on your monitor.

You're probably familiar with general purpose operating systems like Windows Mac OS and Linux iOS and Android also fall into this category.

Most general purpose operating systems are designed with human interaction as the most important feature.

So the scheduler is designed to prioritize such tasks

that may mean some timing deadlines can be missed or pushed back and a little lag in responsiveness,

especially if it's not really noticed by a human, is acceptable.

Additionally, the scheduler is often non-deterministic, which means we can't know exactly which task will execute when and for how long.

If you're making something that requires an OS and strict timing deadlines, like a medical device or engine controller,

missing a deadline to say fire a spark plug would be catastrophic.

This is where a real-time operating system or RTOS can save the day.

Most RTOS's offer many of the same functions as general purpose operating systems

but they are designed so that the scheduler can guarantee meeting timing deadlines on the tasks.

While some RTOS's might provide high-level device drivers,

you'll usually see things intended for microcontrollers like Wi-Fi and Bluetooth stacks or simple LCD drivers.

You can also find bare bones RTOS's that provide just a scheduler.

With these, you'll need to import or write your own file systems and device drivers.

Note that while most RTOS's provide methods for meeting timing deadlines, that's not the only reason to use an RTOS in your project.

The ability to run multiple tasks concurrently can be a lifesaver as we'll see in a moment.

If you've written programs for microcontrollers, including Arduino, you're probably familiar with this kind of structure.

When your program starts, it performs some setup functions

and then it executes your tasks in a round robin fashion inside a while forever loop.

These tasks might read from sensors, perform some calculations based on those readings, and then say display something on a gorgeous LED display.

This type of simple programming architecture is known as a super loop.

It's incredibly easy to implement, has very little overhead, and is great when you only need to accomplish a handful of tasks on your microcontroller. In fact,

there's nothing wrong with the super loop for the vast majority

of simple microcontroller projects you're usually better off with this type of program flow as it saves on CPU cycles and memory

and it's much easier to debug than using an RTOS you

might even have created a couple of interrupts to break the

flow of execution to handle an external event like a button push or perform some action at specific timed intervals

If you need to meet strict timing deadlines for one or two tasks,

you might be better off using just interrupt service routines to accomplish those tasks with precise timing.

In my experience, if you need to meet a timing deadline of less than about one millisecond, your best bet is an interrupt anyway.

If you're trying to do something with an interval of less than a few hundred nanoseconds, you either need an incredibly fast processor,

or it's time to start looking at custom hardware like an FPGA.

Now, the unfortunate thing about this super loop architecture is that you cannot execute tasks concurrently.

If task two starts taking a long time and task three is your update display task, you'll start to experience some lag.

Similarly, if you're polling for user input like from a serial terminal or reading a sensor, you might miss data if other tasks take too long.

To fix that, we can use the concept of running multiple tasks at the same time.

On a multi-core processor, this is actually physically possible.

However, since many microcontrollers only have one core, the CPU time needs to be split up among the tasks.

We can also give higher priority to some tasks so that they happen sooner or take more CPU time.

For example, if we prioritize the user input task, users will likely experience less lag,

but it might mean background tasks take longer to execute.

We'll talk more about time slicing and prioritization in a future video.

Note the terminology used here.

A task is any piece of work we want to get done in code.

A thread is a unit of CPU utilization with its own program counter and set of memory.

A process is an instance of a computer program that's being executed.

Usually a process will have one or more threads used to accomplish tasks.

Threads within a process will often share resources like heap memory and can pass resources to each other.

You'll often find that in our toss is capable of handling only one process, but a general purpose OS can run many processes.

Note that in free our toss, the term task is used to mean something closer to a thread and you'll often see these terms used interchangeably.

Because of this, I will use the term task

when referring to units of CPU utilization so

that it makes sense within the free our toss ecosystem interrupts still work within an RTOS

so long as they have a higher priority than any of

the tasks they will stop code execution for all tasks run your interrupt service routine

and return execution to where it left off you can have more than one interrupt

but we won't get into handling nested interrupts which can get nasty

if you're writing code for a simple 8

or 16-bit microcontroller with 2 kilobytes of ram you're probably best sticking with the super loop approach

and using the inexpensive controller to do only a a handful of tasks.

While you can get a simple scheduler to run on such a device,

the memory and CPU overhead of switching tasks would not leave you with many resources left for your actual program.

People have ported free RTOS to the Arduino Uno.

It's definitely a good way to tinker around with it, but I don't know how ultimately useful it is.

As you move into more and more powerful microcontrollers, it becomes much more viable to run in RTOS as you've got clock cycles

and memory to spare for things like a scheduler.

While you can still run a bare metal super loop on something like an ESP32,

I usually find that the whole reason I bought something with that much computing power is to run several concurrent tasks.

Which brings me to the ultimate question of, why would you want an RTOS?

There are a number of reasons, but the best one that comes to mind is for when you need to do several things concurrently currently.

An ESP 32 is capable of handling user input, reading and writing to an SD card, controlling hardware, and crunching numbers all at the same time.

The big one for something like this is the wireless stack.

These libraries require large amounts of RAM and processing power.

They also need to respond to events from the network in a short amount of time, which means using an RTOS can be a massive help in this case.

It can help you divide up these different features into individual tasks.

An RTOS can be great if you're part of a team working on a larger project.

You can divide up the tasks among the team members, knowing that each one will run concurrently.

There will be some overhead and debugging to make sure everything works together though.

Over the next few videos, I'll go over important RTOS concepts like prioritization and resource management.

We'll practice these concepts by implementing small demo projects in Free RTOS on the ESP32.

The reason I chose Free RTOS for this series is because it's currently the most popular real-time operating system for IoT devices,

as shown by this 2018 survey from the Eclipse Foundation.

While Linux still reigns supreme for most of these devices, it and Windows are general purpose operating systems, with the exception of RT Linux.

You can see that the bare metal super loop architecture is still quite popular and an acceptable solution to many problems.

FreeRTOS is also free and open source, making it easy for you to try out.

100

Note that as of 2017, Amazon has taken over maintenance of the FreeRTOS project.

101

I also recommend keeping an eye on the Zephyr project as

102

it's a relative newcomer to the field backed by the Linux Foundation.

103

The ESP32 is a powerful IoT microcontroller that's packed with features.

104

Also, you can find inexpensive ESP32 development boards.

105

Any of them should work for this series as long as they have an associated Arduino package.

106

I know some of you will balk at the idea of using Arduino for our coding, but hear me out.

107

Most embedded programmers and electronics tinkerers will have some experience with Arduino, and if not, it's easy to learn.

108

Because of that, it creates a level playing field for anyone wanting to try out RTOS concepts.

109

I don't need to teach a vendor tool or chip-specific libraries on top of trying to teach free RTOS.

110

Because the ESP32 runs a modified version of FreeRTOS out of the box, there is hardly any setup involved in creating tasks in Arduino.

111

Almost every code example you see, including task management, semaphores, mutexes, and so on, can easily be ported to your own build system.

112

I'll try to point out where the ESPRTOS differs from vanilla FreeRTOS.

113

An RTOS may not be the right answer to every firmware problem you run across, but sometimes it is the right tool for the job,

114

especially when you need to do things like run concurrent tasks and meet timing deadlines.

115

At the end of most of these videos, I'll issue you a challenge,

116

and I encourage you to try it out on your own ESP32 or whatever device you're running free RTOS on.

117

I'll then post a link to my solution so that you can see how your solution compares.

118

In the next video I'll show you how to get started with free RTOS

119

and create your own task to blink an LED.

ऐप डाउनलोड करें

धाराप्रवाह बोलने के लिए ज़रूरी सब कुछ

AI उच्चारण स्कोरहर वाक्य का स्कोर

IPA अभ्यासहर ध्वनि में महारत

शब्दावलीअपना शब्द भंडार बनाएँ

शब्द गेमखेलते हुए सीखें

QR स्कैन करें

Download on theApp Store Get it onGoogle Play

उसी चैनल से

How To Read A Datasheet - Electronics with Becky Stern | DigiKey

Daily ConversationWorking Adults

FOR YOU

अनुशंसित वीडियो

324 वाक्य

IT System Administrator Interview Questions and Answers | How to Pass an IT System Admin Interview

Business EnglishInterview EnglishUniversity Students

540 वाक्य

Incremental Cooking in UE 5.7: A Dive Into the UE Cook Pipeline | Unreal Fest Chicago 2026

Business EnglishUniversity StudentsWorking Adults

49 वाक्य

What Are Microservices Really All About? (And When Not To Use It)

Business EnglishUniversity StudentsWorking Adults

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो में शैडोइंग के लिए 119 वाक्य और 1889 शब्द हैं। बोला गया हिस्सा 11:17 लंबा है। वक्ता लगभग 167 शब्द प्रति मिनट की स्वाभाविक गति से बोलता है, जो रोज़मर्रा की बातचीत के करीब है। केवल 78% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं, इसलिए शब्दावली कठिन है।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्द	उच्चारण	अर्थ
loop संज्ञा	/luːp/	कुंडली
interrupt क्रिया	/ˌɪntəˈɹʌpt/	टोकना
thread संज्ञा	/ˈθɹɛd/	धागा, सूत
resource संज्ञा	/ɹɪˈzɔːs/	संसाधन
accomplish क्रिया	/əˈkɑm.plɪʃ/	सफलता, उपलब्धि
architecture संज्ञा	/ˈɑː.kɪˌtɛk.t͡ʃə/	वास्तुकला, स्थापत्य
execution संज्ञा	/ˌɛk.sɪˈkjuː.ʃən/	निष्पादन, अमल
priority संज्ञा	/pɹaɪˈɒɹɪti/	अग्रिमता, प्राथमिकता
routine संज्ञा	/ɹuˈtin/	दिनचर्या
hardware संज्ञा	/ˈhɑɹdˌwɛɹ/	हार्डवेयर
acceptable विशेषण	/əkˈsɛp.tə.bəl/	स्वीकार्य
controller संज्ञा	/kənˈtɹoʊlɚ/	लेखानियंत्रक
divide क्रिया	/dɪˈvaɪd/	बांटना
stack संज्ञा	/stæk/	धुआँरा
interval संज्ञा	/ˈɪntɚvəl/	अंतराल

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	are designed · is designed · can be missed
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	you've written · have created · have ported
Relative clauses who / which + उपवाक्य — व्यक्ति या वस्तु के बारे में अतिरिक्त जानकारी	deterministic, which means · interrupts which can · time, which means

ध्यान देने योग्य उच्चारण

वक्ता 31 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे you're, I'll, you'll। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।

“sh” और “zh” की ध्वनियाँ: accomplish /əˈkɑm.plɪʃ/, execution /ˌɛk.sɪˈkjuː.ʃən/, exception /əkˈsɛpʃən/, interaction /ˌɪn.təˈɹæk.ʃən/, calculation /ˌkælkjuˈleɪʃn̩/
लंबे शब्द — बलाघात सही रखें: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, execution /ˌɛk.sɪˈkjuː.ʃən/, priority /pɹaɪˈɒɹɪti/, incredibly /ɪŋˈkɹɛdɪbli/, acceptable /əkˈsɛp.tə.bəl/

इस वीडियो से अभ्यास कैसे करें

पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर loop, interrupt, thread जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: Introduction to RTOS Part 1 - What is a Real-Time Operating System (RTOS)? | Digi-Key Electronics - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

ऐप डाउनलोड करें

How To Read A Datasheet - Electronics with Becky Stern | DigiKey

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

What is an Organization? - the Nature of Organizations

Every LINUX Concept Explained in 8 Minutes.

Real-Time Digital Twins Using CFD, Sensors & AI - Haris Kokkinos | Podcast #165

The Ultimate IoT Roadmap in 2026? | Embedded Systems & IoT Career Roadmap

PLC Programming #5: User-Defined Data Types (UDTs) Explained

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

Object-Oriented UX (OOUX)

What is a Run@Rate? Meaning of a Run@Rate!