Collaboration diagram for Emulator (UNIX):
Nut/OS can be compiled for a native unix target.
The following hardware is currently emulated: RTC and UART. A RTC clock is provided. All AVR UARTS are mapped to STDIO but this can configure at app start-up using command line paramters. Syntax:
MyNutOSAPP.unix [-u0 deviceName] [-u1 deviceName] [-u2 deviceName]
The unix emulation provides a third uart for debugging purposes as devDebug2, devUsart2 and devUsartAvr2)
Modules | |
Initialization | |
Starting Nut/OS. | |
System Support | |
Hardware dependant functions used by Nut/OS. | |
Data Structures | |
struct | _UNIXDCB |
UNIX devices low level information structure. More... | |
struct | _UNIXDCB |
UNIX devices low level information structure. More... | |
Typedefs | |
typedef _UNIXDCB | UNIXDCB |
Variables | |
NUTDEVICE | devUart0 |
UART 0 Device information structure. | |
NUTDEVICE | devUart1 |
UART 1 Device information structure. | |
NUTDEVICE | devUart2 |
NUTDEVICE | devUsartAvr0 |
USART0 device information structure. | |
NUTDEVICE | devUsartAvr1 |
USART1 device information structure. | |
NUTDEVICE | devUsartAvr2 |
NUTDEVICE | devDebug0 |
Debug device 0 information structure. | |
NUTDEVICE | devDebug1 |
UART 1 Device information structure. | |
NUTDEVICE | devDebug2 |
|
USART device low level information type. |
|
USART0 device information structure. An application must pass a pointer to this structure to NutRegisterDevice() before using the serial communication driver of the AVR's on-chip USART0. The device is named uart0. |
|
USART1 device information structure. An application must pass a pointer to this structure to NutRegisterDevice() before using the serial communication driver of the AVR's on-chip USART1. The device is named uart1. |