PS2 Open PS2 Loader v1.1.0

[jolek]

I also made a tests with slim console.
Results are the same, although at the end of a test when I press "start" to exit to OSDSYSY,
Kingstone still "works" (no BSOD). Intenso still refuse to work.

Kingston SLIM result.log:

FreeUsbd v.0.1.2
USB HDD FileSystem Driver v1.6
USBHDFSD: registerDriver=0
USBHDFSD: probe: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: bNumInterfaces 1
USBHDFSD: bInterfaceClass 8 bInterfaceSubClass 6 bInterfaceProtocol 50
USBHDFSD: connect: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: register Input endpoint id =1 addr=81 packetSize=64
USBHDFSD: register Output endpoint id =2 addr=02 packetSize=64
USBHDFSD: connect ok: epI=1, epO=2
Listing contents of mass0:/...
USBHDFSD: configuring devices...
USBHDFSD: setting configuration controlEp=0, confNum=1
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50
USBHDFSD: setting interface controlEp=0, interface=0 altSetting=0
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50
USBHDFSD: mass_stor_warmup
USBHDFSD: callback: res 0, bytes 1, arg 1f7bc0
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD: cbw_scsi_inquiry
USBHDFSD: callback: res 0, bytes 31, arg 1f7bd8
USBHDFSD: callback: res 0, bytes 13, arg 1f7ba8
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Vendor: Kingston
USBHDFSD: Product: DataTraveler 2.0
USBHDFSD: Revision: 1.00
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bd8
USBHDFSD: callback: res 0, bytes 13, arg 1f7ba8
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_capacity
USBHDFSD: callback: res 0, bytes 31, arg 1f7bd8
USBHDFSD: callback: res 0, bytes 13, arg 1f7ba8
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: sectorSize 512 maxLBA 3987455
USBHDFSD: cbw_scsi_read_sector - 0x00000000 fab00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b78
USBHDFSD: callback: res 0, bytes 13, arg 1f7b48
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: boot signature 55 AA
USBHDFSD: cbw_scsi_read_sector - 0x00000038 fab00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b50
USBHDFSD: callback: res 0, bytes 13, arg 1f7b20
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Fat type 32 Id FAT32
USBHDFSD: cbw_scsi_read_sector - 0x00000058 fab00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7a18
USBHDFSD: callback: res 0, bytes 13, arg 1f79e8
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00001eb0 fab00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7aa8
USBHDFSD: callback: res 0, bytes 13, arg 1f7a78
USBHDFSD: bulk csw result: 0, csw.status: 0
ART
CD
CFG
CFG-DEV
CHT
USBHDFSD: cbw_scsi_read_sector - 0x00001eb8 fab00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7820
USBHDFSD: callback: res 0, bytes 13, arg 1f77f0
USBHDFSD: bulk csw result: 0, csw.status: 0
DVD
THM
VMC

Intenso SLIM result.log:

FreeUsbd v.0.1.2
USB HDD FileSystem Driver v1.6
USBHDFSD: registerDriver=0
USBHDFSD: probe: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: bNumInterfaces 1
USBHDFSD: bInterfaceClass 8 bInterfaceSubClass 6 bInterfaceProtocol 50
USBHDFSD: connect: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: register Output endpoint id =1 addr=01 packetSize=64
USBHDFSD: register Input endpoint id =2 addr=82 packetSize=64
USBHDFSD: connect ok: epI=2, epO=1
Listing contents of mass0:/...
USBHDFSD: configuring devices...
USBHDFSD: setting configuration controlEp=0, confNum=1
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50
USBHDFSD: setting interface controlEp=0, interface=0 altSetting=0
USBHDFSD: callback: res 4, bytes 0, arg 1f7c50
USBHDFSD: Error - sending set_interface 4
Unable to open mass0:/ - -19

To be add. I always have problems with this old Kingston, no matter it was SLIM or PHAT.
Anyway, it definitely works better with SLIM, games at least boot (although sometimes it also refuses to boot ).
It also don't work with some modern PC with windows 10.

With Intenso, it's a different story.
I bought this flash drive no too long ago.
All devices (like PC, TV, PS3) needs to give him some time to initiate.
It's quite fast flash drive though.

So, to sum up.
These not fully compatible devices with OPL\other PS2 homebrew, have also some problems with other devices\platforms.
So far the most compatible device is... PS3, I never had any problems with any device.

