SeaLevel SBC-R9 SBC-R9-KT ARM9 RISC Single Board Computer QuickStart Kit User manual
Add to my manuals78 Pages
advertisement
SBC-R9 ARM9 RISC Single Board Computer
Sealevel Systems, Inc. Sealevel.com Phone 864.843.4343
Contents
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 2
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 3
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 4
Safety Instructions
A sudden electrostatic discharge can destroy sensitive components. Proper packaging and earthing rules must therefore be observed. Always take the following precautions.
Transport boards and cards in electrostatically secure containers or bags.
Keep electrostatically sensitive components in their containers, until they arrive at an electrostatically protected workplace.
Only touch electrostatically sensitive components when you are properly earthed.
Store electrostatically sensitive components in protective packaging or on anti-static mats.
The following measures help to avoid electrostatic damages to the device:
Cover workstations with approved antistatic material. Always wear a wrist strap connected to workplace as well as properly grounded tools and equipment.
Use antistatic mats, heel straps, or air ionizers for more protection.
Always handle electrostatically sensitive components by their edge or by their casing.
Avoid contact with pins, leads, or circuitry.
Turn off power and input signals before inserting and removing connectors or connecting test equipment.
Keep work area free of non-conductive materials such as ordinary plastic assembly aids and Styrofoam.
Use field service tools such as cutters, screwdrivers, and vacuum cleaners which are conductive.
Always place drives and boards PCB-assembly-side down on the foam.
5 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Introduction
The SBC-R9 is an application-ready platform for your next product design. The system is based on the 200MHz Atmel AT91SAM9263 microcontroller boasting a 32-bit ARM® instruction set for maximum performance. With up to 256MB RAM and 256MB NAND Flash memory, the unmatched I/O features of the SBC-R9 extend the possible uses beyond traditional ARM applications.
To provide the fastest time to market, the Windows CE 6.0 BSP binary and low-level drivers for system I/O are included. Additionally, the SBC-R9 software package is equipped with the
Sealevel Talos I/O Framework, which offers a high-level object-oriented .NET Compact
Framework (CF) device interface. This interface provides an I/O point abstraction layer with built-in support for the specific needs of analog and digital I/O such as gain control and debouncing.
Atmel AT91SAM9263 ARM® Processor
Up to 256MB SDRAM and 256MB NAND Flash Memory
Dual SD/MMC Expansion Card Slots
LCD and Backlight Controller
Resistive Touchscreen Controller
10/100 BaseT Ethernet
Two USB 2.0 Ports; USB Device Port
CAN Bus Interface
On-board Serial, Digital, and Analog I/O
Compatible with Windows Embedded CE 6.0 and Linux
Low Power Requirements
Power and Status LED Indicators
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 6
Before You Get Started
The SBC-R9 is shipped with the following items. If any of these items are missing or damaged, please contact Sealevel for replacement.
SBC-R9 ARM9 Embedded RISC Single Board Computer
SD Card with CE runtime image, Talos .NET Framework, application samples, and documentation
CD with Setup files and documentation
Microsoft® Windows® CE 6.0 Core license
Warning - The highest level of importance used to stress a condition where damage could result to the product or the user could suffer serious injury.
Important – The middle level of importance used to highlight information that might not seem obvious or a situation that could cause the product to fail.
Note – The lowest level of importance used to provide background information, additional tips, or other non-critical facts that will not affect the use of the product.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 7
The SBC-R9 QuickStart Kit (Item# SBC-R9-KT) is available, which includes the most common accessories. For applications with specialized hardware requirements, developers can use the
SBC-R9 as a platform for application development while Sealevel designs a customized target system specific to the user’s application requirements.
The SBC-R9-KT includes the following items:
SBC-R9 ARM9 Embedded RISC Single Board Computer
SD Card with CE runtime image, Talos .NET Framework, application samples, and documentation
CD with setup files and documentation
Microsoft Windows CE 6.0 Core License
TR134 – 100-240VAC to 12VDC @ 2.5A, wall mount power supply
CA179 – USB Type A to USB Type B, device cable
CA429 – R9 serial debug cable
CA246 – CAT5 patch cable, 6' length
CA273 – 40-pin IDC ribbon cable to (4) DB9M connectors
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 8
Depending upon your application, you are likely to find one or more of the following items useful with the SBC-R9. All items can be purchased from our website ( www.sealevel.com
) by calling our sales team at (864) 843-4343.
USB Type A to USB Type B, 72" in Length - Device Cable (Item# CA179)
The CA179 is a 72" standard USB device cable that connects USB peripherals with a Type B connector to the
Type A connector on a host computer. The CA179 is USB
2.0 compliant and is compatible with USB 1.1 and 1.0 devices.
CAT5 Patch Cable, 7' in Length – Blue (Item# CA246)
Standard 7' CAT5 UTP Patch Cable (RJ45).
40-Pin IDC Ribbon Cable to (4) DB9 Male Connectors, 14" in Length (Item# CA273)
40-Pin IDC Ribbon Cable terminates to (4) DB9 Male
Connectors, 14" in Length.
R9 Serial Debug Cable, 72" in Length (Item# CA429)
The CA429 is a 72" serial debug cable with a 1x4 connector on one end and a standard DB9F connector on the other end. The DB9F connector is compatible with any standard RS-232 DB9M serial port.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 9
100-240VAC to 12VDC @ 2.5A, Wall Mount Power Supply (Item# TR134)
The TR134 is a wall mount (wall wart style) power supply rated for 100-240VAC input and 12VDC output at 2.5 amps. The 72" cable has a two-position socket (Molex
09-50-1021) for use with products that have a twoposition header (Molex 09-65-2028) for input power.
Connector position 1 indicates positive polarity.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 10
Product Overview
Atmel (AT91SAM9263) — 200MIPS RISC Processor
16KB Data Cache, 16KB Instruction Cache, Write Buffer
Integrated Memory Management Unit (MMU)
Up to 256MB SDRAM (64 MB Standard)
256MB NAND Flash
Two SD Memory Card Sockets
Supports Passive or Active Displays
16-bit Color in TFT/STN Modes
Resolution Up to 2048 x 2048
Supports 5-wire Resistive Touchscreens
10/100 BaseT Ethernet
USB Device Port
Two USB 2.0 Ports
CAN Bus
Dedicated RS-485 Expansion
Four Software Configurable RS-232/422/485 Ports
Eight Optically Isolated Inputs (5 – 24V)
Eight Open-Collector Outputs (5 – 30V; 3 with PWM)
Eight Analog Inputs (12-bit or 16-bit)
Two 32-bit Quadrature Counters
Dual LED Indicators for Power and Status
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 11
See Appendix B for the Connector Reference Table, which details the connectors, jumpers, and test points located on the SBC-R9.
12 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Technical Description
The SBC-R9 base configuration includes 128MB SDRAM and 256MB NAND Flash. For memory intensive applications, the board can be ordered preconfigured with up to 256MB SDRAM.
The SBC-R9 includes a 10/100 BaseT Ethernet interface accessed via the RJ45 connector located at (J14).
The RJ45 port on the left side of the SBC-R9 is a RS-485 Expansion Port (labeled J5) and is NOT an Ethernet port. Damage to Ethernet networking equipment can result if connected to the RS-485 RJ45 connector.
Pin Signal
4
5
6
7
8
1 TX+
2 TX-
3 RX+
NC
NC
RX-
NC
NC
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 13
The SBC-R9 provides two USB 2.0 host ports, and one device port. The host USB ports are located at (J7) and (J8). The device USB port is located at (J13).
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
J7, J8
Molex
35362-0450
2.00mm (.079") Pitch Sherlock™ Wire-to-Board Header, Vertical, with
Positive Lock, 4 Circuits
Molex 35507-0400 Sherlock™ Wire-to-Board Housing with Molex
0502128100 2.00mm (.079”) Pitch Crimp Terminals
Pin Signal
1 5VDC
2 Data-
3 Data+
4 GND
Connector:
Manufacturer:
Description:
J13
Samtec
High Retention USB Type B
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 14
A variety of LCDs can be directly controlled by the SBC-R9’s on-board LCD controller. All LCD power and control signals are available on header connector P2.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P2
Samtec
TFML-125-02-S-D
Locking terminal strip, 50 pos, 0.050” pitch
Samtec SFML-125-T2-S-D or Samtec TFMDL-25-T-03.00
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 15
Signal
R3
R4
R5
GND
G0
G1
G2
G3
GND
DCLK
HSYNC
VSYNC
GND
R0
R1
R2
G4
G5
GND
B0
B1
B2
B3
B4
B5
Position
13
14
15
16
9
10
11
12
5
6
7
8
1
2
3
4
21
22
23
24
25
17
18
19
20
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Position
38
39
40
41
34
35
36
37
30
31
32
33
26
27
28
29
46
47
48
49
50
42
43
44
45
Signal
GND
LCDEN
3.3V
3.3V
HDMODE
VDMODE
NC
NC
NC
NC
Touch UL
Touch LL
Touch UR
Touch LR
Touch Wiper
NC
NC
NC
NC
LCDLED3
GND
LCDLED2
GND
LCDLED1
GND
16
Debug the R9 through the RS-232 debug port.
Connector:
Manufacturer:
Part Number:
Description:
J6
Amp/Tyco
9-146278-0-04
Header, 0.100” Polarized 4 pos, pin 3 Removed
Pin RS-232
1 RX
2 GND
3 Key
4 TX
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 17
Connect to a variety of serial peripherals via the SBC-R9’s software configurable RS-
232/422/485 ports. Each port is located on connector (P4).
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P4
Sullins
SBH11-PBPC-D20-ST-BK
Box Header, 0.100” Polarized 40 pos (2x20)
SFH213-PPPC-D20-ID-BK-M181 or equivalent
Pin RS-232 RS-422/485 Port Pin RS-232 RS-422/485
1 DCD
2 DSR
3
4
RX
RTS
5
6
TX
CTS
7 DTR
8 RI
9 GND
10 GND
11 RI
12 DTR
13 CTS
14 TX
15 RTS
16 RX
17 DSR
18 DCD
19 DCD
20 DSR
RX+
NC
RX-
NC
TX-
NC
TX+
NC
GND
GND
NC
TX+
NC
TX-
NC
RX-
NC
RX+
RX+
NC
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL4
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL3
SERIAL2
SERIAL2
21 RX
22 RTS
23 TX
24 CTS
25 DTR
26
29
30
31
RI
27 GND
28 GND
RI
DTR
CTS
32 TX
33 RTS
34 RX
35 DSR
36 DCD
37 NC
38 NC
39 NC
40 NC
Port
SERIAL2
SERIAL2
SERIAL2
SERIAL2
SERIAL2
SERIAL2
SERIAL2
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
RX-
NC
TX-
NC
TX+
NC
GND
GND
NC
TX+
NC
TX-
NC
RX-
NC
RX+
NC
NC
NC
NC
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 18
COM Port Assignments
Serial Port
RS232 Debug Port
RS485 Expansion Port
SERIAL1
SERIAL2
SERIAL3
SERIAL4
Assignment
COM0
COM1
COM2
COM3
COM4
COM5
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 19
The DB9 pin out is achieved using the CA273 accessory cable. The 40-pin connector is in the first column and corresponding DB9 connectors are in the second column.
Pin Serial4
4
5
6
7
8
9
1
2
3
8
4
9
5
1
6
2
7
3
Pin Serial3
10
11
12
13
14
15
16
17
18
5
9
4
8
3
7
2
6
1
Pin Serial2
19
20
21
22
23
24
25
26
27
8
4
9
5
1
6
2
7
3
Pin Serial1
28
29
30
31
32
33
34
35
36
5
9
4
8
3
7
2
6
1
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 20
Connect directly to a Control Area Network (CAN) bus via connector (J3). A Molex 4-pin vertical 2mm locking header is used for the connection.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
J3
Molex
35362-0450
2.00mm (.079") Pitch Sherlock™ Wire-to-Board Header,
Vertical, with Positive Lock, 4 Circuits
Molex 35507-0400 Sherlock™ Wire-to-Board Housing with Molex 0502128100
2.00mm (.079”) Pitch Crimp Terminals
Pin Signal
1 CAN High
2 GND
3 CAN Low
4 Shield
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 21
Directly monitor 8 optically isolated inputs, which are found on connector (P5). The non-polarized inputs can range from 5-24VDC and provide 300V external isolation.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P5
Sullins
SBH11-PBPC-D08-ST-BK
Box Header, 0.100” Polarized 16 pos (2x8)
Sullins SFH213-PPPC-D08-ID-BK-M181 or equivalent
Pin Signal
1 Input 1A
2 Input 1B
3 Input 2A
4 Input 2B
5 Input 3A
6 Input 3B
7 Input 4A
8 Input 4B
9 Input 5A
10 Input 5B
11 Input 6A
12 Input 6B
13 Input 7A
14 Input 7B
15 Input 8A
16 Input 8B
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 22
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 23
Directly control 8 outputs via the SBC-R9’s open-collector outputs found on connector (P6). The open collector outputs have a range of 5 – 30V with a maximum sink current of 500mA on a single output with a combined maximum sink current of 580mA on all outputs.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P6
Sullins
SBH11-PBPC-D05-ST-BK
Box Header, 0.100” Polarized 10 pos (2x5)
Sullins SFH213-PPPC-D05-ID-BK-M181 or equivalent
Pin Signal
6
7
8
9
10
1 Output 1/ PWM1
2 Output 2 / PWM2
3 Output 3 / PWM3
4 Output 4
5 Output 5
Output 6
Output 7
Output 8
OCVCC
GND
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 24
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 25
The SBC-R9 base configuration includes a 12-bit ADC. Software programmable input ranges are 0V to 5V,
0V to 10V, ±5V or ±10V. Interface a variety of transducers and other analog signals via eight 12-bit analog inputs located on connector (P1). For applications requiring higher resolution, the board can be ordered preconfigured with a 16-bit A/D converter.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P1
Sullins
SBH11-PBPC-D08-ST-BK
Box Header, 0.100” Polarized 16 pos (2x8)
Sullins SFH213-PPPC-D08-ID-BK-M181 or equivalent
Pin Signal
1 AIN1+
2 AIN1-
3 AIN2+
4 AIN2-
5 AIN3+
6 AIN3-
7 AIN4+
8 AIN4-
9 AIN5+
10 AIN5-
11 AIN6+
12 AIN6-
13 AIN7+
14 AIN7-
15 AIN8+
16 AIN8-
26 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
High-speed input monitoring is accomplished with minimal software overhead using the two onboard 32-bit quadrature counters. Both counters are available on a single connector (P7). Input levels are LVTTL (0 –
3.6VDC).
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P7
Sullins
SBH11-PBPC-D05-ST-BK
Box Header, 0.100” Polarized 10 pos (2x5)
Sullins SFH213-PPPC-D05-ID-BK-M181 or equivalent
Pin Signal
1 A
3 B
5 #INDEX
7 GND
9 3.3VDC
Pin Signal
2 A
4 B
6 #INDEX
8 GND
10 3.3VDC
27 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
The SBC-R9 provides two SD/MMC Card slots, Slot A (bottom of board) and Slot B (top of board), located on the right side of the board. Each slot will accept standard-capacity SD/MMC Cards up to 2GB. SD/MMC Card slot A may be used for booting.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 28
The SBC-R9 provides a RS-485 Expansion Port. The port is available via a RJ-45 connector (J5), as well as via a Molex 4-pin vertical 2mm locking header (J10). This offers two convenient options for adding additional expansion modules from the SeaI/O product line.
The RJ45 port (J5) is a RS-485 Expansion Port and is NOT an Ethernet port. Damage to Ethernet networking equipment can result if connected to the RS-485 RJ45 connector.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
J5
Xmultiple
XRJM-S-01-8-8-F2 or XRJM-S-01-8-8-0
RJ45 Socket, W/O LEDs, Shielded
Standard RJ45 Plug
Pin Signal
1 9-30VDC Source
2 9-30VDC Source
3 Not connected
4
5
485+
485-
6 Not Connected
7 Common (GND)
8 Common (GND)
8
1
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
J10
Molex
35362-0450
2.00mm (.079") Pitch Sherlock™ Wire-to-Board Header,
Vertical, with Positive Lock, 4 Circuits
Molex 35507-0400 Sherlock™ Wire-to-Board Housing with Molex 0502128100
2.00mm (.079”) Pitch Crimp Terminals
Pin
1
2
3
4
Signal
485-
485+
Common (GND)
Shield (GND)
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 29
The SBC-R9 can be powered with the Sealevel TR134.
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P3
Molex
09-65-2028
3.96mm Pitch Friction Lock Header
Molex 09-50-1021
Be sure that you connect the power lead to the proper pin. Reversing the polarity of the power input will damage your SBC-R9.
Pin Signal
1
2
9-30VDC
GND
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 30
The SBC-R9 features two LED indicators for power and status. The Green LED (Top) is illuminated when power is applied to the board. The Yellow LED (Bottom) is a GPIO controllable indicator accessible through the TALOS API.
Designator:
Description:
D9
Dual Stacked LED Indicators
LED Color Signal
Top Green Power
Bottom Yellow Status
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 31
Software
Remove the contents from the box.
Insert the accompanying CD into your PC and run the installation program. This will install Talos Framework binaries, OS Runtime Images, documentation, and examples on your PC. (See Figure 1.)
Figure 1. Installation Wizard
After installation, the package can be found in Windows by clicking Start All Programs Sealevel
Systems R9 Development.
Verify that the accompanying SD Card (located on the bottom card slot A (J15) of the SBC-R9) is correctly inserted. The contents of the SD Card will allow the SBC-R9 to run Windows CE 6.0 OS when power is applied to the board.
32 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
To avoid accidental damage, be sure to follow proper ESD procedures by grounding yourself and the board.
To avoid accidental damage, be sure to observe proper power connector polarity. See Power Pin-out
section.
Apply power to the SBC-R9 by connecting the TR134 Molex connector to the SBC-R9 (P3) connector, noting proper polarity. Attach the other end of the TR134 into a 120VAC wall outlet. (See Figure 2.)
Figure 2.
Connect the TR134 Molex connector to the SBC-R9 (P3) connector
Use a standard USB device cable and connect the Type B connector to the SBC-R9. (See Figure 3.) Connect
Type A connector into the host PC.
Figure 3
.
Connect the Type B connector to the SBC-R9
You are now ready to set up a USB communication interface between the host PC and the SBC-R9 board.
Depending on which operating system you are using – Windows 7, Vista, or XP – the setup experience will vary.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 33
If your host PC is running Windows Vista or later and you are connected to the internet, then Windows
Mobile Device Center software will install automatically. If you are not connected to the internet but have obtained the Mobile Device Center software manually then running their setup will achieve the same result. (See Appendix A.)
After installation, a negotiation will begin between the PC and the SBC-R9 board and the device center connection screen will appear. (See Figure 4.)
Figure 4. Device Center connected screen
Using your mouse, click “Connect without setting up your device”. The idea is to explore the file system on the SBC-R9 without setting up synchronization with contacts, calendar, or e-mail. Now choose “File
Management Browse the contents of your device” from the screen. (See Figure 5.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 5. Device Center File Management
SBC-R9 Manual 34
This action opens a standard Windows Explorer where the default file contents of the SBC-R9 can be read or written to. (See Figure 6.)
Figure 6. Contents of SBC-R9
If your host PC is running Windows XP, ActiveSync is required to establish connection to the SBC-R9.
ActiveSync differs from Mobile Device Center in that having an internet connection will not establish an automatic download and installation. For installation procedures, refer to Microsoft’s website. (See
Appendix A). After installation, a negotiation will begin between the PC and the SBC-R9 board, and the
“New Partnership” dialog will appear. (See Figure 7.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 7. ActiveSync New Partnership screen
SBC-R9 Manual 35
Using your mouse, select “No” and then select “Next”. The ActiveSync main dialog will appear. Click the
“Explore” icon. This action opens a standard Windows Explorer where the default file contents of the
SBC-R9 can be read or written. (See Figure 8.)
Figure 8. ActiveSync Main Dialog screen
You are now ready to set up a complete development environment for building and debugging smart device applications and libraries. The next section guides you by example using Microsoft Visual Studio.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 36
With .NET Compact Framework coupled with our Talos .NET Framework, C# and VB.NET programmers can develop powerful embedded applications on the SBC-R9 such as mobile, robotics, home automation, industrial, and a broad range of other embedded applications. The low cost of licensing for Windows 6.0 CE has created an ideal environment to develop a new generation of embedded products around the SBC-R9.
Our Talos Framework allows access to the more specific I/O sections of the SBC-R9 development board such as analog and digital I/O points, CAN bus, quadrature counter inputs, and the multielectrical interface serial ports. A complete list of the API documentation can be found either in
Windows by clicking Start All Programs Sealevel Systems R9 Development Talos
Documentation.html.
Writing .NET applications for the SBC-R9 is very similar to writing desktop or console applications for Windows XP, Vista, and 7. The only difference is the amount of resources available. Because the memory footprint is smaller compared to a desktop computer, care should be taken where allocation of memory is concerned, such as large object creation.
Visual Studio Professional 2005 or 2008
.NET Compact Framework 3.5
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 37
For this demonstration, we will construct a smart device console application using Visual C#. Start
Visual Studio and select File New Project. A ‘New Project’ dialog will appear. Select a project type of Visual C# Smart Device. Click ‘Smart Device Project’ as the Template. Make sure the combo box has .NET Framework 3.5 selected. Type the name of the project. In this case, call it
HelloWorld. (See Figure 9.)
Figure 9. Visual Studio New Project dialog
Click the "OK" button. The next configuration screen allows you to select the type of project you are creating. Click "Windows CE" for the target platform, .NET Compact Framework version 3.5 and click the "Console Application" icon for the template. (See Figure 10.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 10. Visual Studio Add Smart Device dialog
SBC-R9 Manual 38
Once you have selected all of the configuration options, click the "OK" button. You will now see a console application template called HelloWorld in Visual Studio. (See Figure 11.)
Figure 11. Visual Studio Main Window
We can now add the references to the Talos Framework. Right click on the “References” and click the
"Add Reference…" selection. (See Figure 12.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 12. Adding References to Project
SBC-R9 Manual 39
An ‘Add Reference’ dialog will appear. Click on the ‘Browse’ tab then search for the installed library path “C:\Program Files\Sealevel Systems\R9 Development\Assemblies”. If you don’t see a list of the
R9 libraries as shown in Figure 12, then refer to the SBC-R9 QuickStart section for software installation details. While holding down the CTRL key, click on both "SLCorLib.dll" and "Talos.dll".
Click the “OK” button. (See Figure 13.)
Figure 13. Core library reference
Both DLLs should appear in your “References” list. (See Figure 14.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 14. Verification of added library references
SBC-R9 Manual 40
Now that the Talos Framework has been referenced, you have access to all the I/O points exposed on the
SBC-R9 device.
For this simple HelloWorld application, we will just echo the string “Hello World” in the console window.
This can be accomplished by adding the following code to the automatically created Program::Main() method. This code will echo “Hello World” and then pause for 5 seconds. static void Main( string [] args)
{
Console .WriteLine( "Hello World" );
System.Threading.
Thread .Sleep(5000);
}
From Visual Studio’s menu bar, select “Build Build HelloWorld”. After the build process has completed select from the same menu bar, “Build Deploy HelloWorld”. A “Deploy HelloWorld” dialog will appear for you to choose the appropriate target. Choose “Windows CE Device” then press the ‘Deploy’ button. (See
Figure 15.)
Figure 15. Choose Windows CE Device and Deploy
After the deployment phase, the “Hello World” message will appear on the Debug Serial console output (See
Using the Debug Port section).
Examples can be found from the installation directory under ‘..\R9 Development\Samples\C#’ and ‘..\R9
Development\Samples\VB.NET’.
41 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
This guide details the process of debugging an application developed for the SBC-R9 embedded IO system. The SBC-R9 development platform easily integrates into standard Microsoft development tools to make the debugging process extremely easy. The following sections detail the requirements to begin debugging an application on Microsoft Windows 7, Vista, or XP.
Microsoft Mobile Device Center using Vista or ActiveSync using XP
Microsoft Visual Studio Professional 2005 or 2008
USB Cable or Ethernet connection
Debugging your SBC-R9 applications is a simple process that requires a USB cable or Ethernet connection, Microsoft Device Synchronization software, and Visual Studio. Depending on your version of
Windows, you will need to follow a different process to install the device synchronization software as outlined in the SBC-R9 Quick Start section.
Once the SBC-R9 has been successfully attached to your PC, it is easy to begin debugging an application on the SBC-R9. This section will demonstrate how to attach the Microsoft Visual Studio debugger to the
SBC-R9, show the use of breakpoints in the debugger, and show how to access useful information while debugging an application.
We will be using the GPIO example application found in the "samples" directory of the Talos Framework installation. The same methods will apply to any application you wish to debug on the SBC-R9.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 42
Once your solution is opened, it is necessary to specify the device target that you would like to use in conjunction with the debugger. The default option is an emulator. Click "Windows CE Device" from the target device drop down. Then click the "Connect to Device" button. (See Figure 16.)
Figure 16. Device Target Selection
If you would like to use the faster Ethernet connection for debugging instead of the USB connection,
refer to Appendix C – Application Debugging over Ethernet.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 43
Now select the “Connect to Device” icon to initiate synchronization between Visual Studio and the SBC-
R9 device. (See Figure 17.)
Figure 17. Connect to Device icon
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 44
You should now see a connection dialog appear. (See Figure 18.)
Figure 18. Connection Status Dialog
Setting breakpoints allows you to stop execution of your application at any point and examine the state of the application. A breakpoint may be set by selecting a line and pressing the "F9" hotkey. (See Figure
19.)
Figure 19. Breakpoint selection
To begin debugging the application, click the "Start Debugging" button. (See Figure 20.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 20. Run Debugger icon
SBC-R9 Manual 45
Although you previously set up the target device, upon starting the first debug session, you will be prompted to select the device to deploy the application to. Select the "Windows CE Device" as was done earlier when selecting the target. (See Figure 21.)
Figure 21. Target Deployment dialog
Once the application is deployed to the SBC-R9, it will begin execution. As soon as the first breakpoint is reached, execution will cease and you will gain full control over the running application. You may use the debugging options to continue execution, execute a single line, or execute multiple lines. You may view the status of each variable by either hovering over it with the cursor or by examining the windows at the bottom of Visual Studio just as you would with a desktop application. (See Figure 22.)
Figure 22. Examining program variables
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 46
When program execution is halted due to a break point condition being met, the debugger will display the state of all local variables. In addition to those variables, class specific variables can be grouped together as a view to aid in debugging your application. This is accomplished by right clicking on a variable and selecting "Add Watch". Each addition appends a tab to the “Watch n” window where n is incremented for each variable added. (See Figure 23.) Each watch window provides a convenient tree type structure for viewing hierarchical class variables.
Figure 23. Watch view
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 47
After your application is built using Visual Studio, either a debug or release executable, it may be desirable to copy it onto the SDCARD or NAND Flash. This would provide a means to store and execute your application without the need for connectivity to a host computer. The first step is transferring your application to a suitable directory on the SDCARD or on-board NAND Flash. To accomplish this you will need to establish connectivity via Mobile Device Center or ActiveSync as outlined in the SBC-R9 Quick Start section above.
Figure 24. Application Placement
The Relio R9 Runtime image comes pre-loaded with a utility program called “SpringBoard”. This utility provides a solution for automatically running your applications at startup. Rather than copying your application files to ‘/Windows/Startup/’ - which is in volatile memory - the executables should be copied to
‘/Storage Card/startup/’ or `/nandflash/startup/’. After Windows CE runs, SpringBoard automatically starts applications located in the NAND Flash followed by applications in the Storage Card.
SpringBoard also provides a way to specify program arguments by supplying an XML configuration file. You will need to create a simple XML file called “startup.xml”. This XML file should consist of an element list each with an application name and the desired arguments for that application. (See Figure 24.) This file must reside in the following location: ‘/storage card/startup/startup.xml’ and/or
‘/nandflash/startup/startup.xml’.
If the startup.xml file is not found or is not desired, SpringBoard will still automatically run all the applications placed in the aforementioned directory structure, only no arguments will be included for those applications.
<?xml version="1.0" encoding="utf-8" ?>
-
<programs>
<program name="sample1.exe" arguments="/i 1019 /w JSmith" />
<program name="sample2.exe" arguments="-e 2000" />
<program name="sample3.exe" arguments="/help" />
</programs>
Figure 25. startup.xml
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 48
Upon power up, the SBC-R9 follows a specific boot sequence. The initial sequence is “firstboot”. The firstboot process initializes the low level hardware and is responsible for loading the next sequence called
“eboot”. Eboot provides a configuration menu for setting connection types and start up memory locations.
Connection types include Ethernet and USB. Memory locations include SDCARD and NAND Flash. Ultimately, eboot attempts to load and execute the OS runtime image based on those configuration settings.
The SBC-R9 development board checks the root directory of the bottom SDCARD for a valid Eboot boot loader (boot.bin). The file must be named boot.bin and the SDCARD must be formatted as FAT 12/16/32. If no boot image is found, the device will next check the raw data in the NAND Flash.
Only the bottom SDCARD slot (Slot A) or NAND Flash can be used for booting to an OS runtime image.
The SBC-R9 ships with an SDCARD loaded with the OS files listed below:
Boot.bin
Eboot.bin
NK.bin
In the event that Sealevel produces updated OS file versions or a backup is desired, the OS files will need to be copied to the root directory of an SDCARD or programmed to the NAND Flash. There are a variety of ways to copy files to the SDCARD; please see the section labeled “Upgrading the OS runtime image on
SDCARD” below for more detail. Please see the section labeled “Upgrading the OS runtime image on NAND
Flash” for further detail into that process. The NAND Flash cannot be programmed until any existing OS runtime image has been removed and the SDCARD is removed or the OS image on it is removed.
This procedure requires an available RS-232 COM port or USB to RS-232 serial port adapter attached to a host PC, an SBC-R9 Serial Debug cable (Item# CA429), and any terminal client application such as PuTTY
(See Appendix A). For this procedure, we will demonstrate the use of PuTTY.
Connect the 4-pin keyed female end of the SBC-R9 RS-232 cable into the SBC-R9 connector J6. Connect the
DB9 end of the SBC-R9 RS-232 cable into an available serial port on the host PC.
49 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Run PuTTY and select “Serial” from the Category section of the dialog. Identify the proper COM port number and always assign the speed (baud) equal to 115200. Set Data bits to 8, Stop bits to 1, Parity to None, and
Flow control to None. (See Figure 26.)
Figure 26. PuTTY Serial configuration
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 50
Select “Session” from the Category section of the dialog. A saved session of this configuration can be performed to avoid reconfiguration in the future. Next select Serial for the connection type. Type a name for this session under “Saved Sessions”, then press the “Save” button. (See Figure 27.)
Figure 27. PuTTY Session configuration
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 51
Press “Open” to start a new terminal session. A blank terminal window will appear. Debug messages may not appear until power is applied to the SBC-R9 board. Press the reset button on the SBC-R9 to display the
Ethernet boot loader configuration screen. (See Figure 28.) When the unit boots, the following menu on the debug port terminal will appear (no user input is required for booting):
“Press [ENTER] to download now or [SPACE] to cancel.
Initiating image download in 2 seconds"
Once the prompt period expires, the OS runtime will be loaded from SDCARD or NAND Flash (depending on boot sequence and boot files available) into RAM and executed. At this point, the OS is running and all console output is redirected to the debug serial port. (See Figure 28.)
Figure 28. Application Debug Text Output
Eboot configuration settings can be modified by hitting the “space” key during the 2 second boot prompt period. When modifying the configuration, a menu such as the one below is displayed. (See
Figure 29.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 29. Eboot configuration output
SBC-R9 Manual 52
Modifying any of these settings may render your SBC-R9 unbootable.
When upgrading an existing OS runtime stored in the NAND Flash, it is necessary to first erase the NAND
Flash of a pre-programmed unit. This is accomplished through the “Image flash menu” (‘n’ key) in Eboot.
The flash menu has an option to “Erase all sectors” of the NAND Flash (‘1’ key). (See Figure 30.)
Figure 30. Eboot Image Flash Menu
The “Erase all sectors” option in Eboot will erase the entire NAND Flash, so be sure to back up any data you wish to save before attempting to erase the device.
53 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Factory OS runtime images are stored in the “Boot Files” directory of the R9 Development installation (see
Quick start guide). There a few ways to upgrade the OS runtime image (*.bin) located on your bootable
SDCARD:
a memory card reader (preferred method)
USB connection with Windows Mobile Device Center or ActiveSync
FTP connection.
When inserting the SDCARD into your memory card reader, you may be prompted with an “AutoPlay” option. Choose “Open folder to view files”. If the “AutoPlay” feature has been disabled, navigate to the memory card reader manually. (See Figure 31).
Figure 31. AutoPlay screen
The OS runtime image consists of three binary (.bin) files as demonstrated below. (See Figure 32).
Figure 32. SDCARD File Contents
To save the existing OS runtime image, backup the files previously stored on the SDCARD.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 54
Copy the new OS runtime image to the SDCARD. A popup will appear asking you to override your current files. Select the "Copy and Replace" option to over-write the existing OS runtime image. The new
OS runtime image will be loaded the next time the device is booted with the SDCARD. (See Figure 33.)
Figure 33. Copy and Replace
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 55
Another way to upgrade the OS runtime image is to connect via Windows Mobile Device Center or Active
Sync; for instructions on installing Windows Mobile Device Center or ActiveSync refer to the ‘SBC-R9
Quick Start’ section above.
Using the device file explorer, navigate to the “Storage Card” folder to view the SDCARD contents. (See
Figures 34/35.)
Figure 34. WindowsCE Device Explore
Figure 35. Storage Card contents
To save the existing OS runtime image, backup the SDCARD contents.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 56
Copy the new OS runtime image to the SDCARD. A popup will appear asking you to over-write your current files. (See Figure 36.)
Figure 36. Copy and Replace
Select the "Copy and Replace" option to over-write the existing OS runtime image. Reboot the SBC-R9 once the file has been copied. The new OS runtime image will be loaded on bootup.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 57
Use an FTP program to connect to the SBC-R9 and upload the new OS runtime image to the SDCARD.
FileZilla (See Appendix A), an open-source FTP client, is used in the example below. By default, FTP is open to anonymous access with no password needed. (See Figure 37.)
Figure 37. Connect to device through FTP
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 58
Select the "Storage Card" folder for the remote site. (See Figure 38.)
Figure 38. Select Storage Card
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 59
Navigate to the “Boot Files” directory of the R9 Development installation. Select the OS Runtime files to copy (*.bin). Right-click and select “Upload” to begin the file transfer. (See Figure 39.)
Figure 39. Upload the file
You may be asked how to proceed when replacing existing files. Select the “Overwrite” radio button and click “OK”. (See Figure 40.)
Figure 40. Over-write files
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 60
Once the files have been uploaded, (See Figure 41.) reboot the device. The new OS runtime image will be loaded on bootup.
Figure 41. Uploading boot files
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 61
Factory OS runtime images are stored in the “Boot Files” directory of the R9 Development installation (see
Quick start guide). The OS runtime image present in the NAND Flash is programmed through the USB device port connection. Prior to programming an OS runtime, the existing image must be erased. The procedure to erase the NAND Flash is documented in the Debug Port section.
Once the NAND Flash has been erased, use a standard USB device cable and connect the Type B connector to the SBC-R9. Connect Type A connector into the host PC. (See Figure 42.)
Figure 42. TR134 power supply and Type B USB connector
In Microsoft Windows 7, the device is recognized as a GPS camera and will typically enumerate as a COM port. Check the device manager to determine the COM# associated with the device. If prompted with the
New Hardware wizard or the device is not recognized, then install the driver using the following steps (XP menus shown, but Vista is similar). In the Found New Hardware Wizard, specify "Install from a list or specific location" and click Next. (See Figure 43.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 43. Found New Hardware Wizard
SBC-R9 Manual 62
Select "Search for the best driver in these locations" and check "Include this location in the search". Use the
Browse button to browse to the “Utilities\SAM-BA\XP driver” directory of the R9 Development installation and click “Next”.
The driver should be installed, and will come in as "AT91 USB to Serial Converter." Click Finish to complete.
(See Figure 44.)
Figure 44. Driver Installed
Determine COM port assignment using Device Manager > Ports. The USB function port should be listed.
For Windows 7, it may be listed as a GPS camera, otherwise it should be “AT91 USB to Serial Converter.”
Take note of the COM port assignment, to modify the programming batch file used to program the new OS
Runtime image. (See Figure 45.)
©Sealevel Systems, Inc.
SL9210 01/2012
Figure 45. AT91 COM Port
SBC-R9 Manual 63
Sample scripts have been provided in the R9 Development installation to automate the process of writing a complete OS runtime to the device. The script is configured to target a device attached to COM49 by default. This can be modified simply by editing the comport variable in the “NAND Program.bat” batch file.
Once the batch file has been updated to reflect your system configuration, simply double-click the batch file to begin the programming process. The process will take a few minutes. (See Figure 46).
Figure 46. Programming NAND (COM17)
Once programming has completed, cycle device power and the OS runtime should boot. (See Figure 47.)
Figure 47. Programming complete
As previously mentioned the process of programming the NAND Flash first erases all content from the NAND Flash. This includes the unique MAC address assigned to your device at the factory. The
“finalize.exe” tool is provided in the “Boot Files” directory of the R9 Development installation.
Finalize is a command line utility that accepts a MAC address in dashed notation (00-0A-0B-16-12-
34). The application should be executed on the device after reprogramming the NAND Flash to reassign the MAC address. Once the application has been executed, the setting is applied upon device restart and persists.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 64
The Windows CE that runs on the SBC-R9 is initially configured obtain its IP address via DHCP. Settings may be required for DNS or WINS server IP addresses or if you want to set up a static IP address. We have included an application in the OS that enables device configuration through a simple XML file format. The configuration is stored in a file that is kept up-to-date on the NAND Flash of the device. Likewise, edits to this file can be read as requests to modify the device’s configuration. The configuration file can be accessed through ActiveSync using the USB device port connection or through an FTP client if you already know the IP address of the device. This section defines the XML configuration structure and corresponding values applicable for each element of the structure. Throughout this section the following definitions apply:
Term Definition Example
[int] A number 123
[String]
[Multi-line String]
[Version]
[Boolean]
[MACAddress]
[IPAddress]
Series of printable characters This is a test string!234567609 strings separated by \r\n A\r\nNew\r\nMulti-liner
A version number
A binary state
A hardware identifier
An IPv4 network address
1.2.3.4
True / False
00-0A-0B-16-11-1A
192.168.0.100
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 65
The act of writing a new configuration file to the device will trigger a scan of that file (approximately every 10 seconds). If the file is invalid, it will be replaced with the current configuration. If a single element is invalid, that element and corresponding elements will be replaced with default values.
To apply a new configuration, use the <Action> element with a value of "apply" as documented below.
Sample configuration.xml read from device.
The configuration element is the root XML element. This element must be present or the configuration file will not be considered valid. Invalid configurations will be replaced with a default configuration.
The system element contains all of the system information elements. This element must be a child of the Configuration element. This element must be present or the configuration file will not be considered valid.
The OS element contains a string representation of the Operating System name. This element must be a child of the System element. In the case of R9 products, this will be equivalent to "WinCE".
The version element contains a dot-notation version string. This element must be a child of the
System element. This version is associated with the Operating System element.
This element contains a string representation of the specific OS Runtime Image. This element must be a child of the System element.
This element contains a dot-notation version string. This element must be a child of the System element. This version is associated with the OS Runtime Image.
SBC-R9 Manual 66 ©Sealevel Systems, Inc.
SL9210 01/2012
This element contains a Processor Identification string. This element must be a child of the System element.
This element may contain the device name string. This element must be a child of the System element. This identifier is used as the WinCE host name.
This element may contain the device description string. This element must be a child of the System element. This element can be used to further identify a device.
This element may contain a string that can be used to identify a person or department responsible for maintaining a device. This element must be a child of the System element.
This element may contain a string that can be used to identify the Company to which the device
Owner is associated. This element must be a child of the System element.
This element may contain a multi-line string (\r\n separated) to identify the location of the device
Owner. This element must be a child of the System element.
This element may contain a string representation of a telephone contact number for the device
Owner. This element must be a child of the System element.
This element may contain a string representation of a telephone extension for the device Owner.
This element must be a child of the System element.
The Ethernet element contains a list of Ethernet interfaces available to the device. This element must be a child of the Configuration element.
The interface element is a container for the interface settings that are specific to the interface identifiable as "name". This element must be a child of the Ethernet element. The name attribute is readonly and is used to uniquely distinguish Interface settings for the case where there are multiple Ethernet interfaces available.
This element contains a Boolean value indicating whether DHCP Address resolution is enabled or disabled. This element must be a child of the Ethernet element. Valid values are True or False.
This element contains a dash delimited string containing the unique MAC address of this interface.
This element must be a child of the Ethernet element. The first 3 octets identify the device as a
Sealevel product (00-0A-0B). The fourth octet can be used to determine the product family (16).
And the last two octets will be unique for each device (11-1A).
This element may contain the current DHCP acquired IP Address or the current static IP address depending on the state of the DHCP element. This element must be a child of the Ethernet element.
Assigning a value to this element when DHCP is enabled has no effect.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 67
This element may contain the current DHCP acquired Subnet Mask or the current static Subnet Mask depending on the state of the DHCP element. This element must be a child of the Ethernet element.
Assigning a value to this element when DHCP is enabled has no effect.
This element may contain the current DHCP acquired Gateway address or the current static Gateway address depending on the state of the DHCP element. This element must be a child of the Ethernet element. Assigning a value to this element when DHCP is enabled has no effect.
The Wifi element is a container for wireless bridge settings if such a bridge is present. This element must be a child of the Ethernet element. The "enabled" attribute will reflect whether the Interface is able to communicate with an approved wireless bridging module.
This element contains the SSID string to be used when forming the wireless connection. This element must be a child of the Wifi element.
This element contains the overall Wireless configuration mode. This element must be a child of the Wifi element.
This element contains the wireless channel offset to use in Adhoc mode. This element must be a child of the Wifi element.
This element contains the security method for use in establishing the wireless connection. This element must be a child of the Wifi element.
This key is used to set the wireless connection passphrase or value. This element must be a child of the Wifi element. Depending on the wireless configuration, the "encoding" attribute will need to be set accordingly. For security purposes this value cannot be read once it has been set.
The Sealevel element contains a list of Sealevel internal configuration parameters used for Sealevel supplied software plug-ins. This element must be a child of the Configuration element. The plug-in application should contain documentation for the configuration parameters used by that plug-in.
The User element can be used to contain a list of user configurable parameters for use in custom software. This element must be a child of the Configuration element. Any elements stored under this element will be automatically persisted to the registry key HKLM/Software/User. They can be accessed through that key at any time by custom software.
This element may be used to trigger predetermined device behavior. This element must be a child of the Configuration element. For example, setting a value of "apply" to this element will result in the specified configuration being applied to the hardware and trigger a device restart so the settings will take effect.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 68
Specifications
Length
7.3”
Width
4.9”
Height
0.75”
For CAD drawing with dimensions, see Appendix D – CAD Drawing.
Supply Line 7 – 30VDC Input
Rating 10 W Max (2.5W Nominal)
Connector:
Manufacturer:
Part Number:
Description:
Mates with:
P3
Molex
09-65-2028
Locking Header, 2 pos, vertical, 3.96mm pitch
Molex 09-50-1021
Specification Operating
Temperature Range -40º to 85º C
Humidity Range
Storage
-60º to 150º C
10 to 90% R.H. Non-Condensing 10 to 90% R.H. Non-Condensing
All Sealevel Systems printed circuit boards are built to UL 94V0 rating and are 100% electrically tested.
These printed circuit boards are solder mask over bare copper or solder mask over tin nickel.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 69
Appendix A – Resources
Professional Microsoft Windows Embedded CE 6.0, Wrox, Phung.
Programming Windows Embedded CE 6.0 Developer Reference, Microsoft Press, Boling. http://msdn.microsoft.com/en-us/library/cc526055.aspx
Atmel SAM-BA In-System Programmer (ISP) http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883
FileZilla Open-Source FTP Client http://www.filezilla-project.org
Microsoft Windows Embedded Home Page www.microsoft.com/windows/embedded/default.mspx
What’s New in Windows Embedded CE 6.0 R2 http://msdn.microsoft.com/en-us/embedded/bb894656.aspx
Microsoft Windows Embedded CE Operating System Components http://www.microsoft.com/windowsembedded/en-us/products/windowsce/component-library.mspx#type
Microsoft Windows Embedded CE 6.0 Evaluation Edition http://www.microsoft.com/downloads/details.aspx?familyid=7E286847-6E06-4A0C-8CAC-
CA7D4C09CB56&displaylang=en
Microsoft Windows CE 6.0 Bare Essentials Video http://www.microsoft.com/video/en/us/details/ffe10273-38ec-4e4f-8ed8a06174e2c5df?vp_evt=eref&vp_video=Windows+CE+6.0+Bare+Essentials
Microsoft Windows Embedded CE 6.0 Online Documentation http://msdn.microsoft.com/en-us/library/aa924073.aspx
Microsoft Windows CE 6.0 Documentation Search Tool http://search.live.com/macros/windows_embedded/ce6/?FORM=OIJG
Microsoft ActiveSync Download http://www.microsoft.com/windowsmobile/en-us/help/synchronize/ActiveSync-download.mspx
Microsoft Mobile Device Center 6.1 http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
Microsoft .NET Compact Framework http://msdn.microsoft.com/en-us/netframework/aa497273.aspx
PuTTy Telnet/SSH Client Application http://en.wikipedia.org/wiki/PuTTY
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 70
Appendix B – SBC-R9 Connector Reference
The following table details the connectors, jumpers, and test points located on the SBC-R9. The connectors, jumpers, and test points are labeled by reference designator on the board silkscreen.
Reference
Designator
Signal Description
P1
P2
P3
P4
P5
P6
P7
J3
J5
J6
J7
J8
J10
J11
J13
J14
J15
Jumpers
J1
J2
J4
J16
Test Points
TP1
TP2
TP3
TP4
(8) 12-bit analog inputs
LCD, Backlight, and touchscreen controller
7-30VDC input power
(4) RS-232, RS-422, RS-485 serial ports
(8) Optically isolated inputs (5-24V)
(8) Open-collector digital outputs
(2) 32-bit Quadrature counters
CAN 2.0b Bus interface
RS-485 expansion port (RJ45 connector)
RS-232 serial debug port
USB 2.0 host port A (Type A)
USB 2.0 host port B (Type A)
RS-485 expansion port (Molex connector)
SD/MMC expansion card slot B
USB 2.0 device port (Type B)
10/100 BaseT Ethernet interface
SD/MMC expansion card slot A
Jumper - NAND Flash write protect
Jumper - NAND Flash enable (Installed by default)
Jumper - CAN Bus Termination (Installed by default)
Jumper - Enable Push-button Reset (Installed by default)
Test Point - Analog ground
Test Point - Received analog input
Test Point – Ground
Test Point – Ground
71 ©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual
Appendix C – Application Debugging over
Ethernet
Applications can be debugged over an Ethernet connection in place of USB by configuring Visual Studio to directly connect to your device. For this method to work properly, the Ethernet connection to the device must be properly configured to allow normal TCP/IP communications and you must know the IP address of the device you wish to execute the application on. For further information about configuring the Ethernet of the device see the Network Configuration section.
To configure Visual Studio to use your device for debugging over Ethernet, click the “Device Options” button on the Device toolbar. See below.
On the “Device Options” dialog, select the “Windows CE” platform and click the “Properties…” button. See below.
On the “Windows CE Device” properties dialog click the “Configure…” button. See below.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 72
Now click the “Use specific IP address” radio button and type the IP address of the device in the text box.
See below.
Click the “OK” button on all of the dialog windows and you should now be able to connect to the device through Ethernet for debugging. The application debugging guide can be continued as normal.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 73
Appendix D – CAD Drawing
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 74
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 75
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 76
Appendix E – How to Get Assistance
When calling for technical assistance, please have the device installed and ready to run diagnostics. If possible, have your user manual and current settings ready.
The Sealevel website is an excellent resource located at www.sealevel.com. The most current software updates and user manuals are available via our homepage by clicking on the 'Drivers' or 'Manuals' links located under ‘Technical Support.’ Manuals and software can also be downloaded from the product page for your device.
The FAQ section of our website answers many common questions. Refer to this helpful resource by visiting www.sealevel.com/faq.asp.
Monday – Friday
8:00 am to 5:00 pm EST
Phone: +1 (864) 843-4343
Email: [email protected]
RETURN AUTHORIZATION MUST BE OBTAINED FROM SEALEVEL SYSTEMS BEFORE RETURNED
MERCHANDISE WILL BE ACCEPTED. AUTHORIZATION CAN BE OBTAINED BY CALLING SEALEVEL
SYSTEMS AND REQUESTING A RETURN MERCHANDISE AUTHORIZATION (RMA) NUMBER.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 77
Warranty
Sealevel's commitment to providing the best I/O solutions is reflected in the Lifetime Warranty that is standard on all Sealevel manufactured I/O products. Relio™ industrial computers are warranted for a period of two years and the Relio™/SeaPAC™/SBC R9 family is warranted for a five year period from date of purchase. We are able to offer this warranty due to our control of manufacturing quality and the historically high reliability of our products in the field. Sealevel products are designed and manufactured at its Liberty,
South Carolina facility, allowing direct control over product development, production, burn-in and testing.
Sealevel achieved ISO-9001:2000 certification in 2002.
Sealevel Systems, Inc. (hereafter "Sealevel") warrants that the Product shall conform to and perform in accordance with published technical specifications and shall be free of defects in materials and workmanship for the warranty period. In the event of failure, Sealevel will repair or replace the product at
Sealevel's sole discretion. Failures resulting from misapplication or misuse of the Product, failure to adhere to any specifications or instructions, or failure resulting from neglect, abuse, accidents, or acts of nature are not covered under this warranty.
Warranty service may be obtained by delivering the Product to Sealevel and providing proof of purchase.
Customer agrees to insure the Product or assume the risk of loss or damage in transit, to prepay shipping charges to Sealevel, and to use the original shipping container or equivalent. Warranty is valid only for original purchaser and is not transferable.
This warranty applies to Sealevel manufactured Product. Product purchased through Sealevel but manufactured by a third party will retain the original manufacturer's warranty.
Products returned due to damage or misuse and Products retested with no problem found are subject to repair/retest charges. A purchase order or credit card number and authorization must be provided in order to obtain an RMA (Return Merchandise Authorization) number prior to returning Product.
If you need to return a product for warranty or non-warranty repair, you must first obtain an RMA number.
Please contact Sealevel Systems, Inc. Technical Support for assistance:
Available
Phone
Monday – Friday, 8:00AM to 5:00PM EST
864-843-4343 [email protected]
Sealevel Systems, Incorporated acknowledges that all trademarks referenced in this manual are the service mark, trademark, or registered trademark of the respective company.
©Sealevel Systems, Inc.
SL9210 01/2012
SBC-R9 Manual 78
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 5 Safety Instructions
- 5 ESD Warnings
- 5 Electrostatic Discharges (ESD)
- 5 Grounding Methods
- 6 Introduction
- 6 Features
- 7 Before You Get Started
- 7 What’s Included
- 7 Advisory Conventions
- 8 QuickStart Kit
- 9 Optional Items
- 9 Cables
- 10 Power Supply
- 11 Product Overview
- 11 Specifications
- 11 Processor
- 11 Memory
- 11 LCD Controller
- 11 Touchscreen Controller
- 11 Bus Interfaces
- 11 Industrial I/O
- 11 Indicators
- 12 Block Diagram
- 13 Technical Description
- 13 Memory
- 13 Ethernet
- 15 LCD and Touchscreen Controllers
- 17 Serial Debugging
- 18 Serial Communications
- 20 CA273 Accessory Cable
- 21 CAN Bus
- 22 Optically Isolated Inputs
- 24 Open Collector Outputs
- 26 Analog Inputs
- 27 Quadrature Counters
- 27 Quadrature Counter
- 28 SD/MMC Cards
- 29 RS-485 Expansion
- 30 Power
- 31 LED Indicators
- 32 Software
- 32 SBC-R9 Quick Start
- 34 Windows Device Center
- 35 Windows ActiveSync for XP
- 36 Connection Complete
- 37 Application Development
- 42 Application Debugging
- 42 Introduction
- 42 Requirements
- 42 Debugging an Application
- 43 Attach the Debugger
- 45 Breakpoints
- 47 Watching Variables
- 48 Target Deployment and Execution
- 49 SDCARD Boot Sequence
- 49 OS File Restoration
- 49 Using the Debug Port
- 54 Upgrading the OS Runtime Image on SDCARD
- 54 Memory Card Reader
- 56 USB Connection: Using Windows Mobile Device Center or ActiveSync
- 58 FTP Connection
- 62 Upgrading the OS Runtime Image on NAND Flash
- 65 Network Configuration
-
66
-Structure -
66
-Structure -
67
- Structure -
68
- Structure -
68
- Structure -
68
- Writeonly [string] - 69 Specifications
- 69 Dimensions
- 69 Power