/nrf52832-nimble/packages/NimBLE-latest/docs/ble_hs/ |
H A D | ble_att.rst | 9 must support both the client and server functionality of the ATT protocol. The only devices which d… 12 Most ATT functionality is not interesting to an application. Rather than use ATT directly, an appli… 13 …rofile, which sits directly above ATT in the host. NimBLE exposes the few bits of ATT functionality 14 …passed by higher level GATT functions. This section documents the ATT functionality that the NimBLE
|
/nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/ |
H A D | syscfg.yml | 215 Automatically enable LPN functionality once provisioned and start 347 Mesh functionality. 353 Bluetooth Mesh functionality. 359 Bluetooth Mesh functionality. 365 Bluetooth Mesh functionality. 371 Bluetooth Mesh functionality. 377 Bluetooth Mesh functionality. 395 the Bluetooth Mesh functionality. 401 Bluetooth Mesh functionality. 407 Bluetooth Mesh functionality. [all …]
|
/nrf52832-nimble/nordic/nrfx/mdk/ |
H A D | nrf52_to_nrf52810.h | 39 …* It redefines the old nRF51 or nRF52832 names into the new ones as long as the functionality is s… 40 …* functionality is gone, there old names are not defined, so compilation will fail. Note that also… 46 …SPIM1_SPIS1_TWIM1_TWIS1_SPI1_TWI1_IRQHandler are not redefined since functionality is not equivale… 55 … SPIM1_SPIS1_TWIM1_TWIS1_SPI1_TWI1_IRQn are not redefined since functionality is not equivalent. */
|
H A D | nrf52_to_nrf52840.h | 39 …* It redefines the old nRF51 or nRF52832 names into the new ones as long as the functionality is s… 40 …* functionality is gone, there old names are not defined, so compilation will fail. Note that also…
|
H A D | system_nrf52840.c | 59 …/* Enable SWO trace functionality. If ENABLE_SWO is not defined, SWO pin will be used as GPIO (see… in SystemInit() 67 …/* Enable Trace functionality. If ENABLE_TRACE is not defined, TRACE pins will be used as GPIOs (s… in SystemInit()
|
H A D | nrf51_to_nrf52810.h | 39 …* It redefines the old nRF51 names into the new ones as long as the functionality is still support… 40 …* functionality is gone, there old names are not defined, so compilation will fail. Note that also…
|
H A D | nrf51_to_nrf52840.h | 39 …* It redefines the old nRF51 names into the new ones as long as the functionality is still support… 40 …* functionality is gone, there old names are not defined, so compilation will fail. Note that also…
|
H A D | system_nrf52.c | 63 …/* Enable SWO trace functionality. If ENABLE_SWO is not defined, SWO pin will be used as GPIO (see… in SystemInit() 71 …/* Enable Trace functionality. If ENABLE_TRACE is not defined, TRACE pins will be used as GPIOs (s… in SystemInit()
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ |
H A D | sys.c | 57 * lwIP functionality, multiple threads support can be implemented in the 59 * functionality. Timer scheduling is implemented in lwIP, but can be implemented 62 * In addition to the source file providing the functionality of sys_arch,
|
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/ |
H A D | sys_arch.txt | 13 lwIP functionality, multiple threads support can be implemented in the 15 functionality. Previous versions of lwIP required the sys_arch to 19 In addition to the source file providing the functionality of sys_arch, 168 such functionality is needed in lwIP, the following function will have
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/ |
H A D | sys_arch.txt | 14 lwIP functionality, multiple threads support can be implemented in the 16 functionality. Timer scheduling is implemented in lwIP, but can be implemented 19 In addition to the source file providing the functionality of sys_arch, 201 such functionality is needed in lwIP, the following function will have
|
/nrf52832-nimble/packages/NimBLE-latest/docs/mesh/ |
H A D | index.rst | 65 Models define basic functionality of nodes on a mesh network. Mesh Profile Specification defines fo… 66 to configure and manage network. Mesh Model Specification includes models defininig functionality t…
|
/nrf52832-nimble/packages/NimBLE-latest/nimble/ |
H A D | pkg.yml | 21 pkg.description: Generic functionality for the nimble Bluetooth Smart stack; used by both the contr…
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/apps/snmp/ |
H A D | snmpv3_priv.h | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826 (internal API, do not use in client code).
|
H A D | snmpv3.c | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826.
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/apps/snmp/ |
H A D | snmpv3_priv.h | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826 (internal API, do not use in client code).
|
H A D | snmpv3.c | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826.
|
/nrf52832-nimble/rt-thread/components/net/uip/rt-thread/ |
H A D | clock-arch.c | 36 * Implementation of architecture-specific clock functionality
|
/nrf52832-nimble/rt-thread/components/net/uip/unix/ |
H A D | clock-arch.c | 36 * Implementation of architecture-specific clock functionality
|
/nrf52832-nimble/rt-thread/components/net/uip/uip/ |
H A D | uip_clock.h | 5 * and the platform specific clock functionality. The clock
|
/nrf52832-nimble/rt-thread/components/net/uip/ |
H A D | uip-1.0-changelog.txt | 8 * Removed uIP zero-copy functionality in order to simplify uIP device
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/include/lwip/apps/ |
H A D | snmpv3.h | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826.
|
/nrf52832-nimble/packages/NimBLE-latest/porting/nimble/src/ |
H A D | os_cputime_pwr2.c | 23 * This module implements cputime functionality for timers for which:
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/apps/ |
H A D | snmpv3.h | 3 * Additional SNMPv3 functionality RFC3414 and RFC3826.
|
/nrf52832-nimble/rt-thread/tools/kconfig-frontends/docs/ |
H A D | kconfig-language.txt | 422 It is a common idiom to implement a feature/functionality that are 427 An example is the generic IOMAP functionality. 440 For each architecture using the generic IOMAP functionality we would see:
|