I think that when the device is compatible there should be no problems,
at least not with OPL.

BTW I also remember that I've problems when I was saving compatibility setting (e.g mode 2=ON), then I want to run game.
OPL freezes at some debug color.
But I don't remember that it was fixed, or just some devices still have problems with it.
Maybe when I have some time, I can test it.

 

[sp193]

Please help to confirm that the new fix helped the affected devices: https://www.sendspace.com/file/1n2um0
Related github issue: https://github.com/ps2dev/ps2sdk/issues/79

Have we got any debug version of the OPL to find the other problem with the hanging on the last debug screen?

Here is a custom version that may do that: https://www.sendspace.com/file/2zpe2f
OPL's IP address is determined from the UI. If you have not used SMB before, you will need to enter your network setting into OPL. However, it is not required to start SMB support, from what I remember.

Once OPL has started, you can start PLANETTY and point it to the PS2's IP address, as before.

I also made a tests with slim console.
Results are the same, although at the end of a test when I press "start" to exit to OSDSYSY,
Kingstone still "works" (no BSOD). Intenso still refuse to work.

About the test crashing, that is unintended.

To be add. I always have problems with this old Kingston, no matter it was SLIM or PHAT.
Anyway, it definitely works better with SLIM, games at least boot (although sometimes it also refuses to boot ).
It also don't work with some modern PC with windows 10.

This is very strange. I always thought it would be made to work (well) with Windows.
Anyway, thanks for sharing your logs.

 

[jolek]

Please help to confirm that the new fix helped the affected devices: https://www.sendspace.com/file/1n2um0
Related github issue: https://github.com/ps2dev/ps2sdk/issues/79

USB test from 161018 seems to helps Intenso.
Intrenso slim 161018 result.log:

FreeUsbd v.0.1.2
USB HDD FileSystem Driver v1.6
USBHDFSD: registerDriver=0 
USBHDFSD: probe: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: bNumInterfaces 1
USBHDFSD: bInterfaceClass 8 bInterfaceSubClass 6 bInterfaceProtocol 50
USBHDFSD: connect: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: register Output endpoint id =1 addr=01 packetSize=64
USBHDFSD: register Input endpoint id =2 addr=82 packetSize=64
USBHDFSD: connect ok: epI=2, epO=1 
Listing contents of mass0:/...
USBHDFSD: configuring devices... 
USBHDFSD: setting configuration controlEp=0, confNum=1 
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50 
USBHDFSD: setting interface controlEp=0, interface=0 altSetting=0
USBHDFSD: callback: res 4, bytes 0, arg 1f7c50 
USBHDFSD: Error - sending set_interface 4
USBHDFSD: callback: res 4, bytes 0, arg 1f7c58 
USBHDFSD: Error - sending clear halt 4
USBHDFSD: callback: res 0, bytes 0, arg 1f7c58 
USBHDFSD: mass_stor_warmup
USBHDFSD: callback: res 0, bytes 1, arg 1f7bd0 
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD: cbw_scsi_inquiry
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Vendor: Intenso 
Product: Alu Line       
Revision: 8.05
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc8 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b98 
USBHDFSD: bulk csw result: 0, csw.status: 1
USBHDFSD: cbw_scsi_test_unit_ready 1
USBHDFSD: cbw_scsi_request_sense
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc8 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b98 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_capacity
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: sectorSize 512 maxLBA 123699199
USBHDFSD: cbw_scsi_read_sector - 0x00000000 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b58 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b28 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: boot signature 55 AA
USBHDFSD: cbw_scsi_read_sector - 0x00000800 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b30 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b00 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Fat type 32 Id FAT32   
USBHDFSD: cbw_scsi_read_sector - 0x00000820 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f79f8 
USBHDFSD: callback: res 0, bytes 13, arg 1f79c8 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00004000 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f79f8 
USBHDFSD: callback: res 0, bytes 13, arg 1f79c8 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00004290 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f79f8 
USBHDFSD: callback: res 0, bytes 13, arg 1f79c8 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e08 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7a88 
USBHDFSD: callback: res 0, bytes 13, arg 1f7a58 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e10 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e18 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e20 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e28 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e30 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e38 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e40 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00007e48 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e08 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e10 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e18 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e20 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e28 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e30 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e38 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e40 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x06fd2e48 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x074edf48 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x074edf50 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
*
ART
CD
*
CFG-DEV
CHT
*
DVD
*
THM
*
VMC
*
USBHDFSD: cbw_scsi_read_sector - 0x074edf58 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
*

