All of lore.kernel.org
 help / color / mirror / Atom feed
From: el.einad <el.einad@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot 2010 - devkit8000 issue
Date: Wed, 8 Sep 2010 10:50:54 -0700 (PDT)	[thread overview]
Message-ID: <29642184.post@talk.nabble.com> (raw)
In-Reply-To: <AANLkTik63tA7HBGOVrjv7Nm4UzktVvMNYoCWe0_NL38u@mail.gmail.com>


I have a similar issue: I have a beagleboard rev C4 and I'm trying to use a
custom kernel instead of Angstrom. I downloaded the last u-boot using git
from git://gitorious.org/beagleboard-validation/u-boot.git
I compiled this u-boot and then I compiled the MontaVista kernel
(http://www.beagleboard.org/~arago/esc-boston-2009/mvista/beaglekernel24.v1.tar.bz2).
Thus I obtained a uImage.
I copied MLO, u-boot.bin and uImage into a SD card and tryed to boot from
this:

...
OMAP3 beagleboard.org # mmc init
mmc1 is available
OMAP3 beagleboard.org # fatload mmc 0:1 0x82000000 uimage
reading uimage

1568464 bytes read
OMAP3 beagleboard.org # bootm 0x82000000
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.24_mvl5024-beagle_ESC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1568400 Bytes =  1.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... 

----HANGS HERE----

Please help me, I'm trying everything but nothing works....




Thomas Weber-16 wrote:
> 
> Hello,
> 
> the u-boot and the linux-kernel from the TimLL cd are patched with an
> unofficial machine identifier. They are not working with any other of
> your sources. You need to update both, u-boot and linux-kernel.  Can
> you write me, which u-boot and linux-kernel version you are using?
> 
> Thomas
> 
> On Sat, Jun 12, 2010 at 7:30 PM, JaimeR <jaime.rebolledo@gmail.com> wrote:
>>
>> Hello
>>
>> I have a clone of beagleboard (devkit8000) I update the u-boot from
>> 2009-11
>> to 2010 version. I use a set of scripts to boot based on autoboot method.
>> The thing is, now I can not boot and hangs at kernel loading. I've tested
>> several kernels provided by manufacturer, linux-omap-2.6, some other from
>> git:/gitorious/devkit8000 and all of them end like:
>>
>> ## Booting kernel from Legacy Image at 82000000 ...
>> ...
>> ? Verifying Checksum ... OK
>> ? Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> hangs here
>>
>> and some others
>>
>> ? Verifying Checksum ... OK
>> ? Loading Kernel Image ...
>>
>> hangs here.
>>
>> these are my u-boot environment variables. Some of you can give a clue ?
>> I
>> ve tested almost everything.
>>
>> bootdelay=3
>> baudrate=115200
>> loadaddr=0x82000000
>> console=ttyS2,115200n8
>> vram=12M
>> dvimode=1024x768MR-16 at 60
>> defaultdisplay=dvi
>> nfsopts=hard,tcp,rsize=65536,wsize=65536
>> commonargs=setenv bootargs console=${console} vram=${vram}
>> omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay}
>> mmcargs=run commonargs; setenv bootargs ${bootargs} root=/dev/mmcblk0p2
>> ${kernelopts}
>> nandargs=run commonargs; setenv bootargs ${bootargs}
>> omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay}
>> root=/dev/mtdblock4 rootfstype=jffs2 ${kernel}
>> netargs=run commonargs; setenv bootargs ${bootargs} root=/dev/nfs
>> nfsroot=${serverip}:${rootpath},${nfsopts}
>> ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${}
>> loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
>> bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
>> loaduimage=fatload mmc 0 ${loadaddr} uImage
>> eraseenv=nand unlock 0x260000 0x20000; nand erase 0x260000 0x20000
>> mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
>> nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
>> 280000 400000; bootm ${loadaddr}
>> netboot=echo Booting from network ...; dhcp ${loadaddr}; run netargs;
>> bootm
>> ${loadaddr}
>> autoboot=if mmc init 0; then if run loadbootscript; then run bootscript;
>> else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else
>> run nandboot;i
>> ethaddr=02:fa:19:01:f0:1e
>> dieid#=6db2000400000000040365fa1901f01e
>> ethact=dm9000
>> bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw
>> rootwait
>> bootargs_back=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw
>> rootwait
>> bootcmd=mmc init;fatload mmc1 0 0x82000000 uImage.bin;bootm 0x82000000
>> stdin=serial
>> stdout=serial
>> stderr=serial
>> kernelopts=rw
>> --
>> View this message in context:
>> http://old.nabble.com/u-boot-2010---devkit8000-issue-tp28866288p28866288.html
>> Sent from the Uboot - Users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> 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/u-boot-2010---devkit8000-issue-tp28866288p29642184.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

      reply	other threads:[~2010-09-08 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 17:30 [U-Boot] u-boot 2010 - devkit8000 issue JaimeR
2010-06-13  7:23 ` Thomas Weber
2010-09-08 17:50   ` el.einad [this message]

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=29642184.post@talk.nabble.com \
    --to=el.einad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.