Minicom Advanced Systems CMG-DCM manual Libgconfigdb

Page 93

Operator's guide

flashdcm -rroot-file-bboot-file-sbaud-rate-proot- password-dport

where root-file and boot-file are the images you wish to

transmit, baud-rate is the baud rate of the DCM's console port, root-password is the password of the user root on the DCM (not any other administrative account), and port is the port number of the

serial interface (on the second computer or DCM) which you will be using.

If the device has several serial interfaces, the command serialmap may help you determine which port number corresponds to which device:

[root @ dcm] # serialmap

Library version: libserialmap Version 1.0.5 with

LIBGCONFIGDB

4 serial ports

Port

0, Key

7000, name ttyS0, device /dev/ttyS0, baud

38400

1, Key

7001, name ttyS1, device /dev/ttyS1, baud

Port

19200

2, Key

7002, name ttyS2, device /dev/ttyS2, baud

Port

19200

3, Key

7003, name ttyS3, device /dev/ttyS3, baud

Port

19200

 

 

flashdcm also has an -eoption, which wipes clean the Flash memory used for the filesystem before providing the new firmware. Some surface DCM units require you to do this when installing a root image. If you use the -eoption to install a root image, you must also provide a new boot image, since the boot image in memory will be erased.

6.Power up the DCM. The second computer or DCM will detect messages coming from the bootloader of the DCM, and automatically interrupt the boot process to provide the new firmware.

7.Wait for the new firmware to be uploaded. The DCM will reboot automatically at the end of transmission, and the flashdcm process will terminate. This may take several minutes.

At this point, you will have a minimal installation of the DCM software, and can proceed to commissioning the system.

December 2005

93

Image 93
Contents CMG-DCM Table of Contents December Inside the DCM Introduction CMG-DCM Inside the DCM Network services Serial port servicesSee .4, Connecting to a local network for full details Installing the CMG-DCM Power supplyOverview Connecting over a serial link Connecting to a single computer192.168.0.x Connecting over EthernetConnecting over USB Using an internal modemConnecting to a local network Gcfgdbset option-namenew-value Connecting to the Internet Wi-FiSetting up the CMG-DCM Connecting digitizers and external hardwareWeb setup Setting up digitizers Using Scream Usage General notesDCM as a data store Gnblocks port-number Page CMG-DCM DCM as a GCF data source Accessing the DCM command line through gcfout Sensor arrays DCM as a network data hub Communicating with digitizers Configuring digitizers Data storage and retrieval Using miniSEED format Real-time data transmission CD1.0 and CD1.1 Troubleshooting DCM installations Cannot see the DCMs Web site over Http or Https Cannot connect to the DCMs Scream! serverCannot Gcfping the DCMs Scream! server DCM is not receiving any data streams Can Gcfping the DCMs Scream! server, but no data appearsDCM is receiving streams, but they do not contain any data Use the Serial port configuration → port name Web page, or143032 up 34 min, load average 1.24, 1.32 General Configuration optionsDisk CMG-DCM Serial port configuration CMG-DCM Page Ethernet port Network configurationStatic routes DNS setup Incoming mail setup Outgoing mail setup Remote access Administrators PPP Mgetty Scream Data transferAutoDRM Scream! ClientHttp server Http clientCD1.0 CD1.1 CD1.1 subframe configuration DSS Server configuration Seed Page CMG-DCM Data Viewer ActionsStream list Icon barDigitizer Setup General digitizer settings Digitizer output control CMG-DCM Trigger criteria CMG-DCM Tap # Rate Bandwidth Samples/s Auxiliary Mux channels Sensor mass control Partition, and format disk Disk toolsCheck disk filesystem Flush flashDisk files CameraRecent Log Entries Summary Network configurationData Out Port, Serial Port A, Serial Port B DNS configurationFlash Status Tamper linesDisk Status Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Data flow MonitoringDigitizer status Tamper lines Over the Internet Updating the DCMFrom the hard disk Removing support packagesFirmware Libgconfigdb Appendix A.1 Modular DCM units Appendix a Connector pinoutsPort a and B Data OUT portNetwork connector USB connectorDM/AM module output Appendix A.2 Integrated DCM unitsAppendix B.1 Sensor response codes Appendix B Sensor and digitizer typesDigitizer Appendix B.2 Digitizer type codes