Spell-check code/comments in the Webserver/AVRISP-MKII projects.
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = atmega32u4\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = \r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
*\r
* \section SSec_Description Project Description: \r
*\r
- * MIDI host demonstration application. This demo will enumerate an attached USB-MIDI device, and print incomming MIDI note\r
+ * MIDI host demonstration application. This demo will enumerate an attached USB-MIDI device, and print incoming MIDI note\r
* on and off messages on any channel to the serial port. Pressing the board joystick will send note on and off messages to\r
* the attached MIDI device, with the board HWB controlling the note channel.\r
*\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
\r
#include "RNDISEthernetHost.h"\r
\r
-/** Buffer to hold incomming and outgoing Ethernet packets. */\r
+/** Buffer to hold incoming and outgoing Ethernet packets. */\r
uint8_t PacketBuffer[1024];\r
\r
/** LUFA RNDIS Class driver interface configuration and state information. This structure is\r
USB_HostState = HOST_STATE_Configured;\r
break;\r
case HOST_STATE_Configured:\r
- PrintIncommingPackets();\r
+ PrintIncomingPackets();\r
\r
break;\r
}\r
}\r
}\r
\r
-/** Prints incomming packets from the attached RNDIS device to the serial port. */\r
-void PrintIncommingPackets(void)\r
+/** Prints incoming packets from the attached RNDIS device to the serial port. */\r
+void PrintIncomingPackets(void)\r
{\r
if (RNDIS_Host_IsPacketReceived(&Ethernet_RNDIS_Interface))\r
{\r
\r
/* Function Prototypes: */\r
void SetupHardware(void);\r
- void PrintIncommingPackets(void);\r
+ void PrintIncomingPackets(void);\r
\r
void EVENT_USB_Host_HostError(const uint8_t ErrorCode);\r
void EVENT_USB_Host_DeviceAttached(void);\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
*\r
* \section SSec_Description Project Description: \r
*\r
- * MIDI host demonstration application. This demo will enumerate an attached USB-MIDI device, and print incomming MIDI note\r
+ * MIDI host demonstration application. This demo will enumerate an attached USB-MIDI device, and print incoming MIDI note\r
* on and off messages on any channel to the serial port. Pressing the board joystick will send note on and off messages to\r
* the attached MIDI device, with the board HWB controlling the note channel.\r
*\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
LEDs_SetAllLEDs(LEDMASK_USB_ERROR);\r
}\r
\r
-void PrintIncommingPackets(void)\r
+void PrintIncomingPackets(void)\r
{\r
uint8_t ErrorCode;\r
\r
USB_HostState = HOST_STATE_Configured;\r
break;\r
case HOST_STATE_Configured:\r
- PrintIncommingPackets();\r
+ PrintIncomingPackets();\r
\r
break;\r
}\r
\r
/* Function Prototypes: */\r
void SetupHardware(void);\r
- void PrintIncommingPackets(void);\r
+ void PrintIncomingPackets(void);\r
void RNDIS_Host_Task(void);\r
\r
void EVENT_USB_Host_HostError(const uint8_t ErrorCode);\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
\r
/** Selects the EVK527 specific board drivers, including Temperature, Button, Dataflash, Joystick and LED drivers. */\r
#define BOARD_EVK527 9\r
+ \r
+ /** Disables board drivers when operation will not be adversely affected (e.g. LEDs) - use of board drivers\r
+ * such as the Joystick driver, where the removal would adversely affect the code's operation is still disallowed. */\r
+ #define BOARD_NONE 10\r
+ \r
+ #if !defined(__DOXYGEN__)\r
+ #define BOARD_ BOARD_NONE\r
+ \r
+ #if !defined(BOARD)\r
+ #define BOARD BOARD_NONE\r
+ #endif\r
+ #endif\r
\r
#endif\r
\r
/* Includes: */\r
#include "../../Common/Common.h"\r
\r
- #if !defined(BOARD)\r
- #error BOARD must be set in makefile to a value specified in BoardTypes.h.\r
+ #if (BOARD == BOARD_NONE)\r
+ #error The Board Buttons driver cannot be used if the makefile BOARD option is not set.\r
#elif (BOARD == BOARD_USBKEY)\r
#include "USBKEY/Buttons.h"\r
#elif (BOARD == BOARD_STK525)\r
}\r
\r
/* Includes: */\r
- #if !defined(BOARD)\r
- #error BOARD must be set in makefile to a value specified in BoardTypes.h.\r
+ #if (BOARD == BOARD_NONE)\r
+ #error The Board Buttons driver cannot be used if the makefile BOARD option is not set.\r
#elif (BOARD == BOARD_USBKEY)\r
#include "USBKEY/Dataflash.h"\r
#elif (BOARD == BOARD_STK525)\r
/* Includes: */\r
#include "../../Common/Common.h"\r
\r
- #if !defined(BOARD)\r
- #error BOARD must be set in makefile to a value specified in BoardTypes.h.\r
+ #if (BOARD == BOARD_NONE)\r
+ #error The Board Joystick driver cannot be used if the makefile BOARD option is not set.\r
#elif (BOARD == BOARD_USBKEY)\r
#include "USBKEY/Joystick.h"\r
#elif (BOARD == BOARD_STK525)\r
/* Includes: */\r
#include "../../Common/Common.h"\r
\r
- #if !defined(BOARD)\r
- #error BOARD must be set in makefile to a value specified in BoardTypes.h.\r
+ #if (BOARD == BOARD_NONE)\r
+ static inline void LEDs_Init(void) {};\r
+ static inline void LEDs_TurnOnLEDs(const uint8_t LEDMask) {};\r
+ static inline void LEDs_TurnOffLEDs(const uint8_t LEDMask) {};\r
+ static inline void LEDs_SetAllLEDs(const uint8_t LEDMask) {};\r
+ static inline void LEDs_ChangeLEDs(const uint8_t LEDMask, const uint8_t ActiveMask) {};\r
+ static inline void LEDs_ToggleLEDs(const uint8_t LEDMask) {};\r
+ static inline uint8_t LEDs_GetLEDs(void) { return 0; }\r
#elif (BOARD == BOARD_USBKEY)\r
#include "USBKEY/LEDs.h"\r
#elif (BOARD == BOARD_STK525)\r
#include "../../Common/Common.h"\r
#include "../Peripheral/ADC.h"\r
\r
- #if !defined(BOARD)\r
- #error BOARD must be set in makefile to a value specified in BoardTypes.h. \r
+ #if (BOARD == BOARD_NONE)\r
+ #error The Board Temperature Sensor driver cannot be used if the makefile BOARD option is not set.\r
#elif ((BOARD != BOARD_USBKEY) && (BOARD != BOARD_STK525) && \\r
(BOARD != BOARD_STK526) && (BOARD != BOARD_USER) && \\r
(BOARD != BOARD_EVK527))\r
* - Added ADC MUX masks for the standard ADC input channels on all AVR models with an ADC, altered demos to use these masks\r
* as on some models, the channel number is not identical to its single-ended ADC MUX mask\r
* - New Webserver project, a RNDIS host USB webserver using the open source uIP TCP/IP network stack and FatFS library\r
+ * - New BOARD value option BOARD_NONE (equivelent to not specifying BOARD) which will remove all board hardware drivers which\r
+ * do not adversely affect the code operation (currently only the LEDs driver)\r
*\r
* <b>Changed:</b>\r
* - Slowed down software USART carried PDI programming in the AVRISP project to prevent transmission errors\r
* - Openkubus, an open source hardware-based authentication dongle: http://code.google.com/p/openkubus/\r
* - Orbee, a USB connected RGB Orb for notifications: http://www.franksworkshop.com.au/Electronics/Orbee/Orbee.htm\r
* - Programmable XBOX controller: http://richard-burke.dyndns.org/wordpress/pan-galactic-gargantuan-gargle-brain-aka-xbox-360-usb-controller/\r
- * - Purdue Interactive Kiosk: https://engineering.purdue.edu/477grp4/\r
* - Reprap with LUFA, a LUFA powered 3D printer: http://code.google.com/p/at90usb1287-code-for-arduino-and-eclipse/\r
* - SEGA Megadrive/Genesis Development Cartridge: http://www.makestuff.eu/wordpress/?page_id=398\r
* - Stripe Snoop, a Magnetic Card reader: http://www.ossguy.com/ss_usb/\r
* - BAP, A tiny LUFA based AVR Programmer: http://www.busware.de/tiki-index.php?page=BAP\r
* - Digital Survey Instruments Magnetometer and Pointer: http://www.digitalsurveyinstruments.com/\r
* - Lightweight CC110x USB dongle for 868MHz Protocols: http://busware.de/tiki-index.php?page=CUL\r
+ * - MIDIFighter, a USB-MIDI controller: http://www.midifighter.com/\r
* - Mobo 4.3, a USB controlled all band (160-10m) HF SDR transceiver: http://sites.google.com/site/lofturj/mobo4_3\r
* - SEGA Megadrive/Super Nintendo Cartridge Reader: http://www.snega2usb.com\r
* - XMEGA Development Board, using LUFA as an On-Board Programmer: http://xmega.mattair.net/\r
*/\r
static void TINYNVM_SendWriteNVMRegister(const uint8_t Address)\r
{\r
- /* The TPI command for writing to the I/O space uses wierd addressing, where the I/O address's upper\r
+ /* The TPI command for writing to the I/O space uses weird addressing, where the I/O address's upper\r
* two bits of the 6-bit address are shifted left once */\r
XPROGTarget_SendByte(TPI_CMD_SOUT | ((Address & 0x30) << 1) | (Address & 0x0F));\r
}\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = atmega32u2\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USER\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb646\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USER\r
MCU = at90usb1287
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring
+# Target board (see library "Board Types" documentation, NONE for projects not requiring
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called
# "Board" inside the application directory.
-BOARD = USER
+BOARD = NONE
# Processor frequency.
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
uip_ipaddr(&DHCPServerIPAddress, 255, 255, 255, 255);\r
AppState->DHCPClient.Connection = uip_udp_new(&DHCPServerIPAddress, HTONS(DHCPC_SERVER_PORT));\r
\r
- /* If the connection was sucessfully created, bind it to the local DHCP client port */\r
+ /* If the connection was successfully created, bind it to the local DHCP client port */\r
if(AppState->DHCPClient.Connection != NULL)\r
{\r
uip_udp_bind(AppState->DHCPClient.Connection, HTONS(DHCPC_CLIENT_PORT));\r
*/\r
bool DHCPClientApp_GetOption(uint8_t* DHCPOptionList, uint8_t Option, void* Destination)\r
{\r
- /* Look through the incomming DHCP packet's options list for the requested option */\r
+ /* Look through the incoming DHCP packet's options list for the requested option */\r
while (*DHCPOptionList != DHCP_OPTION_END)\r
{\r
/* Check if the current DHCP option in the packet is the one requested */\r
/* Copy request option's data to the destination buffer */\r
memcpy(Destination, &DHCPOptionList[2], DHCPOptionList[1]);\r
\r
- /* Indicate that the requested option data was sucessfully retrieved */\r
+ /* Indicate that the requested option data was successfully retrieved */\r
return true;\r
}\r
\r
DHCPOptionList += (DHCPOptionList[1] + 2);\r
}\r
\r
- /* Requested option not found in the incomming packet's DHCP options list */\r
+ /* Requested option not found in the incoming packet's DHCP options list */\r
return false;\r
}\r
#endif\r
} \r
}\r
\r
-/** HTTP Server State handler for the Request Process state. This state manages the processing of incomming HTTP\r
+/** HTTP Server State handler for the Request Process state. This state manages the processing of incoming HTTP\r
* GET requests to the server from the receiving HTTP client.\r
*/\r
static void HTTPServerApp_OpenRequestedFile(void)\r
} MIME_Type_t;\r
\r
/* Macros: */\r
- /** TCP listen port for incomming HTTP traffic */\r
+ /** TCP listen port for incoming HTTP traffic */\r
#define HTTP_SERVER_PORT 80\r
\r
/* Function Prototypes: */\r
#include <uip.h>\r
\r
/* Macros: */\r
- /** TCP listen port for incomming TELNET traffic */\r
+ /** TCP listen port for incoming TELNET traffic */\r
#define TELNET_SERVER_PORT 23\r
\r
/* Enums: */\r
\r
/** \file\r
*\r
- * uIP Managament functions. This file contains the functions and globals needed to maintain the uIP\r
+ * uIP Management functions. This file contains the functions and globals needed to maintain the uIP\r
* stack once an RNDIS device has been attached to the system.\r
*/\r
\r
{\r
if ((USB_CurrentMode == USB_MODE_HOST) && (USB_HostState == HOST_STATE_Configured))\r
{\r
- uIPManagement_ProcessIncommingPacket();\r
+ uIPManagement_ProcessIncomingPacket();\r
uIPManagement_ManageConnections();\r
}\r
}\r
}\r
}\r
\r
-/** Processes incomming packets to the server from the connected RNDIS device, creating responses as needed. */\r
-static void uIPManagement_ProcessIncommingPacket(void)\r
+/** Processes Incoming packets to the server from the connected RNDIS device, creating responses as needed. */\r
+static void uIPManagement_ProcessIncomingPacket(void)\r
{\r
/* If no packet received, exit processing routine */\r
if (!(RNDIS_Host_IsPacketReceived(&Ethernet_RNDIS_Interface)))\r
\r
LEDs_SetAllLEDs(LEDMASK_USB_BUSY);\r
\r
- /* Read the incomming packet straight into the UIP packet buffer */\r
+ /* Read the Incoming packet straight into the UIP packet buffer */\r
RNDIS_Host_ReadPacket(&Ethernet_RNDIS_Interface, uip_buf, &uip_len);\r
\r
/* If the packet contains an Ethernet frame, process it */\r
/* Filter packet by MAC destination */\r
uip_arp_ipin();\r
\r
- /* Process incomming packet */\r
+ /* Process Incoming packet */\r
uip_input();\r
\r
/* If a response was generated, send it */\r
void uIPManagement_UDPCallback(void);\r
\r
#if defined(INCLUDE_FROM_UIPMANAGEMENT_C)\r
- static void uIPManagement_ProcessIncommingPacket(void);\r
+ static void uIPManagement_ProcessIncomingPacket(void);\r
static void uIPManagement_ManageConnections(void);\r
#endif\r
\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = USBKEY\r
MCU = at90usb1287\r
\r
\r
-# Target board (see library "Board Types" documentation, USER or blank for projects not requiring\r
+# Target board (see library "Board Types" documentation, NONE for projects not requiring\r
# LUFA board drivers). If USER is selected, put custom board drivers in a directory called \r
# "Board" inside the application directory.\r
BOARD = XPLAIN\r
projects / pub / USBasp.git / commitdiff