WASP fusion stopped working after swiss update=FIXED

[andre104623]

OK I fucked up I didnt notice the switchs. You didn't have to make a new version of swiss because I'm a dumb ass

[andre104623]

Implemented a check in r270 for incorrect switch config.

Wow that's like the icing on the cake.

[emu_kidid]

We only learn from mistakes with unknown devices like the WKF/WASP, wasn't trying to put salt on the wound...

Apparently if they're set and you manage to boot a game it runs slow too, so I figured I'd help anyone else that might have this issue

[andre104623]

We only learn from mistakes with unknown devices like the WKF/WASP, wasn't trying to put salt on the wound...

Apparently if they're set and you manage to boot a game it runs slow too, so I figured I'd help anyone else that might have this issue

Well whatever life goes on

[keropi]

really nice addition emu_kidid ! I wonder what the future will bring for the little wasp/wkf

[tesla246]

really nice addition emu_kidid ! I wonder what the future will bring for the little wasp/wkf

Maybe audiostreaming?

[keropi]

^ with some extra MEGA<circuitcity> ? bring it on!

[megalomaniac]

I was thinking of our chat session last night.

The switch position was not the root cause of the problems encountered after flashing a new version of swiss.
The actual problem with the WASP freezing was from the FFC cable. After you booted with no SD card in the slot then there was no freeze and you had access to the GC menu. After remove and reconnect of both FFC cables, that's when WASP booted as normal.


When WASP successfully booted and read an SD card you happened to have the 1.2 restore iso on the card.
This is what caused the SW3 SW4 message to appear....only after restoring back to original firmware...
This type of switch position validation was never used in swiss so there was no ability to identify the invalid switch configuration.

After doing a few tests, it has been determined invalid switch positions causes the WKF/WASP to have issues reading data from its SD card. This can explain your previous thread regarding the playback/performance issues you had experienced.

[andre104623]

I was thinking of our chat session last night.

The switch position was not the root cause of the problems encountered after flashing a new version of swiss.
The actual problem with the WASP freezing was from the FFC cable. After you booted with no SD card in the slot then there was no freeze and you had access to the GC menu. After remove and reconnect of both FFC cables, that's when WASP booted as normal.


When WASP successfully booted and read an SD card you happened to have the 1.2 restore iso on the card.
This is what caused the SW3 SW4 message to appear....only after restoring back to original firmware...
This type of switch position validation was never used in swiss so there was no ability to identify the invalid switch configuration.

After doing a few tests, it has been determined invalid switch positions causes the WKF/WASP to have issues reading data from its SD card. This can explain your previous thread regarding the playback/performance issues you had experienced.

Well Im glad we got the problem solved now I installed the pin29 switch and haven't touched anything else

[andre104623]

Ok so after installing pin29 switch I updated wiikey to 1.5 then followed mega's "installing swiss autoboot guide" and now everything is great and working fine. I must note that even that everyone says ipl 1.0 will not work with wiikey this is false I was able to load swiss from wbfs sd card from wiikey menu 1.5

[megalomaniac]

The problem is playing game titles not homebrew

[andre104623]

The problem is playing game titles not homebrew

Well autoboot is working great thank you for all the help and sorry for almost giving you a heart attack I'm looking forward to getting the other wasp and megadrive next week and hopefully ide-exi soon