Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a cirrus logic EP9307(ARM9) based board with a SDRAM and FLASH. At present the booting sequence is RS232 -> Redboot -> Ethernet -> Zimage -> Ethernet -> Ramdisk.
I want to remove the flash chip and load the kernel from SDCARD. This chip has a inbuilt bootloader to boot from either a serial port, EEPROM, etc, I have written second stage bootloader to initialize the sdcard and load a test program from it. I want to load the kernel directly from the second stage bootloader(this will uncompress the zimage and then load the kernel on sdram) instead of using redboot.
I have been reading over the internet about passing the kernel tags which has all the target hardware information.
Has any one done some thing similar. Any pointers would help me a lot.
Is your obstacle how to pass arguments to the kernel? If so, then a possible solution may be to build a kernel with acceptable default arguments. I've just done this for an ARM based SBC, and it seems to work. If you set the arguments in the kernel directly, it will overcome the problem of your bootloader having to supply them. I don't know the mechanics of passing arguments to a kernel. I suppose there must be some documented data structure that gets put somewhere that the kernel can find it.
make menuconfig -> Boot Options -> Default kernel command string
I am trying to pass the tagged list to the kernel. At present I have redboot which decompresses the kernel, passes kernel parameters and then loads the kernel. Is there any way I can see what parameters are being passed by redboot.
I am using 2.6.8.1 kernel. Where can i get more information on Zimage created by the kernel. I am trying to find the decompression algorithim for Zimage.
I have a EP9307 based custom designed board. At present it is using the same setup as the development kit for EP9307.
At present we use redboot to download zimage on to flash and then boot the kernel by loading it into sdram.
I want to load the Zimage from SDCARD directly. I have modified first stage bootloader to load from EEprom, This in turn loads the second stage bootloader which initializes the SDCARD and loads a test program.
All the paramters are passed as a tags list to the kernel. At present redboot is passing them. Is there any way to see what these paramaters are. Secondly do i need to have a decompression code in the second stage bootloader to decompress Zimage.
According to the second link Zimage already has a decompression code inbuilt which is used to decompress Zimage.
I am bit confused here. Can some please give some inputs on this.
All I want to do is load Zimage, Ramdisk from SDCARD. I am new to linux environment.
I believe (and please correct me if I'm wrong) the decompression code gets built into the kernel, and is invoked by the kernel itself. No need to decompress a priori. I doubt very much that there is any runtime tool that displays the tags passed to the kernel. I'm not familiar with redboot, but assuming it is open-source, you should be able to tell at least what tags are used. The content of the tags may be discernible from boot-time configuration data, if it exists.
--- rod.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.