bootstrap code is not running
Hi,
I am working in Board Bring up project on GESBC-9x25 I have made SDCard into 2 partitions(boot & rootfs). I have created bootstrap binary for sdcard support(BOOT.BIN) I have created u-boot.bin & uImage BOOT.BIN, u-boot.bin & uImage kept in my boot partition of SDCard. rootfs kept in rootfs partition of SDCard. inserted my SDCard into board SDCard slot. when i power on the board, only ROM code is executing... It is not taking my images at all... How to tell the processor, have look an SDcard for my remaining images like that. here on my board, i didn't find boot pins.to change order of boot sequence. i want to boot up the board with linux... how to do this... can any one help me plz..... |
Quote:
And did you try reading the user manual?? Seeing their website?? It has a COMPLETE description, downloadable images, and how-to guides. http://www.glomationinc.com/Support/...ers-manual.pdf http://www.glomationinc.com/SupportW...ct.GESBC-9G25i |
bootstrap code is not running
1 Attachment(s)
Hi,
I have gone through all the above mentioned links... Actually, the board will come with pre-installed linux on to board Nand flash... while shipping itself. My requirement is to boot from SDCard,so what i have did is, i erased all the Nand contents by typing in u-boot prompt. u-boot# nand erase clean with that above command, pre-installed bootstrap, u-boot,uImage and rootfs are cleaned and gone... i have prepared all images again and put into my SDcard boot partition I inserted SDCard onto board SD slot. when i power on the board now, only ROM code is executing...and cursor stopped... If i want to change boot sequence,what is the procedure??? and here there is no boot pins on board. can anyone help me please, how to boot linux on this GESBC-9x25 board. Thanks very much. |
Quote:
But it doesn't matter because the first boot device is SPI flash (which doesn't exist on that Glomation board), and the second device is the MMC/SDcard. The NAND flash is the third boot device, so the SDcard has precedence over the NAND flash. So that means that you didn't have to erase the NAND flash. Quote:
How did you format the boot partition? Quote:
What source file did you use? What version? What configuration did you use? Quote:
What version? What configuration did you use? I probably still have a SDcard image for a SAM9G25 project I did a few years ago. I don't recall any difficulties in building it. Regards |
Hi,
I have made only 2 partitions of SDCard by using script in this link... http://processors.wiki.ti.com/index....tition_SD_Card How BOOT STRAP(BOOT.BIN) is built ------------------------------------------------------------------------------------------------------------------------ 1.I cloned the source code from this site. git clone git://github.com/linux4sam/at91bootstrap.git 2.selected and make default configurations for this board. venkatesh@venkatesh:~/at91bootstrap$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- at91sam9x5eksd_uboot_defconfig 3.compiled and created Boot strap binary venkatesh@venkatesh:~/at91bootstrap$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- After this step the binary will be present in "at91bootstrap/binaries" directory You will see "at91sam9x5ek-sdcardboot-uboot-3.8.4.bin" file which is our Boot Strap file... changed it's name to BOOT.BIN and kept in boot partition of SDCard. ____________________________________________________________________________________________________ _____________________ How U-boot is built --------------------------------------------------------------------------------------------------------------------- 1. downloaded u-boot-2015.04 source code from denx site. 2. u-boot configuraton venkatesh@venkatesh:~/u-boot-2015.04$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- at91sam9x5ek_mmc_defconfig 3.u-boot compilation: venkatesh@venkatesh:~/u-boot-2015.04$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- then we will find "u-boot.bin" in parent directory of source. that copied to boot partition of SDCard.. ____________________________________________________________________________________________________ _____________________ Boot sequence for this GESBC-9x25 Board: ROM CODE | BOOT STRAP(BOOT.BIN) | u-boot.bin | uImage | RFS ____________________________________________________________________________________________________ ___________ If i did mistake please correct me... and please help me How to boot linux on GESBC-9x25 board. Thank you very much... |
Quote:
Those are directions for TI Sitara SoCs. You're using an Atmel SAM9 SoC. They may have different requirements. Instead you should be following SD card boot for AT91SAM SoC Quote:
If all you want is source to build, then the better alternative is to use a release tarball: https://github.com/linux4sam/at91bootstrap/releases Quote:
But before you worry about the toolchain, you need to bisect the problem, and try to determine if AT91Bootstrap has been loaded and tried to execute. Why did you erase the NAND flash? Was the board booting from NAND even though the SDcard was inserted? When you try to boot with the SDcard and only see the "RomBOOT" message (as in your minicom screenshot), type "V#" (your keystrokes will not be echoed). Is there any response? Regards |
All times are GMT -5. The time now is 12:06 AM. |