Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Geckoloader Wii: Difference between revisions

From GameBrew
(Created page with "{{#seo: |title=Wii Homebrew Loaders (Loader) - GameBrew |title_mode=append |image=geckoloaderwii.jpg |image_alt=geckoloader }} {{Infobox Wii Homebrews |title=geckoloader |imag...")
 
No edit summary
Line 16: Line 16:
|license=Mixed
|license=Mixed
|download=https://dlhb.gamebrew.org/wiihomebrews/geckoloaderwii.7z
|download=https://dlhb.gamebrew.org/wiihomebrews/geckoloaderwii.7z
|website=#LNF
|website=
|source=#LNF
|source=
}}
}}
https://wiibrew.org/wiki/Geckoloader
'''Geckoloader''' is a native Wii application which helps you to load and execute Wii homebrew binaries in the easiest and fastest way possible. It acts as a server which will receive binaries directly using a usbgecko adapter. A client tool to transfer such files is included.


==Screenshots==
== Requirements ==
==Media==
*a usbgecko adapter
<youtube></youtube>
*a way to boot Wii homebrew
 
== Features ==
*100% native Wii mode
*no medium ejecting, rewriting and inserting required whatsoever
*this is especially useful for wii coders (fast development cycle)
*reloading. the stub is placed at the memory location 0x80001800. this is PSO reload compatible, which means that any application can jump back there so that you can load another binary without reboot. the libogc exception handler also jumps to this address (when pressing Z on a GameCube pad)
*the protocol used for uploading is compatible to the official geckotool (you can use your client of choice)
*as always, this is open source ;)
 
== Architecture ==
geckoloader consists of 3 parts
*stub
*loader
*boot
 
*the boot code contains the other two code parts, and it is the executable that you have to run. it will write the loader code to the onboard usbgecko flash and place the stub into memory
*the boot code will then execute the stub
*the stub's job is to read the loader code from flash and execute it
*finally, the loader code will accept incoming Wii executables sent using a client application from the pc side
 
*the chosen architecture has the advantage that the tiny stub is the only component which has to stay intact in memory. while the usage of the usbgecko onboard flash might seem unnecessary at first, its purpose is the reloading feature. you will upload and run Wii applications. these in return will allocate memory and write to it. if the loader code would stay somewhere in memory, any executed application might overwrite it this way, but since it sits on the onboard usbgecko flash, no application can corrupt it.
 
== Usage ==
=== Wii-side ===
*use the [[Twilight Hack Wii|Twilight hack]] in combination with the included geckoloader.elf to get this running
*the boot code will show up
*you have to write the loader code to the onboard usbgecko flash once, press the Wii RESET button when asked to
*after that you will see the loader code in action
*use a compatible client (like the included one <code>geckoupload</code>, or the official windows geckotool) to send a Wii binary
*the transfered binary should execute
*if you loaded a game/app which has an option to jump back to 0x80001800, you will be presented with the loader code again. from there, you can transfer another binary again (no reboot required)
 
'''hint:''' try to upload the included <code>test.elf</code> first. it just prints a string to screen and has an option to jump back to the loader
 
=== Client-side ===
*the client uses a default tty device (except on windows), you can overwrite it using the environment variable <code>USBGECKODEVICE</code>
*Set USBGECKODEVICE too the com your device uses (example, COM4)
*RESTART AFTER SETTING YOUR ENV VAR !!! ELSE IT WILL NOT WORK
*make sure that your console is ready to receive an executable
*pass the filename of the binary to <code>geckoupload</code>, for example:<code>geckoupload test.elf</code>
 
you can use this client to transfer
*wii .dol's and .elf's to the geckoloader described on this page
*gamecube .dol's to the official usbgecko boot dvd
 
== Windows Driver Setup ==
If your USBGecko install didn't provide you with a COM port then try the following:
# Go to device manager and select the device 'USB Serial Converter' which is the USB Gecko device.
# Right click and select properties, then go to the 'advanced' tab.
# Click the 'Load VCP' box so its selected then press ok.
# Unplug the cable and then reinsert.
 
This should now give you a COM port, which you will need for geckoupload.
 
== Notes ==
*you can not run GameCube binaries with this loader since we're working in Wii mode here (that's a good thing)
*the default libogc base address for Wii homebrew is at 0x80003f00. this gives a PSO compatible stub 0x1900 bytes of memory for code. hence, the stub's main() functions were written in c so that it's easy to improve/fix
*the loader initially puts a received binary in MEM2 to avoid overlaps. it will be relocated from there. unfortunately the loader itself has a base address in MEM1. putting it in MEM2 is on my TODO list
*you can use the trucha signer to boot this app straight from dvd
 
== Changelog ==
'''v0.0.4'''
*HBC assimilated geckoloader. v0.0.4 is a pure gamecube-only version
 
'''v0.0.3''
*a gamecube pad isn't required anymore, the wii reset button is used to confirm the flash process
*the loader code is executed straight away if it has been flashed before (no interaction required)
*.elf file support thanks to tmbinc
*the stub doesn't overwrite the globals anymore, fixed by WinterMute
*a received binary is now written to MEM2 before relocating
*ported the client to win32 (binary included)
*the client now uses default device names on linux and os x
*the audio and dsp subsystems are initialized on reloading (no more annoying noise)
 
'''v0.0.2b'''
*fixed a timing issue in the usbgecko flash code. since i couldn't reproduce this on my setup, thanks go out to bLAStY and NoNameNo for helping me hunting this one down
*the included client now works on os x thanks to bushing
*added an extra check for malformed .dol files (some doltool converted .elf's)
*included a tiny test application
 
''*v0.0.2'''
*first public release
 
