Design of a CMOS Clock with Synchronisation Capability


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Design of a CMOS Clock with Synchronisation Capability
# 1  
Old 10-07-2008
Design of a CMOS Clock with Synchronisation Capability

HPL-2008-125 Design of a CMOS Clock with Synchronisation Capability - Castle, Rob
Keyword(s): Memory Spot, CMOS
Abstract: A Memory Spot is a very small integrated circuit containing non-volatile memory, a protocol processor to handle the communications and memory access, and a wireless interface. It has no battery or other external connections and receives its power from the device being used to communicate with it, vi ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Programming

Thread synchronisation

hi, i have to do a program with following condition. please help me to write the program. conditions-i have to create a thread with handle called first and it should call the member function(may do anything lik print anything) of a class called thread1 and for example let take that this first... (5 Replies)
Discussion started by: senthil.march
5 Replies

2. Shell Programming and Scripting

Synchronisation of 2 arrays

If the element found in array2 doesn't exist in array1 i want i to be deleted. This code doesn't work correctly. What's wrong? Is there a simpler solution? for (( i=0; i<=${#array2}; i++ )) do for (( v=0; v<=${#array1}; v++ )) do if }" = "{$array1}" ] then count=1 break... (3 Replies)
Discussion started by: iums1
3 Replies

3. UNIX for Dummies Questions & Answers

Need help on file synchronisation in unix

i want to do file synchronisation...its a client-server model..have to do system call 'ls -l' in both client and server ..the server has to keeep track of client files and have to keep a back up of client files..and tracking must be done based on time stamp.. suppose if client contains a file... (2 Replies)
Discussion started by: shilpam,edappal
2 Replies

4. UNIX for Advanced & Expert Users

Thread synchronisation problem...

Hello, hope my english will be sufficient to be clear enough... I'm in progress on some script that should copy one big source file (200GB average) on one sata drive, to multiple (30+) sata drives. Hardware is not the problem but copy performance is... If i launch all copy process at the same... (4 Replies)
Discussion started by: Gnaag
4 Replies

5. Solaris

CMOS settings on SUN V20Z from Solaris10

Hello Guys, and good day to everybody. I am battling to redirect console on this V20Z 'beast', and would really like to know if it's possible to 'see' CMOS settings from Solaris10 point of view. Machine is remote and I can't easily go and reboot the box and press F2 etc... So is there a... (3 Replies)
Discussion started by: mponjevic
3 Replies

6. Shell Programming and Scripting

sh : URGENT synchronisation insmod in script

Hello, By now in linux 2.4, I have a sh script wich start 2 modules as follow : /sbin/insmod module1.o /sbin/insmod module2.o I added an application in user space named "user_app" which communicate with module1 with a /proc. I now tape the commands myself during code execution on a... (1 Reply)
Discussion started by: crip01
1 Replies

7. Windows & DOS: Issues & Discussions

EISA CMOS checksum error

I have a UNIX server w/an Adaptec aha-2740 card and i keep getting this error during post: EISA CMOS checksum error. It then tries to boot from the floppy. Upon researching this problem i found that it could be one of two things. Either it is the battery on the m/b (which i have all but ruled out),... (3 Replies)
Discussion started by: dlee35
3 Replies

8. UNIX for Advanced & Expert Users

shared memory synchronisation

hello everybody i want to do synchronisation to access a shared memory bu i don't know too much how well i know that i should use semaphore have you any example of synchronisation of a shared memory by use of semaphore because i haven't find any thanks (0 Replies)
Discussion started by: student00
0 Replies

9. UNIX for Dummies Questions & Answers

cmos check sums

not entirely unix orientated but.... anyway i've got an old 486dx? 100 that i'll looking to turn into a unix running machine. But everytime i turn it on it comes up with and invalid CMOS checksum, after i've been into the set up and reset that it works fine, tried a new batter and that didn't sort... (1 Reply)
Discussion started by: stevox
1 Replies
Login or Register to Ask a Question
NVRAMTOOL(1)						      General Commands Manual						      NVRAMTOOL(1)

