Problem in reading a Hex file and then.....

[rsk]

Hi Friends,

My requirement is as follows;

A file is consisting of data in hexadecimal format(i.e a 32 bit data for
example like "0xdeadbeef ").

I have to read each of such data into my 'c' code
and i need to assign them to a 32 bit integer array.

Then i have to part select this array bit by bit like array[31]
array[30]...........arra y[0] and do some specific operations.

I am facing difficulty in assigning this 32 bit hex data to the 32 bit
array.

Can you please kindly help me on this.

With Best Regards,
RSK...

[santosh]

rsk wrote:

Hi Friends,

My requirement is as follows;

A file is consisting of data in hexadecimal format(i.e a 32 bit
data for example like "0xdeadbeef ").

I have to read each of such data into my 'c' code
and i need to assign them to a 32 bit integer array.

Then i have to part select this array bit by bit like array[31]
array[30]...........arra y[0] and do some specific operations.

I am facing difficulty in assigning this 32 bit hex data to the
32 bit array.

Can you please kindly help me on this.

If you know the size of your file you can declare the exact size
of the array during compile-time. Otherwise you need to resize
the array on-the-fly as you program reads more of the file.

In any case, make the type of the array as long, and open the
file with fopen in binary read mode. Then use fread in a loop to
fill the array of longs. Stop when fread returns a less than
expected read count. You can distinguish between end-of-file and
a read error by testing with feof or ferror.

The do whatever you want with the array. If it's dynamically
allocated don't forget to free it when you're done. Similarly
close the file after reading it.

In C, the type long is guaranteed to be 32 bits. The type int may
or may not be. If you want a type exactly of 32 bits use
int32_t, though beware that it's improperly supported C99. I'd
just use long.

For any more help, post the code you've written to do what you
want and point out the exact place where you're having
difficulty. DO NOT RETYPE CODE. CUT & PASTE IT.

[rsk]

Thank you so much santosh.So kind of you...
With Best Regards,
Ravi

[Keith Thompson]

"rsk" <kr******@yahoo .co.inwrites:

My requirement is as follows;

A file is consisting of data in hexadecimal format(i.e a 32 bit data for
example like "0xdeadbeef ").

[snip]

Let's be sure we really understand your data format, since I've seen a
lot of confusion on this point.

Does the file actually contain data represented in hexadecimal? In
other words, for the value 3735928559 (0xdeadbeef), does the file
actually contain the (probably ASCII) characters 'd', 'e', 'a', 'd',
'b', 'e', 'e', 'f'? (And if so, are they preceded by the characters
'0', 'x'?) Or are 32-bit numbers stored in the file in a 32-bit
binary format?

We've seen people here refer to raw binary as "hexadecima l", probably
because that's how binary files are often *viewed*. But in fact,
binary ahd hexadecimal are very different formats.

If the values are stored in hex, how are the values separated? Does
each hexadecimal literal occur on a line by itself (terminated with
'\n')? Or are there multiple literals per line, and are they
separated by spaces, tabs, commas, arbitrary whitespace, or something
else?

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Thad Smith]

santosh wrote:

rsk wrote:

In C, the type long is guaranteed to be 32 bits.

Variables of type long are guaranteed to have /at least/ 32 bits. They
may have more.

The type int may
or may not be. If you want a type exactly of 32 bits use
int32_t, though beware that it's improperly supported C99.

Why do you say that int32_t is improperly supported [in] C99?

For any more help, post the code you've written to do what you
want and point out the exact place where you're having
difficulty. DO NOT RETYPE CODE. CUT & PASTE IT.

Good advice.

--
Thad

[santosh]

Thad Smith wrote:

santosh wrote:

>rsk wrote:

[ ... ]

>If you want a type exactly of 32 bits use int32_t, though beware that
it's improperly supported C99.

Why do you say that int32_t is improperly supported [in] C99?

I should have written that better. What I meant was C99 itself was
improperly supported by compiler vendors. Hence if the OP decides to use
C99 types, he might encounter compilation problems when moving his code to
an implementation that partially or fully lacks support for C99, like MS
Visual C++ and many compilers targetting embedded platforms.

[rsk]

No they don't precede by the charecters like '0', 'x',Actually the .txt
file contains the commands in hex format as
deadbeef
00000001
00000002
00000003
00000004
00000005
00000006
00000007
00000008
00000009
0000000a
0000000b
0000000c
0000000d
0000000e
0000000f
00000010
00000011
00000012
00000013
00000014

[rsk]

Santosh,i have a doubt when the file is containing data in hex for mat can
i open the file with fopen in binary mode?

[Malcolm McLean]

"Thad Smith" <Th*******@acm. orgwrote in message
news:46******** *************** @auth.newsreade r.octanews.com. ..

santosh wrote:

>rsk wrote:

>In C, the type long is guaranteed to be 32 bits.

Variables of type long are guaranteed to have /at least/ 32 bits. They
may have more.

>The type int may
or may not be. If you want a type exactly of 32 bits use
int32_t, though beware that it's improperly supported C99.

Why do you say that int32_t is improperly supported [in] C99?

int32_t may exist or it may not. Your compiler may be an old compiler or it
may be a compiler with a few C99 features. In future your code might even
have to be run through a conforming C99 compiler.
This causes huge problems, and the only answer is to be extremely
conservative.

--
Free games and programming goodies.
http://www.personal.leeds.ac.uk/~bgy1mm

[rsk]

Hi friends,

the command.txt contains a sequence of hex numbers
like

adcdef45
12435fde