== Thanks ==
*shagkur, for helping me getting the stub working and providing the linkerscript
*the DevkitPro team
*team tweezers for making all of this possible
*all open source Wii coders
*nuke for sharing code for his adapter
 
== External links ==
* Wiibrew - https://wiibrew.org/wiki/Geckoloader

Revision as of 04:14, 23 September 2022

geckoloader
File:Geckoloaderwii.jpg
General
Authordhewg
TypeLoader
Version0.0.3
LicenseMixed
Last Updated2008/03/11
Links
Download

Geckoloader is a native Wii application which helps you to load and execute Wii homebrew binaries in the easiest and fastest way possible. It acts as a server which will receive binaries directly using a usbgecko adapter. A client tool to transfer such files is included.

Requirements

  • a usbgecko adapter
  • a way to boot Wii homebrew

Features

  • 100% native Wii mode
  • no medium ejecting, rewriting and inserting required whatsoever
  • this is especially useful for wii coders (fast development cycle)
  • reloading. the stub is placed at the memory location 0x80001800. this is PSO reload compatible, which means that any application can jump back there so that you can load another binary without reboot. the libogc exception handler also jumps to this address (when pressing Z on a GameCube pad)
  • the protocol used for uploading is compatible to the official geckotool (you can use your client of choice)
  • as always, this is open source ;)

Architecture

geckoloader consists of 3 parts

  • stub
  • loader
  • boot
  • the boot code contains the other two code parts, and it is the executable that you have to run. it will write the loader code to the onboard usbgecko flash and place the stub into memory
  • the boot code will then execute the stub
  • the stub's job is to read the loader code from flash and execute it
  • finally, the loader code will accept incoming Wii executables sent using a client application from the pc side
  • the chosen architecture has the advantage that the tiny stub is the only component which has to stay intact in memory. while the usage of the usbgecko onboard flash might seem unnecessary at first, its purpose is the reloading feature. you will upload and run Wii applications. these in return will allocate memory and write to it. if the loader code would stay somewhere in memory, any executed application might overwrite it this way, but since it sits on the onboard usbgecko flash, no application can corrupt it.

Usage

Wii-side

  • use the Twilight hack in combination with the included geckoloader.elf to get this running
  • the boot code will show up
  • you have to write the loader code to the onboard usbgecko flash once, press the Wii RESET button when asked to
  • after that you will see the loader code in action
  • use a compatible client (like the included one geckoupload, or the official windows geckotool) to send a Wii binary
  • the transfered binary should execute
  • if you loaded a game/app which has an option to jump back to 0x80001800, you will be presented with the loader code again. from there, you can transfer another binary again (no reboot required)

hint: try to upload the included test.elf first. it just prints a string to screen and has an option to jump back to the loader

Client-side

  • the client uses a default tty device (except on windows), you can overwrite it using the environment variable USBGECKODEVICE
  • Set USBGECKODEVICE too the com your device uses (example, COM4)
  • RESTART AFTER SETTING YOUR ENV VAR !!! ELSE IT WILL NOT WORK
  • make sure that your console is ready to receive an executable
  • pass the filename of the binary to geckoupload, for example:geckoupload test.elf

you can use this client to transfer

  • wii .dol's and .elf's to the geckoloader described on this page
  • gamecube .dol's to the official usbgecko boot dvd

Windows Driver Setup

If your USBGecko install didn't provide you with a COM port then try the following:

  1. Go to device manager and select the device 'USB Serial Converter' which is the USB Gecko device.
  2. Right click and select properties, then go to the 'advanced' tab.
  3. Click the 'Load VCP' box so its selected then press ok.
  4. Unplug the cable and then reinsert.

This should now give you a COM port, which you will need for geckoupload.

Notes

  • you can not run GameCube binaries with this loader since we're working in Wii mode here (that's a good thing)
  • the default libogc base address for Wii homebrew is at 0x80003f00. this gives a PSO compatible stub 0x1900 bytes of memory for code. hence, the stub's main() functions were written in c so that it's easy to improve/fix
  • the loader initially puts a received binary in MEM2 to avoid overlaps. it will be relocated from there. unfortunately the loader itself has a base address in MEM1. putting it in MEM2 is on my TODO list
  • you can use the trucha signer to boot this app straight from dvd

Changelog

v0.0.4

  • HBC assimilated geckoloader. v0.0.4 is a pure gamecube-only version

'v0.0.3

  • a gamecube pad isn't required anymore, the wii reset button is used to confirm the flash process
  • the loader code is executed straight away if it has been flashed before (no interaction required)
  • .elf file support thanks to tmbinc
  • the stub doesn't overwrite the globals anymore, fixed by WinterMute
  • a received binary is now written to MEM2 before relocating
  • ported the client to win32 (binary included)
  • the client now uses default device names on linux and os x
  • the audio and dsp subsystems are initialized on reloading (no more annoying noise)

v0.0.2b

  • fixed a timing issue in the usbgecko flash code. since i couldn't reproduce this on my setup, thanks go out to bLAStY and NoNameNo for helping me hunting this one down
  • the included client now works on os x thanks to bushing
  • added an extra check for malformed .dol files (some doltool converted .elf's)
  • included a tiny test application

*v0.0.2'

  • first public release

Thanks

  • shagkur, for helping me getting the stub working and providing the linkerscript
  • the DevkitPro team
  • team tweezers for making all of this possible
  • all open source Wii coders
  • nuke for sharing code for his adapter

External links

Advertising: