I wanted to update the firmware and dev menu on one of my RVT-H’s in order to run applications compiled with SDK 3.3 patch 2. SDK 3.3 patch 2 uses the firmware version 56.21.29 and the docs say that the system should have the correct firmware installed for the current SDK being used. If you try to launch an application on the console without the correct firmware version installed you will likely receive a message like this: Expected Firmware – 56.21.29 Actual Firmware – 56.20.26 I decided to document the firmware update process in case it would be of help to other people. All of this info is in the documentation, but it is sometimes nice to see a video demonstration. NOTE: The rvtrwriter software has a button labelled “H Reader Update”. This is not for updating the Wii firmware, it is for updating the firmware on the internal HDD using a .bin file. The docs say that the dev environment should use Cygwin with openssl 0.9.8b and GNU make version 3.80. I am not sure if these are needed for making the update disc, but best install them anyway if your going to be using the SDK. To check your openssl version in Cygwin type “openssl version”, to check the make version type “make --version”. Once you have done that, get the firmware update file from your desired SDK and place it in the folder with the makeUpdateDisc application (Part of Wii Mastering Tools Package). The update file that I am using is swupdate_56.21.29_eu.gcm. Navigate to the directory in Cygwin and type “makeUpdateDisc <input filename>”. Example: “makeUpdateDisc swupdate_56.21.29_eu.gcm” This will produce a .rvm file with the same name. You can specify an output filename if you wanted. Then connect your RVT-H to your PC and run the rvtwriter application. Select an empty bank on the hard drive, then select the browse button and navigate to your newly created .rvm update file. Once the process has finished, power off the console, disconnect from PC and connect to TV. Navigate to the bank where you installed the image and launch it. If you have an RVT-R that you would like to update, you would follow the exact same process to generate the .rvm file and then you would use the rvtwriter software to burn the .rvm file to a blank RVT disc. It is also the same procedure when creating a Wii system menu changer disc. (This was filmed on a VM and some parts of the video flicker for a few seconds) UPDATE: Compiling a demo Some people may have issues when trying to compile a demo from the SDK, so I thought that it might be useful to provide a bit of info here. If you try to compile an application CodeWarrior will detect the time/date on your PC and will throw an error. "processor Gecko is not supported by the current set of licenses. Please contact <license@Freescale.com> for licensing needs" You can set the date on your PC back to January 2012, but it also detects the creation and modification date of the files and folders in the SDK. It will complain if it detects that any files/folders have been created/modified in the "future". I just used a program called Attribute Changer 8 to batch modify the creation/modified/accessed date for each of the files/folders in the SDK.
There is no need to convert the firmware file to .rvm for the NDEV, you just run the .gcm file directly using ODEM. Example: ODEM -r -l swupdate_56.21.29_eu.gcm
How did you get the 3.3 patch 2 SDK up and running? When I downloaded that SDK and it was missing some files required for setup.