NAME
nvramtool - read/write coreboot-related information SYNOPSIS
nvramtool [OPTS] [-n] -r NAME nvramtool [OPTS] -e NAME nvramtool [OPTS] -a nvramtool [OPTS] -w NAME=VALUE nvramtool [OPTS] -p INPUT_FILE nvramtool [OPTS] -i nvramtool [OPTS] -c [VALUE] nvramtool [OPTS] -l [ARG] nvramtool [OPTS] -d nvramtool [OPTS] -Y nvramtool [OPTS] -b OUTPUT_FILE nvramtool [OPTS] -B INPUT_FILE nvramtool [OPTS] -x nvramtool [OPTS] -X DUMPFILE nvramtool [OPTS] -v nvramtool [OPTS] -h DESCRIPTION
nvramtool is a utility for reading/writing coreboot parameters and displaying information from the coreboot table. The coreboot table resides in low physical memory. It is created at boot time by coreboot, and contains various system information such as the type of mainboard in use. It specifies locations in the CMOS (nonvolatile RAM) where the coreboot parameters are stored. This program is intended for (x86-based) systems that use coreboot. For information about coreboot, see http://www.coreboot.org/. PARAMETERS
[-n] -r NAME Show the value of the coreboot parameter given by NAME. If -n is specified, show only the value. Otherwise show both parameter name and value. -e NAME Show all possible values for parameter given by NAME. -a Show the names and values for all coreboot parameters. -w NAME=VALUE Assign VALUE to coreboot parameter given by NAME. -p INPUT_FILE Assign values to coreboot parameters according to the contents of INPUT_FILE. The format of this file is described below. -i This is similar to the -p option, except that the contents of the input file are taken from standard input. -c [VALUE] If VALUE is present then set the CMOS checksum for the coreboot parameters to VALUE. Otherwise, show the checksum value. -l [ARG] If ARG is present then show information from the coreboot table as specified by ARG. Otherwise show all possible values for ARG. -d Do a low-level dump of the coreboot table. -Y Write CMOS layout information to standard output. If redirected to a file, the layout information may be used as input for the '-y LAYOUT_FILE' option (see below). -b OUTPUT_FILE Write the contents of CMOS memory to the binary file OUTPUT_FILE. The first 14 bytes of OUTPUT_FILE do not contain actual CMOS data, and are always written as zeros. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -B INPUT_FILE Read binary data from INPUT_FILE and write the data to CMOS memory. The first 14 bytes of INPUT_FILE are skipped and data is writ- ten to CMOS starting at the 15th byte of the CMOS area. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -x Show a hex dump of all CMOS data. The first 14 bytes of the dump do not contain actual CMOS data, and are always shown as zeros. This is because the first 14 bytes of the CMOS area do not contain CMOS memory. These bytes are involved with the functioning of the real time clock. -X DUMPFILE Read binary data from DUMPFILE (presumably a CMOS dumpfile created using the -b OUTPUT_FILE option) and show a hex dump of the data. -v Show version information for this program. -h Show a help message for this program. OPTIONS
In all cases above, [OPTS] evaluates to the following: [-y LAYOUT_FILE | -t] The '-y LAYOUT_FILE' option tells nvramtool to obtain CMOS layout information from the contents of LAYOUT_FILE. Likewise, the '-t' option tells nvramtool to obtain CMOS layout information from the CMOS option table (contained within the coreboot table). If neither option is specified, the CMOS option table is used by default. LAYOUT_FILE follows the format of the cmos.layout files provided by coreboot. If the coreboot installed on your system was built without specifying HAVE_OPTION_TABLE, then the coreboot table will not contain a CMOS option table. In this case, the '-y LAYOUT_FILE' option must be used. These two options are silently ignored when used in combination with other options (such as -h, for instance) for which they are not appli- cable. FILE FORMAT
For the -p option, INPUT_FILE must consist of a sequence of lines such that each line is either a blank line, a comment, or an assignment. A blank line consists only of zero or more whitespace characters (spaces and tabs). A comment is constructed as follows: [ws]#[text] Here, [ws] indicates optional whitespace characters and [text] indicates optional text. Blank lines and comments are both ignored. An assignment is constructed as follows: [ws]NAME[ws]=[ws]VALUE[ws] Here, NAME is the name of a coreboot parameter and VALUE is the value that will be assigned to NAME. VALUE is allowed to contain white- space characters, but it must begin and end with nonwhitespace characters. Note that each comment must appear on a line by itself. If you attempt to add a comment to the end of an assignment, then the comment will be interpreted as part of VALUE. It is useful to observe that the output produced by both the -a and the '[-n] NAME' options (without -n specified) adheres to this file format. BUGS
This program does not implement any type of synchronization to ensure that different processes don't stomp on each other when trying to access the nonvolatile RAM simultaneously. Therefore, corruption of the BIOS parameter values may occur if multiple instances of this pro- gram are executed concurrently. AUTHORS
David S. Peterson <dsp@llnl.gov> <dave_peterson@pobox.com> Stefan Reinauer <stepan@coresystems.de> Linux September 2008 NVRAMTOOL(1)