Code search not finding values??

[strakn]

Ok so I just purchased a usb gecko se.  I installed the drivers, and can get wiird and gecko dotNEt to connect, although usually
I would have some difficulty getting them to connect (needing to unplug usb cable when it said it wasnt connected then plug it back
in and retry)

Now what I realize is that performing code searches with both wiird and geckodotnet are not finding all of the values and sometimes the values are wrong. Example I know there is the value 0x00000008 at address 0x80A1B058 but when i do a 32bit code search for that value it doesn't find it and usually doesnt seem to find any values over 81 mem area. I know the value is there I can see it in memory viewer it will change if i poke it and i can see the change on the screen, but it just wont show up in the code search for wiird or gecko.net

I have tried updating the drivers, I have tried on 3 different computers now (xp,vista and 7) same issue.
I have reprogrammed the eeprom with .ept file that nuke linked to in another thread.
The only other thing I can think of besides a defective usbgecko is the cable, its the one that came with the usb gecko
if trying another cable(s) doesn't work, Is there anything else I can try before returning the unit?

Edit--

If I narrow the search parameter down to a very small search, sometimes it will show the value of a known location.

Edit 2 -

I have tried 2 other cables, shorter ones with ferrite beads on them and still no luck.

[dcx2]

That's odd...

Try pausing the game.  Then do an unknown search.  Then do an equal search.  Since the game is paused, all values from the first dump should be identical to the second dump.  Subsequent equal searches while the game is still paused should result in the same number of search results.  If you start losing results, then something is definitely fishy.

[strakn]

Thanks for tip, that should prove that the data is somehow being corrupted.  The data seems to not get corrupted when dumping small chunks as memory viewer does, or when chan ging the default search parameter to very narrow field. It will be a few hours before im back at the wii.

I have sent an email to usbgecko support hopefully they will have input on my problem.

[Link]

That problem happened during WiiRd development.. however, with new USB Gecko drivers it seemed to fix itself kenobi and me were unable to reproduce it on one day and well.. logically we were happy. Please try replacing the USB cable just for the sake of testing, otherwise try a different USB port (not the one directly next to the one you're using, a totally different one, it should be on a different internal USB hub  -normally each PC has 2 USB ports per USB hub) - it will be worth a try I guess.

[dcx2]

He said he tried different cords and PCs.  Although you bring up a good point...where did he get the drivers?

[strakn]

I got the drivers right from the chip manufactures website.
http://www.ftdichip.com/Drivers/D2XX.htm

Also on the xp machine i tested it already had an older version of the ftdi drivers 2.04.x

I did what you suggested dcx2, starting an unknown value search while paused, then doing consecutive equal to searches,
the found results kept going down, I even tried executing a breakpoint intead of using pause (probably same thing) and
got the same diminishing results. I did this with both gecko.net and wiird gui, same results.

I did a resynchronizing comare to the dumps in hexworkshop and there were many deletions,insertions and replacements.

I am really at a loss, as to the cause of this, the only two variables I have not changed are the wii and the usbgecko, unfortunatley
there is no other wii i can test with.

[strakn]

Ok so I used the FTClean utility to completely remove the drivers, then I installed an older version of the drivers and get this message

[spoiler][/spoiler]

Used FTClean again and tried newest driver and this is what It what it says in wiird 0.9.3 it just stays there trying to reset
[spoiler][/spoiler]

I can no longer even get a connection to the usb gecko

Nuke I see you have been active within the past few days, If you see this please provide some input, I have sent an email to [email protected] but have not heard anything back.

[dcx2]

You seem like a competent fellow, so I trust you can follow these instructions, but be careful.  This is how I remove drivers from Windows.

While the USB Gecko is connected (I don't think it needs to be connected to the Wii, just the PC), go to device manager (tip: start -> run -> devmgmt.msc ) and uninstall the device.  Once it is uninstalled, remove it from the PC.

From admin command prompt, run pnputil -e.  You will see a list of all the drivers you have installed.  Note the driver package provider; you're looking for FTDI (if there are multiple instances, you want all of them).  Once you find them, note published names, oemXxx.inf

Then, from the same command prompt, run pnputil -f -d oemXxx.inf.  This will remove the driver from the driver store, so that Windows will ask you for the driver when it is connected again.  Do this for each instance of FTDI.

Now when the device is connected, Windows will ask you what to do.  I recommend just getting the driver from Windows Update.

[strakn]

Ok I followed your steps but there was no driver package provider for FTDI. (Probably beause the last thing I did was use FTClean to remove the drivers after my previous troubleshooting failed)

So I reinstalled the drivers again and then removed them with your method, I connected the usbgecko and windows told me to insert the disk that came with it, I skipped that and told it I didnt have the disk, forcing windows to check online, Windows said it could not find any drivers online, so the only other option was to use ones I downloaded...no good.

[dcx2]

For real, Windows Update didn't find the driver?  I know they have FTDI drivers.  That's so strange...

In Device Manager, go to the Properties of the device, Details tab, change the dropdown to "Hardware Ids".  What are the VID and PID?  I wanna see if they're different from the FTDI chip I use.

[strakn]

USB\VID_0403&PID_6001&REV_0600
USB\VID_0403&PID_6001

edit;

when i tried to update the drivers on the xp machine (the one that already had drivers preinstalled) when i pointed to the new drivers it said the best ones were aleady installed

[dcx2]

0403:6001 looks good, I don't understand why Windows can't find the driver online...

I'm at a loss, sorry.

[strakn]

thanks for all your help dcx2.

I have received an email back from ian/nuke (i think they are the same) and have pointed him to this thread
in the hopes any steps to resolve this issue will not need to be repeated.

it is very discerning reading up on all the codetypes and trying to learn some basic asm,
then when the time comes to put it to use not being able to.

[megazig]

i had an issue with corrupted dumping also. ian pointed me at doing a tx check and i fixed the codehandler. a link is on the rvlution site for riivolution. it will need a mod to geckoos unless you run it from riivolution

[Nuke]

Tomorrow I will spend the day to fix this. The handler mem dump routine has a bug, but Gecko.NET will also need editing for the update.

Might take a couple of days testing etc, before a public push though.

Sorry for the inconvenience.