legofan623
Well-Known Member
nvm
Nvm
- Thread starter legofan623
- Start date
Blargaman91
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
One must check the dip switch as well. You may want to put that in there.
One must check the dip switch as well. You may want to put that in there.
legofan623
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
Added dip switches
Added dip switches
legofan623
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
Added SD card
Added SD card
megalomaniac
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
this is a very nice attempt to try to make things simple but there is just so much more to it that these simple steps...
where should i begin to explain all the flaws in this chart???
this is a very nice attempt to try to make things simple but there is just so much more to it that these simple steps...
where should i begin to explain all the flaws in this chart???
legofan623
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
Well yeah obviously it's not going to solve all the problems you have with your chip, it's meant to just outline all the stuff you should do before making a help post.
Well yeah obviously it's not going to solve all the problems you have with your chip, it's meant to just outline all the stuff you should do before making a help post.
megalomaniac
Well-Known Member
Re: WiiKey/WASP Graphic Troubleshooting Flow Chart
i want to focus just on the very first step in this flow chart...there is just so much left out within the very first part of this...
about the blue LED...
it should not ever blink unless there is swiss autoboot installed...
so does it have swiss autoboot or original 1.4 WKF/WASP firmware?
if there is no swiss autoboot then you need a pin29 swich to actuate loading the initial iso...
if that does not load the initial iso, then you need to check pin29...
is pin 29 using a normally closed switch with leads connected to pin29 and GND?
if pressing pin29 and still no load is there any error messages on screen?
check continuity of all pins...
^^^^all this so far is just for the blue LED if on 1.4 firmware
im sure there is more i failed to mention since i just wanted to provide a quick intro on how flawed this chart is...
and if swiss autoboot is installed there will be similar steps as above and some will be different
also, before leaving the flow of the blue LED dont forget to mention if there is a red LED lit instead...
there are just to many holes in this chart to be of any real troubleshooting use for someone who is having problems....and your assumptions of this applying to MEGAdrive is incorrect because no matter the connection method, MEGAdrive, breakout board, modified FFC, or wired, troubleshooting is all the same....MEGAdrive and breakout board only eliminate the very real potential for broken wires...
i want to focus just on the very first step in this flow chart...there is just so much left out within the very first part of this...
about the blue LED...
it should not ever blink unless there is swiss autoboot installed...
so does it have swiss autoboot or original 1.4 WKF/WASP firmware?
if there is no swiss autoboot then you need a pin29 swich to actuate loading the initial iso...
if that does not load the initial iso, then you need to check pin29...
is pin 29 using a normally closed switch with leads connected to pin29 and GND?
if pressing pin29 and still no load is there any error messages on screen?
check continuity of all pins...
^^^^all this so far is just for the blue LED if on 1.4 firmware
im sure there is more i failed to mention since i just wanted to provide a quick intro on how flawed this chart is...
and if swiss autoboot is installed there will be similar steps as above and some will be different
also, before leaving the flow of the blue LED dont forget to mention if there is a red LED lit instead...
there are just to many holes in this chart to be of any real troubleshooting use for someone who is having problems....and your assumptions of this applying to MEGAdrive is incorrect because no matter the connection method, MEGAdrive, breakout board, modified FFC, or wired, troubleshooting is all the same....MEGAdrive and breakout board only eliminate the very real potential for broken wires...
legofan623
Well-Known Member
Re: General WASP/WiiKey Troubleshooting Flow Chart
@Dyxlesci
Whoops... Fixed
.
@megalomaniac
See the edited op
@Dyxlesci
Whoops... Fixed
.@megalomaniac
See the edited op
megalomaniac
Well-Known Member
Re: General WASP/WiiKey Troubleshooting Flow Chart
- there is no such thing as swiss 1.4 autoboot...
- is this flow chart only applicable to anyone using a pin29 switch?
- what special factors would exist? either the WKF/WASP is in process of trying to get connected to a GameCube or not...there are no "other" special factors because EVERYTHING is a special factor when you consider the WKF/WASP were never designed for use on a GameCube and here we are trying to modify systems to make something work that was never intended to work....
flowchart also still assumes type of connection method previous:
flow >
check connection multimeter >
resolder >
use jumper wires....
how can you assume a certain type of connection method was used?
for example someone bought a MEGAdrive V3, plug n play...the Dang thing has a DVD plug that literally slides right into the DVD drive port on the mainboard...
this guy also had a WASP with original WKF 1.4 firmware, not swiss autoboot...
he could not get the thing working because he did not understand about the pin29 switch or the lid switch....
this is considering V3 is 100% electrically tested to confirm no breaks or shorts and after about 80 emails back and fourth i dont know if he actually succeeded...this flow chart would not help even in the most simplistic of scenarios when you consider all the main data lines were 100% connected yet it indicates to pinout and/or resolder.... you cannot account for any predefined scenarios when trying to troubleshoot WKF/WASP...
A flow chart to cover WKF/WASP troubleshooting is just not as simple as you think...
even when trying to cover some of the most basic of symptoms it still lacks to accomplish anything since the flow does not correctly address basic scenarios...you cannot even assume what a basic scenario is...
one thing you have to consider is does the person even know what the pin29 switch or lid switch are used for? and does that person even know if they need em or should be using em?
both of these "basic scenarios" are not even factored into the flow chart..
someone posted a video recently asking for assistance in troubleshooting and showed the lid connected to GND, which is completely wrong. The video did help to discover the issue....yet none of these are on the flow chart...
there are too many variables...
currently, the flow chart does not even factor in what happens when the SD card is inserted and now the blue LED flashes....is it fixed? is it still not working?
....and another thing, dont start the flowchart with a negative question...
legofan623 said:
- there is no such thing as swiss 1.4 autoboot...
- is this flow chart only applicable to anyone using a pin29 switch?
- what special factors would exist? either the WKF/WASP is in process of trying to get connected to a GameCube or not...there are no "other" special factors because EVERYTHING is a special factor when you consider the WKF/WASP were never designed for use on a GameCube and here we are trying to modify systems to make something work that was never intended to work....
flowchart also still assumes type of connection method previous:
flow >
check connection multimeter >
resolder >
use jumper wires....
how can you assume a certain type of connection method was used?
for example someone bought a MEGAdrive V3, plug n play...the Dang thing has a DVD plug that literally slides right into the DVD drive port on the mainboard...
this guy also had a WASP with original WKF 1.4 firmware, not swiss autoboot...
he could not get the thing working because he did not understand about the pin29 switch or the lid switch....
this is considering V3 is 100% electrically tested to confirm no breaks or shorts and after about 80 emails back and fourth i dont know if he actually succeeded...this flow chart would not help even in the most simplistic of scenarios when you consider all the main data lines were 100% connected yet it indicates to pinout and/or resolder.... you cannot account for any predefined scenarios when trying to troubleshoot WKF/WASP...
A flow chart to cover WKF/WASP troubleshooting is just not as simple as you think...
even when trying to cover some of the most basic of symptoms it still lacks to accomplish anything since the flow does not correctly address basic scenarios...you cannot even assume what a basic scenario is...
one thing you have to consider is does the person even know what the pin29 switch or lid switch are used for? and does that person even know if they need em or should be using em?
both of these "basic scenarios" are not even factored into the flow chart..
someone posted a video recently asking for assistance in troubleshooting and showed the lid connected to GND, which is completely wrong. The video did help to discover the issue....yet none of these are on the flow chart...
there are too many variables...
currently, the flow chart does not even factor in what happens when the SD card is inserted and now the blue LED flashes....is it fixed? is it still not working?
....and another thing, dont start the flowchart with a negative question...
legofan623
Well-Known Member
Re: General WASP/WiiKey Troubleshooting Flow Chart
Jesus christ nevermind about the flowchart then
Jesus christ nevermind about the flowchart then
Similar threads
