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 13:26:11 -0700 (PDT) [thread overview]
Message-ID: <28393589.post@talk.nabble.com> (raw)
In-Reply-To: <4B8557E2E5753944B2BB2E52F7C2A30C02C0C8AA@MAIL.AES.local>
Rick,
I have custom board with DRAM starting at 0x00000000 - 0x20000000 so I could
not load it to 0x80000000 since I do not have that much memory. I noticed in
your report that the load address is 0x80000000 but the kernel image was
built with:
Load Address: 80008000
Entry Point: 80008000.
I was wondering what does your bootm command line looks like and if yours
bootargs look like mine?
Ogi
Rick Ball wrote:
>
> I think you want to load the kernel to memory at 0x00000000, even though
> the u-boot load address is set to 0x8000 - my kernel, which I load to
> memory at 0x80000000 because that's where my SDRAM is, looks like this:
>
> Load address: 0x80000000
> Loading: #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ##########################
> done
> Bytes transferred = 2128612 (207ae4 hex)
> ## Booting kernel from Legacy Image at 80000000 ...
> Image Name: Linux-2.6.29-rc3-omap1
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2128548 Bytes = 2 MB
> Load Address: 80008000
> Entry Point: 80008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux...........................................................................................................................................
> done, booting the kernel.
>
>
> Rick
>
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
> On Behalf Of Marek Vasut
> Sent: Wednesday, April 28, 2010 2:35 PM
> To: u-boot at lists.denx.de
> Cc: ogara
> Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
>
> 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
> _______________________________________________
> 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--tp28392641p28393589.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-04-28 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 18:50 [U-Boot] trying to bring linux-2.6.32.3 from RAM? ogara
2010-04-28 19:34 ` Marek Vasut
2010-04-28 19:44 ` Rick Ball
2010-04-28 20:26 ` ogara [this message]
2010-04-28 20:33 ` Rick Ball
2010-04-28 21:18 ` ogara
2010-04-29 4:53 ` Nikumbh, Raj
2010-04-28 19:52 ` ogara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28393589.post@talk.nabble.com \
--to=radivojejovanovic@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox