You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Various Documentation Updates + bump version to SDK1.5.0-develop (#1220)
* minor cleanup of lwip+tinyusb docs, and bump sdk verison number to 1.5.0-develop
* Update cyw43_arch docs for async_context_use
* remove accidental copy of some comments
Copy file name to clipboardExpand all lines: src/rp2_common/pico_cyw43_arch/include/pico/cyw43_arch.h
+35-4Lines changed: 35 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -55,12 +55,28 @@ extern "C" {
55
55
*
56
56
* * \em 'poll' - This not multi-core/IRQ safe, and requires the user to call \ref cyw43_arch_poll periodically from their main loop
57
57
* * \em 'thread_safe_background' - This is multi-core/thread/task safe, and maintenance of the driver and TCP/IP stack is handled automatically in the background
58
+
* * \em 'freertos' - This is multi-core/thread/task safe, and uses a separate FreeRTOS task to handle lwIP and and driver work.
58
59
*
59
60
* As of right now, lwIP is the only supported TCP/IP stack, however the use of \c pico_cyw43_arch is intended to be independent of
60
61
* the particular TCP/IP stack used (and possibly Bluetooth stack used) in the future. For this reason, the integration of lwIP
61
62
* is handled in the base (\c pico_cyw43_arch) library based on the #define \ref CYW43_LWIP used by the \c cyw43_driver.
62
63
*
63
-
* Whilst you can use the \c pico_cyw43_arch library directly and specify \ref CYW$#_LWIP (and other defines) yourself, several
64
+
* \note As of version 1.5.0 of the Raspberry Pi Pico SDK, the \c pico_cyw43_arch library no longer directly implements
65
+
* the distinct behavioral abstractions. This is now handled by the more general \ref pico_async_context library. The
66
+
* user facing behavior of pico_cyw43_arch has not changed as a result of this implementation detail, however pico_cyw43_arch
67
+
* is now just a thin wrapper which creates an appropriate async_context and makes a simple call to add lwIP or cyw43_driver support
68
+
* as appropriate. You are free to perform this context creation and adding of lwIP, cyw43_driver or indeed any other additional
69
+
* future protocol/driver support to your async_context, however for now pico_cyw43_arch does still provide a few cyw43_ specific (i.e. Pico W)
70
+
* APIs still for connection management, locking and GPIO interaction.
71
+
*
72
+
* \note The connection management APIs at least may be moved
73
+
* to a more generic library in a future release. The locking methods are now backed by their \ref pico_async_context equivalents, and
74
+
* those methods may be used interchangeably (see \ref cyw43_arch_lwip_begin, \ref cyw43_arch_lwip_end and \ref cyw43_arch_lwip_check for more details).
75
+
*
76
+
* \note For examples of creating of your own async_context and addition of \c cyw43_driver and \c lwIP support, please
77
+
* refer to the specific source files \c cyw43_arch_poll.c, \c cyw43_arch_threadsafe_background.c and \c cyw43_arch_freertos.c.
78
+
*
79
+
* Whilst you can use the \c pico_cyw43_arch library directly and specify \ref CYW$#_LWIP (and other defines) yourself, several
64
80
* other libraries are made available to the build which aggregate the defines and other dependencies for you:
65
81
*
66
82
* * \b pico_cyw43_arch_lwip_poll - For using the RAW lwIP API (in `NO_SYS=1` mode) without any background processing or multi-core/thread safety.
@@ -145,7 +161,7 @@ extern "C" {
145
161
* which defaults to \c CYW43_COUNTRY_WORLDWIDE. Worldwide settings may not give the best performance; consider
146
162
* setting PICO_CYW43_ARCH_DEFAULT_COUNTRY_CODE to a different value or calling \ref cyw43_arch_init_with_country
147
163
*
148
-
* By default this method initializes the cyw43_arch code's own \ref async_context by calling
164
+
* By default this method initializes the cyw43_arch code's own async_context by calling
149
165
* \ref cyw43_arch_init_default_async_context, however the user can specify use of their own async_context
150
166
* by calling \ref cyw43_arch_set_async_context() before calling this method
151
167
*
@@ -161,7 +177,7 @@ int cyw43_arch_init(void);
161
177
* was enabled at build time). This method must be called prior to using any other \c pico_cyw43_arch,
162
178
* \c cyw43_driver or lwIP functions.
163
179
*
164
-
* By default this method initializes the cyw43_arch code's own \ref async_context by calling
180
+
* By default this method initializes the cyw43_arch code's own async_context by calling
165
181
* \ref cyw43_arch_init_default_async_context, however the user can specify use of their own async_context
166
182
* by calling \ref cyw43_arch_set_async_context() before calling this method
* \brief <a href="https://github.com/hathach/tinyusb">TinyUSB</a> Device-mode support for the RP2040
3
+
* <a href="https://github.com/hathach/tinyusb">TinyUSB</a> Device-mode support for the RP2040. The TinyUSB documentation site can be found <a href="https://docs.tinyusb.org/en/latest/">here</a>.
4
4
*
5
5
* \defgroup tinyusb_host tinyusb_host
6
-
* \brief <a href="https://github.com/hathach/tinyusb">TinyUSB</a> Host-mode support for the RP2040
6
+
* <a href="https://github.com/hathach/tinyusb">TinyUSB</a> Host-mode support for the RP2040.
0 commit comments