Overview | makebootp | netboot | unpack | display | evo_eeprom |
As noted elsewhere Wyse thin clients actually have two BIOSs:
During a software development cycle it is real pain to have to repeatedly flash the thin client's memory, but if you just use NetXfer to directly download and execute your code you'll have other problems or side effects due to the simple BIOS.
My solution to the problem was to take 'grub legacy' source code and throw away most of it except for the networking bit. What's left is a simple DHCP client (to get an IP address), an SFTP client to download code from the server, and bit of code that understands the file format used by NetXfer. This is netboot which is intended to be programmed into the flash memory of the Compaq/Wyse thin client.
What this gives you is something that behaves just like NetXfer - but without the need to hit the 'p' key on power-up. (For convenience my default is to configure the setup to use the higher numbered ports to avoid conflict with my Netgear router/DHCP server). But another big gain is that any downloaded code will be running with the fully featured BIOS in place. This makes a development/test cycle much easier - right BIOS in place, no need to re-flash the memory - with the only downside that it takes a little longer to boot.
Once you're happy with your software you have to option of flashing the thin client with your new firmware or just continuing to boot from the network - your choice.
Just type make in the tools/netboot directory to get loader.bin.
Having compiled the netboot program all you need to do is:
makebootp -f F576_Wye74.bin -L loader.bin
..to create a bootp.bin file that's ready to be downloaded and flashed into the thin client using the standard NetXfer approach. (The above example shows a build for a Wyse WT3125SE).
With the bootloader programmed into flash you'll see the following behaviour: