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
