News:

I have updated the spam detection on registrations, and as such I am enabling new users.  If we have spam, I will change it back to by approval.

Main Menu

I've got a problem patching!

Started by John1981, February 14, 2006, 04:35:19 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

John1981

Hey Guys,

Im new here. I followed the How To guide to upgrading my DMS drive.
Stupidly the first time I attempted it. I didn't copy across the log folder or backup folder to my DMS. However it didnt seem to cause any problems. I then went through the guide again and correctly followed it to the letter. However I don't get a file called bootload.log I get two files called patch and phatpatch.

The contents of patch says:

"backing up drive signature 2048+0 records in 2048+0 records out backup drive sig complete starting patch backing up drive signature 2048+0 records in 2048+0 records out backup drive sig complete
starting patch backing up drive signature 2048+0 records in 2048+0 records out backup drive sig complete starting patch backing up drive signature"

The contents of phatpatch says:

"PhatPatch v0.2 -bushing first 2 words of flash=c102 0025 writing auto-id command (AA, 55, 90) Flash chip reports manufacturer id=c102, device id=0025 Resetting flash. Testing patch locations: Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1] Expected: 0033 1a00    Actual: 0033 1a00 Match! Programming... Waiting... Waiting... Waiting........................"

And it says waiting about 200 times.

Any ideas?

John

sbingner

just try running it a few times, sometimes it locks it up instead of going on to the next patch... but it always programs it properly.  I'll patch eventually ;)

John1981

Hi,

I tried leaving it on for 45 mins today. I plugged it into my PC and checked it. Still no bootload.log and phatpatch.log is over 6mb in size and has waiting repeating over and over several thousand times.

Any more thoughts?

John

judb

You have to shut the keg off and verify that the lights are off before turning it back on around 9 times for it to be patched fully because sometimes it locks up...

copy a file like rc.sig and rename it bootload.log and that file should start getting updated.. you have to create the file that way before it gets written to.

John1981

judb I did what you said. I copied rc.sig and renamed it bootload.log. I went out to the car, plugged in the DMS, turned the ignition on went to access playlist 1. Stuck it on pause. Waited 60 seconds, turned the ignition off and waited for the red light to go out. Then turned the ignition on again and went through the process 9 times.
Came back inside, and this time I cant open phatpatch.log, windows says its corrupted. There is also no contents in bootload.log.

John1981

Ignore what my last message. I just realised it has worked. Thanks.

John1981

Its all looking good. Ive uploaded some tracks onto the DMS, will go test tomorrow morning.

John1981

ok I went through all the steps, I didnt have any plugins to backup. I copied over the 1mb file using DD. I created two partitions on the drive as required.

However when I use the recovery CD it threw up an error with the partitions, and asked me if I wanted to fix. I selected Yes. Next thing I know it skipped it?
It did everything else OK, I added some music using the software. But the headunit is now not seeing the DMS. I think its something to do with the partition table.

Any thoughts???

judb

You ran the recoery disk and told it to repartition and reformat but it didn't?  that should fix all your issues.

the other thing that COULD be causing it would show up in the bootload.log.  you should create that file by copying another file (like ramdisk.sig and renaming it bootload.log) and post the contents of that.