[U-Boot] trying to bring linux-2.6.32.3 from RAM?

From: ogara <radivojejovanovic@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
Date: Wed, 28 Apr 2010 12:52:04 -0700 (PDT)	[thread overview]
Message-ID: <28393231.post@talk.nabble.com> (raw)
In-Reply-To: <201004282134.39118.marek.vasut@gmail.com>

ogara wrote:
> 
>>Hi, the image is probably corrupted ? Also, why do you load it to 0x8000 ?
It's 
>>relocated anyway, but this way it has to be relocated twice)
> 
I boot it from 0x8000 because the image was built with load and execute
address 0x8000. Image is not corrupted for sure since I can boot this exact
file from hard drive without any problems. I was just wondering if my
procedure is correct or I am missing something? Could you explain what do
you mean by "this way it has to be relocated twice".
Ogi

Marek Vasut wrote:
> 
> Dne St 28. dubna 2010 20:50:35 ogara napsal(a):
>> Hi All,
>> I am trying to bring linux from RAM. I have compiled the kernel and
>> created
>> uImage. I bring the image over tftp into the memory and then execute
>> bootm
>> memaddress. Unfortunately here is the output from my command line:
>> 
>>  tftp 0x8000 ipaddress:uImage
>> Using egiga0 device
>> TFTP from server ipaddress; our IP address is ipaddress; sending through
>> gateway ipaddress
>> Filename 'uImage'.
>> Load address: 0x8000
>> Loading:
>> #################################################################
>>         
>> #################################################################
>>         
>> #################################################################
>>          ###################
>> done
>> Bytes transferred = 3132020 (2fca74 hex)
>> bootm 0x8000
>> ## Booting kernel from Legacy Image at 00008000 ...
>>    Image Name:   Linux-2.6.32.3
>>    Created:      2010-04-28  18:44:34 UTC
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    3131956 Bytes =  3 MB
>>    Load Address: 00008000
>>    Entry Point:  00008000
>>    Verifying Checksum ... OK
>>    XIP Kernel Image ... OK
>> OK
>> 
>> Starting kernel ...
>> 
>> undefined instruction
>> pc : [<00008008>]          lr : [<00647d1c>]
>> sp : 005ffce8  ip : 000008e0     fp : 000006fc
>> r10: 00724db0  r9 : 005fff90     r8 : 005fffcc
>> r7 : 00000002  r6 : 0072372d     r5 : 00000154  r4 : 00000000
>> r3 : 00008000  r2 : 00000100     r1 : 000006fc  r0 : 0001c200
>> Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
>> Resetting CPU ...
>> 
>> Now, the image is good for sure because I do not have issues bringing
>> this
>> image from the hard drive. Do I need anything else (ftd or ramdisc) to
>> boot
>> from RAM or the procedure presented is correct?
>> my bootargs are:
>> bootargs=console ttyS0,115200 root /dev/ram rw
>> 
>> Thank you for your help,
>> Ogi
> 
> Hi, the image is probably corrupted ? Also, why do you load it to 0x8000 ?
> It's 
> relocated anyway, but this way it has to be relocated twice)
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://old.nabble.com/trying-to-bring-linux-2.6.32.3-from-RAM--tp28392641p28393231.html
Sent from the Uboot - Users mailing list archive at Nabble.com.