Specifications

Why?
Answer:
Most probably everything is OK. The message is printed because the flash sector or ERPROM
containing the environment variables has never been initialized yet. The message will go away as
soon as you save the envrionment variables using the saveenv command.
14.2.6. Net: No ethernet found
Question:
I have ported U-Boot to a custom board. It seems to boot OK, but it prints:
Net: No ethernet found.
Why?
Answer:
Some network drivers (especially on ppc4xx) respond with such a message when no valid MAC
address has been defined. Please make sure that a valid MAC address has been defined in the
environment (using the "setenv" command). Then store the environment (using the "saveenv"
command). After the next reboot, the Ethernet interface should be available.
14.2.7. Wrong debug symbols after relocation
Question:
I want to debug U-Boot after relocation to RAM, but it doesn't work since all the symbols are at
wrong addresses now.
Answer:
To debug parts of U-Boot that are running from ROM/flash, i. e. before relocation, just use a
command like "powerpc-linux-gdb uboot" as usual.
For parts of U-Boot that run from RAM, i. e. after relocation, use "powerpc-linux-gdb"
without arguments, and use the add-symbol-file command in GDB to load the symbol table at
the relocation address in RAM. The only problem is that you need to know that address, which
depends on RAM size, length reserved for U-Boot, size of "protected RAM" area, etc. If in doubt,
enable DEBUG mode when building U-Boot so it prints the address to the console.
Hint: I use definitions like these in my .gdbinit file:
define rom
symbol-file
file u-boot
end
define ram
symbol-file
add-symbol-file u-boot 0x01fe0000
end
Note: when you want to switch modes during one debug session (i. e. without restarting GDB) you
can "delete" the current symbol information by using the symbol-file command without
arguments, and then either using "symbol-file u-boot" for code before relocation, or
14.2.7. Wrong debug symbols after relocation 162