Conflicting Resolution Reporting on 3.1 in Electron Shepherds’s AVE-HDMI on Wii CPU-40

[Ghost-Mop]

Hi, I finished installing two of the new Wii HDMI kits this weekend and my CPU-40 is claiming different resolutions in the three/four most common places but my CPU-20 is reading 720x480p across the board, leading me to question the 40’s behavior. On the CPU-40’s install, in the OSD I can see 686x912i60 IN, 720x480p60 OUT, but the top right resolution notifier will also state 686x912i60, or whatever slight variation of those numbers but always mismatched to the OSD’s claimed output. Attached are some pics of the install (yes that is a pink XCM case and probably too much kapton tape)

I played with a few games, Mario Kart Wii, Mario Parties 8/9, and Animal Crossing: City Folk but I can test out a GameCube game when I get home later, if that could prove useful.

The hardware seems to be working fine and Shane Kent (name-drop!) of Electron Shepherd recommended against re-installing unless a solution couldn’t be found here.

Is there a fix for this in the OSD, Priiloader, system menu, etc? Will I be best suited to try and re-flow my install? Is this just a quirk of a CPU-40 install?

I do apologize if this is the wrong place to ask for help!

Quizzically Yours, Max

[ikorb]

You probably have a problem with VDATA0. You could try the diagnostic mode to confirm - please be aware that the results are only fully valid if the console is running a 3.0d or later updater at the time (you don't need to actually start the update) because that draws a test pattern at the top of the screen so the diagnostic mode has something known to compare against.

[Ghost-Mop]

i've been fiddling with the updater at https://github.com/ikorb/gcvideo/blob/main/Updater/obj-wii/gcvupdater.dol but its showing as "unconfigured" and that i should be using a "configured one instead" prompting only my ability to exit. At the wii main menu, i get no bits stuck at 1 or 0, the 0-7 in unexpected (as expected), both clocks OK and AData OK but in the initial screen of the "unconfigured" updater i get ADATA missing/silent and 0+2 stuck at 0.

Is there somewhere better i can obtain a "configured" updater or does it need done case-by-case per console or per gcvideo implementation iteration?

[ikorb]

Don't use the stub, use one from a release

[Ghost-Mop]

so it thinks we’re getting crosstalk!

[ikorb]

Yes, a problem with VData bit 0 exactly matches the "detects progressive input as interlaced with twice the expected vertical resolution" symptom. Since it is not detected as stuck, it might be floating, shorted to something adjacent or connected to an unrelated signal.

I recommend contacting your hardware vendor about debugging a bad installation since they should know that hardware better.

[Ghost-Mop]

I’ll shoot him an email, would you like me to update the thread here or close?

[ikorb]

I'll just close it