system does not handle this correctly. It expects there to be falback and normal images. So you have to trick it to make it work right.
The trick is to set FALLBACK_SIZE=ROM_SIZE
The default config has it set to 0x30000. I suspect it was set that way to allow for the addition of the VGA bios that can't be included in the default distribution.
I tested and for me this builds a 256k image that has the reset vector in the right spot. I don't have any epia hardware so I can't test that it actually still boots though.
On 6/18/06, Richard Smith smithbone@gmail.com wrote:
system does not handle this correctly. It expects there to be falback and normal images. So you have to trick it to make it work right.
The trick is to set FALLBACK_SIZE=ROM_SIZE
Looks like you need to comment out the following lines in the config as well or I think the addresses of the various entry points will be wrong.
option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x30000
On Sun, 18 Jun 2006 16:23:53 -0500, Richard Smith wrote
On 6/18/06, Richard Smith smithbone@gmail.com wrote:
system does not handle this correctly. It expects there to be falback and normal images. So you have to trick it to make it work right.
The trick is to set FALLBACK_SIZE=ROM_SIZE
Looks like you need to comment out the following lines in the config as well or I think the addresses of the various entry points will be wrong.
option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x30000
Don't know if I missed something, but this Config.lb gives the same reboots after kernel has been loaded :(
/Per
----8<---------------------------------------------------
# Sample config file for EPIA-M # This will make a target directory of ./epia-m
target epia-m
mainboard via/epia-m
option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1
option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1
### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=0x30000
## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000
# ### ### Compute the start location and size size of ### The linuxBIOS bootloader. ###
# # EPIA-M # #romimage "normal" # option USE_FALLBACK_IMAGE=0 # option ROM_IMAGE_SIZE=0xc000 # option ROM_SECTION_OFFSET=0x10000 # option ROM_SECTION_SIZE=0x18000 # option XIP_ROM_BASE=0xfffd0000 # option LINUXBIOS_EXTRA_VERSION=".0Normal" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi # payload /filo.elf #end
romimage "fallback" option FALLBACK_SIZE=ROM_SIZE option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 # option ROM_SECTION_OFFSET=0x10000 # option ROM_SECTION_SIZE=0x30000 # option XIP_ROM_BASE=0xfffe0000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi payload /filo.elf # payload /memtest end
buildrom ./linuxbios.rom ROM_SIZE "fallback"
----8<---------------------------------------------------
Don't know if I missed something, but this Config.lb gives the same reboots after kernel has been loaded :(
All I was trying to solve was your incorrect build size. If it boots at all then my suggestion worked. *grin*