Mailing List Archive: ivtv: devel

Extracting firmware fails

Index | Next | Previous | View Threaded

astfgl at iamnota

Feb 21, 2003, 3:55 PM

Post #1 of 6 (1195 views)
Permalink

Extracting firmware fails

I received my band new old-model PVR-250 yesterday, and
eagerly started extracting the firmware images. Unfortunately,
the ivtvfwextract script failed. It appears that my CDROM
has a slightly different driver zip file from the one the
script was developed against.

Specifically, in it's default behavious the script searches
the cdrom for a file named "pvr48xxx.exe", extracts the file
"hcw98gp2.sys" from it, and then extracts the firmware.

My CDROM has the "pvr48xxx.exe" file, but that file does not
contain a "hcw98gp2.sys" file.

There is a .sys file in my "pvr48xxx.exe", called "hcwpvrp2.sys",
and modifying the script to extract it appears to work, though
I have no way of confirming that the firmware images are real
firmware images and not random code.

glen.

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

linpvr at projectplasma

Feb 21, 2003, 4:21 PM

Post #2 of 6 (1136 views)
Permalink

Re: Extracting firmware fails [In reply to]

On Sat, 22 Feb 2003, Glen Harris wrote:

> There is a .sys file in my "pvr48xxx.exe", called "hcwpvrp2.sys",
> and modifying the script to extract it appears to work, though
> I have no way of confirming that the firmware images are real
> firmware images and not random code.
>
> glen.

If you exec the following from the command line, the first two lines should
match.

# od -v -w4 -t x4 -N 64 {encoder_image}
0000000 00000da7
0000004 aa55bb66
0000010 0000002c
0000014 07032001
0000020 00000250
0000024 0001001c
0000030 00001000
0000034 00080000
0000040 00020000
0000044 00000006
0000050 00000000
0000054 00000000
0000060 00000000
0000064 cc44dd33
0000070 00000000
0000074 02010011
0000100

# od -v -w4 -t x4 -N 64 {decoder_image}
0000000 000003a7
0000004 aa55bb66
0000010 0000002c
0000014 dead2008
0000020 00000250
0000024 0001001c
0000030 00001000
0000034 001a0000
0000040 00020000
0000044 00000002
0000050 00000000
0000054 00000000
0000060 00000000
0000064 cc44dd33
0000070 00000810
0000074 00000000
0000100

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

astfgl at iamnota

Feb 21, 2003, 5:16 PM

Post #3 of 6 (1133 views)
Permalink

Re: Extracting firmware fails [In reply to]

PlasmaJohn wrote:
> On Sat, 22 Feb 2003, Glen Harris wrote:
>
>
>>There is a .sys file in my "pvr48xxx.exe", called "hcwpvrp2.sys",
>>and modifying the script to extract it appears to work, though
>>I have no way of confirming that the firmware images are real
>>firmware images and not random code.
>>
>>glen.
>
>
> If you exec the following from the command line, the first two lines should
> match.

Yep, they match. Looks like I have a different version of the CDROM.
Seeing it's an old model card, I'd say they've been sitting in a
warehouse for a while due to the high price/low demand of the card.

FYI, the CDROM is marked "Version 1.1", has a serial number/code
"CD-PVRPCI-250/350-V1.1" and is copyrighted 2000-2002.

Cheers, glen.

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

hp at bitrange

Feb 21, 2003, 6:20 PM

Post #4 of 6 (1132 views)
Permalink

Re: Extracting firmware fails [In reply to]

On Sat, 22 Feb 2003, Glen Harris wrote:

> I received my band new old-model PVR-250 yesterday, and
> eagerly started extracting the firmware images. Unfortunately,
> the ivtvfwextract script failed. It appears that my CDROM
> has a slightly different driver zip file from the one the
> script was developed against.

Or really, there are both hcw98gp2.sys and hcwpvrp2.sys in
pvr48xxx.exe on my CD (version 1.5), both files containing
identical firmware. I cut-and-pasted the wrong filename during
development. Doh! John has always talked about hcwpvrp2.sys.
The error is all mine.

> Specifically, in it's default behavious the script searches
> the cdrom for a file named "pvr48xxx.exe", extracts the file
> "hcw98gp2.sys" from it, and then extracts the firmware.
>
> My CDROM has the "pvr48xxx.exe" file, but that file does not
> contain a "hcw98gp2.sys" file.

Fixed, it now looks for hcwpvrp2.sys.

> There is a .sys file in my "pvr48xxx.exe", called "hcwpvrp2.sys",
> and modifying the script to extract it appears to work, though
> I have no way of confirming that the firmware images are real
> firmware images and not random code.

The script looks for the same magic numbers you'd look for
manually. If the driver successfully uploads it, everything
should be fine.

Thanks again for the report and sorry about the trouble!

brgds, H-P

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

linpvr at projectplasma

Feb 21, 2003, 8:08 PM

Post #5 of 6 (1130 views)
Permalink

Re: Extracting firmware fails [In reply to]

On Fri, 21 Feb 2003, Hans-Peter Nilsson wrote:

> Or really, there are both hcw98gp2.sys and hcwpvrp2.sys in
> pvr48xxx.exe on my CD (version 1.5), both files containing
> identical firmware. I cut-and-pasted the wrong filename during
> development. Doh! John has always talked about hcwpvrp2.sys.
> The error is all mine.

I'm not sure. Actually, I am -- look at:

http://ivtv.sourceforge.net/firmware-upload.html

Right there I specified the '98gp file. I knew that both .sys files had
firmware in them, I had assumed that one was for Win98 and the other for
NT/2k/XP. If you read the .inf file, it looks like '98 loads both (or does
that mean one is a fallback if the other is missing?)

Ok, I'll update the page sometime this weekend.

John

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

hp at bitrange

Feb 21, 2003, 10:40 PM

Post #6 of 6 (1132 views)
Permalink

Re: Extracting firmware fails [In reply to]

On Fri, 21 Feb 2003, PlasmaJohn wrote:
> http://ivtv.sourceforge.net/firmware-upload.html
>
> Right there I specified the '98gp file. I knew that both .sys files had
> firmware in them, I had assumed that one was for Win98 and the other for
> NT/2k/XP. If you read the .inf file, it looks like '98 loads both (or does
> that mean one is a fallback if the other is missing?)

Checking... *blink*

Ok, call me confused. Correction -- you always talked about
*hcw98gp2.sys*, even in pre-webpage conversation. Please, let's
never again use those two filenames. :-) I obviously can't tell
them apart. hcwbzzzz.sys and hcwbzzzz.sys?

Anyway, the current extractor script should work until
someone spots a hcw98gp2.sys without eh, the other .sys.
(When that happens, let's look for both -- or even check the
.inf file.)

brgds, H-P

-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads