arm
所属分类：Linux/Unix编程
开发工具：C/C++
文件大小：18511KB
下载次数：1088
上传日期：2008-03-31 09:49:02
上 传 者：
lisuweizhai
说明： 嵌入式系统设计与实例开发实验教材二源码
多线程应用程序设计
串行端口程序设计
AD接口实验
CAN总线通信实验
GPS通信实验
Linux内核移植与编译实验
IC卡读写实验
SD驱动使用实验
GPRS通信实验
音频驱动及应用实验
嵌入式Web服务器实验
IDE—CF卡模块读写实验
PS2键盘鼠标驱动实验
(Examples of embedded systems design and development of experimental teaching materials Second source multi-threaded application design program design AD serial port CAN bus communication interface experiment experiment experiment GPS communications Linux kernel compiled Experimental Transplantation and Experimental IC card reader SD driver to use experimental GPRS communication experiment audio driver and application experiments embedded Web server experiment IDE-CF card module to read and write experimental PS2 keyboard and mouse-driven experiment)
文件列表:
嵌入式系统设计与实例开发实验教材二源码 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\Rules.mak (145, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.2多线程应用程序设计 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.2多线程应用程序设计\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.2多线程应用程序设计\pthread.c (3283, 2006-01-20)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.2多线程应用程序设计\Rules.mak (145, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.3串行端口程序设计 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.3串行端口程序设计\.n_tty.o.flags (396, 2005-09-05)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.3串行端口程序设计\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.3串行端口程序设计\term.c (2835, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.3串行端口程序设计\tty.c (719, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验\main.c (1442, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验\s3c2410-adc.c (3952, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验\s3c2410-adc.h (228, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.4AD接口实验\s3c2410.h_chip.H (1919, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.5DA接口实验 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.5DA接口实验\.s3c2410-exio.o.flags (426, 2005-09-05)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.5DA接口实验\da_main.c (1786, 2005-07-26)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.5DA接口实验\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.5DA接口实验\s3c44b0-spi.h (218, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.6CAN总线通信实验 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.6CAN总线通信实验\.s3c2410-can-mcp2510.o.flags (447, 2005-09-05)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.6CAN总线通信实验\main.c (2303, 2005-03-18)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.6CAN总线通信实验\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.6CAN总线通信实验\up-can.h (1212, 2005-03-18)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.7 GPS通信实验 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.7 GPS通信实验\gps.c (3628, 2005-08-19)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.7 GPS通信实验\gps.h (501, 2005-08-19)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.7 GPS通信实验\main.c (3536, 2005-08-19)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.7 GPS通信实验\Makefile (293, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验 (0, 2006-03-02)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\.s3c2410-gprs.o.flags (426, 2005-09-05)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\gprs.c (1513, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\gprs.h (324, 2005-05-16)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\keyshell.c (1777, 2005-09-03)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\main.c (2543, 2005-08-31)
嵌入式系统设计与实例开发实验教材二源码\源代码\2.8GPRS通信实验\Makefile (393, 2005-08-19)
... ...
$Id: README.icn,v 1.1.4.1 2001/11/20 14:19:33 kai Exp $
You can get the ICN-ISDN-card from:
Thinking Objects Software GmbH
Versbacher Rthe 159
97078 Würzburg
Tel: +49 931 2877950
Fax: +49 931 2877951
email info@think.de
WWW http:/www.think.de
The card communicates with the PC by two interfaces:
1. A range of 4 successive port-addresses, whose base address can be
configured with the switches.
2. A memory window with 16KB-256KB size, which can be setup in 16k steps
over the whole range of 16MB. Isdn4linux only uses a 16k window.
The base address of the window can be configured when loading
the lowlevel-module (see README). If using more than one card,
all cards are mapped to the same window and activated as needed.
Setting up the IO-address dipswitches for the ICN-ISDN-card:
Two types of cards exist, one with dip-switches and one with
hook-switches.
1. Setting for the card with hook-switches:
(0 = switch closed, 1 = switch open)
S3 S2 S1 Base-address
0 0 0 0x300
0 0 1 0x310
0 1 0 0x320 (Default for isdn4linux)
0 1 1 0x330
1 0 0 0x340
1 0 1 0x350
1 1 0 0x360
1 1 1 NOT ALLOWED!
2. Setting for the card with dip-switches:
(0 = switch closed, 1 = switch open)
S1 S2 S3 S4 Base-Address
0 0 0 0 0x300
0 0 0 1 0x310
0 0 1 0 0x320 (Default for isdn4linux)
0 0 1 1 0x330
0 1 0 0 0x340
0 1 0 1 0x350
0 1 1 0 0x360
0 1 1 1 NOT ALLOWED!
1 0 0 0 0x308
1 0 0 1 0x318
1 0 1 0 0x328
1 0 1 1 0x338
1 1 0 0 0x348
1 1 0 1 0x358
1 1 1 0 0x368
1 1 1 1 NOT ALLOWED!
The ICN driver may be built into the kernel or as a module. Initialization
depends on how the driver is built:
Driver built into the kernel:
The ICN driver can be configured using the commandline-feature while
loading the kernel with LILO or LOADLIN. It accepts the following syntax:
icn=p,m[,idstring1[,idstring2]]
where
p = portbase (default: 0x320)
m = shared memory (default: 0xd0000)
When using the ICN double card (4B), you MUST define TWO idstrings.
idstring must start with a character! There is no way for the driver
to distinguish between a 2B and 4B type card. Therefore, by supplying
TWO idstrings, you tell the driver that you have a 4B installed.
If you like to use more than one card, you can use the program
"icnctrl" from the utility-package to configure additional cards.
You need to configure shared memory only once, since the icn-driver
maps all cards into the same address-space.
Using the "icnctrl"-utility, portbase and shared memory can also be
changed during runtime.
The D-channel protocol is configured by loading different firmware
into the card's memory using the "icnctrl"-utility.
Driver built as module:
The module icn.o can be configured during "insmod'ing" it by
appending its parameters to the insmod-commandline. The following
syntax is accepted:
portbase=p membase=m icn_id=idstring [icn_id2=idstring2]
where p, m, idstring1 and idstring2 have the same meanings as the
parameters described for the kernel-version above.
When using the ICN double card (4B), you MUST define TWO idstrings.
idstring must start with a character! There is no way for the driver
to distinguish between a 2B and 4B type card. Therefore, by supplying
TWO idstrings, you tell the driver that you have a 4B installed.
Using the "icnctrl"-utility, the same features apply to the modularized
version like to the kernel-builtin one.
The D-channel protocol is configured by loading different firmware
into the card's memory using the "icnctrl"-utility.
Loading the firmware into the card:
The firmware is supplied together with the isdn4k-utils package. It
can be found in the subdirectory icnctrl/firmware/
There are 3 files:
loadpg.bin - Image of the bootstrap loader.
pc_1t_ca.bin - Image of firmware for german 1TR6 protocol.
pc_eu_ca.bin - Image if firmware for EDSS1 (Euro-ISDN) protocol.
Assuming you have installed the utility-package correctly, the firmware
will be downloaded into the 2B-card using the following command:
icnctrl -d Idstring load /etc/isdn/loadpg.bin /etc/isdn/pc_XX_ca.bin
where XX is either "1t" or "eu", depending on the D-Channel protocol
used on your S0-bus and Idstring is the Name of the card, given during
insmod-time or (for kernel-builtin driver) on the kernel commandline.
To load a 4B-card, the same command is used, except a second firmware
file is appended to the commandline of icnctrl.
-> After downloading firmware, the two LEDs at the back cover of the card
(ICN-4B: 4 LEDs) must be blinking intermittently now. If a connection
is up, the corresponding led is lit continuously.
For further documentation (adding more ICN-cards), refer to the manpage
icnctrl.8 which is included in the isdn4k-utils package.
近期下载者：
相关文件：
收藏者：