Binflash - NEC/Optiarc firmware flasher and dumper

crazycat · 10-01-2008

binflash 1.40+ for win32 (console and gui) not work with FrogASPI (NeroASPI still work, WinXP-SP2). Drive switch to safe mode and next 'Error dumping firmware' and drive switch to Normal-mode.

P.S. binflash 1.39 work fine with FrogASPI.

kriko · 10-01-2008

Is it possible to use binflash in linux with new PATA stack? I tried, however with no success (works with old IDE drivers, just had to disable DMA).

**Liggy** · 10-01-2008

Quote:

Originally Posted by crazycat

binflash 1.40+ for win32 (console and gui) not work with FrogASPI (NeroASPI still work, WinXP-SP2). Drive switch to safe mode and next 'Error dumping firmware' and drive switch to Normal-mode.
P.S. binflash 1.39 work fine with FrogASPI.

I have to admit, that I cannot really explain this behaviour. I just checked my Subversion repository and looked at the differences between 1.39 and 1.40. But I did not change a single line in the way Binflash communicates with the drives. I just added support for AD-5170S drives by treating them the same way as e.g. AD-5170A drives. (Just some comparisons and variable assignments)

Quote:

Originally Posted by kriko

Is it possible to use binflash in linux with new PATA stack? I tried, however with no success (works with old IDE drivers, just had to disable DMA).

How does the new PATA stack work? How would I have to address devices?

kriko · 10-01-2008

Quote:

Originally Posted by Liggy

How does the new PATA stack work? How would I have to address devices?

Devices are recognised as scsci. DVD-RW in my case is recognised this way (/dev/sr0):

Code:

Binflash - NEC version - (C) by Liggy and Herrie
Visit http://binflash.cdfreaks.com

List of supported devices:

Device   : /dev/sg1
Vendor   : Optiarc
Model    : DVD RW AD-7170A
Firmware : 1.04

Device   : /dev/scd0
Vendor   : Optiarc
Model    : DVD RW AD-7170A
Firmware : 1.04

With "./necflash -flash -v file.bin /dev/sg1" it stalls:

Code:

Identified drive: 28
Detected drive from Firmware: 28

Entering safe mode
Sending firmware to drive at 0x030000

Drive light is blinking, however necflash process doesn't show any activity.

EDIT: dumping firmware works. Flashing it via:

Code:

./necflash -flash -v file.bin /dev/scd0

seems to work fine. I guess drive under /dev/sg1 is operating differently?

Strange, because I wasn't able to flash it under current kernel, I had to compile a new one with old IDE drivers, now somehow works.
(I was flashing with dumped firmware, described problem happened when I tried to upgrade from 1.03 to 1.04 fw)

crazycat · 11-01-2008

Quote:

Originally Posted by Liggy

I have to admit, that I cannot really explain this behaviour. I just checked my Subversion repository and looked at the differences between 1.39 and 1.40. But I did not change a single line in the way Binflash communicates with the drives. I just added support for AD-5170S drives by treating them the same way as e.g. AD-5170A drives. (Just some comparisons and variable assignments)

maybe changes beetwen 1.40 and 1.41+ ? I test 1.39 and 1.42 (and 1.43 now, and problem stay).

P.S. I install FrogASPI as system default ASPI and BinFlash Win32-GUI always show default my drive as ASPI. So - i just press dump/flash and use ASPI. But after 1.39 i must select SPTX-access (or use NeroASPI).

**Liggy** · 11-01-2008

I just did some debugging with my NEC ND-7551A and I must say that FrogASPI is definitely broken in some way.

In order to retrieve the current bootcode version I send an Inquiry to the drive. The firmware version was reported to be 1-02. This means I have to switch to the bootcode in order to retrieve the version. The corresponding command was sent successfully (LED blinking) but a subsequent Inquiry still gives 1-02 instead of 0.04 that it should be (and is with Nero ASPI or SPTX). Since I added some bootcode version checks in Binflash 1.41 this could actually mean that some functionality is broken with FrogASPI but these fixes need to be made in FrogASPI not Binflash.

crazycat · 11-01-2008

Quote:

but a subsequent Inquiry still gives 1-02 instead of 0.04 that it should be

I trace ASPI calls and see this Inquiry 'strange' behavior with FrogASPI. I think FrogASPI cache Inquiry data at opening device and return cached inquiry-data while device opened (for speed-up).

**Liggy** · 11-01-2008

Quote:

Originally Posted by crazycat

