I am trying to get Rootage running on my cab (D01 windows 10) using BT5.30
Was able to flash v1 firmware successfully (?), but I get a "fpga download failed" error when trying to flash v2
In trying to use v1, iidxiotest only recognizes keys 1-14 (with a delay) and nothing else. Addtionally P1 Start, P2 Start, VEFX, and Effector ar stuck at "1".
Running the game using iidxio-ezusb.dll results in the game constantly advancing screens (due to the Start puttons being actively "pressed")
Expected behavior
ezusb-boot successfully flashes all v2 firmware, iidxiotest successfully confirms all necessary inputs.
Current behavior
Using ezusb-boot to flash v2 firmware:
ezusb-iidx-fpga: [v2] Reset failed
ezusb-iidx-fpga-flash: Downloading FPGA firmware failed
Using v1 firmware, iidxiotest shows D01 not working properly.
Detailed Description
Steps to reproduce
Possible solution
Context (Environment)
Bemanitools version(s) affected
BT 5.30
Supplemental Tools 1.2
Game(s) and version(s) affected
IIDX26
Log output
See attachment.
Configuration files
See attachment.
Command line arguments
APIs used
iidxio-ezusb.dll
OS version
Windows 10 Pro Build 18362.19h1_release.190318-1201 (Test Mode)
Hardware specs
CPU: AMD Pro A10-8770E R7 2.8GHz
RAM: 8GB DDR4 2400MHz
GPU: AMD Radeon R7 Graphics
Controllers/IO: D01
In GitLab by @hvzero1 on Jun 14, 2020, 02:51
## Summary
I am trying to get Rootage running on my cab (D01 windows 10) using BT5.30
- Was able to flash v1 firmware successfully (?), but I get a "fpga download failed" error when trying to flash v2
- In trying to use v1, iidxiotest only recognizes keys 1-14 (with a delay) and nothing else. Addtionally P1 Start, P2 Start, VEFX, and Effector ar stuck at "1".
- Running the game using iidxio-ezusb.dll results in the game constantly advancing screens (due to the Start puttons being actively "pressed")
## Expected behavior
ezusb-boot successfully flashes all v2 firmware, iidxiotest successfully confirms all necessary inputs.
## Current behavior
Using ezusb-boot to flash v2 firmware:
ezusb-iidx-fpga: [v2] Reset failed
ezusb-iidx-fpga-flash: Downloading FPGA firmware failed
Using v1 firmware, iidxiotest shows D01 not working properly.
## Detailed Description
<!--- Provide a detailed description of the issue. Include links to screenshots or videos if necessary -->
## Steps to reproduce
1.
2.
3.
4.
## Possible solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
## Context (Environment)
### Bemanitools version(s) affected
BT 5.30
Supplemental Tools 1.2
### Game(s) and version(s) affected
IIDX26
### Log output
See attachment.
<!--- Provide log output as attachment. Make sure to censor sensitive data like PCBIDs or device names if necessary -->
### Configuration files
See attachment.
<!--- Provide any configuration files that you used, e.g. iidxhook-XX.conf. Make sure to censor sensitive data like
PCBIDs -->
### Command line arguments
<!--- Provide how you run the game from the command line, e.g. which gamestart.bat you used and any additional arguments
that you provided to it. Also provide the contents of the gamestart.bat you used if you altered it. -->
### APIs used
* iidxio-ezusb.dll
### OS version
Windows 10 Pro Build 18362.19h1_release.190318-1201 (Test Mode)
### Hardware specs
* CPU: AMD Pro A10-8770E R7 2.8GHz
* RAM: 8GB DDR4 2400MHz
* GPU: AMD Radeon R7 Graphics
* Controllers/IO: D01
I don't know if the C02 firmware is compatible with D01 IO boards. If there are issues flashing the base or FPGA firmware, it is expected that the hardware is not working correctly. Do you happen to know the differences of D01 compared to C02 boards?
I don't know if the C02 firmware is compatible with D01 IO boards. If there are issues flashing the base or FPGA firmware, it is expected that the hardware is not working correctly. Do you happen to know the differences of D01 compared to C02 boards?
I'm actually unsure about that. I was operating under the assumption that I had a C02 since it was originally a Gold Cabinet. I reconnected my Sinobuz PCB and confirmed it was D01 on the startup screen. I'll try to search around again to see what I can find.
In GitLab by @hvzero1 on Jun 14, 2020, 17:16
I'm actually unsure about that. I was operating under the assumption that I had a C02 since it was originally a Gold Cabinet. I reconnected my Sinobuz PCB and confirmed it was D01 on the startup screen. I'll try to search around again to see what I can find.
The D01 board is somewhat similar to the C02 with the exception that it is not entirely backwards compatible like the C02 board is. C02 boards can upgrade any twinkle based cabinet but D01 cannot. These were shipped starting 10th Style up to DistorteD before being replaced with IO2 starting with Gold.
When you boot up Sinobuz, the FPGA check shows "D01" (instead of "C02") I assume?
The D01 board is somewhat similar to the C02 with the exception that it is not entirely backwards compatible like the C02 board is. C02 boards can upgrade any twinkle based cabinet but D01 cannot. These were shipped starting 10th Style up to DistorteD before being replaced with IO2 starting with Gold.
When you boot up Sinobuz, the FPGA check shows "D01" (instead of "C02") I assume?
would getting D01 firmware, and following the same steps theoretically work?
would using Sinobuz to flash prior to running Rootage with BT5 work?
lastly, when I bought The Sinobuz PCB a while back, they also sent a C02. Does it make sense to switch over?
Thanks
In GitLab by @hvzero1 on Jun 15, 2020, 19:11
A few more questions.
- would getting D01 firmware, and following the same steps theoretically work?
- would using Sinobuz to flash prior to running Rootage with BT5 work?
- lastly, when I bought The Sinobuz PCB a while back, they also sent a C02. Does it make sense to switch over?
Thanks
would getting D01 firmware, and following the same steps theoretically work?
You need the D01 base firmware and the "firmware" that is written to the FPGA which seems to be different as the way turntables and other stuff is wired up is very different to a C02 board/cabinet.
would using Sinobuz to flash prior to running Rootage with BT5 work?
Yeah, that would do the trick to get the firmwares flashed. However, I don't know if the usb protocol is 100% compatible with the one used for C02 boards. Might be worth a try to let the game initialize the board, then try another game with bemanitools and the iidxio-ezusb.dll and the iidxio-test tool included with BT5.
lastly, when I bought The Sinobuz PCB a while back, they also sent a C02. Does it make sense to switch over?
I think your cabinet wiring will not be entirely compatible. C02 cabinets have two main interfaces that go into the IO board: a 40 pin connector (like the one used on IDE drives) and a RJ45 connector (like on ethernet cables).
D01 cabinets also have the 40 pin connector but multiple other cables for turntables, top unit lights and the front button panel with the 16seg board.
> would getting D01 firmware, and following the same steps theoretically work?
You need the D01 base firmware and the "firmware" that is written to the FPGA which seems to be different as the way turntables and other stuff is wired up is very different to a C02 board/cabinet.
> would using Sinobuz to flash prior to running Rootage with BT5 work?
Yeah, that would do the trick to get the firmwares flashed. However, I don't know if the usb protocol is 100% compatible with the one used for C02 boards. Might be worth a try to let the game initialize the board, then try another game with bemanitools and the iidxio-ezusb.dll and the iidxio-test tool included with BT5.
> lastly, when I bought The Sinobuz PCB a while back, they also sent a C02. Does it make sense to switch over?
I think your cabinet wiring will not be entirely compatible. C02 cabinets have two main interfaces that go into the IO board: a 40 pin connector (like the one used on IDE drives) and a RJ45 connector (like on ethernet cables).
D01 cabinets also have the 40 pin connector but multiple other cables for turntables, top unit lights and the front button panel with the 16seg board.
Confirming that running Sinobuz first to initialize the IO works. iidxtest works correctly, and Rootage uses everything correctly. So I'm guessing I'd need to track down the D01 firmware (if thats even a thing) to have this process be more seamless for a dedicated setup.
In GitLab by @hvzero1 on Jun 16, 2020, 04:07
Confirming that running Sinobuz first to initialize the IO works. iidxtest works correctly, and Rootage uses everything correctly. So I'm guessing I'd need to track down the D01 firmware (if thats even a thing) to have this process be more seamless for a dedicated setup.
I derived a task from this issue since we now have a clear goal on how to fix this.
Task #55 follows up accordingly with steps to get the firmware.
Therefore, I will close this issue and further discussion on the feature to be implemented takes place in issue #55.
I derived a task from this issue since we now have a clear goal on how to fix this.
Task #55 follows up accordingly with steps to get the firmware.
Therefore, I will close this issue and further discussion on the feature to be implemented takes place in issue #55.
@hvzero1 I dumped the D01 FPGA firmware
Can you please flash this when initializing your D01 IO instead of the fpga.bin from the supplements package and check if everything's working fine?
@hvzero1 I dumped the [D01 FPGA firmware](https://dev.s-ul.net/djhackers/bemanitools/uploads/9f00c62ebb190d28687d7d66c66fb103/fpga-d01.bin)
Can you please flash this when initializing your D01 IO instead of the `fpga.bin` from the supplements package and check if everything's working fine?
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 @hvzero1 on Jun 14, 2020, 02:51
Summary
I am trying to get Rootage running on my cab (D01 windows 10) using BT5.30
Expected behavior
ezusb-boot successfully flashes all v2 firmware, iidxiotest successfully confirms all necessary inputs.
Current behavior
Using ezusb-boot to flash v2 firmware:
ezusb-iidx-fpga: [v2] Reset failed
ezusb-iidx-fpga-flash: Downloading FPGA firmware failed
Using v1 firmware, iidxiotest shows D01 not working properly.
Detailed Description
Steps to reproduce
Possible solution
Context (Environment)
Bemanitools version(s) affected
BT 5.30
Supplemental Tools 1.2
Game(s) and version(s) affected
IIDX26
Log output
See attachment.
Configuration files
See attachment.
Command line arguments
APIs used
OS version
Windows 10 Pro Build 18362.19h1_release.190318-1201 (Test Mode)
Hardware specs
I don't know if the C02 firmware is compatible with D01 IO boards. If there are issues flashing the base or FPGA firmware, it is expected that the hardware is not working correctly. Do you happen to know the differences of D01 compared to C02 boards?
In GitLab by @hvzero1 on Jun 14, 2020, 17:16
I'm actually unsure about that. I was operating under the assumption that I had a C02 since it was originally a Gold Cabinet. I reconnected my Sinobuz PCB and confirmed it was D01 on the startup screen. I'll try to search around again to see what I can find.
The D01 board is somewhat similar to the C02 with the exception that it is not entirely backwards compatible like the C02 board is. C02 boards can upgrade any twinkle based cabinet but D01 cannot. These were shipped starting 10th Style up to DistorteD before being replaced with IO2 starting with Gold.
When you boot up Sinobuz, the FPGA check shows "D01" (instead of "C02") I assume?
In GitLab by @hvzero1 on Jun 14, 2020, 20:05
Yes that’s correct (re: Sinobuz boot up)
In GitLab by @hvzero1 on Jun 15, 2020, 19:11
A few more questions.
Thanks
You need the D01 base firmware and the "firmware" that is written to the FPGA which seems to be different as the way turntables and other stuff is wired up is very different to a C02 board/cabinet.
Yeah, that would do the trick to get the firmwares flashed. However, I don't know if the usb protocol is 100% compatible with the one used for C02 boards. Might be worth a try to let the game initialize the board, then try another game with bemanitools and the iidxio-ezusb.dll and the iidxio-test tool included with BT5.
I think your cabinet wiring will not be entirely compatible. C02 cabinets have two main interfaces that go into the IO board: a 40 pin connector (like the one used on IDE drives) and a RJ45 connector (like on ethernet cables).
D01 cabinets also have the 40 pin connector but multiple other cables for turntables, top unit lights and the front button panel with the 16seg board.
In GitLab by @hvzero1 on Jun 16, 2020, 04:07
Confirming that running Sinobuz first to initialize the IO works. iidxtest works correctly, and Rootage uses everything correctly. So I'm guessing I'd need to track down the D01 firmware (if thats even a thing) to have this process be more seamless for a dedicated setup.
I derived a task from this issue since we now have a clear goal on how to fix this.
Task #55 follows up accordingly with steps to get the firmware.
Therefore, I will close this issue and further discussion on the feature to be implemented takes place in issue #55.
closed
reopened
@hvzero1 I dumped the D01 FPGA firmware
Can you please flash this when initializing your D01 IO instead of the
fpga.binfrom the supplements package and check if everything's working fine?In GitLab by @hvzero1 on Aug 12, 2020, 05:46
@icex2 Thanks for the update, I will hopefully try to confirm this tomorrow.
In GitLab by @hvzero1 on Aug 13, 2020, 05:55
Tested this with ezusb-boot v1 and everything worked as expected! Thanks a lot for making this happen.
Perfect. I added the binary blob to the bemanitools-supplement repository.
closed