Dual Strike suddenly not working

33 views
Skip to first unread message

Nick Chow

unread,
Feb 27, 2012, 1:33:13 PM2/27/12
to Strike Devices Support Mailing List
I was at a gaming session Friday night and was playing SC5 on the 360,
when one of the PS3 stations needed another stick, so I unplugged it
from the 360 and brought it over to the PS3 and all I got when I
plugged it into the PS3 was the ring of 4 xbox controller # indicator
lights just sat there blinking. When I brought it back to the 360
nothing happened at all. It had been working fine on both the 360 and
the ps3 previously but crapped out mid session. It was a Dual Strike
v2 but without the screw terminals for the buttons. Any ideas on what
happened? What i might need to check?

Michael Pohl

unread,
Feb 28, 2012, 7:25:35 AM2/28/12
to strike-...@googlegroups.com
Please re-install the firmware following the instructions here: <https://docs.google.com/document/d/17Nyr6vPujHAXz3PxjKwKBWEf8Lf6xNjQocsVg_qAqNc/preview#heading=h.791cba2b84e6>

This might solve your problem, if not you will have to do an RMA.

Regards,
Michael

Nick Chow

unread,
Feb 28, 2012, 9:44:41 AM2/28/12
to Strike Devices Support Mailing List
When I plug it into my PC it loads as a generic HIDcompliant device
with no details, and when I run the batch file i get this error:

Leaving bootloader after finishing.
Flash file: "dual_strike_firmware_atmega168_V3.3.1.hex"
Uploading flash data...
Page size = 128 (0x80)
Device size = 16384 (0x3800)
Uploading 14336 (0x3800) bytes starting at 0 (0x0)
0x01500 ... 0x01580Error uploading data block: Communication error
with device
Press any key to continue . . .

In multiple attempts, it gets to various stages of completion, but
always throws the communication error.

Thanks,
Nick
On Feb 28, 7:25 am, Michael Pohl <pohl-mich...@gmx.net> wrote:
> Please re-install the firmware following the instructions here: <https://docs.google.com/document/d/17Nyr6vPujHAXz3PxjKwKBWEf8Lf6xNjQo...>

Michael Pohl

unread,
Feb 28, 2012, 11:24:57 AM2/28/12
to strike-...@googlegroups.com
Such errors usually point towards a bad USB connection. If you can rule that out absolutely (e.g. by connecting a very short USB cable and trying again) please do an RMA.

Bye,
Michael

Reply all
Reply to author
Forward
0 new messages