I trace ASPI calls and see this Inquiry 'strange' behavior with FrogASPI. I think FrogASPI cache Inquiry data at opening device and return cached inquiry-data while device opened (for speed-up).

I'm not going to open and close the device each time I change between firmware areas just to compensate a broken ASPI implementation

mpata · 20-01-2008

I'm having trouble flashing my NEC ND-3500AG
drive in a USB enclosure.

This is probably due to faulty hardware, I'm also having trouble reading most of the DVDs and CDs I have. But it's still able to performe burning.

Anyway, binflash v1.24 is able to dump the device's firmware but not write it back nor set, read or clean the booktype.

And the latest version of binflash v1.43 is only able to scan for devices (successfully).

Probably the drive is broken, but why isn't v1.43 able to dump the firmware as v1.24 was?

This happens on Mac OS X.4 (powerpc), I can only test this drive on PPC or Sparc64 (ide, no usb). But there are no binaries for sparc64 available.

Thanks for your time and this nice tool.

**Liggy** · 21-01-2008

Quote:

Originally Posted by mpata

This is probably due to faulty hardware, I'm also having trouble reading most of the DVDs and CDs I have. But it's still able to performe burning.

I guess it's probably due to your USB enclosure. Try flashing your drive attached directly to an IDE channel without the enclosure.

Quote:

Originally Posted by mpata

Probably the drive is broken, but why isn't v1.43 able to dump the firmware as v1.24 was?

You USB enclosure seems to prevent several command from being sent to the drive. Between 1.24 and 1.43 several changes were made. Probably also some checks were introduced that your USB enclosure doesn't understand.

Quote:

Originally Posted by mpata

I can only test this drive on PPC or Sparc64 (ide, no usb). But there are no binaries for sparc64 available.

And I don't think there will ever be. First of all I know nothing about how to identify devices or send commands on Solaris (I assume that's your OS for the Sparc64 CPUs). I currently rely on the fPLSCSI library for accessing drives and all platforms supported in this library are supported by Binflash. Second issue is that I don't have a compiler for these platforms available. While I have access to several sparc64 servers at work, neither of them has the compiler package installed as far as I know.

mpata · 21-01-2008

Quote:

Originally Posted by Liggy

I guess it's probably due to your USB enclosure. Try flashing your drive attached directly to an IDE channel without the enclosure.

You USB enclosure seems to prevent several command from being sent to the drive. Between 1.24 and 1.43 several changes were made. Probably also some checks were introduced that your USB enclosure doesn't understand.

And I don't think there will ever be. First of all I know nothing about how to identify devices or send commands on Solaris (I assume that's your OS for the Sparc64 CPUs). I currently rely on the fPLSCSI library for accessing drives and all platforms supported in this library are supported by Binflash. Second issue is that I don't have a compiler for these platforms available. While I have access to several sparc64 servers at work, neither of them has the compiler package installed as far as I know.

On Sparc64 I've OpenBSD installed, if you want remote access to it there's no problem.

Anyway I'll see if I can have access to a firewire enclosure, so I can reflash the drive.

thanks!

**Liggy** · 21-01-2008

Quote:

Originally Posted by mpata

On Sparc64 I've OpenBSD installed, if you want remote access to it there's no problem.

Thanks for the offer, but I still don't know how to get device access there and I don't intend to add this to fPLSCSI. I might however add it to my own device library later.

Quote:

Originally Posted by mpata

Anyway I'll see if I can have access to a firewire enclosure, so I can reflash the drive.

You might end up with the same problem again. It usually depends on the enclosure. Some will work and some won't. You might even be lucky and find another USB enclosure that allows flashing your drive. So the best solution is always to attach to an IDE controller instead of using an enclosure.

GeBo · 23-01-2008

Hello all,

