http://etherboot.org/wiki/ 2026-04-04T01:34:50-07:00 http://etherboot.org/wiki/ http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico text/html 2006-07-20T08:12:17-07:00 http://etherboot.org/wiki/dev/bin2intelhexc?rev=1153408337&do=diff Bin2IntelHex.c This is code for a ROM binary converter from Binary to IntelHex format. /* name : bin2intelhex.c * from : Jean Marc Lacroix <jeanmarc.lacroix@free.fr> * date : 06/12/1997. * abstract : Y have rewrite this program from ????? with some modifications * to add : * - the Intel specification. * - correct a bug because my prom programmer don't understand the * initial format. Y suspect a bug in the calcul of the lrc * in the original program. * - correct the format of printf … text/html 2006-07-16T10:01:15-07:00 http://etherboot.org/wiki/dev/devmanual?rev=1153069275&do=diff EtherBoot developers' manual This manual is probably outdated and needs some rework. Submitted unchanged into this wiki to allow transition to the upcoming wiki-only website by Anselm Martin Hoffmeister. Revision information Written by Ken Yap, Georg Baum text/html 2010-05-02T04:29:11-07:00 http://etherboot.org/wiki/dev/fnrec?rev=1272799751&do=diff Overview Fnrec is a tool that collects a trace of functions called before a crash or hang. It can be used to determine what led to the issue and which function was called last. How tracing works Fnrec uses the gcc -finstrument-functions compiler flag to trace each function call and record it into a memory buffer. The memory buffer has a magic number at the start to identify it as valid and not just random bytes in memory. As gPXE runs, it records each function call into the memory buffer. … text/html 2010-03-28T21:27:45-07:00 http://etherboot.org/wiki/dev/gdbstub?rev=1269836865&do=diff GDB remote debugging Overview You can use the GNU Project Debugger (GDB) to debug gPXE. You either need two computers or virtualization software (e.g. QEMU). One host runs gPXE while the other runs GDB. gPXE supports debugging via serial port or over the network. For serial, you need a null modem serial cable. For network, you need the machine to be connected to a network with UDP port 43770 traffic allowed. text/html 2007-08-18T14:43:41-07:00 http://etherboot.org/wiki/dev/netdriverapi?rev=1187473421&do=diff gPXE Network Driver API Documentation net_device::open ( struct net_device *netdev ) Here MAC address is programmed over the device (NIC). Then receive buffer for the device is created and its memory is released in net_device::close(). This address for the ring buffer is transfer to the NIC’s register. This is the place where configuration of the device is also done like enable transmission, receive. Other parameters like burst rate, transfer threshold, reception of broadcast and multicast … text/html 2009-10-17T03:33:25-07:00 http://etherboot.org/wiki/dev/prefixdebugging?rev=1255775605&do=diff This page describes the boot prefixes and debugging tips. Debugging a boot prefix can be challenging because most code is assembly and it is not possible to call into gPXE for utility and I/O functions. How to identify a prefix issue A crash, hang, or other issue may be prefix-related if it occurs before gPXE prints its banner. If gPXE fails to load then it may be a prefix issue. Odd behavior when exiting gPXE may also be prefix issues. text/html 2006-07-16T08:15:22-07:00 http://etherboot.org/wiki/dev/todo?rev=1153062922&do=diff Development would be boring without the ToDo-List dangling over our heads like Damokles' sword... * Separating MII functionality into mii.c * Check EtherBoot default timeout settings * Improving ATA-over-Ethernet above "demo" status * Improve EtherBoot documentation