USBLD 0.2 works with drive, but get yellow screen with OPL 7.0

[Cloke]

I've been getting super frustrated with trying to figure how to get games up and running so hoping someone may have an answer. I purchased an iomega 320GB portable external drive to store PS2 games on. The problem is, it does not seem to want to run Open PS2 Loader via Swap Magic.

I have been successful at using the swap method with my drive, using my PSP to boot up the loader then swapping in my hard drive via USB. The problem is in not being able to load games with Open PS2 Loader. I am using 0.7, and get the yellow screen after I start up the game (NiGHTS for instance). I made sure that the drive is defragmented with Power Defrag.

However, when using the old version of USB Loader 0.2 and swapping in my drive, the game works fine. I also tried 0.3 and the Loader displays a message than seems to crash after I press Up + L1?

Any advice on what could be causing my yellow screen problems? It seems this is with newer versions of OPL... Is there any benefit to using 0.7 over 0.2, mainly speed/video playback increases?

[SP193]

Any advice on what could be causing my yellow screen problems? It seems this is with newer versions of OPL...

OPL is simply incompatible with your drive (Like mine).

Is there any benefit to using 0.7 over 0.2, mainly speed/video playback increases?

Yes, and because 0.7 has far better game compatibility over 0.2.

Not to mention that 0.2 isn't really OPL, but a hacked USBAdvance.

[loki7777]

At this time i think all should be ok with newer usb hdd. With rev 317 we get

cdvdman: be compatible with mass storage having sector size of 512, 1024, 2048

Of course it is beta OPL not this version that is public available.

[izdubar]

Jimmi has commited lately a few enhancement to support USB drive with 1024/2048/4096 sector size.

That should help a lot compatibility with newer USB drive (as now manufacturer use 4096 as default, instead of 512 before).

But you have to compile the latest revision on the source repository to verify this with you drive, and then report us your result.

[SP193]

Jimmi has commited lately a few enhancement to support USB drive with 1024/2048/4096 sector size.

That should help a lot compatibility with newer USB drive (as now manufacturer use 4096 as default, instead of 512 before).

But you have to compile the latest revision on the source repository to verify this with you drive, and then report us your result.

I think that I'll try 0.7 too.... but as far as I know OPL's problem is NOT because of non-512 byte sector sizes (But some kind of USB device initialization/control issue).

It also fails on my normal 512-byte sector 80GB Hitachi when I insert it into one of my cheap cases.

The developers should check the initialization functions, and check if the USB SCSI command structures are all correct (And congruent with the original USBHDFSD's). I found that that the structures in the USB SCSI command functions (In a normal USBHDFSD module) did not have the fields of the CBW structure filled in according to the order as declared... so when the OPL devs declared the structures as static, they may have made errors (I did too, but I've fixed them).

PS2ESDL works with that case, and the improved performance in video playback over OPL is quite noticeable (Different methods of reading + sector caching + streaming read ahead).

So you can see that the case does work with my PS2 (But OPL has a software issue).
In a nutshell, some USB devices don't like the way OPL handles them, and doesn't feed the PS2 with the requested data properly.

If they want the latest PS2ESDL v0.726A's source to see what are the differences, I won't mind sharing.
I've posted this issue on OPL's forums a few months ago, but nobody paid any attention (White/yellow screen for all games).

[izdubar]

I think that I'll try 0.7 too.... but as far as I know OPL's problem is NOT because of non-512 byte sector sizes (But some kind of USB device initialization/control issue).

I think that there is not one single issue, but several. I just try to sum up what I understood from various discussions:

• One of them is due to some delay required by some USB device or controller (SATA to USB).
• Another one was the support for 512 physical sector size only (and not for 1024/2048/4096).
• And maybe there is another one, related to what you explain with command block wrapper (However the in-game OPL only load the usbd.irx, and does nothing with usbdfshd)

The developers should check the initialization functions, and check if the USB SCSI command structures are all correct (And congruent with the original USBHDFSD's). I found that that the structures in the USB SCSI command functions (In a normal USBHDFSD module) did not have the fields of the CBW structure filled in according to the order as declared... so when the OPL devs declared the structures as static, they may have made errors (I did too, but I've fixed them).

