DMS Hack works, but...

[syscon7]

I didn't get the expected results in the patch log file.
I got the following:

Code: [Select]

No such file or directory
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0001 03a0
Unverified!
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02db eb00
Unverified!
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02f7 eb00
Unverified!
Segmentation fault

When I use a DMS (either original or unsigned new one), the radio reverts back to a radio station on a power cycle. Pushing the CD button gets me back to the Phatbox and music. I have the radio and Phatbox running on my test bench.

I hacked another box and that one was verified on completion. That works normally in the car with an unsigned DMS.

The Phatbox on the bench is one I got from a seller on eBay. Possible flaky box?

Any comments on the unverified results in the patch log?

syscon7

[sbingner]

You had to corrupt your ramdisk, but you never completed the hack after doing so.

[syscon7]

I thought I'd run the hack procedure a couple of times after I corrupted the ramdisk.sig file but I don't think it took. I just tried running it one more time and this time it worked. I'm getting all verified. I've got one more Phatbox to modify so I'll see how it works on that one. Can I start the hack procedure with a corrupted ramdisk.sig? Or should I start it with a good ramdisk.sig, then rerun the hack with a corrupt ramdisk.sig?

I may have run it the first time with a corrupt ramdisk.sig...

syscon7

[sbingner]

if you read the patches you'll see this:

Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350

now, what do you think that tells you about the state your ramdisk.sig will need to be in for your system to boot and run the patcher?

[syscon7]

Duh...

Sorry 'bout that. When all else fails, RTFM...

syscon7