Hi,
Thanks for the help. I changed the option FALLBACK_SIZE=262144 in the targets/newisys/khepri/Config.lb and I was able to build the khepri.rom file of size 512K. Would be nice to document the same somewhere.
I also managed to try loading the same on a khepri board that I could lay my hands on. However the system did not boot . Is there a way to enable some beep() or something similar early on to know that the processor has started executing the LinuxBIOS code. I do not have a scope or other hardware that I could use to probe. There was some output on the serial but that from the service processor that my khepri board has. Any pointers?
Regards Anil
On 7/12/06, Lu, Yinghai yinghai.lu@amd.com wrote:
Please change FALLBACK_SIZE in MB Config.lb http://config.lb/ to
#default FALLBACK_SIZE=0x40000
YH
*From:* linuxbios-bounces@linuxbios.org [mailto: linuxbios-bounces@linuxbios.org] *On Behalf Of *Anil B G *Sent:* Wednesday, July 12, 2006 7:58 AM *To:* linuxbios@linuxbios.org *Subject:* [LinuxBIOS] Build issue for khepri target
Hi,
I am new to LinuxBIOS. I downloaded the latest snapshot of LinuxBIOSv2 and tried building it for a couple of boards (newisys/intel etc).
I was able to build it for intel but when I tried to build it for newisys/khepri I got the following error:
gcc -o buildrom /home/anil/LinuxBios/LinuxBIOSv2/util/buildrom/buildrom.c ./buildrom linuxbios.strip linuxbios.rom payload 0x20000 0x20000 payload (77000) + linuxbios (131072) size larger than ROM (131072) size! make[1]: *** [linuxbios.rom] Error 1 make[1]: Leaving directory `/home/anil/LinuxBios/LinuxBIOSv2/targets/newisys/khepri/khepri/fallback' make: *** [fallback/linuxbios.rom] Error 1
I disabled the fallback option and then was able to get the khepri.romwhose size was 384K. I am using the FILO as the payload.
Is the size of 384K fine? Has any one used LinuxBIOSv2 on khepri? Would appreciate any help.
Pls. let me know if any addl. info is reqd.
The gcc version is 3.4.3
Regards
Anil