English dropdown-ico

Sonic Alert 2.8 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Sonic Alert 2.8, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Sonic Alert 2.8 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Sonic Alert 2.8. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Sonic Alert 2.8 should contain:
- informations concerning technical data of Sonic Alert 2.8
- name of the manufacturer and a year of construction of the Sonic Alert 2.8 item
- rules of operation, control and maintenance of the Sonic Alert 2.8 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Sonic Alert 2.8 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Sonic Alert 2.8, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Sonic Alert service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Sonic Alert 2.8.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Sonic Alert 2.8 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    1 User’s Manual fo r the Bounda ry Devices Neon R  b oa rd Decemb er 28, 2005 Decem b er 28, 2005 Revision 2.8[...]

  • Page 2

    2 1 Revision History Date Revision Description 2005-03-20 1.0 First draft 2005-04-03 1.3 Added minidebug instructions 2005-06-11 2.0 Added displa y config, net w orking notes 2005-06-27 2.1 Added connector pin-outs (Figure 2) 2005-07-23 2.2 Up dated U-Bo ot v ersion 2005-08-09 2.3 Added notes on mac address command 2005-09-15 2.4 Bump ed BSP revis[...]

  • Page 3

    CONTENTS 3 Con ten ts 1 Revision History 2 2 In tended Audience 5 3 Ov erview of features 5 4 Hardw are feature 5 4 . 1 L a y o u t ................ ............... 5 4 . 2 M o u n t i n g ............................. 6 4.3 Connector reference . . . . . . . . . . . . . . . . . . . . . . . 6 4.4 Electrical c haracteristics . . . . . . . . . . . . .[...]

  • Page 4

    CONTENTS 4 6.2.3 Con trol Keys . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.4 Blast proto col . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.5 Quic k-start download and burn . . . . . . . . . . . . . 30 6.3 T eraT erm blast extensions . . . . . . . . . . . . . . . . . . . . 32 6.4 Using U-Bo ot Netw orking . . . . . . . . . . . . . . [...]

  • Page 5

    5 2 In tended Audience This do cumen t aims to pro vide the information needed to in tegrate the Neon R  b oard in to y our application. As such, it addresses b oth hardw are and soft w are in tegration. 3 Ov erview of features The follo wing are highligh ts of the Neon R  b oard. • Av ailable with Windows Ce or Lin ux Operating Systems •[...]

  • Page 6

    4.2 Moun ting 6 Figure 1: Neon b oard 4.2 Moun ting The Neon R  b oard measures 2.75” b y 6.75”, slightly larger than the Hitac hi R  6.2” displa y , to allow for easy moun ting. There are four moun ting holes 1/4” from eac h edge in eac h of the four corners, and the holes are 1/8” in diameter. 4.3 Connector reference The follo win[...]

  • Page 7

    4.3 Connector reference 7 A A B B C C D D E E 4 4 3 3 2 2 1 1 J1 J12 J7 J14 J22 J16 J19 J4 J2 J23 J21 J1 J13 J18 J10 J9 J6 J8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 INTERNAL SPEAKER PLUS INTERNAL SPEAKER MINUS STERIO OUTPUT PIN1 GENERAL PURPOSE OUTPUT PIN2 GENERAL PURPOSE OUTPUT PIN3 GENERAL PURPOSE OUTPUT PIN4 POWER PIN 1 MICROPHONE MINUS INPUT PIN 2 MICRO[...]

  • Page 8

    4.4 Electrical c haracteristics 8 Description Man ufacturer P art USB Master F CI 87520-0010B USB Sla v e SINGA TRON KS-001-BNW I2C F CI 68897-001 Ethernet Halo HFJ11-2450E Stereo Audio Singatron 2SJ-43723N13 Bac kligh t in v erter Molex 53048-0210 MMC/SD A VX 14 5638 009 511 862 TFT Displa y T ouc h Screen Molex 52207-0590 Serial P ort F CI 68897-[...]

  • Page 9

    9 5 Soft w are features As pro vided b y Boundary Devices, the Neon R  b oard supp orts either Win- do ws CE 5 R  or Lin ux. T o simplify the installation of either, the Das U-Bo ot b o ot loader is in- stalled on our ev aluation b oards, and tw o MMC cards are shipped to allow the use of either op erating system. 5.1 Das U-Bo ot The Das U-Bo[...]

  • Page 10

    5.1 Das U-Bo ot 10 Base/diffutils Dev el/bin utils Dev el/gcc Dev el/mak e Dev el/patc h utils Utils/bzip2 W e b/wget The second requiremen t for building is the X-Scale cross-compiler itself. The GNUARM pro ject pro vides a w ealth of information needed to build a cross-compiler for ARM pro cessors. Thankfully , it also provides an installer . As[...]

  • Page 11

    5.1 Das U-Bo ot 11 y our application. In general, the file u-boot-1.1.2/include/configs/neon.h defines thes e c hoices. In particular, the distributed copy curren tly expects a Windows BMP file named bdlogo.bmp to b e presen t on the MMC card and writes it to the displa y , then loads an op erating system image from a file named nk.nb0 to RAM a[...]

  • Page 12

    5.1 Das U-Bo ot 12 5.1.5 U-Bo ot Memory lay out The follo wing diagram sho ws the general la y out of RAM within Das U-Boot . 0xA4000000 0xA3FF8000 32K segmen t used for page tables.        P age T ables 0xA3FF7FFF 0xA2000000 Un used RAM        Un used High 0xA1FFFFFF Extra space b et w een Das U-Bo ot and [...]

  • Page 13

    5.1 Das U-Bo ot 13 5.1.6 U-Bo ot Init Script The Das U-Bo ot bo ot loader comes with scripting facilities in the form of the Hush parser and the autoscript command. Y ou should notice when first compiling the pac k age that the Boundary Devices sample uses this to defer most b oard initialization to the MMC card. It do es this b y setting the CONF[...]

  • Page 14

    5.2 Windo ws CE 14 5.2 Windo ws CE As men tioned earlier, the Neon R  b oard ships with a runnable Windo ws CE 5.0 image on MMC card. A Board Supp ort Pac k age is also a v ailable and necessary to tailor the op erating system for a giv en application. The follo wing sections describ e the pro cess of producing an image match- ing the one shipp [...]

  • Page 15

    5.2 Windo ws CE 15 5.2.3 Building the demo The Platform Builder pro ject used to construct our sample image ma y be found on the Boundary Devices w eb site. After installation of the BSP , this pro ject may be copied to a new direc- tory within the WINCE500 PBW orkspaces directory and built using Plat- form Builder. C:WINCE500PBWorkspaces>md b[...]

  • Page 16

    5.3 Lin ux Support 16 5.3 Lin ux Supp ort The Lin ux En vironmen t for Boundary Devices boards consists of four pri- mary pieces, a to olchain, the k ernel and device driv ers, a user-space build to ol based on PTXDist and a Ja v ascript runtime used to demostrate the capabilities of the hardw are. 5.3.1 Crossto ol Lin ux T o olchain Before the k e[...]

  • Page 17

    5.3 Lin ux Support 17 Note that this will tak e a lo o ong time 2 . Find something else to do while y ou w ait. When complete, you should find a whole slew of programs in y our /opt/crosstool/gcc-3.4.3-glibc-2.3.5/arm-xscale-linux-gnu/bin/ di- rectory: -rwxr-xr-x 1 username cvsd 1900724 Jul 18 20:48 arm-linux-addr2line -rwxr-xr-x 2 username cvsd 1[...]

  • Page 18

    5.3 Lin ux Support 18 GCC_DIR=gcc-3.4.3 GCC_EXTRA_CONFIG= Then, create a shell script named crosstool-0.37/contrib/newlib/arm-e lf.sh with the follo wing con ten t. #!/bin/sh set -ex TARBALLS_DIR=/armArchives RESULT_TOP=/opt/crosstool export TARBALLS_DIR RESULT_TOP GCC_LANGUAGES="c,c++" export GCC_LANGUAGES # You should do the mkdir befor[...]

  • Page 19

    5.3 Lin ux Support 19 5.3.4 Kernel 2.4.19 Arm-Lin ux k ernel v ersion 2.4.19 Linux k ernel patc hes for ARM pro cessors PXA P atc hes In tel PXA supp ort for ARM-Lin ux Boundary Devices patc hes Boundary Devices supp ort 5.3.5 Kernel 2.6 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.11.tar.bz2 bzcat linux-2.6.11.11.tar.bz2 | tar xvf[...]

  • Page 20

    5.3 Lin ux Support 20 5.3.6 Userland build to ol As men tioned b efore, w e at Boundary Devices use a v ariant of an older v ersion of the PTXDist to ol to k eep trac k of the cross-compilation needs for v arious libraries. This allows in ter-library dependencies to b e expressed, and also allo ws the canonical source lo cations to b e used during [...]

  • Page 21

    5.3 Lin ux Supp ort 21 the comp onen ts may tak e a while, it is often useful to p erform this step b y itself after configuration. The get mak efile target c an be used to p erform this step. Note that the original w eb lo cations are generally used for each library supp orted b y the userland build. This is generally a go o d thing, but also me[...]

  • Page 22

    5.3 Lin ux Supp ort 22 5.3.7 Userland libraries and applications The follo wing libraries and applications are included in the userland build. Name Description Link b dScript Boundary Devices Ja v ascript Boundary Devices busyb o x Shell and utilities Busyb o x cramfs to ols Cramfs Utilities SourceF orge lib curl HTTP library and more lib curl pro [...]

  • Page 23

    5.3 Lin ux Supp ort 23 5.3.8 Notes ab out userland ro ot filesystems Section 5.3.6 refers to the cr amfs target without really indicating its’ use. The cr amfs option is one of three primary ’bundled’ targets: 1. cramfs - Creates a single file as a read-only , gzip-compressed image of a filesystem tree. When y ou can nail do wn the con ten[...]

  • Page 24

    5.3 Lin ux Supp ort 24 Lin ux b o ot command line parameters to the kernel also helps here. T ypical usage includes is of the follo wing form, which supplies both the MTD partition information and the ro ot filesystem reference: mtdparts=phys_mapped_flash:1024k(armboot),256k(params),-(rootfs1) root=/dev/mtdblock3 rootfstype=cramfs In English, this[...]

  • Page 25

    5.3 Lin ux Supp ort 25 5.3.9 mmcinitrd.u-b o ot The mmcinitrd.u-boot userland Mak efile target has a lot of parts, but its’ goal is simple Pro vide an application developer a means of staying focused on dev elopment without the possibility of trashing a flash. It presumes the existence of an SD card formatted with the VF A T filesys- tem, and [...]

  • Page 26

    26 6 Dev elopmen t T o ols 6.1 minidebug minidebug is a small (under 16k) debugger designed to fit completely within the instruction cac he on the PXA-255 pro cessor to allow testing of boards ev en in the absence of ROM or RAM. It also includes features to do wnload ov er either serial or Ethernet, al- lo ws the displa y and man upulation of regi[...]

  • Page 27

    6.2 JT AG system-lev el debugger 27 6.1.1 mdebug The mdebug image adds Ethernet and wireless do wnload capabilities using the Blast proto col to the Neon R  . The SSID and DLW commands ab o v e are only v alid when mdebug is present. The follo wing is an example of the use of mdebug and DLW . Note that the first commands used do w nload mdebug [...]

  • Page 28

    6.2 JT AG system-lev el debugger 28 a new device. That said, w e also use it extensively as a terminal em ulator during dev elopment and ha ve added a n umber of extensions for that purp ose. The curren t release supp orts the PXA250, PXA255, PXA270, and SA1100 (lart un tested). It chec ks the IDCODE register and uses the appropriate BSDL structure[...]

  • Page 29

    6.2 JT AG system-lev el debugger 29 jtag -i Iden tify the flash part used This option tries to iden tify the part num b er of the Flash EEPRO M. Curren tly supp orted parts are 28F160F3B, 28F320J3A, 28F128J3A, 28F320C3B, and 28F320S3, though not all hav e b een tested. It should b e relativ ely easy to add new parts. jtag -f Generate the appropria[...]

  • Page 30

    6.2 JT AG system-lev el debugger 30 6.2.3 Con trol Keys Once running, the jtag program resp onds to a num b er of command se- quences, all b eginning with [Ctrl A] . [Ctrl A] B Send a break [Ctrl A] S Send a file using XMo dem [Ctrl A] L T oggle logging to jtag.log [Ctrl A] T Send an ascii file [Ctrl A] P Cho ose baud rate [Ctrl A] Q Quit [Ctrl A[...]

  • Page 31

    6.2 JT AG system-lev el debugger 31 to receiv e a file. Use the [Ctrl A] S sequence to instruct jtag to prompt for and send a file using XMo dem. T o abort the op eration, either when prompting for a filename or b efore, use [ctrl-C] . . dl a1f00000 CCCCCCCCCCCCCC enter binary file name: u-boot.bin CCCCCCCCCCCCCCCC...............................[...]

  • Page 32

    6.3 T eraT erm blast extensions 32 6.3 T eraT erm blast extensions As an alternativ e to the jtag exe cutable, Boundary Devices has also pro- duced an extension to the T eraT erm op en-source terminal emulator wit h supp ort for the Blast R  proto col. It has the follo wing b enefits ov er the use of jtag: • Do es not require Cygwin and iop e[...]

  • Page 33

    6.4 Using U-Boot Netw orking 33 6.4 Using U-Bo ot Net working One of the most useful features of the Das U-Bo ot loader is its’ abilit y to transfer files across a net work. As sho wn b elow, the dhcp command is t ypically used to p erform b oth a BOOTP / DHCP request and transfer a file. $ $ set bootfile nk4.nb0 $ set serverip 192.168.0.26 $ d[...]

  • Page 34

    34 7 Configuration Notes 7.1 Displa y configuration The Neon R  supp orts a v ariety of LCD panels. The follo wing sec tion de- scrib es the pro cess of configuring the b oard for a kno wn, curren tly supp orted displa y panel as well as a Das U-Boot utility command for testing settings on a new panel. If y ou know the t yp e of panel at comp[...]

  • Page 35

    7.1 Displa y configuration 35 field name type description name string used to identify the panel pixclo c k num b er Divisor for the pixel clo c k. Generally 3 for QV GA, 1 for higher resolution. xres n umber Horizontal pixel coun t yres n umber V ertical pixel coun t act high n umber Clo ck polarity , 0 (default) or 1 hsync len num b er Horizont[...]

  • Page 36

    7.1 Displa y configuration 36 $ lcdp ------------------------------------ name : crt1024x768 pixclock : 65000000 xres : 1024 yres : 768 act_high : 1 hsync_len : 200 left_margin : 24 right_margin : 161 vsync_len : 6 upper_margin : 3 lower_margin : 29 active : 0 7.1.2 What displa ys are supp orted...? The lcdp command follo wed b y a question mark w[...]

  • Page 37

    7.1 Displa y configuration 37 vsync_len : 20 upper_margin : 17 lower_margin : 3 active : 1 ------------------------------------ name : hitachi_hvga pixclock : 1 xres : 640 yres : 240 act_high : 1 hsync_len : 64 left_margin : 34 right_margin : 1 vsync_len : 20 upper_margin : 8 lower_margin : 3 active : 1 ------------------------------------ name : [...]

  • Page 38

    7.1 Displa y configuration 38 name : crt1024x768 pixclock : 65000000 xres : 1024 yres : 768 act_high : 1 hsync_len : 200 left_margin : 24 right_margin : 161 vsync_len : 6 upper_margin : 3 lower_margin : 29 active : 0 $ 7.1.3 Select a supp orted display If y ou s upply a supported panel name on the lcdp command line, the displa y con troller will b[...]

  • Page 39

    7.1 Displa y configuration 39 $ set panel hitachi_wvga $ save Saving Environment to Flash... Un-Protected 1 sectors Erasing Flash... Erased 1 sectors Writing to Flash... done Protected 1 sectors $ reset resetting ... $S00#b3 Reset A0008000 U-Boot 1.1.2 (Jun 10 2005 - 22:31:50) U-Boot code: A1F00000 -> A1F20500 BSS: -> A1F54520 RAM Configurat[...]

  • Page 40

    7.2 Memory size configuration 40 pixclock : 1694498816 xres : 800 yres : 600 act_high : 1 hsync_len : 200 left_margin : 24 right_margin : 161 vsync_len : 6 upper_margin : 4 lower_margin : 29 active : 1 As with switc hing to a known panel, the settings tak e effect immediately up on completion of the command. This can b e a very quic k w ay to add[...]

  • Page 41

    7.3 Upgrading U-Boot 41 Use the PHYS SDRAM 1 SIZE v ariable in include/configs/neon.h to sp ecify the actual size for y our hardware. The Windo ws CE image supp orts either, but defaults to 32MB. Set the RAM SIZE 64 MB environmen t v ariable in your pro ject to indicate that 64MB should b e presen t. The RAM size set in the b o ot loader is passed [...]

  • Page 42

    7.4 T ouch P anel Calibration 42 7.4 T ouc h Panel Calibration Under Lin ux, the flash sector at address 0x140000 is used to store the touch- screen calibration settings. If y ou’re using b dScript startup co de, the cali- bration routine will launc h up on first b o ot if not defined. Under Windo ws CE, the touch screen settings are stored on[...]

  • Page 43

    7.5 Ethernet MA C Addresses 43 7.5 Ethernet MA C Addresses Normally , Neon boards come with their MAC addresses pre-programmed during assem bly and test. This is done b y using the U-Bo ot mac command as sho wn b elow. In vok ed without an argument, the command will display the curren t MA C address. Used with a single parameter (MAC address with c[...]