Search results
From Nutwiki
Create the page "Api/" on this wiki! See also the search results found.
Page title matches
- === Connectivity API === * high level graphics and text API (HW independent)22 KB (3,548 words) - 18:02, 27 October 2016
- #REDIRECT [[How to implement a character display API]]54 bytes (8 words) - 18:02, 27 October 2016
- ...mplemented for I2C support. The problem with the [[Legacy I2C API|previous API]] was, that only one type of I2C interface could be used by an application. ...ly. And, there's only one device driver available, which makes use of this API and supports the PCF8563 RTC chip.5 KB (966 words) - 18:02, 27 October 2016
- ...API|new API]] has been presented in Nut/OS 5.0.6. Nevertheless, the legacy API described on this page is still available.10 KB (1,593 words) - 18:02, 27 October 2016
Page text matches
- We can use the routines Led1On() and Led1Off with the NutSleep() API to implement a blinking LED.8 KB (1,059 words) - 18:02, 27 October 2016
- == NUT/OS API == ...sprachige) Dokumentation zum [http://www.ethernut.de/api/index.html Nut/OS API].4 KB (561 words) - 18:02, 27 October 2016
- == Netzwerk-API ==10 KB (1,601 words) - 18:02, 27 October 2016
- ...to use web server for Windows and UNIX. Mongoose provides simple and clean API for embedding it into existing programs. Targeting Web application develope4 KB (642 words) - 18:02, 27 October 2016
- Since Nut/OS 4.7.5 new API functions had been implemented to provide a framework for device drivers th26 KB (4,342 words) - 18:02, 27 October 2016
- This example demonstrates simple GPIO calls using the Nut/OS GPIO API.7 KB (1,009 words) - 18:02, 27 October 2016
- === Connectivity API === * high level graphics and text API (HW independent)22 KB (3,548 words) - 18:02, 27 October 2016
- #REDIRECT [[How to implement a character display API]]54 bytes (8 words) - 18:02, 27 October 2016
- /* These useful API calls create a HTTP response for us. */ * This API call saves us a lot of work. It will parse the19 KB (2,460 words) - 18:02, 27 October 2016
- #REDIRECT [[Legacy I2C API]]28 bytes (5 words) - 18:02, 27 October 2016
- ...mplemented for I2C support. The problem with the [[Legacy I2C API|previous API]] was, that only one type of I2C interface could be used by an application. ...ly. And, there's only one device driver available, which makes use of this API and supports the PCF8563 RTC chip.5 KB (966 words) - 18:02, 27 October 2016
- ...API|new API]] has been presented in Nut/OS 5.0.6. Nevertheless, the legacy API described on this page is still available.10 KB (1,593 words) - 18:02, 27 October 2016
- == API == Over the years a somewhat weird collection of API calls had developed.4 KB (582 words) - 18:02, 27 October 2016
- ** [[Legacy I2C API]] ** [[I2C Bus API]]4 KB (479 words) - 18:02, 27 October 2016
- in the Nut/OS API Manual. With each release, egnite will run Doxygen on the20 KB (3,370 words) - 18:02, 27 October 2016
- == NUT/OS API == ...sprachige) Dokumentation zum [http://www.ethernut.de/api/index.html Nut/OS API].4 KB (558 words) - 18:02, 27 October 2016
- ...his is quite simple to use, particularly because Nut/OS provides the three API functions <tt>NutHttpGetParameterCount</tt>, <tt>NutHttpGetParameterName</t The application calls a number of basic API function, defined in the following header files:17 KB (2,233 words) - 18:02, 27 October 2016
- Prototypes provided by the socket API.13 KB (1,892 words) - 18:03, 27 October 2016
- * [[How to implement a character display API]] * [[How to implement a graphics API]]610 bytes (92 words) - 18:03, 27 October 2016
- == ICMP API == There's currently no official Nut/Net API for using the ICMP protocol. Mike Cornelius and Ralph Mason had been workin6 KB (949 words) - 18:54, 12 July 2017
- ...milar projects, you will probably notice some advantages like the detailed API documentation. Nevertheless, newbies often find it difficult to become fami6 KB (958 words) - 08:59, 13 July 2017
- # No Nut/OS API calls are allowed except NutEventPostFromIrq(). Though, many C runtime func * We use the Nut/OS API to register our timer interrupt handler.11 KB (1,578 words) - 09:15, 13 July 2017
- | API Reference<br /> ...tp://www.graphviz.org/ GraphViz] are used to automatically create a Nut/OS API reference from the C source files.21 KB (3,235 words) - 17:55, 13 July 2017
- You can also choose to include or exclude the API Documentation from the build process. This documentation is created from co The Nut/OS API Documentation will be build automatically from the source code. For this we19 KB (2,643 words) - 16:11, 13 July 2017
- API documentation including copyright statements.3 KB (464 words) - 19:09, 13 July 2017
- [[../../api/index.html|Online API Documentation]] [[../../api-beta/index.html|API Documentation of the beta release]]6 KB (862 words) - 19:10, 13 July 2017
- ...nded for experienced C programmers with some basic knowledge of the Nut/OS API. ...natively you may use the MD5 code that is available in nut/gorp/md5.c. The API is quite similar.33 KB (5,353 words) - 09:47, 13 July 2017
- Since Nut/OS 4.7.5 new API functions had been implemented to provide a framework for device drivers th a similar API function had been added for device drivers using the new SPI bus framework:16 KB (2,739 words) - 09:51, 13 July 2017
- ...ts and will hopefully make most drivers available on all platforms. A GPIO API has been created to further reduce platform dependencies. == GPIO API ==7 KB (1,106 words) - 09:52, 13 July 2017
- Nut/OS doesn't offer a mount() API call. Instead _open() is used and the required items are packed into a path12 KB (2,098 words) - 09:57, 13 July 2017
- '''API functions'''<br /> Otherwise your changes will not appear in the Nut/OS API reference.23 KB (3,721 words) - 09:58, 13 July 2017
- The bad news is, that the new library API is incompatible to the old one. Applications needs to be rewritten to make provides an overview of the application programming interface (API) of the MicroHTTP library.2 KB (351 words) - 10:28, 13 July 2017
- ...this documentation. Since then, you may refer to the uHttp samples and the API documentation that comes with the Nut/OS distribution.5 KB (682 words) - 10:28, 13 July 2017
- This page gives you an overview of the application programming interface (API) provided by the [[uhttplib.html|MicroHTTP library]]. ...emote host. Actually, the old HTTP library didn't use any network specific API. Instead it expects, that the applications establishes the connection, atta8 KB (1,356 words) - 10:30, 13 July 2017
- ...tion of Ethernut 3 board with an AT91 microcontroller, a portable watchdog API is required to maintain portability of applications. Version 4.1.5 will provided a first Watchdog API, currently implemented for the ARM7TDMI only.481 bytes (67 words) - 10:33, 13 July 2017
- Another advantage of the segmented buffer API is, that it can handle non-continous memory like the banked RAM on Ethernut20 KB (3,042 words) - 10:33, 13 July 2017
- API documentation including copyright statements.8 KB (1,191 words) - 19:10, 13 July 2017
- ...ation]] for a complete list of provided functions. Use this along with the API documentation of your runtime library, like [http://sourceware.org/newlib/ ...latest beta, then try the Beta API documentation. It is available [[../../api-beta/index.html|online]].4 KB (583 words) - 10:41, 13 July 2017
- * Socket API ...ardware specific details from application code, an almost complete C stdio API is available, which provides:10 KB (1,535 words) - 10:43, 13 July 2017