* - I've censured some irrelevant stuff (folders\files).

kongston 161018 result.log:

FreeUsbd v.0.1.2
USB HDD FileSystem Driver v1.6
USBHDFSD: registerDriver=0 
USBHDFSD: probe: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: bNumInterfaces 1
USBHDFSD: bInterfaceClass 8 bInterfaceSubClass 6 bInterfaceProtocol 50
USBHDFSD: connect: devId=2
USBHDFSD: mass_stor_findDevice devId 2
USBHDFSD: register Input endpoint id =1 addr=81 packetSize=64
USBHDFSD: register Output endpoint id =2 addr=02 packetSize=64
USBHDFSD: connect ok: epI=1, epO=2 
Listing contents of mass0:/...
USBHDFSD: configuring devices... 
USBHDFSD: setting configuration controlEp=0, confNum=1 
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50 
USBHDFSD: setting interface controlEp=0, interface=0 altSetting=0
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50 
USBHDFSD: mass_stor_warmup
USBHDFSD: callback: res 0, bytes 1, arg 1f7bd0 
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD: cbw_scsi_inquiry
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Vendor: Kingston
Product: DataTraveler 2.0
Revision: 1.00
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc8 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b98 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_capacity
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: sectorSize 512 maxLBA 3987455
USBHDFSD: cbw_scsi_read_sector - 0x00000000 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b58 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b28 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: boot signature 55 AA
USBHDFSD: cbw_scsi_read_sector - 0x00000038 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b30 
USBHDFSD: callback: res 0, bytes 13, arg 1f7b00 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Fat type 32 Id FAT32   
USBHDFSD: cbw_scsi_read_sector - 0x00000058 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f79f8 
USBHDFSD: callback: res 0, bytes 13, arg 1f79c8 
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00001eb0 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7a88 
USBHDFSD: callback: res 0, bytes 13, arg 1f7a58 
USBHDFSD: bulk csw result: 0, csw.status: 0
ART
CD
CFG
CFG-DEV
CHT
USBHDFSD: cbw_scsi_read_sector - 0x00001eb8 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7800 
USBHDFSD: callback: res 0, bytes 13, arg 1f77d0 
USBHDFSD: bulk csw result: 0, csw.status: 0
DVD
THM
VMC

Both flash drives allows to exit\boot OSDSYS after I hit "start" button to exit.
Tested only with SCPH-77004.

 

[Agrippa]

Please help to confirm that the new fix helped the affected devices: https://www.sendspace.com/file/1n2um0
Related github issue: https://github.com/ps2dev/ps2sdk/issues/79

Yes, it's listing the contents of the Flash Disk now. Here's the log:

