Manuale d’uso / di manutenzione del prodotto 2.8 del fabbricante Sonic Alert
Vai alla pagina of 43
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.
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.
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 . . . .
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 . .
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.
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 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.
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-.
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 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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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 asc.
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.
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.
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.
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.
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 .
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).
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.
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.
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.
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.
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.
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.
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.
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.
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 hsy.
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.
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.
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.
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.
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.
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.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Sonic Alert 2.8 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Sonic Alert 2.8 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Sonic Alert 2.8 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Sonic Alert 2.8 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Sonic Alert 2.8, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Sonic Alert 2.8.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Sonic Alert 2.8. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Sonic Alert 2.8 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
