Gecko dotNET Bugs and Requests

[Deathwolf]

ropers - did the new drivers resolve your problem?

deathwolf - What Windows are you using?  Are you playing GameCube games with Gecko OS Mod?  I've never tried it, so I don't if it would work.

I'm still on Windows xp and yes, GameCube games with Gecko OS Mod.
After Gecko dNet hooks the game, it freez but it works great on Wii games.

[Deathwolf]

Breakpoint doesn't work anymore on the new Gecko dNet. After setting breakpoint, the game freez and gecko dNet lose connection (On Wii games). Tested 4-6 and still doesn't work....

[dcx2]

I have had no problems with breakpoints, and I know some others who haven't either.  You will have to be more specific about what your problem is.

What type of BP are you setting?  Is Exact checked?  What games are you trying?  (I know for a fact that Super Mario Galaxy should work, because I've been testing that particular game lately)

When it freezes, do you see any registers or disassembly?

Does it freeze if you set a breakpoint that will never be hit?  For example, does it freeze on an Execute BP on address 80000000?  Does it freeze if you hit the Pause button and then the Run button?

Is this a disc-based game or a WiiWare/VC game?  Are you using Gecko OS?  (Bully said he had some issues with a USB Loader, but I was unable to replicate those issues)

What version is your FTDI driver?  See the screenshot a few posts back to see how to answer this.

[Deathwolf]

Game : New Super Mario Bros
Region : PAL
DISC
Gecko 1.9.3.1


BP READ: On life address

Gecko dNet freez after breaking (shows no registers etc) lost connection.
WiiRd breaks on READ but it breaks on a wrong addresses!?
WiiRd breaks on WRITE right!
Gecko dNet doesn't break anything.
IDK why but the new gecko dNet seems it doesn't work for me .

[dcx2]

WiiRd breaks on READ but it breaks on a wrong addresses!?

non-exact Breakpoints are 8 bytes.  It is a common mistake to hit the wrong BP.  You should always check a read or write BP to make sure it hit the correct address.

The latest Gecko.NET will ignore unaligned breakpoints, so you can't hit the wrong address.

---

Did you try setting EXBP on 80000000?

Did you try pressing pause and then run?

Does Search, MemView, and Disassembly work correctly?

Are you using an original USB Gecko, or a USB Gecko SE?

What version is your FTDI driver?  http://wiird.l0nk.org/forum/index.php/topic,4954.msg67958.html#msg67958

[Deathwolf]

uff ok I've tried to connect to USB Gecko over XX times and I'm not able to connect anymore o_O
Yes I'm using the original White USB Gecko.
FTDI is now 2.08.12.

[dcx2]

If you can't connect to the USB Gecko even after rebooting the Wii, you might have to unplug it from the USB port on the computer.  The next version of Gecko.NET should be able to reset the USB Gecko without manually unplugging it.

[Deathwolf]

Hmm ok. WiiRd can connect to USB Gecko but Gecko dNet don't. Hmm ok I'm going to unplug it.

[dcx2]

The new Gecko dNet works fine on Wii games but it freez Gamecube games during hooking the game after patching the hook address 8034b09c. Why is that? However, the Pointer Search tab is great too. Thanks a lot.

I was reading the Gecko OS Mod thread.  Someone else had trouble with hooking.  Did you decrypt an AR code and forget to delete the verifier?

[Deathwolf]

No, nothing.

[Bully@Wiiplaza]

I noticed freezes with the "Ossleepthread" Hook on some games (Mario kart Wii, Pokemon Battle Revolution) while auto update in the memory viewer is checked. It runs fine for a few seconds but then locks up. This only happens on very less games like the two mentioned above. Ossleepthread does never freeze on e.g. Call of Duty games.
However, using another hook like the VBI Hook does fix the freezing problem on the games which freeze with Ossleepthread + Auto Update. Is there an explanation for the freeze?

[dcx2]

Are you using 0.64.8?  I just released it yesterday.  It has some fixes.

However, there appears to be at least one nasty bug in the actual code handler.  It occasionally causes a byte to get lost in transmission.  If one of these bytes belongs to, say, an address that you want to dump, then you end up dumping illegal addresses and it freezes the Wii.  If you go to the BP tab and hit "Step Into", you would probably see some lwzx involving an r12 that's an illegal address...at least that's what I would run into occasionally.

I'm currently working on trying to decipher the code handler.  I'm comparing the USB Gecko interface in the code handler to libogc's USB Gecko interface.  Nuke also released some stand-alone C code that interfaces with the USB Gecko from the Wii-side.  Hopefully, between the three I should be able to figure out what's causing the bug.  The next step is then coming up with some sort of patch to apply that will fix the bug.

[Bully@Wiiplaza]

I didn´t use the newest built yet, but this error happens since LONG ago even with the newer geckodotnet builts (0.64.6) and the newest gecko OS (1.9.3.2.)
You seems to be right to me that the code handler may need a few fixes!
(Would increasing allowed codeslines also work?)

[ropers]

ropers - did the new drivers resolve your problem?

deathwolf - What Windows are you using?  Are you playing GameCube games with Gecko OS Mod?  I've never tried it, so I don't if it would work.

yes it even fix my problem with it connecting with neo gamma.

Thanks for all the work you put into this.

[biolizard89]

So you changed the SetLatencyTimer to 1?  Does that actually work as expected?  The FTDI docs say that 2 is the minimum for the USB Gecko chipset.  (The USB 2.0 Hi-Speed chipset supports 1 and 0 as well, but I wouldn't expect that to work on the USB Gecko chipset.)  I'm very curious about this....