Oops looks like I never opened that merge request for these files back when I aggregated them. It's way overdue but here we go :)
drivers
The WinXP 32bit driver has been retrieved from a Pop'n SD cab.
The WinXP 64bit driver has been retrieved from Cypress website.
The other OS drivers are the same cyusb3.sys as for iidx, but with a small modification :
ezusb.dll is looking for the device by its name (therefore Cypress FX2LP No EEPROM Device has been renamed to Cypress EZ-USB FX2LP - EEPROM missing in the .inf files)
testing
I plugged the IO2 on a win10 computer (made a custom usb cable for it) and managed to run the game without IO hooks.
Note: modding the inf invalidates the driver signature, win10 requires to reboot in "disabled Driver Signature Enforcement" mode to install.
firmware
The firmware binary has been reconstructed by sniffing USB packets during the game boot.
Unfortunately I haven't been able to dump it from BT5 code as originally intended for comparison, but there is very little chance I'd end up with a different file, given the test results.
testing
The binary file has been flashed with ezusb2-tool.exe and it results in the correct KONAMI POPN device enumerating, with the same usb descriptors as when the game itself flashes its firmware.
In GitLab by @shtokopep on May 3, 2021, 03:10
_Merges popn -> master_
Oops looks like I never opened that merge request for these files back when I aggregated them. It's way overdue but here we go :)
## drivers
The WinXP 32bit driver has been retrieved from a Pop'n SD cab.
The WinXP 64bit driver has been retrieved from Cypress website.
The other OS drivers are the same cyusb3.sys as for iidx, but with a small modification :
- `ezusb.dll` is looking for the device by its name (therefore `Cypress FX2LP No EEPROM Device` has been renamed to `Cypress EZ-USB FX2LP - EEPROM missing` in the .inf files)
#### testing
I plugged the IO2 on a win10 computer (made a custom usb cable for it) and managed to run the game without IO hooks.
**Note:** modding the inf invalidates the driver signature, win10 requires to reboot in "disabled Driver Signature Enforcement" mode to install.
## firmware
The firmware binary has been reconstructed by sniffing USB packets during the game boot.
Unfortunately I haven't been able to dump it from BT5 code as originally intended for comparison, but there is very little chance I'd end up with a different file, given the test results.
#### testing
The binary file has been flashed with `ezusb2-tool.exe` and it results in the correct `KONAMI POPN` device enumerating, with the same usb descriptors as when the game itself flashes its firmware.
Oops looks like I never opened that merge request for these files back when I aggregated them. It's way overdue but here we go
Oops^2, I didn't notice/remember or simply forgot you opened this a year ago... I am really sorry for that.
+1 and thanks for lifting everything into this repository.
> Oops looks like I never opened that merge request for these files back when I aggregated them. It's way overdue but here we go
Oops^2, I didn't notice/remember or simply forgot you opened this a year ago... I am really sorry for that.
+1 and thanks for lifting everything into this repository.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In GitLab by @shtokopep on May 3, 2021, 03:10
Merges popn -> master
Oops looks like I never opened that merge request for these files back when I aggregated them. It's way overdue but here we go :)
drivers
The WinXP 32bit driver has been retrieved from a Pop'n SD cab.
The WinXP 64bit driver has been retrieved from Cypress website.
The other OS drivers are the same cyusb3.sys as for iidx, but with a small modification :
ezusb.dllis looking for the device by its name (thereforeCypress FX2LP No EEPROM Devicehas been renamed toCypress EZ-USB FX2LP - EEPROM missingin the .inf files)testing
I plugged the IO2 on a win10 computer (made a custom usb cable for it) and managed to run the game without IO hooks.
Note: modding the inf invalidates the driver signature, win10 requires to reboot in "disabled Driver Signature Enforcement" mode to install.
firmware
The firmware binary has been reconstructed by sniffing USB packets during the game boot.
Unfortunately I haven't been able to dump it from BT5 code as originally intended for comparison, but there is very little chance I'd end up with a different file, given the test results.
testing
The binary file has been flashed with
ezusb2-tool.exeand it results in the correctKONAMI POPNdevice enumerating, with the same usb descriptors as when the game itself flashes its firmware.Oops^2, I didn't notice/remember or simply forgot you opened this a year ago... I am really sorry for that.
+1 and thanks for lifting everything into this repository.
approved this merge request
added 22 commits
djhackers:masterCompare with previous version