Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Little Trouble Understanding some code... Post 302143121 by jim mcnamara on Tuesday 30th of October 2007 04:51:17 PM
Old 10-30-2007
IFS=: makes a colon the default field separator. By grep FIELD1, the code only finds records with the word "FIELD1" in them, probably just one record.

Next, since IFS is a colon, each of the variables in the read statement will be assigned the value of the corresponding field in the file.
LBL1 will be the first field, ie., FIELD1
LBL2 will be the second FEI
and so on.

You now have several variables defined as the contents of the fields in one record from
Param.fle
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help in understanding thisperl code.

Can any body explains the under given lines of code i have difficulties in understanding it, my $errorlog = "/var/log/controler.log"; &initLanguage($language); &launchCbox(); sub launchCbox { ... (1 Reply)
Discussion started by: Raheel Hassan
1 Replies

2. UNIX Desktop Questions & Answers

Understanding the code

hello all, May i know what is this "DEBUG_ME $DEBUG_CMD main" doing in the below code. I am confused with alias also "alias DEBUG_ME='#'". Thanks for your help. set -x alias DEBUG_ME='#' if ; then . /product/apps/informatica/v7/pc/ExtProc/debug.ksh "$1" fi # Declaring the... (1 Reply)
Discussion started by: Ariean
1 Replies

3. UNIX for Dummies Questions & Answers

Having trouble understanding this command: >foo<bar bc

Sometimes it works for me and sometimes I get this error: syntax error on line 1, teletype Basically I've got no idea whats going on, especially at the end of the command: bc Any help is appreciated (1 Reply)
Discussion started by: phunkypants
1 Replies

4. Homework & Coursework Questions

trouble understanding file option and command line arguments

Hi, I am creating a program with the C language that simulates the WC command in Unix. My program needs to count lines, bytes and words. I have not added the code to count bytes and words yet. I am having trouble understanding what the file option/flag '-' does. I can not visualize how it moves... (1 Reply)
Discussion started by: heywoodfloyd
1 Replies

5. Programming

Understanding perl code

What is the difference between the two statements below? A: $a->{"$fruit"}->{"$color"}->{size} = $size B: $size = $a->{"$fruit"}->{"$color"}->{size} Please assist. Thanks! (0 Replies)
Discussion started by: onlinelearner02
0 Replies

6. Shell Programming and Scripting

Help with perl code understanding

Hi, I need to understand below perl code, can some one advise me. perl -MDate::Parse -e'BEGIN{$main::now=time;$main::old=(time-60*30)}' -nE'if(/^(\w+\s+\d+\s+\d+:\d+:\d+)/) {$t=str2time $1; $t > $old && $t < $now && print}' (1 Reply)
Discussion started by: learnbash
1 Replies

7. Shell Programming and Scripting

Trouble understanding shell scripting (mostly wsname)

Am still learning Scripting and I come across a build command that I don't really understand if /local/bin/wsname 2>/dev/null; then base="`/local/bin/wsname`" export base fi if ; then /local/bin/wsname exit 1 fi WSNAME="$base"/ can some one in light me to what... (1 Reply)
Discussion started by: Wpgn
1 Replies

8. Programming

Understanding Assembly Code

As the title suggests, I want to better understand the following assembly code: section .text global main ; must be declared for linker (gcc) main: ; tell linker entry point mov edx, len ; message length mov ecx, msg ; message to write... (2 Replies)
Discussion started by: Azrael
2 Replies

9. Programming

Code trouble

I have a formula for figuring out relitive humidity but it will not compile the trouble is the double ** es= 6.11 * 10.0**(7.5*tc/(237.7+tc)) how do I enter in gcc format...?? thanks Eldon (6 Replies)
Discussion started by: eldondehart
6 Replies

10. What is on Your Mind?

I'm having trouble understanding what it is I need to do

Ok, thank you. Again I'm new to the programming thing, I'm just trying to figure out what exactly it is I need to do. How would I cash out bits? Numerous questions. I'm a dreamer. AI attempts to communicate with me regularly especially through unfinished apps that I'm assuming is my responsibility... (1 Reply)
Discussion started by: C-lo
1 Replies
srec_intel16(5) 						File Formats Manual						   srec_intel16(5)

NAME
srec_intel16 - Intel Hexadecimal 16-bit file format specification DESCRIPTION
This format is also known as the INHX16 format. This document describes the hexadecimal object file format for 16-bit microprocessors. This format is very similar to the srec_intel(5) format, except that the addresses are word addresses. The count field is a word count. The hexadecimal representation of binary is coded in ASCII alphanumeric characters. For example, the 8-bit binary value 0011-1111 is 3F in hexadecimal. To code this in ASCII, one 8-bit byte containing the ASCII code for the character '3' (0011-0011 or 0x33) and one 8-bit byte containing the) ASCII code for the character 'F' (0100-0110 or 0x46) are required. For each byte value, the high-order hexadecimal digit is always the first digit of the pair of hexadecimal digits. This representation (ASCII hexadecimal) requires twice as many bytes as the binary representation. A hexadecimal object file is blocked into records, each of which contains the record type, length, memory load address and checksum in addition to the data. There are currently six (6) different types of records that are defined, not all combinations of these records are meaningful, however. The record are: o Data Record o End of File Record o Extended Segment Address Record o Start Segment Address Record o Extended Linear Address Record o Start Linear Address Record General Record Format +-------+--------+--------+--------+--------+--------+ |Record | Record | Load | Record | Data | Check | |Mark | Length | Offset | Type | | sum | +-------+--------+--------+--------+--------+--------+ Record Mark. Each record begins with a Record Mark field containing 0x3A, the ASCII code for the colon (":") character. Record Length Each record has a Record Length field which specifies the number of 16-bit words of information or data which follows the Record Type field of the record. This field is one byte, represented as two hexadecimal characters. The maximum value of the Record Length field is hexadecimal 'FF' or 255. Load Offset Each record has a Load Offset field which specifies the 16-bit starting load offset of the data words, therefore this field is only used for Data Records (if the words are loaded as bytes, the address needs to be doubled). In other records where this field is not used, it should be coded as four ASCII zero characters ("0000" or 0x30303030). This field one 16-bit word, represented as four hexadecimal characters. Record Type Each record has a Record Type field which specifies the record type of this record. The Record Type field is used to interpret the remaining information within the record. This field is one byte, represented as two hexadecimal characters. The encoding for all the current record types are: 0 Data Record 1 End of File Record 5 Execution Start Address Record Data Each record has a variable length Data field, it consists of zero or more 16-bit words encoded as set of 4 hexadecimal digits, most significant digit first. The interpretation of this field depends on the Record Type field. Checksum Each record ends with a Checksum field that contains the ASCII hexadecimal representation of the two's complement of the 8-bit bytes that result from converting each pair of ASCII hexadecimal digits to one byte of binary, from and including the Record Length field to and including the last byte of the Data field. Therefore, the sum of all the ASCII pairs in a record after converting to binary, from the Record Length field to and including the Checksum field, is zero. Data Record (8-, 16- or 32-bit formats) +-------+--------+--------+--------+--------+--------+ |Record | Record | Load | Record | Data | Check | |Mark | Length | Offset | Type | | sum | |(":") | | | | | | +-------+--------+--------+--------+--------+--------+ The Data Record provides a set of hexadecimal digits that represent the ASCII code for data bytes that make up a portion of a memory image. The contents of the individual fields within the record are: Record Mark This field contains 0x3A, the hexadecimal encoding of the ASCII colon (":") character. Record Length The field contains two ASCII hexadecimal digits that specify the number of 16-bit data words in the record. The maximum value is 255 decimal. Load Offset This field contains four ASCII hexadecimal digits representing the word address at which the first word of the data is to be placed. (For an exquivalent bytes address, double it.) Record Type This field contains 0x3030, the hexadecimal encoding of the ASCII character "00", which specifies the record type to be a Data Record. Data This field contains sets of four ASCII hexadecimal digits, one set for each 16-bit data word, most significant digit first. Checksum This field contains the check sum on the Record Length, Load Offset, Record Type, and Data fields. Execution Start Address Record +-------+--------+--------+--------+--------+--------+ |Record | Record | Load | Record | EIP (4 | Check | |Mark | Length | Offset | Type | bytes) | sum | |(":") | (4) | (0) | (5) | | | +-------+--------+--------+--------+--------+--------+ The Execution Start Address Record is used to specify the execution start address for the object file. This is where the loader is to jump to begin execution once the hex load is complete. The Execution Start Address Record can appear anywhere in a hexadecimal object file. If such a record is not present in a hexadecimal object file, a loader is free to assign a default execution start address. The contents of the individual fields within the record are: Record mark This field contains 0x3A, the hexadecimal encoding of the ASCII colon (":") character. Record length The field contains 0x3032, the hexadecimal encoding of the ASCII characters "02", which is the length, in bytes, of the EIP regis- ter content within this record. Load Offset This field contains 0x30303030, the hexadecimal encoding of the ASCII characters "0000", since this field is not used for this record. Record Type This field contains 0x3035, the hexadecimal encoding of the ASCII character "05", which specifies the record type to be a Start Address Record. EIP This field contains eight ASCII hexadecimal digits that specify the address. The field is encoded big-endian (most significant digit first). Checksum This field contains the check sum on the Record length, Load Offset, Record Type, and EIP fields. End of File Record This shall be the last record in the file. +-------+--------+--------+--------+--------+ |Record | Record | Load | Record | Check | |Mark | Length | Offset | Type | sum | |(":") | (0) | (0) | (1) | (0xFF) | +-------+--------+--------+--------+--------+ The End of File Record specifies the end of the hexadecimal object file. The contents of the individual fields within the record are: Record mark This field contains 0x3A, the hexadecimal encoding of the ASCII colon (":") character. Record Length The field contains 0x3030, the hexadecimal encoding of the ASCII characters "00". Since this record does not contain any Data bytes, the length is zero. Load Offset This field contains 0x30303030, the hexadecimal encoding of the ASCII characters "0000", since this field is not used for this record. Record Type This field contains 0x3031, the hexadecimal encoding of the ASCII character "01", which specifies the record type to be an End of File Record. Checksum This field contains the check sum an the Record Length, Load Offset, and Record Type fields. Since all the fields are static, the check sum can also be calculated statically, and the value is 0x4646, the hexadecimal encoding of the ASCII characters "FF". Size Multiplier In general, binary data will expand in sized by approximately 2.3 times when represented with this format. EXAMPLE
Here is an example INHX16 file. It contains the data "Hello, World" to be loaded at address 0. :0700000065486C6C2C6F5720726F646CFF0AA8 :00000001FF COPYRIGHT
srec_cat version 1.58 Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Peter Miller The srec_cat program comes with ABSOLUTELY NO WARRANTY; for details use the 'srec_cat -VERSion License' command. This is free software and you are welcome to redistribute it under certain conditions; for details use the 'srec_cat -VERSion License' command. AUTHOR
Peter Miller E-Mail: pmiller@opensource.org.au //* WWW: http://miller.emu.id.au/pmiller/ Reference Manual SRecord srec_intel16(5)
All times are GMT -4. The time now is 06:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy