Figure 1.3: Eagle 50 Hardware Block Diagram
The Eagle series of single board computers run on an ARM Cortex-M3 microcontroller with a vast array of peripherals from 10/100 Ethernet to a reprogrammable CPLD. Through example programs and project files this family of single board computers can be developed from concept to production quickly. The Eagle family is available in custom and standard configurations.
The Eagle 50 is a single board computer designed for cost-sensitive control applications that require real-time performance, networking and extensive support of popular peripherals. It delivers 32-bit performance and features at a cost equivalent to legacy 8- and 16-bit controllers. Powered by a Texas Instruments ARM Cortex-M3 microcontroller, capable of over 60 MIPS, the Eagle 50 can fulfill demanding requirements in monitoring, instrumentation, data acquisition, process control, factory automation and many other applications. The 50E adds 100 Mbps Ethernet for high performance networking.
The EAGLE 50-20 development kit comes with all of the necessary hardware and software to quickly develop applications. The development kit includes the following:
The Eagle SBC is also available unbundled, without the power supply and debugger.
Code examples are included with the Eagle 50 to get you started quickly. Applications can run standalone with no operating system or can use a compact real time operating system such as FreeRTOS. You can use popular IDEs together with the GNU and IAR compilers. The microSD card capability simplifies program and data storage. Remote access can be implemented via web or command line interfaces, providing off-site monitoring and maintenance capabilities. The JTAG interface speeds up application development and debugging. Ports of popular Basic and LUA development tools are available for the Eagle 50 to reduce application development time and simplify integration with code libraries developed for industrial and scientific environments. Using these tools, you can achieve significant functionality in a very short time. These open source tools can be easily extended, allowing a virtually unlimited number of possibilities. Micromint USA provides free technical support by phone, email, or fax. Technical support emails are usually answered within one business day. Software and documentation updates are available on our website at www.micromint.com. Each product comes with a one year warranty.
Getting started with the Eagle 50/50E can be done in just 6 steps.
The Eagle 50E and Eagle 50 come from the factory preloaded with applications. The Eagle 50E has an Ethernet application called enet_io that demonstrates web-based I/O control. The Eagle 50 has a micro SD card application called sd_card that demonstrates accessing a micro SD card through a serial command line. The preloaded applications should be run to test the board after receiving it. The full source code for both applications is provided on the Eagle's Wiki. http://wiki.micromint.com/index.php/Eagle_Documentation
The Eagle Single Board Computer's (SBC) with Ethernet are shipped with the enet_io example application from the TI Stellarisware Library. This example application demonstrates web-based I/O control using the Ethernet controller and the lwIP TCP/IP Stack. DHCP is used to obtain an Ethernet address. If DHCP times out without obtaining an address, a static IP address will be chosen using AutoIP. The address that is selected will be shown on COM1, allowing access to the internal web pages served by the application via a normal web browser. Figure 2.1 shows the web page that will first be displayed.
In order to demonstrate this application on an Eagle SBC without the optional USB Debug Port you will need the following software and equipment:
Please follow these steps to run the enet_io application on an Eagle SBC without the optional USB Debug Port:
In order to demonstrate the enet_io application on an Eagle SBC with the optional USB Debug Port you will need the following software and equipment:
Please follow these steps to run the enet_io application on an Eagle SBC with the optional USB Debug Port:
The Eagle 50 SBC is shipped with the sd_card example application from the TI Stellarisware Library. This example application demonstrates reading a file system from a micro SD card. It makes use of FatFs, a FAT file system driver. The application provides a simple command console via the Eagle 50?s COM1 serial port for issuing commands to view and navigate the file system on the SD card. Figure 2.2 shows what is displayed on a terminal program when the application is run.
In order to demonstrate the sd_card application on an Eagle 50 without the optional USB Debug Port you will need the following software and equipment:
Please follow these steps to run the sd_card application on an Eagle 50 without the optional USB Debug Port:
In order to demonstrate the sd_card application on an Eagle 50 with the optional USB Debug Port you will need the following software and equipment:
Please follow these steps to run the sd_card application on an Eagle 50 with the optional USB Debug Port:
The Eagle Code Examples are generated from Stellarisware and may be downloaded from the Software Updates section of the Software Updates section of the Eagle Wiki. After they are downloaded unzip them into a directory of your choice. Descriptions of the examples can be viewed on the Eagle Examples Page.
The Code Examples currently supports the following C and C++ compilers :
The IAR EWARM C/C++ compiler generally produces the smallest code sizes for ARM targets and has excellent integrated debugging capabilities versus the GNU Toolchain. If a GNU chain is used then an IDE needs to be chosen.
An IDE installs when the IAR C/C++ Compiler is installed where the GNU tool chains do not install one. Code::Blocks IDE and the Eclipse IDE are the IDEs currently supported by the Code Examples. Debugging is currently not supported in the Code::Blocks IDE. If a debug environment is needed the Eclipse IDE should be use.
The IAR EWARM Kickstart Edition is a 32 KB code-sized limited version of the IAR C/C++ compiler and debugger. It can be downloaded from IAR's website.
After downloading the EWARM-KS-CD click on the application to install the IAR Embedded Workbench for ARM. Select the ?Install IAR Embedded Workbench? option from the Applications main menu as shown in Figure 2.4. Follow the instructions in the installation application. We suggest that you use the default directories, and the ?Full? installation option.
The Code Examples currently support two GNU tool chains:
Download the Sourcery G++ Lite 2010q1 for ARM EABI version of Sourcery CodeBench Lite Edition for ARM from Mentor Graphics website. When it is finished downloading click on the application to install it and a screen similar to Figure 2.5 should appear. We suggest that you use the default directories during the installation.
If make is not installed on the computer then perform the following steps:
Installing the devkitARM GNU Compiler can be done in 6 steps.
Eclipse is a Java application and has the potential to be run on a wide variety of hardware and operating systems. Eclipse may install on systems with as little as 64MB of memory, however, we recommend to have 1GB of memory or more.
Follow these steps to install the Eclipse IDE:
Codeblocks is a cross-platform IDE built around wxWidgets, designed to be extensible and configurable. It can be downloaded from the Codeblocks website by clicking the following link: http://www.codeblocks.org/downloads
Install Codeblocks by clicking on the downloaded executable.
Follow these steps to compile an example using EWARM.
Follow these steps to compile an example using the Code::Blocks IDE.
Follow these steps to compile an example using the Eclipse IDE.
All example programs include a Makefile that allows you to build binary images from the command line using the GNU toolchain. The GNU ?make? utility is installed as part of the GNU toolchain on the Eagle Setup CD. To build an image using the command line, just change to the project directory and execute ?make?. To build the image for blinky you would perform the following:
There are many options to download firmware to the Eagle SBC. This section covers firmware downloads using a J-Link debugger, USB Debugger, Ethernet Bootloader, and Serial Bootloader. The method used to download firmware will depend on what hardware is being used.
EWARM can be configured to download firmware using a variety of different debuggers. The following section explains how to set-up EWARM for using the J-Link, optional USB Debugger, and the picoJTAG.
Please see the picoJTAGs Wiki: http://wiki.micromint.com/index.php/PicoJTAG_Manual/Getting_Started#IAR_Plugin
CooCox CoFlash is a stand-alone Cortex M Flash Programming software for PCs running Microsoft Windows. It can be downloaded from the following website: http://www.coocox.org/CoFlash_Programmer.htm
Follow these steps to program a Cortex M microcontroller using CoFlash and the picoJTAG:
The Eagle 50E is shipped with an Ethernet bootloader that can be used to update the firmware on the board from an Ethernet connection. The bootloader uses the BOOTP and TFTP protocols to temporarily acquire an IP address and copy the binary image to the board. The LM Flash Programmer implements a small BOOTP and TFTP server to do this. The LM Flash Programmer can be downloaded from Texas Instruments website. http://www.ti.com/tool/lmflashprogrammer
The bootloader uses the first 8 KB of the flash address space (0x00000000 to 0x00001fff). Programs loaded with the bootloader should be linked to start at address 0x00002000. That is done automatically if you use the ?ewarm/application.icf? or ?gcc/application.ld? linker scripts used in the examples.
You can overwrite the bootloader if you so desire by using the ?ewarm/standalone.icf? or ?gcc/ standalone.ld? linker scripts and downloading your binary image via the JTAG. Currently the bootloader cannot be overwritten via the Ethernet port.
Follow the below steps to use the LM Flash Programmer and the Ethernet bootloader:
Ethernet bootloader troubleshooting guide:
The Eagle 50 is shipped with a Serial bootloader that can be used in conjuction with the LM Flash Programming software to update the firmware on the board from a Serial connection. The LM Flash Programmer can be downloaded from Texas Instruments website http://www.ti.com/tool/lmflashprogrammer.
To place the bootloader in update mode you need to press and hold the user button while the board is starting up, e.g. via power up or when pressing the reset button. After the board starts up release the user button and you will see the user LED blinking approximately once per second. That indicates the board is ready to receive a firmware update via a Serial connection.
Programs loaded with the bootloader should be linked to start at address 0x00002000. That is done automatically if you use the ?ewarm/application.icf? or ?gcc/application.ld? linker scripts used in the examples. You can overwrite the bootloader if you so desire by using the ?ewarm/standalone.icf? or ?gcc/ standalone.ld? linker scripts and downloading your binary image via the JTAG. Currently the bootloader cannot be overwritten via the Serial port.
Follow the below steps to set up the LM Flash Loader:
The application can be downloaded using the LM Flash Programmer and the optional USB Debugger by following these steps:
The application can be downloaded using the LM Flash Programmer and COM1 by following these steps:
The TI Flash Programmer can also be invoked from the command line. The command line allows you to program the Eagle SBC though Ethernet Bootloader, Serial Bootloader, or FTDI JTAG. This section provides a step by step procedure for each programming method. Follow these steps to program the board using the command line and the Ethernet Bootloader. The Eagle 50E and Eagle 100 comes with the Ethernet Bootloader.
lmflash -i ethernet -n 192.168.1.201,192.168.1.210,00-21-A3-00-01-02 blinky.bin
Follow these steps to program the board using the command line and the Serial Bootloader. The Eagle 50 comes with the Ethernet Bootloader.
lmflash -i serial -d -p COM7 -b 115200 -o 0x2000 -r blinky.bin
Follow these steps to program the board using the command line and the USB Debug Port
lmflash ?I ftdi ?r ?o 0x2000 blinky.bin 3. The command line will give you status while the board is programming.
To see all options available from the command line, use ?lmflash ?h?. To see other examples of command lines, use ?lmflash ?examples?.
The USB Debugger option for the Eagle 50 and Eagle 50E can be used with the LM Flash Programmer software to program the board. The LM Flash Programmer can be downloaded from Texas Instruments website http://www.ti.com/tool/lmflashprogrammer. The Eagle 50 and Eagle 50E come preprogrammed with a bootloader that uses the first 8 KB of the flash address space (0x00000000 to 0x00001fff). If you wish to keep the bootloader then applications should be linked to start at address 0x00002000.
Follow these steps to download Code Examples using the LM Flash Programmer and keeping the bootloader entact:
Follow these steps to download Code Examples using the LM Flash Programmer without the bootloader:
The Eagle 50 SBC's JTAG port is multiplexed with GPIO pins PB7, PC0, PC1, PC2, and PC3. Somtimes the debug port becomes locked and needs to be reset. Please follow the below steps to unlock the JTAG port.
The following image shows where some of the hardware components are located.
The Eagle 50 includes a Texas Instruments Stellaris LM3S1918 or LM3S6918 (50E) microcontroller. These 32-bit ARM Cortex-M3 RISC microcontroller are capable of 50-MHz operation with a Thumb2 instruction set for smaller object code. It has hardware division and single cycle multiplication for fast calculations. The nested vector interrupt controller provides interrupt handling for 33 interrupts with eight levels of priority. Please see Texas Instruments? LM3S1918 or LM3S6918 Microcontroller Data Sheet for more information and register definitions.
LM3S1918 or LM3S6918 key features:
A Seiko Instruments Inc. Real-Time Clock(RTC) comes optional on the Eagle 50. The RTC features a built-in clock-correction function, alarm interrupter, automatic leap year correction up to 2099. Communication to the RTC is done through an I2C bus that operates up to 400 kHz. The RTC has an alarm output that can be set to the second, minute, hour, day of the week, day, or month. For further information please see Seiko Instruments? S-35390A Data Sheet.
The Eagle 50 includes a National Semiconductor?s DAC104S085 general purpose digital-to-analog converter (DAC). The DAC has four channels with a resolution of 10-bit. The output amplifiers allow for a rail-to-rail output swing from 0 to 3.3V. Communication to the DAC is done through a three wire synchronous serial interface that operates up to 40 MHz. The DAC?s outputs have a settling time of 6µs. It allows for simultaneous output updating. For further information please see National Semiconductor?s DAC104S085 Data Sheet.
NEXT: User Interfaces, Connectors, and Jumpers
The following image shows where the connectors, headers, and jumpers are located on the Eagle 50.
The Eagle SBC requires a DC power supply on connector J1. When the LCD is not in use the power supply must deliver 4.4V to 15.0V. Typical current requirements are 125mA for the Eagle 50 and 250mA for the Eagle 50E, with all common peripherals enabled. When the LCD port is in use, the power supply must deliver 0.3V more than the voltage required for the LCD. This is to account for the voltage drop across the protection diode (D1). The LCD current requirements must be considered in sizing the power supply current capacity. J1 comes standard with a 2.5 mm positive center tapped female power supply jack. It can be populated with a 2 position screw terminal upon request. A diode (D1) will protect the Eagle 50 should polarity of the power supply be reversed. When power is applied LED1 will illuminate. If the optional USB debug port is populated the board is capable of being powered from the USB port by putting a jumper on JP1. WARNING: Power should not be connected to J1 and the user should make sure the board is not drawing too much power from the computers USB port.
| WARNING: Supply voltages over +5VDC while a LCD is connected may damage the LCD. |
The LM3S6918 is equipped with a fully-integrated 10/100 Mbps Ethernet Controller. Both the Ethernet Media Access Control (MAC) and Physical (PHY) layers are integrated in the microcontroller. The RJ-45 connector with integrated magnetics and built in LEDs completes the Ethernet sub-system. Please see the LM3S6918 data sheet for further information on the Ethernet controller.
Both Universal Asynchronous Receivers/Transmitters (UARTs) are level shifted to RS-232 levels. UART0 (COM1) and UART1 (COM2) can be accessed through a 2x5 pin berg header. Please see figure 4.3 for the pin outs of COM1 (J3) and COM2 (J4) connectors. The two serial ports support software handshaking (XON/XOFF) and are considered to be Data Terminal Equipment(DTE). In order to communicate to a Personal Computer a null modem cable is required. To simplify interfacing to devices using hardware handshaking, a loopback is implemented on the modem control signals, from RTS to CTS and from DTR to CD and DSR. Note that the loopbacks do not provide flow control so software handshaking should be used when proper flow control is desired.
If the optional USB Debug port is populated UART0 may be configured to communicate over USB by placing a jumper on JP6. UART0 can be accessed through the Micro-USB connector (J13). If the optional RS-485 driver (U5) is populated then UART1 can be level shifted to RS-232 or RS-485 levels. Figure 4.3 shows the jumper settings selecting RS-232 levels or RS-485 for COM2. The RS-485 transmitter is enabled by making port A bit 3 a logic 1.
The microSD socket (J9) enables micro-secure-digital memory cards to be plugged into the Eagle 50 microcontroller board. The microSD card allows the user the ability of a standard removable media for transferring data to and from the Eagle 50.
There are twenty bits of GPIO available on the J2 connector. Please see the pin out for J2 in Figure 4.5. Eight bits are from port B, eight are from port C and four are from port E. NOTE: If the keypad port (J11) is used then port B on the J2 connector should not be used (pins 3 through 10 of J2) and if the LCD port is used then port C on J2 should not be used (pins 13 through 20 of J2). Some of the ports have alternate functions other than digital inputs and outputs and are shared with some of the hardware on the board. Table 4.5 and table 4.6 lists the alternate functions, the hardware it is shared with, and a brief description of the alternate function. For further information on the alternate functions please refer to the LM3S1918 (50) or the LM3S6918 (50E) data sheet.
The J2 connector also has the input and output for the hibernation module. Pin 29 is the WAKE input that brings the microcontroller out of hibernation mode when it is asserted. Pin 30 is the HIB output that indicates the microcontroller is in hibernation mode. The power source (VBAT) for the hibernation module can be accessed from Pin 28 of J2.
There are twenty-two bits of GPIO available on the J12 connector. Please see the pin out for J12 in figure 4.5. Eight bits are from port F, eight are from port G, four are from port H and two are from port A. J12 is not populated for the Eagle 50E. The pins used for Ethernet (PF2, PF3, PF4, PF5, PF6, PF7, PG2, PG3, PG4, PG5, PG6, PG7, PH0, PH1, PH2, and PH3) are not available for GPIO in the LM3S6918 processor. If additional GPIOs are needed, J12 could be populated in the field to access PA3, PA7, PF0, PF1, PG0, and PG1. NOTE: If the LCD port is used then port F bits 0 and 1 should not be used (pins 3 and 4 of J12).
| J2 Pin# | GPIO/Alternate Function | Shared With | Alternate Function Brief Description |
| 3 | PB0/CCP0 | Keypad | Capture/Compare/PWM Channel 0 |
| 4 | PB1/CCP2 | Keypad | Capture/Compare/PWM Channel 2 |
| 5 | PB2/ I2C0 SCL | Keypad and Real Time Clock (RTC) | I2C bus 0 clock |
| 6 | PB3/ I2C0 SDA | Keypad and RTC | I2C bus 0 data |
| 7 | PB4/ C0- | Keypad | Analog comparator ch. 0 neg. input |
| 8 | PB5/ C1- | Keypad | Analog comparator ch. 1 neg. input |
| 9 | PB6/ C0+ | Keypad | Analog comparator ch. 0 pos. input |
| 10 | PB7/ TRST | Keypad | JTAG Test Reset |
| 13 | PC0/ TCK/SWCLK | LCD | JTAG Test Clock/SWD clock |
| 14 | PC1/ TMS/SWDIO | LCD | JTAG Test Mode Select/SWD I/O |
| 15 | PC2/ TDI | LCD | JTAG Test Data Input |
| 16 | PC3/ TDO/SWO | LCD | JTAG Test Data Output and SWD Ouput |
| 17 | PC4/ CCP5 | LCD | Capture/Compare/PWM Channel 5 |
| 18 | PC5/ C1+/C0o(Eagle 50E) | LCD | Analog comparator ch. 1 pos. input/ ch. 0 output |
| 19 | PC6/ CCP3 | LCD | Capture/Compare/PWM Channel 3 |
| 20 | PC7/ CCP4 | LCD | Capture/Compare/PWM 4 |
| 23 | PE0/ SSI1Clk | Synchronous Serial Interface bus 1 clock | |
| 24 | PE1/ SSI1Fss | User LED | SSI bus 1 function slave select |
| 25 | PE2/ SSI1Rx | SSI bus 1 receiver | |
| 26 | PE3/ SSI1Tx | SSI bus 1 transmitter | |
| 29 | *WAKE | RTC | Brings the processor out of hibernate mode |
| 30 | *HIB | Indicates the processor is in hibernate mode |
| J12 Pin# | GPIO/Alternate Function | Shared With | Alternate Function Brief Description |
| 3 | PF0 | LCD | |
| 4 | PF1 | LCD | |
| 5 | PF2/LED1(Eagle 50E) | Media Independent Interface LED0 | |
| 6 | PF3/LED2(Eagle 50E) | Media Independent Interface LED1 | |
| 7 | PF4/C0o(Eagle 50) | Analog comparator ch. 0 output | |
| 8 | PF5 C1o(Eagle 50) | Analog comparator ch. 1 output | |
| 9 | PF6/CCP1 | Capture/Compare/PWM Channel 1 | |
| 10 | PF7 | ||
| 13 | PG0/ I2C1 SCL(Eagle 50E) | DAC | I2C bus 1 clock |
| 14 | PG1 | microSD | |
| 15 | PG2 | ||
| 16 | PG3 | ||
| 17 | PG4 | ||
| 18 | PG5 | ||
| 19 | PG6 | ||
| 20 | PG7 | ||
| 23 | PH0/CCP6 | Capture/Compare/PWM Channel 6 | |
| 24 | PH1 | ||
| 25 | PH2 | ||
| 26 | PH3 | ||
| 29 | PA3/SSI0 Fss | SSI bus 0 function slave select | |
| 30 | PA7/I2C1 SDA | I2C bus 1 data |
A 4x4 matrix keypad using a 16-pin (2x8) ribbon cable can be connected to port B of the microcontroller through J11. Please see Figure 4.6 for the pin out of the keypad connector. NOTE: Applications using the keypad connector (J11) should not use port B on the GPIO connector (J2) or the I2C Real-Time Clock.
A standard alphanumeric LCD may be connected to J10 through a 32-pin (2x16) ribbon cable. GPIO Port C is the byte-wide port used for the LCD?s data bus. The LCD?s control signals are connected to PORT D and F of the microcontroller. Port F controls the LCDs register select (PF0) and read/write (PF1) signals. Port D controls the enable signal (PD0) and the backlight (PD1). If port d bit 0 is logic 1 then the backlight will be illuminated. The contrast for the LCD may be adjusted by turning potentiometer R52 located next to J10. Please see figure 4.7 for the LCD?s connector pin out. NOTE: If the LCD port (J10) is used then port C on the J2 connector should not be used (pins 13 through 20 of J2) and Port F bit 0 and 2 should not be used on the J12 connector (pins 3 and 4). AZ Displays ACM2004D series is recommended for use with the Eagle 50/50E. http://www.azdisplays.com/index.php?id=Character_Modules&product=c2004d
The JTAG port (J5) can be used for software download and debugging, reducing the need for an in-circuit emulator. For detailed information on the operation of the JTAG port and TAP controller, please refer to IEEE Standard 1149.1-Test Access Port and Boundary-Scan Architecture.
Debugging and program updates can also be performed using the optional USB debug port accessible through a micro-USB connector (J13). The USB debug port is supported by the following development tools:
With the USB debug port, the Eagle SBC can also be used via the JTAG connector (J5) to debug or program another Eagle SBC that does not have a USB debug port. The USB debug port also allows UART0 to communicate over USB. Please see section 4.3 for further information. To use an external debugger such as the IAR J-link when the optional USB debug port is installed, a jumper must be installed on JP8 to disable the USB debug functionality. J14 is only used by the factory and is never populated.
The Eagle 50?s eight channels of 10-bit ADC can be connected to through J7. Please see figure 4.9 for the pin out of the ADC connector. The ADC is accessed directly through the LM3S1918 or the LM3S6918 microcontroller. It is capable of 500k samples/second and can be configured as eight single ended or four differential channels. The ADC can be triggered to read through software, timers, analog comparators, or GPIO. An internal temperature sensor may be read using the ADC module. Please see the LM3S1918 or the LM3S6918 datasheet for further details.
|
| WARNING: Applying more than 3.0 VDC to an analog input will damage the microcontroller. |
The Eagle 50?s four channels of 10-bit DAC can be connected to through J8. Please refer to figure 4.10 for the pin out of the DAC connector. It is capable of outputting voltages between 0 and 3.3V. The DAC is accessed through the LM3S1918 or the LM3S6918 SSI0 port. Port G bit 0 is the DAC?s sync input for loading the conversion count into the DAC. The DAC can be updated at a maximum of 150 kHz for 1 channel. The data transfer is 16-bits at 25 MHz which is a total of 640 nS per data transfer but the DAC has a settling time of 6 µS so the total time needed is 6.64 µS. All 4 channels of the DAC can be updated at a maximum of 116 kHz. This is accomplished by sending the data for all 4 channels and updating all of the outputs on the last data transfer.
The Eagle 50 comes standard with a user pushbutton, a reset push button, a user LED and a power LED. The user push button is connected to port A bit 6 with a 10kO pull-up resistor connected to it. The user LED can be illuminated by setting port E bit 1 of the LM3S1918 or the LM3S6918.
JP5 on the Eagle 50 is used to connect the coin battery to VBAT of the LM3S1918?s or the LM3S6918?s hibernation module. This will allow the hibernation module to be battery backed should the main power be lost. Due to errors in the silicon of the LM3S1918 and LM3S6918?s hibernation module should not be used to keep an accurate clock. The external RTC (Seiko 35390A) should be used. Please see the ?LM3S1918 RevA2 Errata? or the ?LM3S6918 RevA2 Errata? for further details.
PREVIOUS: Mechanical and Electrical Characteristics
| Characteristic | Minimum | Maximum | Unit |
| Voltage on J1 without LCD | 4.8 | 15.0 | VDC |
| Voltage on J1 with LCD | 4.4 | 5.8 | VDC |
| Voltage on VBAT (JP7 or J2) | 0.0 | 3.3 | VDC |
| Voltage on ADC | 0.0 | 3.0 | VDC |
| Voltage on Digital Input | 0.0 | 5.0 | VDC |
| Operating Temperature | 0 | 70 | ºC |
| Storage Temperature | -50 | 125 | ºC |
The Eagle SBC is currently available for commercial temperature ranges. Contact the Micromint sales department if you require support for industrial temperature ranges.
Test Conditions: Vin (J1) = 5.63V, VCC = 3.3V, LM3Sxxx LDO set to 2.5V
Below is the physical dimensions for the Eagle 50. The mounting holes will accept a #4 size screw.
| DIM | Inches | Millimeters | DIM | Inches | Millimeters | DIM | Inches | Millimeters |
| A | 3.94 | 100.0 | H | 0.63 | 16.0 | O | 1.34 | 34.03 |
| B | 0.116 | 2.95 | I | 0.803 | 20.38 | P | 2.83 | 72.0 |
| C | 0.851 | 21.61 | J | 0.664 | 16.86 | Q | 0.115 | 2.92 |
| D | 0.567 | 14.4 | K | 0.473 | 12.01 | R | 0.895 | 22.73 |
| E | 1.69 | 43.0 | L | 0.275 | 6.98 | S | 0.3 | 7.62 |
| F | 0.4 | 10.16 | M | 0.117 | 2.97 | T | 0.608 | 15.44 |
| G | 0.265 | 6.73 | N | 0.12 | 3.04 | U | 0.76 | 19.3 |
| DIM | Inches | Millimeters | DIM | Inches | Millimeters | DIM | Inches | Millimeters | DIM | Inches | Millimeters |
| A | 0.33234 | 8.4415 | E | 1.26 | 32.0 | I | 0.261 | 6.63 | M | 0.136 | 3.45 |
| B | 0.3543 | 9.0 | F | 0.56693 | 14.40 | J | 0.06 | 1.524 | N | 0.269 | 6.83 |
| C | 0.117 | 2.9721 | G | 0.072 | 1.83 | K | 0.545 | 13.843 | O | 0.177 | 4.5 |
| D | 0.345 | 8.763 | H | 0.63 | 16.00 | L | 0.1 | 2.54 | P | 0.256 | 6.50 |
PREVIOUS: User Interfaces, Connectors, and Jumpers
This section outlines material that may be useful for further reading.
LM3S6918 Microcontroller Data Sheet
http://www.ti.com/product/lm3s6918
This data sheet provides reference information for the LM3S6918 microcontroller, describing the functional blocks of the system-on-chip (SoC) device designed around the ARM® Cortex?-M3 core. All MCU registers are described in the data sheet.
LM3S1918 Microcontroller Data Sheet
http://www.ti.com/product/lm3s1918
This data sheet provides reference information for the LM3S1918 microcontroller, describing the functional blocks of the system-on-chip (SoC) device designed around the ARM® Cortex?-M3 core. All MCU registers are described in the data sheet.
|
|
The Definitive Guide to ARM® Cortex-M3 and Cortex-M4 Processors, Third Edition by Joseph Yiu ISBN: 0124080820 Publisher: Newnes (November, 2013) Overview of the processor and instruction set architecture of the ARM® Cortex®-M3 and Cortex®-M4 processors. Several code examples using IAR, Keil, gcc and CooCox CoIDE. |
|
|
The Designer's Guide to the Cortex-M Processor Family: A Tutorial Approach by Trevor Martin ISBN: 0080982964 Publisher: Newnes (May, 2009) Tutorial-based book giving the key concepts required to develop programs in C with a Cortex M- based processor. |
|
|
ARM System Developer's Guide: Designing and Optimizing System Software ISBN: 1558608745 Publisher: Morgan Kaufmann; (March, 2004) In-depth overview of the ARM architecture with examples that outline impact of programming practices on performance, power and cost. |
Micromint Web Site
Product information and software updates for the Eagle SBCs.
Texas Instruments Web Site
Manuals and application notes for the LM3S1918 and LM3S6918 microcontroller.
