From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] at91sam9260 resets if booted automatically
Date: Tue, 05 Oct 2010 14:55:26 +0200 [thread overview]
Message-ID: <4CAB203E.5020008@googlemail.com> (raw)
Hello u-boot list!
I am using an Eddy-CPU V2.1 from embeddedmodule.com
The u-boot version is 2008.10-rc3:
U-Boot> version
U-Boot 2008.10-rc3 (Sep 3 2009 - 18:30:12)
It is basically an AT91SAM9260 with a complete development kit. I am
running buildroot-2010.08 on it with linux 2.6.34.3. Everything is
working fine and u-boot does the job it should do, except one thing:
If I issue the following command manually, my system gets through to the
login prompt and runs up and healthy:
cp.b ${OS_FLASH} ${OS_SDRAM} ${OS_SIZE}; cp.b ${FileSystem_FLASH}
${FileSystem_SDRAM} ${FS_SIZE}; bootm ${OS_SDRAM} ${FileSystem_SDRAM}
This is as well the content of the bootcmd-variable inside u-boot.
All the variables mentioned in this command are correct in their writing
(case sensitivity) and their content. Everything is ok so far.
If now I power up the board and let it run on its own without manually
issueing the command above, the system boots up to when the login-prompt
should come up (I can even see output of two /etc/init.d-scripts just
before the login-prompt should be there) but in case of having a running
system, the board reboots immediately.
So what is the difference between typing that command manually and
letting it run on its own?
Below is the output of printenv - maybe this could be of use.
Thanks a whole lot for any help in advance,
Dennis
U-Boot> printenv
baudrate=115200
ethaddr=00:05:F4:11:22:33
hostname=Eddy
ethact=macb0
Bootstrap_FLASH=0xD0000000
Bootloader_FLASH=0xD0003180
Config_FLASH=0xD06A7E20
Bootstrap_END=0xD00020FF
Bootloader_END=0xD003FEFF
OS_END=0xD025D57F
FileSystem_END=0xD06A7E1F
Config_END=0xD07FFFFF
Download_SDRAM=0x20000000
bootdelay=1
console=ttyS0,115200
OS_SDRAM=0x21000000
OS_FLASH=0xd0040000
FileSystem_FLASH=0xd0280000
FileSystem_SDRAM=0x21500000
bootcmd=cp.b ${OS_FLASH} ${OS_SDRAM} ${OS_SIZE}; cp.b ${FileSystem_FLASH} ${FileSystem_SDRAM} ${FS_SIZE}; bootm ${OS_SDRAM} ${FileSystem_SDRAM}
OS_SIZE=198418
FS_SIZE=2C8233
bootargs.bak=root=/dev/ram rw console=ttyS0,115200,mem=32M
bootargs=root=/dev/ram rw console=ttyS0,115200,mem=32M
filesize=2C8233
fileaddr=21500000
gatewayip=192.168.0.1
netmask=255.255.255.0
ipaddr=192.168.0.223
serverip=192.168.0.220
OS_Size=0x198458
FileSystem_Size=0x2c8273
stdin=serial
stdout=serial
stderr=serial
Environment size: 913/4220 bytes
U-Boot>
reply other threads:[~2010-10-05 12:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CAB203E.5020008@googlemail.com \
--to=dennis.borgmann@googlemail.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.