Problem flashing firmware (and others)

47 views
Skip to first unread message

el.m...@gmail.com

unread,
Jul 28, 2013, 9:22:30 AM7/28/13
to strike-...@googlegroups.com
Hi,

I'm currently using a Dual Strike v2 and TEasy mod which worked like a charm on 3.2.0. However I did update to 3.3.0 not so long ago and the problem began :
  • Stick won't be recognized by ps3 (autodetection and forced mode)
  • Stick won't be recognized by 360(autodetection and forced mode)
  • Stick won't be recognized in flashing mode by pc (unknow device error, device manager was cleaned of old drivers)
  • Stick gets recognized by pc once in a while when plugging it raw as a TE stick (inputs work as intended, which leads me to believe it's a dsv2 problem rather than a TEasy one).

Is there a know solution to these problems ? Any help would be appreciated.

Cheers.

Michael Pohl

unread,
Sep 18, 2013, 9:16:15 AM9/18/13
to strike-...@googlegroups.com, el.m...@gmail.com
Hi!

Sorry for the late reply, but I answered by E-Mail in July and just now saw that Google hadn't forwarded the mail. So here's my answer from then...

Actually the current firmware version is 3.3.1: http://strike-devices.net/index.php/game-controllers/dual-strike/

I never heard of such problems with version 3.3, but could it be you installed the wrong firmware version? Prior to 3.3 there were also firmware versions for the old Dual Strikes with ATMega8 microcontrollers and the SMD versions, which were for Gummowned's very small Dual Strike - so you might have accidentally used that.

Bye,
Michael

el.m...@gmail.com

unread,
Sep 18, 2013, 2:31:22 PM9/18/13
to strike-...@googlegroups.com, el.m...@gmail.com

Hi,

Thanks for the answer. I'm pretty sure I always used atmega168 updates and it always worked fine. Is there anything that I can do but remove the whole thing, resolder the 360 board and forget about ps3 compatibility ? Is there anyone I can send the board and have it relfashed ?


Any help would be appreciated.

Thanks,

Mikael

Michael Pohl

unread,
Sep 20, 2013, 5:56:06 AM9/20/13
to strike-...@googlegroups.com
> Thanks for the answer. I'm pretty sure I always used atmega168 updates and it always worked fine. Is there anything that I can do but remove the whole thing, resolder the 360 board and forget about ps3 compatibility ? Is there anyone I can send the board and have it relfashed ?

First try installing the current firmware one more time from the website: <http://strike-devices.net/index.php/game-controllers/dual-strike/>

If the device still behaves erratically please run the DS Memory Test and report the results: <https://github.com/IvIePhisto/Dual-Strike/blob/master/Firmware/Releases/MemoryTest.zip>

Regarding reflashing/replacement: When and where did you buy the DS? Where are you situated?

Bye,
Michael

mikael...@gmail.com

unread,
Nov 1, 2013, 11:07:22 AM11/1/13
to strike-...@googlegroups.com
Hi, sorry for the late answer !

The device now always gets detected as an unknown device by windows (even after cleaning the drivers and rebooting) which prevents me from flashing the firmware or running the memory tool. Looks like it is a lost cause and I'll just revert it to a xbox / pc controller only.

As for where I bought it, I don't have a clue since I lost all my emails from that period of time :) (I'm from France).

Thanks for your help anyway.

Mikaël
Reply all
Reply to author
Forward
0 new messages