Re: Error in compiling STPC Consumer
On Thu, 24 Mar 2005 05:54:17 + (GMT), Ramesh Chhaba [EMAIL PROTECTED] wrote: Yes Sir , u was right that I was missing that payload = line in configuration :) So I have aded that line and also enabled STD_FLASH and ELF_BOOT options and also added PAY_LOAD_SIZE = 64KB and ROM_SIZE =126KB But I want to make my romimage within 256KB So what options I acn change to do that currently my image is 356 (approx) KB PAY_LOAD_SIZE is not a maximum size. its the blocksize option thats used in the 'dd' statemnet that copies the payload into a file. So 64k is the minimum it will be but it could be 128k, 192k, 256k, etc. Make your ROM_SIZE be the size you want the image - payload size. You can see all the magic for this in the makefile that the config tool generates. I remember I had to tweak with my numbers till I got to to come out the right size. 356k seems a little large for just linubios and etherboot. How big is your payload? -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
On Thu, 24 Mar 2005, Richard Smith wrote: On Thu, 24 Mar 2005 05:54:17 + (GMT), Ramesh Chhaba [EMAIL PROTECTED] wrote: Yes Sir , u was right that I was missing that payload = line in configuration :) So I have aded that line and also enabled STD_FLASH and ELF_BOOT options and also added PAY_LOAD_SIZE = 64KB and ROM_SIZE =126KB But I want to make my romimage within 256KB So what options I acn change to do that currently my image is 356 (approx) KB PAY_LOAD_SIZE is not a maximum size. its the blocksize option thats used in the 'dd' statemnet that copies the payload into a file. So 64k is the minimum it will be but it could be 128k, 192k, 256k, etc. Make your ROM_SIZE be the size you want the image - payload size. You can see all the magic for this in the makefile that the config tool generates. I remember I had to tweak with my numbers till I got to to come out the right size. 356k seems a little large for just linubios and etherboot. How big is your payload? this is a clear FAQ entry. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
Second thing I have got the BIOS writer guide for STPC So If I think I changes the replaces the code of STPC_ELITE for that of STPC_ATLAS then I can make it for STPC_ATLAS If you are going to have to do a lot of re-write work I encourage you to start over with V2. V1 is a dead end product and will be very difficult for the linuxbios developers to support you as we are all focusing on V2. V2 is so much nicer to work with compared to V1. In V2 almost everything is in C rather than assembly, even all your RAM init code is C due to Eric's marvelous romcc which is a C compiler designed to use registers rather than RAM. The STPC Atlas is basically a fast cryix 486 so I don't know what impact that has on romcc due to its smaller register set and if its been tested on that arch much but its shouldn't be too much effort to make it work. Right Eric? I'll be happy to help you with V2. We have several boards that use the Atlas here at bitworks and I'd love to see them boot linuxbios rather than what we are using now. However, since what I have now works I don't have much leverage at spending developemnt $$ on replacing it. It would be really nice however to be able to boot from IDE CD-ROM or USB which is something our current BIOS can't do. But I have systems that I can test on and help you get V2 up and going. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
this is a clear FAQ entry. For v1 yes but not for v2 and most of our docs now are all for v2. I think I would still make v1 people ask so we can tell them not to use v1. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
On Thu, 24 Mar 2005, Richard Smith wrote: think I would still make v1 people ask so we can tell them not to use v1. ah, good point. Hey richard, previous letter, question is: Q. Should I use V1? A. Your previous letter ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
Richard Smith [EMAIL PROTECTED] writes: Second thing I have got the BIOS writer guide for STPC So If I think I changes the replaces the code of STPC_ELITE for that of STPC_ATLAS then I can make it for STPC_ATLAS If you are going to have to do a lot of re-write work I encourage you to start over with V2. V1 is a dead end product and will be very difficult for the linuxbios developers to support you as we are all focusing on V2. V2 is so much nicer to work with compared to V1. In V2 almost everything is in C rather than assembly, even all your RAM init code is C due to Eric's marvelous romcc which is a C compiler designed to use registers rather than RAM. Right. V1 is essentially frozen so nothing that used to work breaks. The very nice thing about V2 that the structure of the code makes it much easier to write reusable code. The STPC Atlas is basically a fast cryix 486 so I don't know what impact that has on romcc due to its smaller register set and if its been tested on that arch much but its shouldn't be too much effort to make it work. Right Eric? All you have to do is not tell romcc it has mmx or sse registers. For a modern memory controller that gets awfully tight but for a simpler memory controller it should be doable, to make everything fit. I almost had the Opteron memory controller working in just 8 registers. Eric ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Error in compiling STPC Consumer
On Wed, 23 Mar 2005 06:53:22 + (GMT), Ramesh Chhaba [EMAIL PROTECTED] wrote: I am using tulip.zelf as payload that I have taken from the rom-o-matic I have copied this file to the place of linux kernel But when i compile it ,it gives eorror. 6+0 records in 6+0 records out /bin/cp -f linuxbios.rom /root/linuxbios_stpc.bin objcopy -O binary -R .note -R .comment -S /usr/src/linux//vmlinux linux.bin objcopy: there are no sections to be copied! make: *** [linux.bin] Error 1 -- Its still trying to add a kernel to your image. Check your payload statement. LinuxBIOS however built. That's whats in linuxbios_stpc.bin it just does not have a payload. -- Richard A. Smith ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