FreeUsbd v.0.1.2
USB HDD FileSystem Driver v1.6
USBHDFSD: registerDriver=0
USBHDFSD: probe: devId=1
USBHDFSD: mass_stor_findDevice devId 1
USBHDFSD: bNumInterfaces 1
USBHDFSD: bInterfaceClass 8 bInterfaceSubClass 6 bInterfaceProtocol 50
USBHDFSD: connect: devId=1
USBHDFSD: mass_stor_findDevice devId 1
USBHDFSD: register Output endpoint id =1 addr=01 packetSize=64
USBHDFSD: register Input endpoint id =2 addr=82 packetSize=64
USBHDFSD: connect ok: epI=2, epO=1
Listing contents of mass0:/...
USBHDFSD: configuring devices...
USBHDFSD: setting configuration controlEp=0, confNum=1
USBHDFSD: callback: res 0, bytes 0, arg 1f7c50
USBHDFSD: setting interface controlEp=0, interface=0 altSetting=0
USBHDFSD: callback: res 4, bytes 0, arg 1f7c50
USBHDFSD: Error - sending set_interface 4
USBHDFSD: callback: res 4, bytes 0, arg 1f7c58
USBHDFSD: Error - sending clear halt 4
USBHDFSD: callback: res 0, bytes 0, arg 1f7c58
USBHDFSD: mass_stor_warmup
USBHDFSD: callback: res 0, bytes 1, arg 1f7bd0
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD: cbw_scsi_inquiry
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD:   Vendor: Generic
     Product: Flash Disk
     Revision: 8.07
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc8
USBHDFSD: callback: res 0, bytes 13, arg 1f7b98
USBHDFSD: bulk csw result: 0, csw.status: 1
USBHDFSD: cbw_scsi_test_unit_ready 1
USBHDFSD: cbw_scsi_request_sense
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_test_unit_ready
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc8
USBHDFSD: callback: res 0, bytes 13, arg 1f7b98
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_capacity
USBHDFSD: callback: res 0, bytes 31, arg 1f7bc0
USBHDFSD: callback: res 0, bytes 13, arg 1f7b90
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: sectorSize 512 maxLBA 15974399
USBHDFSD: cbw_scsi_read_sector - 0x00000000 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b58
USBHDFSD: callback: res 0, bytes 13, arg 1f7b28
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: boot signature 55 AA
USBHDFSD: cbw_scsi_read_sector - 0x00000800 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7b30
USBHDFSD: callback: res 0, bytes 13, arg 1f7b00
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: Fat type 32 Id FAT32
USBHDFSD: cbw_scsi_read_sector - 0x00000e60 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f79f8
USBHDFSD: callback: res 0, bytes 13, arg 1f79c8
USBHDFSD: bulk csw result: 0, csw.status: 0
USBHDFSD: cbw_scsi_read_sector - 0x00008800 fae00 0x0008
USBHDFSD: callback: res 0, bytes 31, arg 1f7a88
USBHDFSD: callback: res 0, bytes 13, arg 1f7a58
USBHDFSD: bulk csw result: 0, csw.status: 0
   CFG-DEV
   DVD
   THM
   ART
   CD
   VMC
   CHT
   usbtest.elf

Here is a custom version that may do that: https://www.sendspace.com/file/2zpe2f
OPL's IP address is determined from the UI. If you have not used SMB before, you will need to enter your network setting into OPL. However, it is not required to start SMB support, from what I remember.

Once OPL has started, you can start PLANETTY and point it to the PS2's IP address, as before.

Here's the log. But I don't think if something interesting is there:

UDPTTY loaded!
KPRTTY enabled!
ioptrap starts.
initializing host
Thread id: 100a851
host: mounted
IOP cmd: Starting thread
IOP cmd thread started
Naplink thread started
 - PS2 Side application -
Waiting for connection
IOP cmd: Server Thread Started.
IOP cmd: Listening
USBSUPPORT Init
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD:   Vendor: ST1000LM
     Product: 024 HN-M101MBB
     Revision: 0000
USBHDFSD: sectorSize 4096 maxLBA 244190645
USBHDFSD: boot signature 55 AA
USBHDFSD: Fat type 32 Id FAT32
THEMES Trying to set again theme: <OPL>
Failed to load bitmap: mass0:ART/SCES_507.60_BG.bmp
Failed to load bitmap: mass0:ART/SCES_507.60_ICO.bmp
Failed to load bitmap: mass0:ART/SCES_532.47_BG.bmp
Failed to load bitmap: mass0:ART/SCES_532.47_ICO.bmp
CONFIG No file mass0:CFG-DEV/SCES_532.47.cfg.
DVD detected.
USBSUPPORT CleanUp
SYSTEM LaunchLoaderElf loading modules
SYSTEM IRX 1 address start: 0x00097050 end: 0x00098DED
SYSTEM IRX 2 address start: 0x00098DF0 end: 0x000A5150
SYSTEM IRX 3 address start: 0x000A5150 end: 0x000A55ED
SYSTEM IRX 4 address start: 0x000A55F0 end: 0x000AC0A5
SYSTEM IRX 6 address start: 0x000AC0B0 end: 0x000AE4B1
SYSTEM IRX 5 address start: 0x000AE4C0 end: 0x000BF991
SYSTEM IRX 10 address start: 0x000BF9A0 end: 0x000C0775
SYSTEM IRX 11 address start: 0x000C0780 end: 0x000C1985
SYSTEM IRX STORAGE 0x00097000 - 0x000C1990
Preparing GSM...
FNTSYS End

 

[sp193]

Is that all? Once you select a game to boot, it should still continue printing more messages.

