| /nrf52832-nimble/rt-thread/components/drivers/ |
| H A D | Kconfig | 4 bool "Using device drivers IPC"
14 bool "Using serial device drivers"
26 bool "Using CAN device drivers"
36 bool "Using hardware timer device drivers"
68 bool "Using I2C device drivers"
78 bool "Using generic GPIO device drivers"
82 bool "Using ADC device drivers"
86 bool "Using PWM device drivers"
90 bool "Using MTD Nor Flash device drivers"
94 bool "Using MTD Nand Flash device drivers"
[all …]
|
| /nrf52832-nimble/rt-thread/src/ |
| H A D | Kconfig | 61 bool "Using stack overflow checking"
232 bool "Using memory pool"
235 Using static memory fixed partition
238 bool "Using memory heap object"
241 Using memory heap object to manage dynamic memory heap.
290 bool "Using device object"
294 bool "Using ops for each device object"
304 bool "Using console for rt_kprintf"
|
| /nrf52832-nimble/rt-thread/components/utilities/ |
| H A D | Kconfig | 60 These log will not compile into ROM when using LOG_X api.
81 These log will not compile into ROM when using LOG_X api.
123 The log output API can using in ISR (Interrupt Service Routines) also.
140 …e another thread (Such as idle) will read the buffer and output the log. So it will using more RAM.
169 bool "Enable float number support. It will using more thread stack."
173 The default formater is using rt_vsnprint and it not supported float number.
211 The low level output using rt_kprintf().
|
| /nrf52832-nimble/rt-thread/components/dfs/ |
| H A D | Kconfig | 4 bool "Using device virtual file system"
12 bool "Using working directory"
30 bool "Using mount table for file system"
54 bool "Using RT_DFS_ELM_WORD_ACCESS"
107 bool "Using devfs for device objects"
156 bool "Using NFS v3 client file system"
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/ |
| H A D | savannah.txt | 1 Daily Use Guide for using Savannah for lwIP
6 2 - Committers/developers Git access using SSH
26 2 Committers/developers Git access using SSH
40 Try to login using SSH:
58 commit them. Make sure you know what you are doing when using Git to make
89 First, tag the release using Git: (I use release number 1.4.1 throughout
100 Archive the current directory using tar, gzip'd, bzip2'd and zip'd.
110 Upload these files using anonymous FTP:
|
| H A D | sys_arch.txt | 37 allows both using pointers or actual OS structures to be used. This way, memory
85 When using pointers, a simple way is to check the pointer for != NULL.
86 When directly using OS structures, implementing this may be more complex.
119 When using pointers, a simple way is to check the pointer for != NULL.
120 When directly using OS structures, implementing this may be more complex.
189 When using pointers, a simple way is to check the pointer for != NULL.
190 When directly using OS structures, implementing this may be more complex.
221 might want to implement this by using a mutex or disabling tasking. This
248 Be careful with using mem_malloc() in sys_arch. When malloc() refers to
250 mem_init() tries to allcate a semaphore using mem_malloc, which of course
|
| H A D | rawapi.txt | 39 from pbuf- and memory management functions). Application threads using
91 program using the raw TCP/IP interface.
298 should wait and try again either by using the acknowledgment
317 function to be called is set using the tcp_err() function.
380 We can give you some idea on how to proceed when using the raw API.
381 We assume a configuration using a single Ethernet netif and the
396 Give pointers to cleared ip_addr structures when using DHCP,
458 if you're using a little-endian architecture.
470 E.g. when using the cs8900 driver, call cs8900if_service(ethif)
471 as frequently as possible. When using an RTOS let the cs8900 interrupt
[all …]
|
| H A D | ppp.txt | 20 * PPP over serial using HDLC-like framing, such as wired dialup modems
381 Received data on serial port should be sent to lwIP using the pppos_input()
388 safe and can be safely called from an interrupt context, using that is going
394 using the TCPIP API. This is thread safe in all cases but you should avoid
402 at all. Using PPP_INPROC_IRQ_SAFE from an RX thread is discouraged unless you
433 Notify phase callback, enabled using the PPP_NOTIFY_PHASE config option, let
480 using ppp_pcb* control block, therefore all functions changed from "int ppp"
490 * Previous PPP API used CamelCase, we are now using snake_case.
518 * ppp_sighup and ppp_close functions were merged using an optional argument
523 using the dns_setserver() function so you don't need to do that in the PPP
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/ |
| H A D | savannah.txt | 1 Daily Use Guide for using Savannah for lwIP
6 2 - Committers/developers Git access using SSH
26 2 Committers/developers Git access using SSH
40 Try to login using SSH:
58 commit them. Make sure you know what you are doing when using Git to make
89 First, tag the release using Git: (I use release number 1.4.1 throughout
100 Archive the current directory using tar, gzip'd, bzip2'd and zip'd.
110 Upload these files using anonymous FTP:
|
| H A D | ppp.txt | 20 * PPP over serial using HDLC-like framing, such as wired dialup modems
381 Received data on serial port should be sent to lwIP using the pppos_input()
388 safe and can be safely called from an interrupt context, using that is going
394 using the TCPIP API. This is thread safe in all cases but you should avoid
402 at all. Using PPP_INPROC_IRQ_SAFE from an RX thread is discouraged unless you
433 Notify phase callback, enabled using the PPP_NOTIFY_PHASE config option, let
480 using ppp_pcb* control block, therefore all functions changed from "int ppp"
490 * Previous PPP API used CamelCase, we are now using snake_case.
518 * ppp_sighup and ppp_close functions were merged using an optional argument
523 using the dns_setserver() function so you don't need to do that in the PPP
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/ |
| H A D | savannah.txt | 1 Daily Use Guide for using Savannah for lwIP
6 2 - Committers/developers CVS access using SSH (to be written)
28 3 Committers/developers CVS access using SSH
43 Try to login using SSH:
59 commit them. Make sure you know what you are doing when using CVS to make
104 Login CVS using pserver authentication, then export a clean copy of the
112 Archive this directory using tar, gzip'd, bzip2'd and zip'd.
124 Upload these files using anonymous FTP:
|
| H A D | sys_arch.txt | 38 allows both using pointers or actual OS structures to be used. This way, memory
86 When using pointers, a simple way is to check the pointer for != NULL.
87 When directly using OS structures, implementing this may be more complex.
156 When using pointers, a simple way is to check the pointer for != NULL.
157 When directly using OS structures, implementing this may be more complex.
185 might want to implement this by using a mutex or disabling tasking. This
212 Be carefull with using mem_malloc() in sys_arch. When malloc() refers to
214 mem_init() tries to allcate a semaphore using mem_malloc, which of course
|
| H A D | rawapi.txt | 31 this thread! Application threads using the sequential- or socket API
76 program using the raw TCP/IP interface.
277 should wait and try again either by using the acknowledgment
296 function to be called is set using the tcp_err() function.
370 We can give you some idea on how to proceed when using the raw API.
371 We assume a configuration using a single Ethernet netif and the
424 Give pointers to cleared ip_addr structures when using DHCP,
472 if you're using a little-endian architecture.
482 E.g. when using the cs8900 driver, call cs8900if_service(ethif)
483 as frequently as possible. When using an RTOS let the cs8900 interrupt
[all …]
|
| /nrf52832-nimble/rt-thread/components/finsh/ |
| H A D | Kconfig | 22 bool "Using symbol table for commands"
62 bool "Using module shell"
67 bool "Using module shell in default"
71 bool "Only using module shell"
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/netif/ppp/polarssl/ |
| H A D | README | 11 The PolarSSL API was not changed at all, so if you are already using
15 If you are not using the embedded copy you must include external
19 using our cleaned PolarSSL library.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/src/netif/ppp/polarssl/ |
| H A D | README | 11 The PolarSSL API was not changed at all, so if you are already using
15 If you are not using the embedded copy you must include external
19 using our cleaned PolarSSL library.
|
| /nrf52832-nimble/packages/NimBLE-latest/apps/ext_advertiser/src/ |
| H A D | ext_advertiser.c | 82 /* advertise using random addr */ in start_ext_max_events()
177 /* enable advertising using legacy PDUs */ in start_legacy_duration()
180 /* advertise using random addr */ in start_legacy_duration()
226 /* this is simple non-connectable scannable instance using legacy PUDs that
241 /* enable scannable advertising using legacy PDUs */ in start_scannable_legacy_ext()
245 /* advertise using random addr */ in start_scannable_legacy_ext()
329 /* advertise using random addr */ in start_scannable_ext()
381 /* advertise using ID addr */ in start_non_connectable_ext()
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | pt-doc.txt | 84 implement sequential flow of control without using complex state
136 Protothreads are implemented using \ref lc "local continuations". A
147 -# by using machine specific assembler code,
148 -# by using standard C constructs, or
149 -# by using compiler extensions.
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/ |
| H A D | main_page.h | 30 * program using the raw TCP/IP interface.
203 * http://www.pebblebay.com/a-guide-to-using-direct-memory-access-in-embedded-systems-part-two/
252 We can give you some idea on how to proceed when using the raw API.
253 We assume a configuration using a single Ethernet netif and the
263 Give pointers to cleared ip_addr structures when using DHCP,
317 * from pbuf- and memory management functions). Application threads using
382 if you're using a little-endian architecture.
394 E.g. when using the cs8900 driver, call cs8900if_service(ethif)
395 as frequently as possible. When using an RTOS let the cs8900 interrupt
396 wake a high priority task that services your driver using a binary
|
| H A D | lwip.Doxyfile | 12 # For lists, items can also be appended using:
30 # double-quotes, unless you are using Doxywizard) that should identify the
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
172 # using the -I flag.
280 # using this tag. The format is ext=language, where ext is a file extension, and
375 # subgrouping. Alternatively, this can be done per class using the
382 # are shown inside the group in which they are included (e.g. using \ingroup)
413 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
658 # controlled using \showinitializer or \hideinitializer command in the
712 # For LaTeX the style of the bibliography can be controlled using
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/src/include/lwip/ |
| H A D | mem.h | 69 /* MEM_SIZE would have to be aligned, but using 64000 here instead of
81 /** mem_init is not used when using pools instead of a heap */
83 /** mem_trim is not used when using pools instead of a heap:
104 /** Calculate safe memory size for an aligned buffer when using an unaligned
|
| /nrf52832-nimble/rt-thread/documentation/ |
| H A D | Doxyfile | 9 # For lists items can also be appended using:
37 # Using the PROJECT_BRIEF tag one can provide an optional one line description
148 # are normally passed to the compiler using the -I flag.
243 # Doxygen has a built-in mapping, but you can override or extend it using this
292 # NO to prevent subgrouping. Alternatively, this can be done per class using
298 # unions are shown inside the group in which they are included (e.g. using
340 # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
542 # documentation can be controlled using \showinitializer or \hideinitializer
592 # .bib extension is automatically appended if omitted. Using this command
595 # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
[all …]
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
| H A D | FAQ | 117 After installing zlib 1.1.4 on Solaris 2.6, running applications using zlib
124 the C compiler (cc or gcc). You must recompile applications using zlib
127 using zlib.
148 format using deflateInit2(). You can also request that inflate decode
149 the gzip format using inflateInit2(). Read zlib.h for more details.
273 Note that you should be using the most recent version of zlib. Versions
322 "deflate" transfer encoding using the zlib format would be the more
324 for), using the "gzip" transfer encoding is probably more reliable due to
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/include/lwip/ |
| H A D | sys.h | 160 * When using pointers, a simple way is to check the pointer for != NULL.
161 * When directly using OS structures, implementing this may be more complex.
232 * When using pointers, a simple way is to check the pointer for != NULL.
233 * When directly using OS structures, implementing this may be more complex.
375 * When using pointers, a simple way is to check the pointer for != NULL.
376 * When directly using OS structures, implementing this may be more complex.
451 mechanism than using semaphores. Otherwise semaphores can be used for
473 * disabling interrupts for an embedded system or by using a semaphore or
486 * using a semaphore or mutex. This macro will default to calling the
|
| /nrf52832-nimble/packages/NimBLE-latest/ext/tinycrypt/documentation/ |
| H A D | tinycrypt.rst | 145 * Before using HMAC-PRNG, you *must* find an entropy source to produce a seed.
153 the entropy seed using a mandatory call to the re-seed function.
170 * Before using CTR-PRNG, you *must* find an entropy source to produce a seed.
244 represented using little-endian words - so the least significant word is
253 * A cryptographically-secure PRNG function must be set (using uECC_set_rng())
274 * Authenticate using a shared secret (HMAC-SHA256);
294 the unpredictability of the implementation by using the NIST Statistical Test
|