The Firmware Page

After you flash with 2.04, reboot the case then read with "2.14"......

If it still does not flash you may have to reconcile yourself with an unflashable chip, which I suspect you may have.

List of Flashable Chips:
http://club.cdfreaks.com/showthread.php ... post801831

The ASPI I refer to is 4.60 version

Have you got a mirror for that .PNG file? thanks

I've attached the image to dishinit's post above...

Flash EEPROM in my enclosures are..

PMC Flash
PM37LV512-70JC

Not in that list so would it be possible to purchase replacement PCB boards with the newer flashable EEPROM's? or anyone know of up to date enclosures that are flash upgradeable? (UK)

ta

its quite annoying to have the enclosure and for it to just be scrap (

Don't worry. Mine also same with yours. I flashed to v160 firmware with old ROMWriter, and then upgrade to the latest v185 firmware using the new ROMWriter.
My enclosure bought from http://www.u-maxtec.com directly from China.

ansarpro,
Just confirming, You used Rom UpDater 2.04 for your 1st firmware upgrade to 09/07/2004....v160, and then rebooted and confirmed update using 2.14 Rom UpDater?
Then used 2.2RSC2 Rom UpDater to go to 10/09/2004....v185
and Could you post a screen shot of what your Rom Read is? or just enter as text for us to see.
I would like to add your flash chip to successful flash list as it is not on official Prolific list.

I have a PL-3507 based ext Hard Drive Case from CompUSA.com. SKU 306103.

It has an AMTEL AT49BV512 Chip. When I flash with 2.0.4 it says flash successfull but when I reboot case and read with 2.1.4 it shows

FW ver.2004.04.07.106

Gotta love it I cant return cause I cant find my receipt to bring back to the store. It has hosed 2 harddrives. One minute they were working the next I got H:\ is not Accessible The file or Directory is corrupted and Unreadable. Luckily I tested with a 10gb and a 4.3gb so I am not out a 200gb.

Any thoughts?? Should I contact prolific?

thx
Eric

[quote="ehask"]I have a PL-3507 based ext Hard Drive Case from CompUSA.com. SKU 306103.

It has an AMTEL AT49BV512 Chip. When I flash with 2.0.4 it says flash successfull but when I reboot case and read with 2.1.4 it shows

FW ver.2004.04.07.106

Gotta love it I cant return cause I cant find my receipt to bring back to the store. It has hosed 2 harddrives. One minute they were working the next I got H:\ is not Accessible The file or Directory is corrupted and Unreadable. Luckily I tested with a 10gb and a 4.3gb so I am not out a 200gb.

Any thoughts?? Should I contact prolific?

thx

Whoops! double post

Hi,
This looks like the same problem I have posted here: http://forum.rpc1.org/viewtopic.php?t=31559

OH wow, I forgot about this one....Two Versions of the ATMEL Chip...
Sci Fi, Did you have any success hacking the chip?

Do you have specs on the amtel? I am a Electronics tech by trade but work for Verizon COmmunications now. I will pull the board and investigate the pin 31 scenario

Eric

I see pin31 is hooked directly to the PL-3507C chip around pin 17 or 18 hard to tell. If pin 31 of the Amtel is open(not connected) will that allow flashing??

Eric

Ummm

Hee hee

On one of my external cases the chip is identified by the firmware updater as Atmel BV512. The chip itself has PL3507-03433C silk screened on top. So much for that.

Today I used ROMWriter220RS32.exe to perform an update to the 042204 firmware that was currently installed and operating. I did NOT do the version to version updating as mentioned in previous posts.

Without problem or hesitation and using usb, the update went just swell. I then safely removed the device from windows, powered down the external case for a short time and fired it back up. I disconnected both the usb cable as well as the power cord for this event.

The firmware now reads as 2004.11.09.185 as is working fine.

Guys, keep in mind that the case must be shut down (powered off) as well as being disconnected from the computer for the firmware upgrade to "take".

I believe you will find the Atmel BV512 Flash somewhere in the vicinity of your PL-3507. Think of the PL-3507 as the CPU and Atmel as the harddrive for the cpu. It holds the code that lets the cpu function properly.


I dont think its going to be as easy I as I thought to write enable the Atmel in my case. It looks like pin31 needs to be at different states for normal operation and WE. I may take a shot at cutting pin 31 pin from the board to test as I can easily resolder if it doesnt work.

Eric
Rackspeed Web Hosting

I've tried updating the frimware on my Plumax to 0907 and 110904 and still my drive is not recognised. I also tried setting my cable to both master and slave with no success.. This is driving me crazy. What could I be doing wrong?

Thanks
Shawn

Shawn,
Beach-hobo posted in CDFreaks this response to someone else who was having drive recognition problems with 1394 devices assuming you are using Win XP SP1/2:

"I would recommend that with everything attached (after you receive the beep), that using the Windows Device Manager uninstall all the 1394a devices.

Power down the computer and case. Power up the computer and let windows redetect the 1394a parts first. Then power on the case and let windows redetect the DVD drive 1394a connection. Check with the device manager that nothing is flagged with a yellow X.

I have had to do this before with either or both a DVD firmware update or a case firmware update. For some reason windows sometimes needs a little help.

Good Luck...
P.S. With the PL-3507 - the drive MUST be MASTER..."

Let us know how it goes.

Hey everyone. I'm yet another victim of the partition corruption problem.
Firmware 2004.04.07.106 here.

I have a few questions that I was hoping someone could answer for me:

1)About what you said about setting the drive to master....
There are two options and I'm unsure as to which to go with.
No jumper = master/single
jumper in middle = master with slave present ( and there is no slave)

What do you recommend?
At the time of my first corruption the jumper was set to Cable Select.

2) Also, anyone know of a easy way to reproduce the partition corruption problem? I'm going to flash the firmware and try again, but last time it took 5 days of intensive use before I got the error.

3)I have a 200gb HDD in the enclosure, any idea if it will help to split it into 2 partitions instead of one?

4)Also, does it make a difference if its FAT32 or NTFS?

5) Optimize for performance or quick removal?


Many thanks

PS: I managed to flash to the latest firmware direclty using the 2.2.0 Rom Writer. Btw, I found people complaining about the same problems with this chipsets on Macs as well....

lewcid,
A response to your questions;

1) Make sure you are at 11/09/2004 v185 firmware on your Pl-3507 chipset.
Set Drive to master/single, run BusTrace Stress test (see next answer)
If problem, then try Master with Slave

2) BusTrace Delayed Write Stress Test here:
http://www.bustrace.com/downloads/free_utilities.htm

3) I have 250GB, NTFS, no partitions, no problems.

4) Format NTFS unless you have need for Fat 32.

5) I am optimized for performance.

Hi there,

Thanks for your reply.

I am now at the 11/09/2004 v185 firmware, optimed for performance. So far so good, but its only been a few hours.

'Unfortunately' for me the BusTrace Stress test passed with flying colors before and after the firmware upgrade. So, I have no idea if my problems are gone or just waiting to happen again. Took 5 days the first time. Any other ideas on how to test?

Before the crash, I had one 200GB NTFS partition. To see if it would help, I'v e now split it into two equal FAT32 partitions. I know that NTFS is preferrable, but do you know if one or the other is more likely to cause problems? I might run PQMagic overnight and convert back to NTFS.

It's nice to be able to confer with someone else who has been through this. Thanks again.