Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
The load address actually doesn't matter. You can tftp your uImage anywhere in RAM and then just give a bootm command. It will get the kernel and booting would happen fine. Though as I see in your bootargs you don't define a filesystem so kernel might hang there. Anyways you should be able to boot the kernel. Hope this helps. -Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of ogara Sent: Thursday, April 29, 2010 2:49 AM To: u-boot@lists.denx.de Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? I understand your point. My memory alignment was off. So now I get: ## Booting kernel from Legacy Image at ... 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: 8000 Entry Point: 8000 Verifying Checksum ... OK ERROR: can't get kernel image! As I said before this file works of hard drive no problem (I just did binary comparison and file matches). Rick Ball wrote: > > Yes, but I think you need to load at address 0 instead of 0x8000, just > like I load at 0x8000 instead of 0x80008000. My kernel is also > compiled to start at an offset of 0x8000, just like yours, but I think the > image has 0x8000 of reserved space at the beginning (so you load it to 0, > but it starts executing at 0x8000). > > I don't think the bootargs are even coming into play - you're executing a > bad instruction at 0x8008 because you loaded the kernel at 0x8000 instead > of 0 (so you're trying to execute the uninitialized reserved space). > > Try changing your tftp command to load at 0 instead of 0x8000, and I think > it should boot. > > Rick > > -Original Message- > From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] > On Behalf Of ogara > Sent: Wednesday, April 28, 2010 3:26 PM > To: u-boot@lists.denx.de > Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? > > > Rick, > I have custom board with DRAM starting at 0x - 0x2000 so I > could not load it to 0x8000 since I do not have that much memory. I > noticed in your report that the load address is 0x8000 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 0x, even >> though the u-boot load address is set to 0x8000 - my kernel, which I >> load to memory at 0x8000 because that's where my SDRAM is, looks like >> this: >> >> Load address: 0x8000 >> Loading: >> # >> >> # >> >> # >> >> # >> >> # >> >> # >> ## >> done >> Bytes transferred = 2128612 (207ae4 hex) ## Booting kernel from Legacy >> Image at 8000 ... >>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-boun...@lists.denx.de >> [mailto:u-boot-boun...@lists.denx.de] >> On Behalf Of Marek Vasut >> Sent: Wednesday, April 28, 2010 2:35 PM >> To: u-boot@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:
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
I understand your point. My memory alignment was off. So now I get: ## Booting kernel from Legacy Image at ... 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: 8000 Entry Point: 8000 Verifying Checksum ... OK ERROR: can't get kernel image! As I said before this file works of hard drive no problem (I just did binary comparison and file matches). Rick Ball wrote: > > Yes, but I think you need to load at address 0 instead of 0x8000, just > like I load at 0x8000 instead of 0x80008000. My kernel is also > compiled to start at an offset of 0x8000, just like yours, but I think the > image has 0x8000 of reserved space at the beginning (so you load it to 0, > but it starts executing at 0x8000). > > I don't think the bootargs are even coming into play - you're executing a > bad instruction at 0x8008 because you loaded the kernel at 0x8000 instead > of 0 (so you're trying to execute the uninitialized reserved space). > > Try changing your tftp command to load at 0 instead of 0x8000, and I think > it should boot. > > Rick > > -Original Message- > From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] > On Behalf Of ogara > Sent: Wednesday, April 28, 2010 3:26 PM > To: u-boot@lists.denx.de > Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? > > > Rick, > I have custom board with DRAM starting at 0x - 0x2000 so I > could not load it to 0x8000 since I do not have that much memory. I > noticed in your report that the load address is 0x8000 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 0x, even >> though the u-boot load address is set to 0x8000 - my kernel, which I >> load to memory at 0x8000 because that's where my SDRAM is, looks like >> this: >> >> Load address: 0x8000 >> Loading: >> # >> >> # >> >> # >> >> # >> >> # >> >> # >> ## >> done >> Bytes transferred = 2128612 (207ae4 hex) ## Booting kernel from Legacy >> Image at 8000 ... >>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-boun...@lists.denx.de >> [mailto:u-boot-boun...@lists.denx.de] >> On Behalf Of Marek Vasut >> Sent: Wednesday, April 28, 2010 2:35 PM >> To: u-boot@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: >>> # >>> >>> # >>> >>> # >>>
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
Yes, but I think you need to load at address 0 instead of 0x8000, just like I load at 0x8000 instead of 0x80008000. My kernel is also compiled to start at an offset of 0x8000, just like yours, but I think the image has 0x8000 of reserved space at the beginning (so you load it to 0, but it starts executing at 0x8000). I don't think the bootargs are even coming into play - you're executing a bad instruction at 0x8008 because you loaded the kernel at 0x8000 instead of 0 (so you're trying to execute the uninitialized reserved space). Try changing your tftp command to load at 0 instead of 0x8000, and I think it should boot. Rick -Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of ogara Sent: Wednesday, April 28, 2010 3:26 PM To: u-boot@lists.denx.de Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? Rick, I have custom board with DRAM starting at 0x - 0x2000 so I could not load it to 0x8000 since I do not have that much memory. I noticed in your report that the load address is 0x8000 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 0x, even > though the u-boot load address is set to 0x8000 - my kernel, which I > load to memory at 0x8000 because that's where my SDRAM is, looks like > this: > > Load address: 0x8000 > Loading: # > # > # > # > # > # > ## > done > Bytes transferred = 2128612 (207ae4 hex) ## Booting kernel from Legacy > Image at 8000 ... >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-boun...@lists.denx.de > [mailto:u-boot-boun...@lists.denx.de] > On Behalf Of Marek Vasut > Sent: Wednesday, April 28, 2010 2:35 PM > To: u-boot@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 8000 ... >>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: 8000 >>Entry Point: 8000 >>Verifying Checksum ... OK >>XIP Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> undefined instruction >> pc : [<8008>] lr : [<00647d1c>] >> sp : 005ffce8 ip : 08e0 fp : 06fc >> r10: 00724db0 r9 : 005fff90 r8 : 005fffcc >> r7 : 0002 r6 : 0072372d r5 : 0154 r4 : >> r3 : 8000 r2 : 0100 r1 : 06fc r0 : 0001c200 >> Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... >> >>
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
Rick, I have custom board with DRAM starting at 0x - 0x2000 so I could not load it to 0x8000 since I do not have that much memory. I noticed in your report that the load address is 0x8000 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 0x, even though > the u-boot load address is set to 0x8000 - my kernel, which I load to > memory at 0x8000 because that's where my SDRAM is, looks like this: > > Load address: 0x8000 > Loading: # > # > # > # > # > # > ## > done > Bytes transferred = 2128612 (207ae4 hex) > ## Booting kernel from Legacy Image at 8000 ... >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-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] > On Behalf Of Marek Vasut > Sent: Wednesday, April 28, 2010 2:35 PM > To: u-boot@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 8000 ... >>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: 8000 >>Entry Point: 8000 >>Verifying Checksum ... OK >>XIP Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> undefined instruction >> pc : [<8008>] lr : [<00647d1c>] >> sp : 005ffce8 ip : 08e0 fp : 06fc >> r10: 00724db0 r9 : 005fff90 r8 : 005fffcc >> r7 : 0002 r6 : 0072372d r5 : 0154 r4 : >> r3 : 8000 r2 : 0100 r1 : 06fc 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@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > ___ > U-Boot mailing list > U-Boot@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. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
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 8000 ... >>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: 8000 >>Entry Point: 8000 >>Verifying Checksum ... OK >>XIP Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> undefined instruction >> pc : [<8008>] lr : [<00647d1c>] >> sp : 005ffce8 ip : 08e0 fp : 06fc >> r10: 00724db0 r9 : 005fff90 r8 : 005fffcc >> r7 : 0002 r6 : 0072372d r5 : 0154 r4 : >> r3 : 8000 r2 : 0100 r1 : 06fc 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@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. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
I think you want to load the kernel to memory at 0x, even though the u-boot load address is set to 0x8000 - my kernel, which I load to memory at 0x8000 because that's where my SDRAM is, looks like this: Load address: 0x8000 Loading: # # # # # # ## done Bytes transferred = 2128612 (207ae4 hex) ## Booting kernel from Legacy Image at 8000 ... 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-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Marek Vasut Sent: Wednesday, April 28, 2010 2:35 PM To: u-boot@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 8000 ... >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: 8000 >Entry Point: 8000 >Verifying Checksum ... OK >XIP Kernel Image ... OK > OK > > Starting kernel ... > > undefined instruction > pc : [<8008>] lr : [<00647d1c>] > sp : 005ffce8 ip : 08e0 fp : 06fc > r10: 00724db0 r9 : 005fff90 r8 : 005fffcc > r7 : 0002 r6 : 0072372d r5 : 0154 r4 : > r3 : 8000 r2 : 0100 r1 : 06fc 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@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
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 8000 ... >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: 8000 >Entry Point: 8000 >Verifying Checksum ... OK >XIP Kernel Image ... OK > OK > > Starting kernel ... > > undefined instruction > pc : [<8008>] lr : [<00647d1c>] > sp : 005ffce8 ip : 08e0 fp : 06fc > r10: 00724db0 r9 : 005fff90 r8 : 005fffcc > r7 : 0002 r6 : 0072372d r5 : 0154 r4 : > r3 : 8000 r2 : 0100 r1 : 06fc 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@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] trying to bring linux-2.6.32.3 from RAM?
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 8000 ... 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: 8000 Entry Point: 8000 Verifying Checksum ... OK XIP Kernel Image ... OK OK Starting kernel ... undefined instruction pc : [<8008>] lr : [<00647d1c>] sp : 005ffce8 ip : 08e0 fp : 06fc r10: 00724db0 r9 : 005fff90 r8 : 005fffcc r7 : 0002 r6 : 0072372d r5 : 0154 r4 : r3 : 8000 r2 : 0100 r1 : 06fc 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 -- View this message in context: http://old.nabble.com/trying-to-bring-linux-2.6.32.3-from-RAM--tp28392641p28392641.html Sent from the Uboot - Users mailing list archive at Nabble.com. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
