@@ -892,6 +892,8 @@ asyncio.run(queue_go(4))
892
892
893
893
## 3.6 ThreadSafeFlag
894
894
895
+ This requires firmware V1.15 or later.
896
+
895
897
This official class provides an efficient means of synchronising a task with a
896
898
truly asynchronous event such as a hardware interrupt service routine or code
897
899
running in another thread. It operates in a similar way to ` Event ` with the
@@ -974,11 +976,6 @@ tasks may wait on that `Event`. As an alternative to explicitly coding this,
974
976
the [ Message class] ( ./TUTORIAL.md#39-message ) uses this approach to provide an
975
977
` Event ` -like object which can be triggered from an ISR.
976
978
977
- #### Note
978
-
979
- ThreadSafeFlag is only available in nightly builds. It will be available in
980
- release builds starting with V1.15.
981
-
982
979
###### [ Contents] ( ./TUTORIAL.md#contents )
983
980
984
981
## 3.7 Barrier
@@ -1188,6 +1185,8 @@ finally:
1188
1185
1189
1186
## 3.9 Message
1190
1187
1188
+ This requires firmware V1.15 or later.
1189
+
1191
1190
This is an unofficial primitive with no counterpart in CPython asyncio. It uses
1192
1191
[ ThreadSafeFlag] ( ./TUTORIAL.md#36-threadsafeflag ) to provide an object similar
1193
1192
to ` Event ` but capable of being set in a hard ISR context. It extends
@@ -1275,11 +1274,6 @@ async def main():
1275
1274
asyncio.run(main())
1276
1275
```
1277
1276
1278
- #### ThreadSafeFlag dependency
1279
-
1280
- ThreadSafeFlag is only available in nightly builds. It will be available in
1281
- release builds starting with V1.15.
1282
-
1283
1277
## 3.10 Synchronising to hardware
1284
1278
1285
1279
The following hardware-related classes are documented [ here] ( ./DRIVERS.md ) :
0 commit comments