Thanks for confirming that the fix to USBHDFSD has allowed devices that have only the default interface setting, to start working again. I shall also incorporate the commit(s) in OPL, at a later time.

 

[Agrippa]

Yes, that's all what it's printed till the moment of hanging up.

 

[TnA]

Great! An even higher device-compatibility is always appreciated!

 

[sp193]

Yes, that's all what it's printed till the moment of hanging up.

That's unfortunate, but maybe the TTY system is now defunct.

It appears that your HDD enclosure reports a sector size of 4096. This means that special handling is required, when either the first address of a request is not aligned with the device's LBAs. Or if the last sector is not aligned with the device's LBAs.

I think I see a possible mistake in how data is read. Previously, data was read in blocks of 4KB, for one reason or another.
This restriction was lifted, but the loop for reading data in blocks was not actually removed since it was also required for special care of devices with 4KB sectors.
However, since the new changes caused the loop to only iterate once,with the assumption that all requested sectors can be read in 1 go, this does not work for devices with 4KB sectors because it is not possible to read half a sector without help from the software.

Please try this: https://www.sendspace.com/file/wfb9nq
This is a normal build of OPL. There will be no log messages to gather, so please run it normally and let us know if it helped.

Great! An even higher device-compatibility is always appreciated!

Even higher? Nah, not exactly. We're trying to regain some "lost ground", from June 8th...

 

[TnA]

Oh, well then I hope after 'regaining some lost ground(s)', that these tests also help to make some more devices more reliable and compatible!

 

[jolek]

Here is a custom version that may do that: https://www.sendspace.com/file/2zpe2f

Here is my log from debug OPL with Intenso.
intrenso OPL slim 161018 result_1.log:

USBHDFSD: connect: devId=2
USBHDFSD: Error - sending set_interface 4
USBHDFSD: usb_bulk_get_max_lun 0
USBHDFSD: Vendor: Intenso 
Product: Alu Line       
Revision: 8.05
USBHDFSD: cbw_scsi_test_unit_ready 1
USBHDFSD: sectorSize 512 maxLBA 123699199
USBHDFSD: boot signature 55 AA
USBHDFSD: Fat type 32 Id FAT32   
THEMES Trying to set again theme: <OPL>
Failed to load bitmap: mass0:ART/SLES_505.04_BG.bmp
Failed to load bitmap: mass0:ART/SLES_505.04_ICO.bmp
Failed to load bitmap: mass0:ART/SLES_501.26_BG.bmp
Failed to load bitmap: mass0:ART/SLES_501.26_ICO.bmp
CONFIG No file mass0:CFG-DEV/SLES_505.04.cfg.
DVD detected.
USBSUPPORT CleanUp
SYSTEM LaunchLoaderElf loading modules
SYSTEM IRX 1 address start: 0x00097050 end: 0x00098DED
SYSTEM IRX 2 address start: 0x00098DF0 end: 0x000A5150
SYSTEM IRX 3 address start: 0x000A5150 end: 0x000A55ED
SYSTEM IRX 4 address start: 0x000A55F0 end: 0x000AC0A5
SYSTEM IRX 6 address start: 0x000AC0B0 end: 0x000AE4B1
SYSTEM IRX 5 address start: 0x000AE4C0 end: 0x000BF991
SYSTEM IRX 10 address start: 0x000BF9A0 end: 0x000C0775
SYSTEM IRX 11 address start: 0x000C0780 end: 0x000C1985
SYSTEM IRX STORAGE 0x00097000 - 0x000C1990
Preparing GSM...
FNTSYS End

intrenso OPL slim 161018 result_2.log:

Failed to load bitmap: mass0:ART/SLES_501.26_BG.bmp
Failed to load bitmap: mass0:ART/SLES_501.26_ICO.bmp
CONFIG No file mass0:CFG-DEV/SLES_501.26.cfg.
DVD detected.
USBSUPPORT CleanUp
SYSTEM LaunchLoaderElf loading modules
SYSTEM IRX 1 address start: 0x00097050 end: 0x00098DED
SYSTEM IRX 2 address start: 0x00098DF0 end: 0x000A5150
SYSTEM IRX 3 address start: 0x000A5150 end: 0x000A55ED
SYSTEM IRX 4 address start: 0x000A55F0 end: 0x000AC0A5
SYSTEM IRX 6 address start: 0x000AC0B0 end: 0x000AE4B1
SYSTEM IRX 5 address start: 0x000AE4C0 end: 0x000BF991
SYSTEM IRX 10 address start: 0x000BF9A0 end: 0x000C0775
SYSTEM IRX 11 address start: 0x000C0780 end: 0x000C1985
SYSTEM IRX STORAGE 0x00097000 - 0x000C1990
Preparing GSM...
FNTSYS End

