Neobrick Instruction Manual

Total Page:16

File Type:pdf, Size:1020Kb

Neobrick Instruction Manual Neobrick Instruction Manual October 30, 2008 1 Connectors 1.1 Power The neobrick has 3 SMA connections for power: +5V, +12V, and GND. The shield on both the +5V and +12V are also connected to ground internally, but the GND return SMA should be connected to minimize voltage drop. The connections are located on the main housing of the neobrick. Note: the order of the SMA connectors is +5V/+12V/GND. Identifying the GND terminal, if the labelling/markings are unreadable, may require using a multimeter to check continuity between GND and the shields of the +5V/+12V and SHUTDOWN signals, as well as pin 5 on the DB9 RS232 connector. 1.2 Adapter box The adapter box on top of the neobrick has three connections: Ethernet, serial (for debugging), and the SHUTDOWN signal. The SHUTDOWN signal, if not connected, should be terminated somehow (pulled down to ground). A simple 50 ohm SMA terminator works ne. The serial connection is wired up as a DTE (so a crossover serial cable - female-to-female is needed) and operates at 115,200 bps, 8 bits, 1 stop bit, no parity, and no ow control. Ethernet is congured as a xed IP address (10.0.0.2), and is wired up as a crossover cable, so only a straight cable from a PC to the Neobrick is needed. 1.3 Internal connections 1.3.1 Adapter box Inside the adapter box, a two-pin shunt connects the RESET output of the watchdog to the RESET input of the CPU. The watchdog resets the system every ~60 seconds if the watchdog Linux process is not running, so any BIOS changes, etc. must be done with the RESET disconnected. 1 1.3.2 Internal to pressure housing The connections inside the pressure housing are: • the 3 SMA power connections, which are soldered directly to the CPU and HDD interface board • a DB9 connection containing the serial port, reset line, and shutdown signal • a 2mm 6-pin header for the Ethernet port Removal of all 3 of these connections will leave the main neobrick electronics removable from the pressure housing. 1.3.3 Between the CPU and HDD The only connection between the CPU and HDD is a 2mm x 44 pin ribbon cable containing the IDE and +5V power signals. These signals go to a SATA-to-IDE interface board which plugs into the HDD directly. The interface board also has a +12V power cable for the HDD. The SATA-to-IDE interface board is then removable from the HDD. The only other connections between the CPU and HDD are 4 standos for mechanical purposes. Block diagrams are shown in Fig. 2 and Fig. 2 Operating System The Neobrick runs a micro distribution of Linux based on a tiny version of the C library called uClibc. The distribution can be found at www.uclibc.org. 2.1 Root lesystem The neobrick does not contain a full distribution of Linux: only a small subset of commands are available due to space concerns: [, [[, ash, basename, cat, chgrp, chmod, chown, chroot, cksum, clear, cp, crond, date, dd, df, dirname, dmesg, du, echo, egrep, env, false, fdisk, fgrep, free, fsck, getty, grep, halt, hdparm, head, hwclock, id, ifcong, ifdown, ifup, init, kill, killall, killall5, klogd, linuxrc, ln, logger, login, logread, ls, md5sum, mesg, mkdir, mknod, more, mount, mv, nohup, ping, powero, ps, pwd, rdate, readlink, reboot, reset, rm, rmdir, route, run-parts, sh, sleep, start-stop-daemon, stty, switch_root, sync, syslogd, tail, telnetd, test, touch, true, tty, umount, uname, usleep, watchdog, yes Note that for some of these commands, they must be executed via busybox, i.e.: busybox sync. Also available are 2 Figure 1: Block diagram of the entire Neobrick system (from outside). Note that the relative orientations of the SMA, adapter box, and RS232 may not be accurate. The order of the SMA connectors is +5V/+12V/GND. 3 Figure 2: Block diagram of the inside of the Neobrick. 4 httpd (does not work), i2cdetect, i2cdump, i2cget, i2cset, vsftpd, nbsd_wd, neobrickd, wd The important software programs which might not be known are wd, nbsd_wd, neobrickd, and vsftpd: • nbsd_wd: the Neobrick Shutdown watchdog. Watches for the assertion of the SHUTDOWN signal. • neobrickd: updates the /mnt/neobrick.status le. • wd: Watchdog daemon. Prevents the hardware watchdog from rebooting the system every 30 s. • vsftpd: the Very Secure FTP Daemon. FTP server. The source code for neobrickd and nbsd_wd are located in the root/ directory of the root-uclibc package. 3 Software patching Since the Neobrick was sealed into the housing relatively early, software patching is needed for ideal operation due to two minor mistakes in the software stored in ash: 1. vsftpd writes a log to /var/log/vsftpd.log . Since /var is a ramdisk on the Neobrick, this log will eventually ll up and could cause problems (note that it also might not - it may simply cause No space left on device for vsftpd, which would be ignored - although the neobrick status le may stop updating). 2. neobrickd outputs the space left/available as a 32-bit integer - a 64-bit value is needed. Since both a telnet server and FTP server are available, software patching is relatively easy. The patchnb script accomplishes this. patchnb opens a connection to the telnet server using the Net::Telnet perl script module, and patches the /etc/vsftpd.conf le. It then informs the FTP server to reload its conguration (via SIGHUP) and transfers a new copy of neobrickd via FTP using the Net::FTP perl module, stops the old copy of neobrickd, replaces it, and starts the new copy. If any part of this process fails, it attempts to reboot the Neobrick and returns with an exit code of 1. If it is unable to connect to the Neobrick, it returns an exit code of 2. If everything completes successfully, it exits with code 0. 5 4 Other information If problems are observed with the neobrick, the simplest thing is to connect a (straight-through) serial cable to the serial port. The settings are 115,200 bps, 8 bits, no parity, and 1 stop bit. The neobrick redirects all console to the serial port, so the BIOS screen and power-on-self-test (POST) are all visible on the serial port. After the BIOS, the console output stops briey (as the system goes through DOS to load Linux) before launching Linux, at which point the console output resumes. Important Note: if the system is unable to launch into Linux, it will reboot after ~1 minute due to the hardware watchdog. The hardware watchdog can be disabled by opening the top of the adapter box and removing the 2-pin shunt connecting the reset line. Note that if the neobrick drive dies, the system will most likely be unable to boot into Linux due to the boot priority table being incorrect. This can be xed by going into the BIOS, going to the Boot Priority menu, selecting Hard Disk Drives and selecting SCSI Disk as the primary boot device. 6.
Recommended publications
  • Data ONTAP® 8.2 Commands: Manual Page Reference for 7-Mode, Volume 1
    Data ONTAP® 8.2 Commands: Manual Page Reference For 7-Mode, Volume 1 NetApp, Inc. Telephone: +1 (888) 463-8277 Part Number: 215-07976_A0 495 East Java Drive Fax: +1(408) 822-4501 May 2013 Sunnyvale, CA 94089 Support telephone: +1(888) 4-NETAPP U.S. Web: www.netapp.com Feedback: [email protected] Table of Contents ...................... 1 About the Data ONTAP Commands: Manual Page Reference, Volume 1 .3.... Manual Pages by Section in This Volume and Complete Index of Both Volumes .5.. acpadmin ................... 18 aggr ..................... 20 arp ..................... 41 autosupport ................... 43 backup .................... 53 bmc ..................... 55 bootfs .................... 57 cdpd ..................... 58 cf ..................... 61 charmap .................... 64 cifs ..................... 66 cifs_access ................... 68 cifs_adupdate .................. 70 cifs_audit ................... 71 cifs_branchcache .................. 72 cifs_broadcast .................. 74 cifs_changefilerpwd .7................ 5 cifs_comment ............. ..... 76 cifs_domaininfo .................. 77 cifs_help .................... 79 cifs_homedir ................... 80 cifs_lookup ................... 81 cifs_nbalias ................... 82 cifs_prefdc ................... 83 cifs_resetdc ................... 85 cifs_restart ................... 86 cifs_sessions ................... 87 cifs_setup ................... 91 cifs_shares ................... 93 cifs_sidcache ................... 102 cifs_stat .................... 104 cifs_terminate
    [Show full text]
  • For the Abstract.The-Revision Deletion, Orcreation,Of Sentences Is
    DOCUMENT REBUKE ED 071 886 LI.004 082 AUTHOR Mathis, Betty. Ann TITLE Techniques for the Evaluation and IMprovement of Computer-Produced Abstracts. INSTITUTION Ohio State Univ".Colulbus..Computer and Information Science, Research.Center.. SPONS AGENCY National Science Foundation, Washington, D.C. REPORT NO OSU-CISRC-TR-15 . PUB DATE Dec 72 NOTE 275p.;(202 References) EDRS PRICE MF-30.65 HC-49.87 DESCRIPTORS *Abstracting;,,Abstracts; Algorithms; *Automation; CoMputers; *Electrohit Data Processing; Evaluation; Periodicals IDENTIFIERS *Automatic Abstracting ABSTRACT An automatic abstracting system, named ADAM, implemented on the IBM 370, receives journal.articles as input and produces abstracts as output. An algorithm has- been.developed which considers every sentence in the input text and rejects sentences which, are not suitable for inclusion in the abstract. All sentences which are not rejected are included in the set of sentences which are candidates for inclusion in the abstract.,The quality of the abstracts can be evaluated by means of a two -step evaluation procedUre.,The 'first step determines the conforMity of the abstracts to the defined criteria for an acceptable abstract The aecond step provides an objective evaluation criterion for abstract quality based on a.compsrison of the abstract with 'its parent documere,-. Based on the results of this evaluation, several techniques have been developed to improve the quality of the abstracts. These procedures -modify the form, arrangement, and content of the sentences selected for the abstract.The-revision deletion, orcreation,of sentences is perfOrmed according to a number of generalized ruletwhich are based on the structural characteriitics of the sentences.. This modification produces' abstracts in which the flow of ideas is improved and which represent a more nearly cohcrent:whole..(AuthorISJ) - - TECIfigICAL REPORT SERIES 4 CO1PUTE13 1r1fiFilliTTO S.
    [Show full text]
  • EM316LNXNM-OT Network Manager with Linux
    EM316LNXNM-OT Network Manager with Linux Fiber Driver Optical Multi-Service Platform Published 2012/10/17 15:28:24 P/N 1275005-100 Revision E6 ( -build r21138- ) For EM316LNXNM v4.7 fdr 39 built Oct 16 2012 - 19:07:17 EM316LNXNM-OT Preface Copyright © 2012 MRV Communications, Inc. All rights reserved. No part of the contents of this document may be reproduced in any form or by any other means without written permission from the publisher. Fiber Driver, Media Cross Connect, MegaVision, and other MRV product names and terms belong to MRV Communications or affiliates. All other brand names or trademarks referenced are the property of their respective owners. This document includes electronic links and URLs that may require internet access. Some references may not be obvious on printed pages. The user assumes sole responsibility for applying the information supplied in product documents. MRV Communications reserves the right to make changes to technical specifications and documentation without notice. This document represents the most recent product versions at the time of writing, which may differ from previous releases. To ensure maximum functionality, use the latest software updates and documents. Contact customer support regarding previous product revisions and documents. PN 1275005-100 Rev E6 intro- 2 EM316LNXNM-OT Preface Table of Contents 1. Support and Safety .......................................................................................................... 1 1.1. Customer Support ................................................................................................
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]
  • Managing Clock Synchronization in Oracle® Solaris 11.4
    Managing Clock Synchronization in ® Oracle Solaris 11.4 Part No: E61003 January 2019 Managing Clock Synchronization in Oracle Solaris 11.4 Part No: E61003 Copyright © 2002, 2019, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • OEP User's Manual
    Omni-EP JK microsystems Omni-EP Manual Unless otherwise noted, this document and the information herein disclosed are proprietary to JK microsystems, Inc. Any person or entity to whom this document is furnished or having possession thereof, by acceptance, assumes custody thereof and agrees that the document is given in confidence and will not be copied or reproduced in whole or in part to meet the pur- poses for which it was delivered. The information in this document is subject to change without notice, and should not be con- strued as a commitment by JK microsystems, Inc. JK microsystems, Inc. will make every effort to inform users of substantive errors. JK microsystems, Inc. disclaims all liability for any loss or damage resulting from the use of this manual or any software described herein, including without limitation contingent, special, or incidental liability. JK microsystems, Inc. recognizes our customer‘s need for a consistent product and will make every effort to provide one. In order to provide the best possible product for all of our custom- ers, we reserve the right to make incremental improvements in our product designs. Omni-EP is a trademark of JK microsystems, Inc. All other brand and product names are trade- marks or registered trademarks of their respective companies. Omni-EP User‘s Manual Version 1.0 Copyright © JK microsystems, Inc. All rights reserved Printed in U.S.A. Document Part No. 94-0034 Published September 2005 2 JK microsystems Omni-EP Manual Limited Warranty JK microsystems, Inc. warrants each Omni-EP to be free from defects in material and work- manship for a period of 90 days from the date of purchase.
    [Show full text]
  • Command Map for 7-Mode Administrators ONTAP 7-Mode Transition Netapp September 12, 2021
    Command map for 7-Mode administrators ONTAP 7-Mode Transition NetApp September 12, 2021 This PDF was generated from https://docs.netapp.com/us-en/ontap-7mode-transition/command- map/reference_how_7_mode_commands_map_to_clustered_ontap_commands.html on September 12, 2021. Always check docs.netapp.com for the latest. Table of Contents Command Map for 7-Mode Administrators. 1 How 7-Mode commands map to ONTAP commands . 1 How 7-Mode options map to ONTAP commands . 37 How 7-Mode configuration files map to clustered Data ONTAP commands . 69 How to interpret the clustered Data ONTAP commands, options, and configuration files maps for 7-Mode administrators. 70 Command Map for 7-Mode Administrators This guide maps 7-Mode commands to their equivalents in ONTAP. How 7-Mode commands map to ONTAP commands You can use the tables provided to find the ONTAP equivalents of 7-Mode commands, with the exception of the options command. The following tables list the ONTAP equivalents of the 7-Mode options command. Information about understanding these tables is also provided. Understanding the 7-Mode to clustered Data ONTAP command map A-E A 7-Mode command ONTAP command acpadmin configure system node run -node {nodename|local} acpadmin configure acpadmin list_all system node run -node {nodename|local} acpadmin list_all acpadmin stats system node run -node {nodename|local} acpadmin stats aggr add aggr add aggr add-disks storage aggregate add-disks aggr create aggr create storage aggregate create aggr destroy aggr delete storage aggregate delete aggr media_scrub
    [Show full text]
  • Sun Blade 6000 Ethernet Switched NEM 24P 10Gbe Program Documentation
    Sun Blade 6000 Ethernet Switched NEM 24p 10GbE Program Documentation Third Party Licenses and Notices Part No.: E26812-01 November 2011 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Utilities Network Management System Installation Guide Release 2.4.0.1.0 F17283-01
    Oracle Utilities Network Management System Installation Guide Release 2.4.0.1.0 F17283-01 September 2019 Oracle Utilities Network Management System Installation Guide, Release 2.4.0.1.0 F17283-01 Copyright © 1991, 2019 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/ or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Learning Embedded Linux Through the File System: a Top-Down Approach
    Learning embedded Linux through the file system: A top-down approach Jason Kridner, [email protected] June 8, 2011, 10:10AM ESC Chicago room 34 http://beagleboard.org/linux_education Abstract Typical introductions to embedded Linux focus on complex tasks, like building device drivers, that are highly desired by at least some people working on your Linux product team. What about the rest of us that simply want to build a quick understanding of how to do some of the simple tasks that are trivial in microcontrollers without using operating systems, like accessing GPIO pins and performing I2C or SPI serial communications? This class takes a quick tops-down overview from the perspective of an electrical engineer looking to take advantage of the latest in GUI building technologies, like Android, Qt, and HTML5, without completely losing access to the underlying hardware for simple system integration tasks. Getting started Much to learn ◦ I‟m used to microcontrollers: just give me the datasheet with register definitions and set me free! Training on boot & device drivers useful ◦ Often geared more at system bring-up ◦ What about the everyday user? ◦ Where is that abstraction benefit? Let‟s just walk a working system Kernel.org documentation http://www.kernel.org/doc/ Documentation extracted from the Linux kernel and mirrored on the web where Google can find it: ◦ Documentation - Text files in the kernel source tarball's Documentation subdirectory. ◦ htmldocs - Kernel Documentation maintained in docbook format (output of "make htmldocs"). ◦ Menuconfig - help text for each kernel configuration option (from kconfig source). ◦ README various README files scattered around Linux kernel source ◦ RFC - List of IETF RFCs referred to by kernel source files.
    [Show full text]
  • Linux, Shell Programming and Perl As Pdf File
    Linux, Shell Programing and Perl by Willi-Hans Steeb, Gert Cronje and Yorick Hardy International School for Scientific Computing Contents 1 Linux Basics 1 1.1 Some Basic Commands . 1 1.2 Working with Files and Directories . 10 1.2.1 Introduction . 10 1.2.2 The Home Directory and Path Names . 11 1.2.3 Important Directories in the Linux File System . 13 1.2.4 Basic Files and Directories Commands . 14 1.2.5 File Name Substitution . 31 1.3 Standard Input/Output, and I/O Redirection . 35 2 Linux Commands 43 3 Advanced Linux 73 3.1 The Unix File System . 73 3.2 Mounting and Unmounting . 76 3.3 MTools Package . 81 3.4 Swap Space and the Loopback Device . 82 3.5 Network File-System . 83 3.6 Linuxconf . 84 3.7 Compressed Files . 85 3.8 The vi and emacs Editors . 88 3.8.1 vi Editor . 88 3.8.2 emacs Editor . 96 3.9 Programming Languages . 99 3.9.1 C and C++ Compiler . 99 3.9.2 Perl . 101 3.9.3 Lisp . 102 3.9.4 Java . 103 4 Linux and Networking 105 4.1 Introduction . 105 4.2 Basic Commands . 106 4.3 email . 116 4.4 ftp Commands . 122 4.5 Telnet . 125 i 4.6 Remote Shell . 127 4.7 Web . 128 4.8 INETD and Socket Programming . 129 5 Shell Programming 133 5.1 What is a shell . 133 5.2 The Shell as a Programming Language . 137 5.2.1 Creating a Script . 138 5.2.2 Making a Script executable .
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]