| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 17 \sa \ref apps "Application programs"
23 \sa \ref uipappfunc "uIP functions called from application programs"
61 for any specific application.
68 addresses, to application level protocols such as SMTP that is used to
71 application". Lower layer protocols are often implemented in hardware
96 communication between the application and the networking stack. An
100 application." A TCP/IP implementation that violates requirements of
108 removed certain mechanisms in the interface between the application
126 or the application for which the incoming packet was intended may have
191 application. Because the data in the buffer will be overwritten by the
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
| H A D | main.html | 21 <dl compact><dt><b>See also:</b></dt><dd><a class="el" href="a00143.html">Application programs</a> …
26 <a class="el" href="a00147.html">uIP functions called from application programs</a> (see below) and…
32 …s. The uIP TCP/IP implementation that is not tailored for any specific application.<h2><a class="a…
34 …application level protocols such as SMTP that is used to transfer e-mail. The uIP is mostly concer…
37 …application and the networking stack. An example of the first kind is "A TCP MUST be able to recei…
38 … size, we have removed certain mechanisms in the interface between the application and the stack, …
44 …ever block, but will return at once. When it returns, the stack or the application for which the i…
56 …application. Because the data in the buffer will be overwritten by the next incoming packet, the a…
57 …application sends dynamic data, it may use the parts of the global packet buffer that are not used…
59 Application Program Interface (API)</a></h2>
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/ |
| H A D | rawapi.txt | 5 lwIP provides three Application Program's Interfaces (APIs) for programs
21 code and the application program must reside in different execution
39 from pbuf- and memory management functions). Application threads using
74 The raw TCP/IP interface allows the application program to integrate
77 code. The TCP/IP code and the application program both run in the same
80 on the application.
84 development is somewhat harder and application programs written for
89 All APIs can be used simultaneously by different application
90 programs. In fact, the sequential API is implemented as an application
105 invoked by the lwIP core when activity related to that application
[all …]
|
| /nrf52832-nimble/rt-thread/documentation/doxygen/ |
| H A D | module.h | 6 * @defgroup Module Application Module
8 * @brief Application Module is a feature let user to execute application in RT-Thread RTOS.
10 * Application Module is implemented as dynamic object loader, but it can handle
11 * the dependences relationship between application and dynamic library, moreover,
12 * it also can handle the kernel object destroy and memory release issue when application
|
| /nrf52832-nimble/nordic/nrfx/drivers/include/ |
| H A D | nrfx_ppi.h | 58 …t)0xFFFFFFFFuL & ~(NRFX_PPI_CHANNELS_USED)) /**< All PPI channels available to the application. */
59 …FFFuL & ~(NRFX_PPI_CHANNELS_USED)) /**< Programmable PPI channels available to the application. */
61 …t)0xFFF0FFFFuL & ~(NRFX_PPI_CHANNELS_USED)) /**< All PPI channels available to the application. */
62 …FFFuL & ~(NRFX_PPI_CHANNELS_USED)) /**< Programmable PPI channels available to the application. */
65 …_GROUP_NUM) - 1) & ~(NRFX_PPI_GROUPS_USED)) /**< All PPI groups available to the application. */
184 * @retval NRFX_ERROR_INVALID_PARAM If group is not an application group or channels are not an
185 * application channels.
198 * @retval NRFX_ERROR_INVALID_PARAM If group is not an application group or channel is not an
199 * application channel.
215 * @retval NRFX_ERROR_INVALID_PARAM If group is not an application group or channels are not an
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/ |
| H A D | rawapi.txt | 5 lwIP provides three Application Program's Interfaces (APIs) for programs
15 code and the application program must reside in different execution
31 this thread! Application threads using the sequential- or socket API
59 The raw TCP/IP interface allows the application program to integrate
62 code. The TCP/IP code and the application program both run in the same
65 on the application.
69 development is somewhat harder and application programs written for
74 Both APIs can be used simultaneously by different application
75 programs. In fact, the sequential API is implemented as an application
87 The function for setting the application connection state is:
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/ |
| H A D | main_page.h | 7 * lwIP provides three Application Program's Interfaces (APIs) for programs
13 * The raw TCP/IP interface allows the application program to integrate
16 * code. The TCP/IP code and the application program both run in the same
19 * on the application.
23 * development is somewhat harder and application programs written for
28 * All APIs can be used simultaneously by different application
29 * programs. In fact, the sequential API is implemented as an application
46 * invoked by the lwIP core when activity related to that application
47 * occurs. A particular application may register to be notified via a
50 * closed, etc. An application can provide a callback function to perform
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/modbus/include/ |
| H A D | mb.h | 46 * This module defines the interface for the application. It contains
48 * A typical application will want to call eMBInit() first. If the device
96 * reading or writing register values. Writing means that the application
213 * is given by the application dependent Modbus slave timeout. Internally the
278 * as an argument. The application should then read the actual register values
284 * to update the application register values.
302 * - eMBErrorCode::MB_ENOREG If the application can not supply values
306 * currently not available and the application dependent response
321 * \param pucRegBuffer If the application registers values should be updated the
327 * \param eMode If eMBRegisterMode::MB_REG_WRITE the application register
[all …]
|
| H A D | mb_m.h | 41 * This module defines the interface for the application. It contains
43 * A typical application will want to call eMBMasterInit() first. If the device
179 * is given by the application dependent Modbus slave timeout. Internally the
222 * as an argument. The application should then read the actual register values
228 * to update the application register values.
246 * - eMBErrorCode::MB_ENOREG If the application does not map an coils
259 * \param pucRegBuffer If the application registers values should be updated the
265 * \param eMode If eMBRegisterMode::MB_REG_WRITE the application register
269 * If the value eMBRegisterMode::MB_REG_READ the application should copy
275 * - eMBErrorCode::MB_ENOREG If the application does not map an coils
[all …]
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/mesh/ |
| H A D | sample.rst | 1 Sample application
4 **blemesh** sample application implements Bluetooth Mesh node that supports On/Off and Level models.
6 To build application use following target. Note that since this application uses Non-resolvable Pri…
28 GATT bearer is enabled so that it is possible to provision those with Bluetooth Mesh application fr…
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/apps/http/ |
| H A D | httpd_structs.h | 65 #define HTTP_HDR_APP HTTP_CONTENT_TYPE("application/octet-stream")
66 #define HTTP_HDR_JS HTTP_CONTENT_TYPE("application/javascript")
67 #define HTTP_HDR_RA HTTP_CONTENT_TYPE("application/javascript")
69 #define HTTP_HDR_SWF HTTP_CONTENT_TYPE("application/x-shockwave-flash")
71 #define HTTP_HDR_PDF HTTP_CONTENT_TYPE("application/pdf")
72 #define HTTP_HDR_JSON HTTP_CONTENT_TYPE("application/json")
106 …CONTENT_TYPES {"ct1", HTTP_CONTENT_TYPE("text/ct1")}, {"exe", HTTP_CONTENT_TYPE("application/exe")}
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/ble_setup/ |
| H A D | ble_sync_cb.rst | 10 occurs in under a second after the application starts. An application
19 Because the NimBLE stack begins in the unsynced state, the application
29 reset, the application should refrain from using the host until sync is
32 An application learns of a host reset by configuring the host's *reset
|
| /nrf52832-nimble/rt-thread/components/net/uip/uip/ |
| H A D | uip.h | 330 * processing. The application is polled for new data.
405 * \note The application data need not be placed in this buffer, so
427 /* Functions that are used by the uIP application program. Opening and
432 * \defgroup uipappfunc uIP application functions
435 * Functions used by an application running of top of uIP.
528 * application will be invoked with the uip_rexmit() event being
529 * set. The application will then have to resend the data using this
616 connection is, and what the application function should do. */
631 * Will reduce to non-zero if there is new data for the application
643 * acknowledged by the remote host. This means that the application
[all …]
|
| H A D | uip.c | 64 * UDP, TCP and the application layers very tightly. To keep the size
74 * application. If the remote host has sent data to the application,
75 * this data is present in the uip_buf and the application read the
76 * data from there. It is up to the application to put this data into
77 * a byte stream if needed. The application will not be fed with data
80 * If the application whishes to send data to the peer, it should put
149 application data. */
151 the application data which is to
167 and the application program. */
754 UIP_TIMEDOUT to inform the application that the in uip_process()
[all …]
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/include/host/ |
| H A D | ble_hs.h | 184 * Those can be used by application to configure stack.
188 * proper options in application's syscfg.
277 * function gets called to give the application the opportunity to make
331 * called during system initialization. This allows the application to
334 * If auto-start is disabled, the application should use this function to start
336 * is stopped. When the host successfully starts, the application is notified
343 * application is notified when the reset occurs via the host reset callback.
360 * started. The NimBLE stack requires an application task to function. One
361 * application task in particular is designated as the "host parent task". In
362 * addition to application-specific work, the host parent task does work for
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/httpd/ |
| H A D | httpd_structs.h | 65 #define HTTP_HDR_APP "Content-type: application/octet-stream\r\n\r\n"
66 #define HTTP_HDR_JS "Content-type: application/javascript\r\n\r\n"
67 #define HTTP_HDR_RA "Content-type: application/javascript\r\n\r\n"
69 #define HTTP_HDR_SWF "Content-type: application/x-shockwave-flash\r\n\r\n"
71 #define HTTP_HDR_PDF "Content-type: application/pdf\r\n\r\n"
72 #define HTTP_HDR_JSON "Content-type: application/json\r\n\r\n"
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/include/mesh/ |
| H A D | main.h | 90 * This callback notifies the application that it should
102 * This callback notifies the application that it should
113 * This callback notifies the application that it should
116 * the application needs to consequently call the
129 * This callback notifies the application that a provisioning
138 * This callback notifies the application that a provisioning
147 * This callback notifies the application that provisioning has
158 * This callback notifies the application that the local node
282 * This API should normally not be used directly by the application. The
|
| /nrf52832-nimble/packages/NimBLE-latest/porting/examples/linux/ |
| H A D | README.md | 35 1. Build the sample application
42 2. Run the sample application
57 Then run the application built in step one. The application is configured
|
| /nrf52832-nimble/nordic/nrfx/drivers/src/ |
| H A D | nrfx_ppi.c | 60 * @brief Check whether a channel is a programmable channel and can be used by an application.
64 * @retval true The channel is a programmable application channel.
74 * @brief Check whether channels can be used by an application.
78 * @retval true All specified channels can be used by an application.
89 * @brief Check whether a channel can be used by an application.
93 * @retval true The channel can be used by an application.
103 * @brief Check whether a channel group can be used by an application.
107 * @retval true The group is an application group.
108 * @retval false The group is not an application group (this group either does not exist or
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/ |
| H A D | UPGRADING | 3 application written for an older version of lwIP to correctly work
13 ++ Application changes:
48 ++ Application changes:
56 ++ Application changes:
65 ++ Application changes:
90 to let abc.h only contain the actual application programmer's API
145 ++ Application changes:
154 shutdown before): Now the application does *NOT* get any calls to the recv
182 the actual application programmer's API
|
| /nrf52832-nimble/rt-thread/libcpu/arm/cortex-r4/ |
| H A D | trap.c | 46 * @note never invoke this function in application
64 * @note never invoke this function in application
82 * @note never invoke this function in application
100 * @note never invoke this function in application
117 * @note never invoke this function in application
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ |
| H A D | altcp.c | 3 * @defgroup altcp Application layered TCP Functions
11 * @defgroup altcp_api Application layered TCP Introduction
16 * altcp (application layered TCP connection API; to be used from TCPIP thread)
19 * e.g. add SSL/TLS (see LWIP_ALTCP_TLS) or proxy-connect support to an application
20 * written for the tcp callback API without that application knowing the
23 * * This interface mimics the tcp callback API to the application while preventing
25 * * This way, an application can make use of other application layer protocols
38 * To make use of this API from an existing tcp raw API application:
48 * state may hold certificates or keys). This way, the application does not
51 * * An application can alternatively bind hard to the altcp_tls API by calling
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | altcp_tcp.h | 3 * Application layered TCP connection API (to be used from TCPIP thread)\n
4 * This interface mimics the tcp callback API to the application while preventing
6 * This way, an application can make use of other application layer protocols
|
| /nrf52832-nimble/rt-thread/libcpu/arm/zynq7000/ |
| H A D | trap.c | 44 * @note never invoke this function in application
63 * @note never invoke this function in application
81 * @note never invoke this function in application
99 * @note never invoke this function in application
116 * @note never invoke this function in application
|
| /nrf52832-nimble/rt-thread/libcpu/arm/lpc24xx/ |
| H A D | trap.c | 45 * @note never invoke this function in application
63 * @note never invoke this function in application
80 * @note never invoke this function in application
97 * @note never invoke this function in application
113 * @note never invoke this function in application
|