With this debug version games boot normally.
Tested only Intenso in SCPH-77004.

Please try this: https://www.sendspace.com/file/wfb9nq

With this version, once I was stuck at green debug color.
Another time everything was fine.

I haven't made too many tests, because I've got only two games (CD games BTW ) on that flash-drive.

Still Intenso & SCPH-77004.

I can make more tests In this weekend, if they are needed.

 

[Agrippa]

Please try this: https://www.sendspace.com/file/wfb9nq
This is a normal build of OPL. There will be no log messages to gather, so please run it normally and let us know if it helped.

Now, it is freezing on the green screen.

 

[sp193]

I can make more tests In this weekend, if they are needed.

Thanks, but I think it is fine.
If it is about trying to make this device more compatible, I don't think it is within our control, if it is a problem that only sometimes happens. Such a thing might not be a logic issue, but some timing problem.
The USB specification determines how long a device may take to do some things, like how long it has to respond after a reset or to comply with a request. So there isn't supposed to be a "need more time" kind of problem.

Here is my log from debug OPL with Intenso.
intrenso OPL slim 161018 result_1.log:

intrenso OPL slim 161018 result_2.log:

With this debug version games boot normally.
Tested only Intenso in SCPH-77004.

With this version, once I was stuck at green debug color.
Another time everything was fine.

I haven't made too many tests, because I've got only two games (CD games BTW ) on that flash-drive.

Still Intenso & SCPH-77004.

Now, it is freezing on the green screen.

:/
Please try this file instead: https://www.sendspace.com/file/8buiu5
I think this should work.

 

[jolek]

Please try this file instead: https://www.sendspace.com/file/8buiu5

With Intenso only once I've BSOD before "launching" PS2 logo.
After this one fail, everything seems to work as it should.
No matter If I plug flash-drive at cold boot, or when I launch OPL.
Tried with SCPH-77004 & 50004.

Today I also tried Kingston in SCPH-50004 with OPNPS2LD-181018.elf...
As I mentioned before.

My PHAT PS2 hates it (have many problems with it).

With Half-Life it'll freeze at dark-yellow (?) debug screen.
With Quake III: Revolution it won't even launch PS2 logo.

I got used to problems with Kingsone, but maybe somehow Intenso will work as it should.

 

[Agrippa]

:/
Please try this file instead: https://www.sendspace.com/file/8buiu5
I think this should work.

Unfortunately, still hangs up on the green screen.

Today I also tried Kingston in SCPH-50004 with OPNPS2LD-181018.elf...

These tests are for 4k sector drives. If you don't have one, you don't need to test.

 

[sp193]

How strange. So @jolek, am I right to say that this build allowed you to boot games on devices with normal sector sizes? Or is it just another defective build?
It is a test meant for devices with 4KB sectors, but coincidentally there is now some problem with making it work at all.

If it can work with some devices, I think I know what is different now. I forgot to check if there are no sectors to read (which is possible if one CD/DVD sector is requested on a 4KB/sector device). I will update this post again tonight, once I have an updated version made.

 

[jolek]

How strange. So @jolek, am I right to say that this build allowed you to boot games on devices with normal sector sizes? Or is it just another defective build?
It is a test meant for devices with 4KB sectors, but coincidentally there is now some problem with making it work at all.

Only once Inteso in SCPH-50004 with OPNPS2LD-181017.elf at cold boot don't want to fully launch.
This loading icon was constantly showing:

and after some time, nothing happens (no game list, neither for HDD or USB).
Like OPL was trying to "launch" the device, but it can't.

With OPNPS2LD-181018.elf only once OPL stuck at green debug screen (tested with Intenso & SCPH-50004).

So with Intenso, OPNPS2LD-181017.elf and OPNPS2LD-181018.elf is working.
Although sometime, I don't know why, something can go wrong.

Maybe the results will be more accurate if I only insert my disk after OPL launch,
not sometimes at cold boot.

Spoiler: Kingston

