Lakshminarayana, Yes, we are using u-boot. The "loadaddr" is available in the u-boot code?
-Hithesh On Wed, Jan 23, 2013 at 10:11 PM, laxmi narayana <[email protected]>wrote: > Hi Hithesh, > I think you are using u-boot in your hardware board. In u-boot you should > set your environment variables like "loadaddr" (to which ram address linux > should be loaded). > Regards, > Lakshminarayana L. > > > On Tue, Jan 22, 2013 at 11:46 PM, Saurabh Shandilya < > [email protected]> wrote: > >> >> >> >> On Sun, Jan 20, 2013 at 10:09 PM, Hithesh <[email protected]> wrote: >> >>> Saurabh, >>> >>> The same image boots up fine on a different board. By different board, I >>> mean the same circuit, same ICs, everything is same. >>> Here are the paste bin links - >>> Bad boot - http://pastebin.com/suAj6HKp >>> Good boot - http://pastebin.com/uw4Z6VGR >>> >>> Sorry for the late reply, Life is not glib at all :( >> >> As I saw in the pastebin files, the footprint of images is *found* >> correct in both the cases and hence in good one case : >> >> 1. >> -E- File size 2584408 <-> Max allowed size 32 >> 2. >> 3. -I- Loading to 0x70007fc0 with size 0x00276f58 >> >> >> works correct as (second the address is in hex) and the address to boot >> on is also correct. >> While for the bad one, >> >> 1. >> -E- File size 2584408 <-> Max allowed size 32 >> 2. >> 3. -I- Loading to 0xffffffbf with size 0x0000003f >> 4. >> >> the address to load up the bin image is wrong and hence the total image >> cannot be placed out there, the only remaining space left is 0x000003f out >> of total 0xfffffff >> So, as also mentioned by Shakthi Sir, I also think that the environment >> variable for the bootloader to load up the image is wrong. >> You may try by getting the control over the bootloader shell and then >> check the value of the variables out there. >> >> >>> On Sun, Jan 20, 2013 at 6:52 PM, Saurabh Shandilya < >>> [email protected]> wrote: >>> >>>> >>>> On Jan 20, 2013 12:06 AM, "newbiex" <[email protected]> wrote: >>>> > >>>> > Hi group, >>>> > >>>> > I am a hardware engineer. I am new to embedded linux. >>>> > I need some help in understanding the messages during embedded linux >>>> boot - >>>> > One of our board is not booting up. The CPU we are using is Atmel >>>> SAM9G45 >>>> > >>>> > Here's the boot message. Can some one explain what's happening at the >>>> end - >>>> > >>>> > >>>> > -- pico-SAM9G45 Bootstrap 3.0 -- >>>> > >>>> > -- AT91SAM9G45-EK >>>> > >>>> > -- Compiled: Jan 27 2011 09:45:18 -- >>>> > >>>> > -I- RTC Config: rcen: 1 osc32en: 0 osc32byp: 0 oscsel: 0 >>>> > >>>> > -I- RTC Config: rcen: 0 osc32en: 1 osc32byp: 0 oscsel: 1 >>>> > >>>> > -I- Setting: MCK = 133MHz >>>> > >>>> > -I- Init DDRAM >>>> > >>>> > -I- Init second bank SDRAM >>>> > >>>> > -I- Loading to 0x70000000 >>>> > >>>> > -I- MEDSdcard init >>>> > >>>> > -I- DMAD_Initialize channel 0 >>>> > >>>> > -I- Card Type 2, CSD_STRUCTURE 1 >>>> > >>>> > -I- SD/MMC TRANS SPEED 25000 KBit/s >>>> > >>>> > -I- SD 4-BITS BUS >>>> > >>>> > -I- CMD6(2) arg 0x80FFFF01 >>>> > >>>> > -I- SD HS Enable >>>> > >>>> > -I- SD/MMC TRANS SPEED 50000 KBit/s >>>> > >>>> > -I- SD/MMC card initialization successful >>>> > >>>> > -I- Card size: 3781 MB >>>> > >>>> > -I- Copy "linux.bin" from SdCard to 0x70000000 >>>> > >>>> > -E- File size 2584408 <-> Max allowed size 32 >>>> > >>>> > -I- Loading to 0xffffffbf with size 0x0000003f >>>> > >>>> > -I- MEDSdcard init >>>> > >>>> > -I- DMAD_Initialize channel 0 >>>> > >>>> > -I- Card Type 2, CSD_STRUCTURE 1 >>>> > >>>> > -I- SD/MMC TRANS SPEED 25000 KBit/s >>>> > >>>> > -I- SD 4-BITS BUS >>>> > >>>> > -I- CMD6(2) arg 0x80FFFF01 >>>> > >>>> > -I- SD HS Enable >>>> > >>>> > -I- SD/MMC TRANS SPEED 50000 KBit/s >>>> > >>>> > -I- SD/MMC card initialization successful >>>> > >>>> > -I- Card size: 3781 MB >>>> > >>>> > -I- Copy "linux.bin" from SdCard to 0xffffffbf >>>> > >>>> > -E- File size 2584408 <-> Max allowed size 63 >>>> > >>>> > -I- Modified jump to 0xffffffff >>>> > >>>> > The messages stop here. >>>> > >>>> > In a good board the copy destination location of linux.bin is >>>> 0x70007fc0 (as seen below). >>>> > Why is the location incorrect in the bad board. >>>> > -I- Copy "linux.bin" from SdCard to 0x70007fc0 >>>> > >>>> > -I- Modified jump to 0x70008000 >>>> > >>>> > Uncompressing Linux... done, booting the kernel. >>>> > >>>> >>>> as i can guess, that your board is initiallising your 4gb high speed >>>> sd- card but not able to jump to the specific address. >>>> Do check the linux.bin image, it may be incorrect. Try recompiling >>>> that image. >>>> Also, if you can get the bootloader shell then from there you may try >>>> to load the image at ram and try to execute there. Do check the footprint >>>> of the image in both the cases. The address to place the image is very >>>> specific to harware/board so just give a look to the documentation of the >>>> board. >>>> And yes, any docs. & full boot up messages for a working board is >>>> really needed for debugging. >>>> Try pastebin. >>>> >>>> > >>>> > -- >>>> > Mailing list guidelines and other related articles: >>>> http://lug-iitd.org/Footer >>>> >>>> -- >>>> Mailing list guidelines and other related articles: >>>> http://lug-iitd.org/Footer >>>> >>> >>> -- >>> Mailing list guidelines and other related articles: >>> http://lug-iitd.org/Footer >>> >> >> >> >> -- >> Regards, >> saurabh shandilya >> http://about.me/shandilyasaurabh >> www.beyondszine.wordpress.com >> 9910118292 >> >> -- >> Mailing list guidelines and other related articles: >> http://lug-iitd.org/Footer >> > > -- > -- > Mailing list guidelines and other related articles: > http://lug-iitd.org/Footer > > > > -- -- Mailing list guidelines and other related articles: http://lug-iitd.org/Footer
