| /nrf52832-nimble/rt-thread/components/drivers/can/ |
| H A D | can.c | 16 #define CAN_LOCK(can) rt_mutex_take(&(can->lock), RT_WAITING_FOREVER) argument
17 #define CAN_UNLOCK(can) rt_mutex_release(&(can->lock)) argument
22 struct rt_can_device *can; in rt_can_init() local
25 can = (struct rt_can_device *)dev; in rt_can_init()
28 can->can_rx = RT_NULL; in rt_can_init()
29 can->can_tx = RT_NULL; in rt_can_init()
32 if (can->ops->configure) in rt_can_init()
33 result = can->ops->configure(can, &can->config); in rt_can_init()
39 * can interrupt routines
41 rt_inline int _can_int_rx(struct rt_can_device *can, struct rt_can_msg *data, int msgs) in _can_int_rx() argument
[all …]
|
| H A D | readme-zh.txt | 3 一 CAN Driver 注册
4 Can driver注册需要填充以下几个数据结构：
39 sndboxnumber : can 发送通道数量，该配置为Can控制器实际的发送通道数量。
64 rt_err_t (*configure)(struct rt_can_device *can, struct can_configure *cfg);
65 rt_err_t (*control)(struct rt_can_device *can, int cmd, void *arg);
66 int (*sendmsg)(struct rt_can_device *can, const void* buf, rt_uint32_t boxno);
67 int (*recvmsg)(struct rt_can_device *can,void* buf, rt_uint32_t boxno);
70 rt_err_t (*configure)(struct rt_can_device *can, struct can_configure *cfg);
72 rt_err_t (*control)(struct rt_can_device *can, int cmd, void *arg);
80 int (*sendmsg)(struct rt_can_device *can, const void* buf, rt_uint32_t boxno);
[all …]
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/ |
| H A D | INSTALL | 21 necessarily a bug. More recommendations for GNU packages can be found
29 you can run in the future to recreate the current configuration, and a
33 It can also use an optional file (typically called `config.cache'
41 diffs or instructions to the address given in the `README' so they can
77 6. You can remove the program binaries and object files from the
79 files that `configure' created (so you can compile the package for
86 7. Often, you can also type `make uninstall' to remove the installed
92 distcheck', which can by used by developers to test that all other
103 You can give `configure' initial values for configuration parameters
114 You can compile the package for more than one kind of computer at the
[all …]
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/src/ |
| H A D | FAQ | 14 2. Where can I get a Windows DLL version?
16 The zlib sources can be compiled without change to produce a DLL.
21 3. Where can I get a Visual Basic interface to zlib?
41 inflate() can be made with more input or output space. A Z_BUF_ERROR
78 11. Can zlib handle .zip archives?
83 12. Can zlib handle .Z files?
88 13. How can I make a Unix shared library?
103 can #include <zlib.h>, it's there. The -lz option will probably link to it.
110 16. Can zlib decode Flate data in an Adobe PDF file?
147 You can request that deflate write the gzip format instead of the zlib
[all …]
|
| /nrf52832-nimble/rt-thread/documentation/ |
| H A D | Doxyfile | 9 # For lists items can also be appended using:
31 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
37 # Using the PROJECT_BRIEF tag one can provide an optional one line description
43 # With the PROJECT_LOGO tag one can specify an logo or icon that is
60 # Enabling this option can be useful when feeding doxygen a huge amount of
135 # can be used to strip a user-defined part of the path. Stripping is
137 # the path. The tag can be used to show relative paths in the file list.
143 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
153 # (but less readable) file names. This can be useful if your file system
174 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
[all …]
|
| /nrf52832-nimble/rt-thread/tools/kconfig-frontends/docs/ |
| H A D | kconfig-language.txt | 37 Every line starts with a key word and can be followed by multiple
39 define attributes for this config option. Attributes can be the type of
41 values. A config option can be defined multiple times with the same
42 name, but every definition can have only a single input prompt and the
48 A menu entry can have a number of attributes. Not all of them are
63 Every menu entry can have at most one prompt, which is used to display
64 to the user. Optionally dependencies only for this prompt can be added
68 A config option can have any number of default values. If multiple
71 defined. This means the default can be defined somewhere else or be
75 prompt is visible the default value is presented to the user and can
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/doc/doxygen/ |
| H A D | lwip.Doxyfile | 12 # For lists, items can also be appended using:
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
66 # option can be useful when feeding doxygen a huge amount of source files, where
155 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
157 # part of the path. The tag can be used to show relative paths in the file list.
161 # Note that you can specify absolute paths here, but also relative paths, which
167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
177 # less readable) file names. This can be useful is your file systems doesn't
[all …]
|
| H A D | lwip.Doxyfile.cmake.in | 12 # For lists, items can also be appended using:
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
66 # option can be useful when feeding doxygen a huge amount of source files, where
155 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
157 # part of the path. The tag can be used to show relative paths in the file list.
161 # Note that you can specify absolute paths here, but also relative paths, which
167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
177 # less readable) file names. This can be useful is your file systems doesn't
[all …]
|
| H A D | main_page.h | 28 * All APIs can be used simultaneously by different application
50 * closed, etc. An application can provide a callback function to perform
65 * Sequential-style APIs, blocking functions. More overhead, but can be called
78 * Can be activated by defining @ref LWIP_SOCKET to 1.\n
135 * lwIP can be used in two basic modes: @ref lwip_nosys (no OS/RTOS
143 * In mainloop mode, only @ref callbackstyle_api can be used.
164 * In OS mode, @ref callbackstyle_api AND @ref sequential_api can be used.
175 * 1) tcpip_callback() can be used get called back from TCPIP thread,
179 * functions can be called when lwIP core lock is aquired, see
225 * *not* *from* *interrupt* *context*. You can allocate a @ref pbuf in interrupt
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/doxygen/ |
| H A D | lwip.Doxyfile | 12 # For lists, items can also be appended using:
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
66 # option can be useful when feeding doxygen a huge amount of source files, where
155 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
157 # part of the path. The tag can be used to show relative paths in the file list.
161 # Note that you can specify absolute paths here, but also relative paths, which
167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
177 # less readable) file names. This can be useful is your file systems doesn't
[all …]
|
| H A D | main_page.h | 11 * Sequential-style APIs, blocking functions. More overhead, but can be called
48 * lwIP can be used in two basic modes: @ref lwip_nosys (no OS/RTOS
54 * In mainloop mode, only @ref callbackstyle_api can be used.
75 * In OS mode, @ref callbackstyle_api AND @ref sequential_api can be used.
86 * 1) tcpip_callback() can be used get called back from TCPIP thread,
90 * functions can be called when lwIP core lock is aquired, see
108 * *not* *from* *interrupt* *context*. You can allocate a @ref pbuf in interrupt
113 * You can only use @ref callbackstyle_api in this mode.\n
125 * You can use @ref callbackstyle_api together with @ref tcpip_callback,
|
| /nrf52832-nimble/packages/NimBLE-latest/docs/ |
| H A D | doxygen.xml | 30 # For lists, items can also be appended using:
55 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
61 # Using the PROJECT_BRIEF tag one can provide an optional one line description
67 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
84 # option can be useful when feeding doxygen a huge amount of source files, where
163 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
165 # part of the path. The tag can be used to show relative paths in the file list.
169 # Note that you can specify absolute paths here, but also relative paths, which
175 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
185 # less readable) file names. This can be useful is your file systems doesn't
[all …]
|
| /nrf52832-nimble/rt-thread/components/net/freemodbus/port/ |
| H A D | portevent_m.c | 5 * This library is free software; you can redistribute it and/or
81 * Note:The resource is define by OS.If you not use OS this function can be empty.
91 …* Note:The resource is define by Operating System.If you not use OS this function can be just retu…
105 * Note:The resource is define by Operating System.If you not use OS this function can be empty.
128 * If you don't use OS, you can change it. in vMBMasterErrorCBRespondTimeout()
132 /* You can add your code under here. */ in vMBMasterErrorCBRespondTimeout()
150 * If you don't use OS, you can change it. in vMBMasterErrorCBReceiveData()
154 /* You can add your code under here. */ in vMBMasterErrorCBReceiveData()
172 * If you don't use OS, you can change it. in vMBMasterErrorCBExecuteFunction()
176 /* You can add your code under here. */ in vMBMasterErrorCBExecuteFunction()
[all …]
|
| /nrf52832-nimble/rt-thread/ |
| H A D | README.md | 22 …AND etc. The developer can easily add low level driver and board configuration, then combined with…
24 …component must be a directory under RT-Thread/Components and one component can be descripted by a …
26 …ly named as User Applicaion (UA) is a dyanmic loaded module or library, it can be compiled standal…
30 RT-Thread RTOS can support many architectures:
46 …ache License 2.0 since RT-Thread v3.1.1. License and copyright information can be found within the…
70 …OS. If you build the porting in the bsp directory, you can use the default setting. Also, you can …
72 When you set these variables correctly, you can use command:
78 If you want to generate the IDE's project file, you can use command:
|
| /nrf52832-nimble/rt-thread/components/CMSIS/RTOS/ |
| H A D | cmsis_os.h | 39 Definitions that are marked with <b>CAN BE CHANGED</b> can be adapted towards the needs of the actu…
40 These definitions can be specific to the underlying RTOS kernel.
48 The following CMSIS-RTOS functions can be called from threads and interrupt service routines (ISR):
81 …file, the objects are defined as external symbols. A single consistent header file can therefore be
104 /// \note CAN BE CHANGED: \b osCMSIS_KERNEL identifies the underlaying RTOS kernel and version numb…
111 #define osFeature_MainThread 1 ///< main thread 1=main can be thread, 0=not available
186 /// \note CAN BE CHANGED: \b os_thread_cb is implementation specific in every CMSIS-RTOS.
190 /// \note CAN BE CHANGED: \b os_timer_cb is implementation specific in every CMSIS-RTOS.
194 /// \note CAN BE CHANGED: \b os_mutex_cb is implementation specific in every CMSIS-RTOS.
198 /// \note CAN BE CHANGED: \b os_semaphore_cb is implementation specific in every CMSIS-RTOS.
[all …]
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/services/dis/ |
| H A D | syscfg.yml | 22 Defines default permissions for reading characteristics. Can be
32 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
43 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
54 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
65 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
76 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
87 Can be set to MYNEWT_VAL_BLE_SVC_DIS_DEFAULT_READ_PERM or use
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/elmfat/ |
| H A D | 00history.txt | 67 Fixed DBCS name can result FR_INVALID_NAME.
84 Fixed btr in f_read() can be mistruncated.
118 Fixed f_unlink() can return FR_OK on error.
195 Fixed f_write() can be truncated when the file size is close to 4GB.
196 Fixed f_open(), f_mkdir() and f_setlabel() can return incorrect value on error.
204 2nd argument of f_rename() can have a drive number and it will be ignored.
214 Fixed a hard error in the disk I/O layer can collapse the directory entry.
224 Fixed a potential problem of FAT access that can appear on disk error.
239 Fixed wrong media change can lead a deadlock at thread-safe configuration.
274 Fixed creating a file in the root directory of exFAT volume can fail. (appeared at R0.12)
[all …]
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/include/ |
| H A D | zlib.h | 50 Compression can be done in a single step if the buffers are large
51 enough (for example if an input file is mmap'ed), or can be done by
65 This library can optionally read and write gzip streams in memory as well.
136 parameter for calls of zalloc and zfree. This can be useful for custom
153 The fields total_in and total_out can be used for statistics or
213 /* The application can compare zlibVersion and ZLIB_VERSION for consistency.
253 accordingly. If not all input can be processed (because there is not
266 should never be zero before the call. The application can consume the
278 that the decompressor can get all input data available so far. (In particular
284 Z_SYNC_FLUSH, and the compression state is reset so that decompression can
[all …]
|
| /nrf52832-nimble/rt-thread/components/dfs/filesystems/jffs2/cyg/compress/ |
| H A D | zlib.h | 50 Compression can be done in a single step if the buffers are large
51 enough (for example if an input file is mmap'ed), or can be done by
65 This library can optionally read and write gzip streams in memory as well.
136 parameter for calls of zalloc and zfree. This can be useful for custom
153 The fields total_in and total_out can be used for statistics or
213 /* The application can compare zlibVersion and ZLIB_VERSION for consistency.
253 accordingly. If not all input can be processed (because there is not
266 should never be zero before the call. The application can consume the
278 that the decompressor can get all input data available so far. (In particular
284 Z_SYNC_FLUSH, and the compression state is reset so that decompression can
[all …]
|
| /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
24 Semaphores can be either counting or binary - lwIP works with both
26 to be posted (implementing as a rendez-vous point where only one message can be
27 posted at a time can have a highly negative impact on performance). A message
38 required for such types can be either allocated in place (globally or on the
50 points to (which can be both a pointer or the actual OS structure).
99 points to (which can be both a pointer or the actual OS structure).
110 Blocks the thread until the mutex can be grabbed.
179 To allow for efficient implementations, this can be defined as a
[all …]
|
| /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
69 * required for such types can be either allocated in place (globally or on the
75 * mem_malloc() you can run into a circular function call problem. In mem.c
77 * can't be performed when sys_arch uses mem_malloc.
81 * Semaphores can be either counting or binary - lwIP works with both
97 * to be posted (implementing as a rendez-vous point where only one message can be
98 * posted at a time can have a highly negative impact on performance). A message
|
| /nrf52832-nimble/rt-thread/components/net/uip/doc/ |
| H A D | uip-doc.txt | 10 their peers to have complex, full-size stacks, but can communicate
12 the order of a few kilobytes and RAM usage can be configured to be as
15 uIP can be found at the uIP web page: http://www.sics.se/~adam/uip/
47 set of features needed for a full TCP/IP stack. It can only handle a
86 can be passed to higher layers.
94 The RFC1122 requirements can be divided into two categories; those
112 of those features they can be removed without loss of generality.
116 The uIP stack can be run either as a task in a multitasking system, or
158 functions can be written in highly optimized assembler rather than
200 handled by the processor, such as RS-232 ports, can copy incoming
[all …]
|
| H A D | pt-doc.txt | 7 event-driven systems implemented in C. Protothreads can be used with
27 systems, the overhead of allocating multiple stacks can consume large
47 - Can be used with or without an OS
139 or local variables. A local continuation can be set in a specific
141 continuation has been set can be resumed in order to restore the state
145 Local continuations can be implemented in a variety of ways:
162 Certain compilers has C extensions that can be used to implement
163 protothreads. GCC supports label pointers that can be used for this
|
| /nrf52832-nimble/rt-thread/components/drivers/include/drivers/ |
| H A D | mmc.h | 108 #define EXT_CSD_CARD_TYPE_HS_26 (1<<0) /* Card can run at 26MHz */
109 #define EXT_CSD_CARD_TYPE_HS_52 (1<<1) /* Card can run at 52MHz */
112 #define EXT_CSD_CARD_TYPE_DDR_1_8V (1<<2) /* Card can run at 52MHz */
114 #define EXT_CSD_CARD_TYPE_DDR_1_2V (1<<3) /* Card can run at 52MHz */
118 #define EXT_CSD_CARD_TYPE_HS200_1_8V (1<<4) /* Card can run at 200MHz */
119 #define EXT_CSD_CARD_TYPE_HS200_1_2V (1<<5) /* Card can run at 200MHz */
123 #define EXT_CSD_CARD_TYPE_HS400_1_8V (1<<6) /* Card can run at 200MHz DDR, 1.8V */
124 #define EXT_CSD_CARD_TYPE_HS400_1_2V (1<<7) /* Card can run at 200MHz DDR, 1.2V */
|
| /nrf52832-nimble/packages/NimBLE-latest/nimble/host/mesh/ |
| H A D | syscfg.yml | 68 This option specifies how many subnets a Mesh network can
74 This option specifies how many application keys the device can
80 This option specifies how many application keys each model can
86 This option specifies how many group addresses each model can
92 This option specifies how many Label UUIDs can be stored.
166 can have. Each segment can contain 12 bytes, so this value should
249 the Friend node can store in its Friend Queue. As an example,
289 Maximum number of groups that the LPN can subscribe to.
310 Size of the Subscription List that can be supported by a
316 Number of Low Power Nodes the Friend can have a Friendship
[all …]
|