If they want the latest PS2ESDL v0.726A's source to see what are the differences, I won't mind sharing.

Like you don't have time to look into OPL code to check and fix the error, I think Jimmi is quite busy on other topic, and couldn't review PS2ESDL whole code either ... so as you seems to know quite precisely what could be a problem, you could probably explain here with more details what you suspect bad (if not already enough in your previous post) ?

[jimmikaelkael]

I think that I'll try 0.7 too.... but as far as I know OPL's problem is NOT because of non-512 byte sector sizes (But some kind of USB device initialization/control issue).

You are wrong:
OPL IOP core was not compatible with 1024, 2048, and 4096 bytes sectors size.
I know that very well since in OPL 0.7, the sector size of 512 is simply hardcoded in the usb IOP core.

It 'should' work with these sector size in the latest revisions.

If it was some initalization problems, you should be stucked at OPL USB drive init (that is, in the GUI), and not on a yellow screen after the ingame IOP reset.

[GillBert]

This subject is very interesting... So, I've made some basic research about "4K Advanced Format" and I'd like to share it here:

http://www.bit-tech.net/hardware/sto...t-hard-disks/1

http://www.anandtech.com/show/2888



[ ]'s.

[SP193]

* One of them is due to some delay required by some USB device or controller (SATA to USB).
* Another one was the support for 512 physical sector size only (and not for 1024/2048/4096).
* And maybe there is another one, related to what you explain with command block wrapper (However the in-game OPL only load the usbd.irx, and does nothing with usbdfshd)

I thought so too - but I don't have time to look at OPL's code to find the bug. It seems as if some USB devices don't like the way OPL handles it - and somehow doesn't respond properly.

These were the same the possibilities I've thought of, except for the 1st point (Which isn't a valid cause of failure for my device).

It 'should' work with these sector size in the latest revisions.

If it was some initalization problems, you should be stucked at OPL USB drive init (that is, in the GUI), and not on a yellow screen after the ingame IOP reset.

OK, since you're here - I think that we should discuss this to fix OPL....

I think that you're right - Even the older OPL builds that used the normal USBHDFSD modules don't work (White screen). Only those that use USBAdvance's USB and CDVDMAN modules work. I've forgotten that.

OPL IOP core was not compatible with 1024, 2048, and 4096 bytes sectors size.
I know that very well since in OPL 0.7, the sector size of 512 is simply hardcoded in the usb IOP core.

The drive I use has 512-byte sectors, and freezes at a white screen for pre-0.6 OPL builds, and I get a yellow screen for all post-v0.5 versions.

All versions of OPL work with the same HDD when it's inserted into another case (Of a different brand).

OPL does intilize the USB device manually (Calls the mass_stor_configureNextDevice() function after calling InitUSB()) right?

I haven't seen the v0.6 source in detail, but I know that you've integrated USBHDFSD into OPL, and have removed all redundant functions (Plus have declared the SCSI command CBW structures as static structures).

That case that doesn't work with OPL works with uLE, and PS2ESDL (Even after customizing it to use a OPL-like system to save memory).

This issue has always been around since OPL v0.41.

Like you don't have time to look into OPL code to check and fix the error, I think Jimmi is quite busy on other topic, and couldn't review PS2ESDL whole code either ... so as you seems to know quite precisely what could be a problem, you could probably explain here with more details what you suspect bad (if not already enough in your previous post) ?

Sorry if I'm vague here, but I'm now busy, and can't leave a very detailed explanation (Plus I didn't study the OPL code in detail, but I know that there is a problem somewhere).

The old version of PS2ESDL on this forum does not have any "useful" code related to this issue.

[Cloke]

At this time i think all should be ok with newer usb hdd. With rev 317 we get

Of course it is beta OPL not this version that is public available.

Dzieki za informacje. Is there a way I may be able to acquire the beta release or the revision anywhere? Any help would be appreciated...