I just purchased an Optiarc 7173A. When trying to burn Ricoh (Gold) DVD+R, the burner starts and directly finishes the job, which left me with 2 coasters...
I also tried a DVD+RW. A small file like Quintian_0.6.9.x.iso did get burned (didn't verify it though, but I got no errors), but a larger file like opensource_dvd70.iso or ubuntu-7.10-desktop-i386.iso failed with an error. Writefailure or so...
I tried to burn using Nautilus and also with K3B, but both times without succes.

K3B debug info shows:

Quote:

System
-----------------------
K3b Version: 1.0.4

KDE Version: 3.5.8
QT Version: 3.3.7
Kernel: 2.6.22-14-386
Devices
-----------------------
LITE-ON DVD SOHD-167T 9S19 (/dev/hdc, ) [CD-ROM, DVD-ROM] [DVD-ROM, CD-ROM] [Geen]

Optiarc DVD RW AD-7173A 1-02 (/dev/hdd, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R sequentieel, DVD-R Dual Layer sequentieel, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW met beperkte overschrijving, DVD-RW sequentieel, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Beperkt overschrijven, Layer Jump]
Burned media
-----------------------
DVD+RW

Used versions
-----------------------
growisofs: 7.0.1

growisofs
-----------------------
WARNING: /dev/hdd already carries isofs!
About to execute 'builtin_dd if=/dev/fd/0 of=/dev/hdd obs=32k seek=0'
/dev/hdd: "Current Write Speed" is 4.1x1352KBps.
0/729608192 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/729608192 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/729608192 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/729608192 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
0/729608192 ( 0.0%) @0x, remaining ??:?? RBU 100.4% UBU 0.0%
17498112/729608192 ( 2.4%) @3.8x, remaining 15:36 RBU 100.0% UBU 3.2%
37191680/729608192 ( 5.1%) @4.3x, remaining 8:22 RBU 100.0% UBU 87.1%
56295424/729608192 ( 7.7%) @4.1x, remaining 5:58 RBU 100.0% UBU 45.2%
72974336/729608192 (10.0%) @3.6x, remaining 5:05 RBU 100.0% UBU 29.0%
92602368/729608192 (12.7%) @4.3x, remaining 4:14 RBU 100.0% UBU 71.0%
:-[ WRITE@LBA=cf90h failed with SK=4h/ASC=08h/ACQ=03h]: Input/output error
:-( write failed: Input/output error
/dev/hdd: flushing cache
/dev/hdd: stopping de-icing
/dev/hdd: writing lead-out

growisofs command:
-----------------------
/usr/bin/X11/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:356254 -speed=4 -use-the-force-luke=bufsize:32m

Then I thought I try to flash the device with Necflash. But when using necflash -v -scan I get:
List of supported devices:
Trying to query device /dev/hdc
device LITE-ON DVD SOHD-167T 9S19 unsupported
Trying to query device /dev/hdd
device Optiarc DVD RW AD-7173A 1-02 unsupported
No supported devices found

But in the list of supported drives the Optiarc AD-7173A is clearly mentioned.

I am running Ubuntu Linux.

Has anyone have a clue?

Thanks in advance.
GeBo
The Netherlands

GeBo · 23-01-2008

Thanks to Liggy's post somewhere else in this forum, I just found out I need root privileges to flash the drive.

GeBo · 23-01-2008

Hmmm, I get an error when flashing the drive.

Quote:

sudo ./necflash -v -flash -s 103bt_orig.bin /dev/hdd
Binflash - NEC version - (C) by Liggy and Herrie
Visit http://binflash.cdfreaks.com

Identified drive: 29
Detected drive from Firmware: 29

Entering safe mode
Sending firmware to drive at 0x030000
Sending firmware to drive at 0x038000
Sending firmware to drive at 0x040000
Sending firmware to drive at 0x048000
Sending firmware to drive at 0x050000
Sending firmware to drive at 0x058000
...

...
Sending firmware to drive at 0x1d0000
Sending firmware to drive at 0x1d8000
Sending firmware to drive at 0x1e0000
Sending firmware to drive at 0x1e8000
Sending checksum 1cf5 to drive
Error while flashing firmware
Error submitting checksum

I already rebooted, but the second time flashing I get the same error...

Any idea?

kriko · 23-01-2008

@GeBo: disable dma on your drive first.

GeBo · 24-01-2008

Quote:

Originally Posted by kriko

@GeBo: disable dma on your drive first.

kriko, you're the best!

I would have never figured that out myself.

Device : /dev/hdd
Vendor : Optiarc
Model : DVD RW AD-7173A
Firmware : 1-03

**Liggy** · 24-01-2008

Quote:

Originally Posted by GeBo

kriko, you're the best!

I would have never figured that out myself.

A search using Google would have helped too

GeBo · 24-01-2008

Quote:

Originally Posted by Liggy

A search using Google would have helped too

Touché!

You know, Liggy, I normally always check Google. I even consider Google my friend

. You are right of course. But at that time, I didn't thought about it...

B.t.w. Liggy, as I 'speak with you' now, my compliments to you (and Dee's and Harry's) for your continuous work on firmware. Years ago I used your firmware on drives and today you lads are still the main source to search for. Still going strong!

GeBo · 26-01-2008

I gave up.

I went back to my 'old' 3520AW, which never let me down. But I thought "newer is better". Boy, was I wrong!

I wrote a mail to Optiarc last week with the following question:

Quote:

Recently I bought a 7173A burner (with Labelflash). However I can't find
any software to use Labelflash on my computer. I've tried the software
on http://labelflash.jp/enjoy/softdl.html, but that is ONLY for Windows.
I am running Ubuntu Linux.

I also tried the Lightscribe software from LaCie, which is available
under Linux, but I found out that Labelflash and Lightscribe are
incompatible...

Please help me to be able to use Labelflash.

This is the response I got:

Quote:

Dear Customer,
thanks for your inquiry.
Unfortunately, we do not design software for our drives. Our firmwares are
also only compatible with windows. Please contact Ubuntu for appropriate
label flash software. And also note that lightscribe an labelflash are two
quite different technologies. Software for lightscribe may not be
compatible with labelflash drives.

Kind Regards,
Support team

Yes, you've read it right: "Our firmwares are also only compatible with windows." To me that sounded bull. But when I got whole week nothing but coasters, I'm starting to believe it...

Again, thanks anyone for your time and effort to help.

B.t.w. I downloaded the latest firmware (3.07) for my 3520AW. Of course the one Liggy made

, with bitsetting capabilities.

Best regards,
Gert

crazycat · 26-01-2008

well, let back to Nec BinFlash

CConstantine · 01-02-2008

Hello,
I flashed my NEC ND-4570A drive
with Sony DW-D150A firmware (version 12/01/07)

it works,
but i can't flash it back to NEC firmware

Identified drive: 24
Detected drive from Firmware: 24

Entering safe mode
Sending firmware to drive at 0x010000
Error sending firmware to drive
Error while flashing firmware

Any comments?

**Liggy** · 01-02-2008

Since flashing is done with the bootcode firmware and that one wasn't changed when you flashed the D150A firmware, there must be a different reason for this procedure to fail. Did you try rebooting your PC or try flashing in a different PC?

CConstantine · 01-02-2008

Yes, I tryed to flash after some rebootings.
the results are the same.
I didnt try to flash device on another PC,
I will try it tomorrow.

I can dump firmware but can't flash

You note, that there is a difference if I flashed
firmware with a bootloader or not. Right?
I really don't know that.
I downloaded Sony DW-D150A firmware there

http://liggydee.cdfreaks.com/page/en/NEC-ND-4570A/
http://liggydee.cdfreaks.com/disclai..._rpc1.zip.html

CConstantine · 02-02-2008

I flashed it back in Windows Safe Mode

Sorry for stupied questions

10-01-2008	#1201
crazycat MyCE Rookie Join Date: Jul 2006 Posts: 45	Re: Binflash - NEC/Optiarc firmware flasher and dumper binflash 1.40+ for win32 (console and gui) not work with FrogASPI (NeroASPI still work, WinXP-SP2). Drive switch to safe mode and next 'Error dumping firmware' and drive switch to Normal-mode. P.S. binflash 1.39 work fine with FrogASPI.

10-01-2008	#1202
kriko New on Forum Join Date: Mar 2005 Posts: 13	Re: Binflash - NEC/Optiarc firmware flasher and dumper Is it possible to use binflash in linux with new PATA stack? I tried, however with no success (works with old IDE drivers, just had to disable DMA).

11-01-2008	#1206
Liggy Senior Administrator Join Date: Apr 2002 Location: Monkey Island Posts: 8,209	Re: Binflash - NEC/Optiarc firmware flasher and dumper I just did some debugging with my NEC ND-7551A and I must say that FrogASPI is definitely broken in some way. In order to retrieve the current bootcode version I send an Inquiry to the drive. The firmware version was reported to be 1-02. This means I have to switch to the bootcode in order to retrieve the version. The corresponding command was sent successfully (LED blinking) but a subsequent Inquiry still gives 1-02 instead of 0.04 that it should be (and is with Nero ASPI or SPTX). Since I added some bootcode version checks in Binflash 1.41 this could actually mean that some functionality is broken with FrogASPI but these fixes need to be made in FrogASPI not Binflash. __________________ You need to flash or dump your NEC DVD burner firmwares on your Mac, Windows, DOS or Linux machine? Just try Binflash. Visit Liggy's and Dee's Optiarc and NEC firmware and tools page for all kind of information about NEC and Optiarc drives. Unrequested PM about drive problems will not be answered!

20-01-2008	#1209
mpata New on Forum Join Date: Jan 2008 Posts: 2	Re: Binflash - NEC/Optiarc firmware flasher and dumper I'm having trouble flashing my NEC ND-3500AG drive in a USB enclosure. This is probably due to faulty hardware, I'm also having trouble reading most of the DVDs and CDs I have. But it's still able to performe burning. Anyway, binflash v1.24 is able to dump the device's firmware but not write it back nor set, read or clean the booktype. And the latest version of binflash v1.43 is only able to scan for devices (successfully). Probably the drive is broken, but why isn't v1.43 able to dump the firmware as v1.24 was? This happens on Mac OS X.4 (powerpc), I can only test this drive on PPC or Sparc64 (ide, no usb). But there are no binaries for sparc64 available. Thanks for your time and this nice tool.

23-01-2008	#1214
GeBo New on Forum Join Date: Dec 2005 Location: Enschede, The Netherlands Posts: 6	Re: Binflash - NEC/Optiarc firmware flasher and dumper Thanks to Liggy's post somewhere else in this forum, I just found out I need root privileges to flash the drive.

23-01-2008	#1216
kriko New on Forum Join Date: Mar 2005 Posts: 13	Re: Binflash - NEC/Optiarc firmware flasher and dumper @GeBo: disable dma on your drive first.

26-01-2008	#1221
crazycat MyCE Rookie Join Date: Jul 2006 Posts: 45	Re: Binflash - NEC/Optiarc firmware flasher and dumper well, let back to Nec BinFlash

01-02-2008	#1222
CConstantine New on Forum Join Date: Oct 2003 Posts: 3	Re: Binflash - NEC/Optiarc firmware flasher and dumper Hello, I flashed my NEC ND-4570A drive with Sony DW-D150A firmware (version 12/01/07) it works, but i can't flash it back to NEC firmware Identified drive: 24 Detected drive from Firmware: 24 Entering safe mode Sending firmware to drive at 0x010000 Error sending firmware to drive Error while flashing firmware Any comments?

01-02-2008	#1223
Liggy Senior Administrator Join Date: Apr 2002 Location: Monkey Island Posts: 8,209	Re: Binflash - NEC/Optiarc firmware flasher and dumper Since flashing is done with the bootcode firmware and that one wasn't changed when you flashed the D150A firmware, there must be a different reason for this procedure to fail. Did you try rebooting your PC or try flashing in a different PC? __________________ You need to flash or dump your NEC DVD burner firmwares on your Mac, Windows, DOS or Linux machine? Just try Binflash. Visit Liggy's and Dee's Optiarc and NEC firmware and tools page for all kind of information about NEC and Optiarc drives. Unrequested PM about drive problems will not be answered!

01-02-2008	#1224
CConstantine New on Forum Join Date: Oct 2003 Posts: 3	Re: Binflash - NEC/Optiarc firmware flasher and dumper Yes, I tryed to flash after some rebootings. the results are the same. I didnt try to flash device on another PC, I will try it tomorrow. I can dump firmware but can't flash You note, that there is a difference if I flashed firmware with a bootloader or not. Right? I really don't know that. I downloaded Sony DW-D150A firmware there http://liggydee.cdfreaks.com/page/en/NEC-ND-4570A/ http://liggydee.cdfreaks.com/disclai..._rpc1.zip.html

02-02-2008	#1225
CConstantine New on Forum Join Date: Oct 2003 Posts: 3	Re: Binflash - NEC/Optiarc firmware flasher and dumper I flashed it back in Windows Safe Mode Sorry for stupied questions

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SONY NEC Optiarc AD-7170 S-ATA Firmware 1.01	Vizor	NEC / Optiarc Writer	20	01-08-2007 20:42
Problem Binflash 1.39 mit Optiarc DVD RW AD-7173A	Fehlerteufel	German: General Chat	8	29-07-2007 12:14
Nec binflash	haveacigar	CD, DVD and Blu-ray Writers	6	19-04-2006 23:34
Flasher needed for Quickee Firmware (Nec 3500)	alexankius	NEC / Optiarc Writer	3	08-12-2004 07:56
flashing difference between official NEC flasher and binflash, etc?	enigma7	NEC / Optiarc Writer	0	07-11-2004 23:12

This page was also found with these words
, 0x3034 firmware optiarc, 1.b2 acer 5500s firmware oem, 1.nc firmware download, 1.z2 7261, 107v2b5 readme, 29 - 3036 firmware, 5515 bios update , 5540 dvd driver vista dell write 64 download, 7591a firmware