This flash-drive sometimes is not showing game list (only "working" icon is showing).
It freezes at green debug color or before PS2 logo should launch.

 

[sp193]

Unfortunately, still hangs up on the green screen.

Okay, so thrice is a charm right? Here you go: https://www.sendspace.com/file/a09wnd
If it still doesn't work, then I'll try to test this on my PS2 over the weekend.

Only once Inteso in SCPH-50004 with OPNPS2LD-181017.elf at cold boot don't want to fully launch.
This loading icon was constantly showing:
and after some time, nothing happens (no game list, neither for HDD or USB).
Like OPL was trying to "launch" the device, but it can't.

With OPNPS2LD-181018.elf only once OPL stuck at green debug screen (tested with Intenso & SCPH-50004).

So with Intenso, OPNPS2LD-181017.elf and OPNPS2LD-181018.elf is working.

Thank you for sharing your findings.

Spoiler: Kingston

This flash-drive sometimes is not showing game list (only "working" icon is showing).
It freezes at green debug color or before PS2 logo should launch.

Although sometime, I don't know why, something can go wrong.

Maybe the results will be more accurate if I only insert my disk after OPL launch,
not sometimes at cold boot.

It should not happen, but I have no answer to this.

 

[sandungas]

Im not sure if what im going to say could be useful, but i know a bit that intenso pendrives and there is something you mentioned that is making me doubt if you are having some mistake

There are at least 3 intenso "series"
The "alu line" (that appears in one of your logs) have a external aluminium body, this is different than the photo posted by jolek
The one from jolek photo is USB 2.0 (plastic body with dark grey color)
And there is other intenso USB 3.0 (with backward compatibility with 2.0) with a plastic body exactly like the jolek photo, but in light grey


-------------
Edit: never minds, my mistake, it seems they are calling "alu line" to the ones with plastic body (cheaters)
The one with aluminium body i was talking about is this one, i think is USB 2.0:

This is the one jolek have, is USB 2.0

And this one is USB 3.0 (but the controller can change to USB 2.0 mode if you connect it to a device that only supports USB 2.0)

 

[Agrippa]

Okay, so thrice is a charm right?

Right man, you've got it. ICO loads without a problem. WRC: Rally Evolved hanged on the Evolution Studios logo with the HDD blinking every few seconds. So I've fired up MODE1+MODE2 combined and it passed successfully. I've never tested the game further. I wonder if it's hardware or software issue, since in earlier OPL versions I didn't have to turn on compatibility modes.

I must admit, that with the new USB drivers, there is a significant improvement in loading times.

Thank you very much for your support!

 

[sp193]

Im not sure if what im going to say could be useful, but i know a bit that intenso pendrives and there is something you mentioned that is making me doubt if you are having some mistake

There are at least 3 intenso "series"
The "alu line" (that appears in one of your logs) have a external aluminium body, this is different than the photo posted by jolek
The one from jolek photo is USB 2.0 (plastic body with dark grey color)
And there is other intenso USB 3.0 (with backward compatibility with 2.0) with a plastic body exactly like the jolek photo, but in light grey

Edit: never minds, my mistake, it seems they are calling "alu line" to the ones with plastic body (cheaters)
The one with aluminium body i was talking about is this one, i think is USB 2.0:

Perhaps they just reused the controllers. Or it's even the same PCB inside. Just whether you want to fork out more money for a shiny case or not.

Right man, you've got it. ICO loads without a problem. WRC: Rally Evolved hanged on the Evolution Studios logo with the HDD blinking every few seconds. So I've fired up MODE1+MODE2 combined and it passed successfully. I've never tested the game further. I wonder if it's hardware or software issue, since in earlier OPL versions I didn't have to turn on compatibility modes.

I must admit, that with the new USB drivers, there is a significant improvement in loading times.

Thank you very much for your support!

Many thanks to you and @jolek. I have issued a pull request to the Ifcaro repository and will be gradually updating my software as well.
Updates to FMCB should also come soon.

@jolek: If you still have problems with USB devices, you can try to play with the test program to see whether the actual problem can be captured.
If there is some procedure that we are lacking in compliance with the USB specification, some adjustments can be made to how we do things in USBHDFSD. However, if it is just due to USBD getting stuck (perhaps due to the hardware getting stuck), then it cannot really be fixed without help from Sony or people who can actually work with USB.