From: Steven Grunza <grunzasr@comcast.net>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Is this the correct list for AM3517 EVM questions?
Date: Tue, 26 Mar 2013 23:07:59 -0400 [thread overview]
Message-ID: <5152628F.2020107@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1303261715150.3036@oneiric>
[-- Attachment #1: Type: text/plain, Size: 3387 bytes --]
On 3/26/2013 5:18 PM, Robert P. J. Day wrote:
> On Tue, 26 Mar 2013, Steven Grunza wrote:
>
> ... snip ...
>
>> So the build finished and I loaded the files onto my SD card. MLO,
>> u-boot.img, and uImage onto the first partition. I untarred the
>> root file system onto the second partition. This is the result on
>> the serial console:
>>
>> 40X???H????????????сSPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
>> Texas Instruments Revision detection unimplemented
>> OMAP SD/MMC: 0
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)
>>
>> AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
>> AM3517EVM Board + LPDDR/NAND
>> I2C: ready
>> DRAM: 256 MiB
>> NAND: 512 MiB
>> MMC: OMAP SD/MMC: 0
>> *** Warning - bad CRC, using default environment
>>
>> In: serial
>> Out: serial
>> Err: serial
>> Die ID #1b7e0000000000000155daa60200c00f
>> Hit any key to stop autoboot: 0
>> reading boot.scr
>>
>> ** Unable to read "boot.scr" from mmc 0:1 **
>> reading uImage
>>
>> 3160284 bytes read
>> Booting from mmc ...
>> ## Booting kernel from Legacy Image at 82000000 ...
>> Image Name: Linux-2.6.37
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 3160220 Bytes = 3 MiB
>> Load Address: 80008000
>> Entry Point: 80008000
>> Verifying Checksum ... OK
>> Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Did I miss a step?
> that was going to be my long weekend project ... are you saying it
> just hung at that point?
>
> rday
>
Yes. Just hung. Here's a little more info on my system. I changed the
loadaddr environment variable to match the reported load address from
u-boot reading the uImage file. Saving the new value fixed the "***
Warning - bad CRC, using default environment" message.
40X?@C?UI??сSPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)
AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
AM3517EVM Board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
In: serial
Out: serial
Err: serial
Die ID #1b7e0000000000000155daa60200c00f
Hit any key to stop autoboot: 0
AM3517_EVM # printenv
baudrate=115200
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run
bootscript; else
if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run
nandboot; fi
bootdelay=10
bootfile=uImage
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
console=ttyO2,115200n8
dieid#=1b7e0000000000000155daa60200c00f
loadaddr=80008000
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootw
ait
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
mmcdev=0
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw
rootfstype=jffs2
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
280000 400000;
bootm ${loadaddr}
stderr=serial
stdin=serial
stdout=serial
Environment size: 911/131068 bytes
AM3517_EVM #
[-- Attachment #2: Type: text/html, Size: 4457 bytes --]
next prev parent reply other threads:[~2013-03-27 3:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 14:18 Is this the correct list for AM3517 EVM questions? Steven Grunza
2013-03-19 17:21 ` Denys Dmytriyenko
2013-03-19 17:43 ` Khem Raj
2013-03-19 18:08 ` Steven Grunza
2013-03-19 18:27 ` Denys Dmytriyenko
2013-03-20 14:23 ` Steven Grunza
2013-03-20 15:17 ` Denys Dmytriyenko
[not found] ` <5149F665.9090204@comcast.net>
[not found] ` <20130320175415.GW32759@edge>
2013-03-20 18:18 ` Steven Grunza
2013-03-20 18:27 ` Denys Dmytriyenko
2013-03-20 18:45 ` Robert P. J. Day
2013-03-20 18:57 ` Denys Dmytriyenko
2013-03-20 19:11 ` Denys Dmytriyenko
2013-03-20 19:58 ` Robert P. J. Day
2013-03-26 19:12 ` Steven Grunza
2013-03-26 21:18 ` Robert P. J. Day
2013-03-27 3:07 ` Steven Grunza [this message]
2013-03-27 19:40 ` Robert P. J. Day
2013-03-27 19:53 ` Steven Grunza
2013-03-27 20:20 ` Robert P. J. Day
2013-03-27 20:35 ` Steven Grunza
2013-03-20 18:48 ` Steven Grunza
2013-03-20 18:58 ` Denys Dmytriyenko
2013-03-19 18:12 ` Steven Grunza
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=5152628F.2020107@comcast.net \
--to=grunzasr@comcast.net \
--cc=meta-ti@yoctoproject.org \
/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.