I dont think there is anything brook can do on their end. The issue is from how the te2 crossbone works with the xb1 te2 pcb.
The te2 crossbone acts like a middle man between the two pcbs since the xb1 pcb is not common ground. The inputs go to the te2 crossbone and then it handles if they connect to the xb1 pcb or the secondary pcb. What I think is happening is during plug in the brook board is checking inputs to see if it should go into bootloader mode or not. However it does that before the te2 crossbone is done doing its startup thing and switching over the input lines to the selected system.
What you can do to work around that is to wire up two buttons inside to home and select directly on the brook board. hold those done during plug in to go into bootloader mode. Using some diodes you could wire up one button to both signals. You can even use the two button holder inside for this.
@GOGO.Zippy
Oh yeah almost forgot the share button for updating, thanks!!!
@Vicko
Thanks id thought that was what i needed to do, but wasnt 100%, was afraid that doing that would draw power from the brook pcb and not be enough to run them both.
@Gummo, connected two extra buttons inside the TE2 to PSKey and Select directly to the Brooks and split off to the Crossbone. I can finally update by holding PSKey and Select inside the case. A simple nice workaround. Thanks for the idea. I was gonna go buy a DPDT switch and everything and drill into the case but thankfully donât need to do that now.
I guess in future Brook firmwareâs they could adjust the timing for holding PSKey and Select like the PS360+ update method so crossbone could complete doing what it needs and brooks PCB do what it needed to.
Thanks alot to @Vicko & Gummo. Everything is working as it should.
@Gummo@Vicko@SaveFighting This is what solved my switching problem on the impv2. Wired a button directly to the imp and it switches properly. So I guess itâs not really a Brook issue since it happened on my imp. Maybe @Phreakazoid can make some type of adjustment to the crossbone? Iâm just asking. I donât even know if itâs upgradable.
Lol. I undid it already since I donât have quick disconnects. But u just run the F wire to a actual physical button and of course a ground wire and problem solved.
Hey guys, so I spent a decent amount of time last night soldering this up and I wasnât too succesful. It probably didnât help that I was doing this at 2am this morning hahahaha
Iâm sure thereâll be others out there that might go through my same experiences so I thought Iâd shareâŠ
My setup:
360 Soul Caliber TE (primary)
Brook Fight Board (seconday)
Imp V2.1 switching mechanism, (F is connected to the RS point of the 360 PCB so this is used as the switching mechanism instead of the guide button)
My 360/BROOK wiring setup:
360 PCB / BROOK PCB
1P = X / SQUARE
2P = Y / TRIANGLE
3P = RB / R1
4P = LB / L1
1K = A / X
2K = B / CIRCLE
3K = RT / R2
4K = LT / L2
GUIDE / HOME
START / OPTION
BACK / SHARE
TURBO / TURBO
My Imp V2 wiring setup (Basic Setup):
Imp USB = wired the TE USB to the USB point of the Imp
Imp SJA = has been soldered to short (the two points made into 1)
Imp SJC = has been soldered to short (the two points made into 1)
Imp VCC = Brook VDD_5V
Imp G = Brook GND
Imp A = 360 GND
Imp D = Brook D+
Imp E = Brook D-
Imp F = 360 RS
Imp V = 360 5V
Imp XD+ = 360 D+
Imp XD- = 360 D-
Main issues overnight were:
had no idea what to expect to see on the PC when the Brook PCB was âactiviatedâ. When I have mine in â360â mode ie. the cable is plugged in with the DS toggle selected, it would appear is Soul Caliber Tournament Edition Fightstick or something like that. When I activated, it came up as â360 controllerâ (which I thought was my 360 PCB) so I thought it wasnât switching properly. After re-reading this whole thread again, the Brook PCB SHOULD come up as 360 controller.
Since I thought it wasnât switching properly, I kept mucking around with it to the point and I believe I have my D+/D- mixed up since I get the âUSB device unrecognisedâ message. After typing out what wires I had above, I think my IMP D and IMP E is mixed up.
Took me a while to realise the diagram I was following (one of the original ones on this forum with the Imp V1.1) was a PCB for the original TE and the PCB for the Soul Caliber TE is slightly different! I had a KGND point wired as the XBOX Guide button, the Guide as the Turbo and I was wondering why it wouldnât âswitchâ. It wasnât only when I got the multimeter out that I found out what was going on.
I will have to re-check all this again when I get home. Re-reading the welcome PDF of the Imp, D should be Brook D- and E should be Brook D+.
So I think my main changes for tonight will be:
Change around Imp D from Brook D+ to Brook D-
Change around Imp E from Brook D- to Brook D+
Wait a long time for the USB drivers to be installed
Try and update the Brook PCB to work with the latest PS4 F/W
By theory that it is how a dual mod work, but in practice not all boards like to âcooperate with each otherâ and some âelectronic wizardryâ is needed.
My 360 PCB is directly soldered on to the Brook PCB and the switching is done by the Imp V2. The mistake I made was the Brook D+ and Brook D- on the Imp D and Imp E.
By simply switching the two around, everything worked as I hoped. The only thing I wish would work is the switching, with the Imp v1.1, I could switch to RS and âleave itâ to the second PCB at all times.
Took me a while to work it out, but every time I plug in the USB cable with the switch on RS, it changes the PCB each time, but if I activate it on the correct PCB, I simply just take it out of RS and every time I plug in, itâll keep it stored.
Using the RS switch makes it easier with upgrading the F/W and it was a breeze using the app.