From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: i.mazanov@gmail.com
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: Re: OMAP baseline test results for v3.7-rc5
Date: Fri, 16 Nov 2012 13:01:43 +0100 [thread overview]
Message-ID: <50A62B27.8060107@visionsystems.de> (raw)
In-Reply-To: <50A629EB.4030700@gmail.com>
On 16.11.2012 12:56, Igor Mazanov wrote:
> Yegor Yefremov wrote:
>>> Boot tests:
>>>
>>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot
>>> - May be fixed now, pending retest:
>>> - http://marc.info/?l=linux-omap&m=135082257727502&w=2
>>> - Not yet part of the automated test suite
>>> * May be due to an old U-boot with FDT support problems used here?
>>> Pending local investigation and re-test
>>
>> I'm also trying to boot 3.7-rc5, but my board has console on ttyO3. So I took arch/arm/boot/dts/am335x-evm.dts and replaced uart definition to
>>
>> uart4: serial@481a6000 {
>> status = "okay";
>> };
>>
>> is it sufficient?
>>
>> In u-boot
>> commit 59852d03867108217fe88e3bfc3e1e9cedfe63c5
>> Merge: 22b6fcb b3e5cd1
>> Author: Tom Rini <trini@ti.com>
>> Date: Fri Nov 9 08:47:25 2012 -0700
>>
>> Merge branch 'master' of git://www.denx.de/git/u-boot-microblaze
>>
>> I use following commands and get following output:
>>
>> U-Boot# mmc rescan ; fatload mmc 0 82000000 uImage;fatload mmc 0 80000000 am335x-evm.dtb
>> reading uImage
>> 4222584 bytes read
>> reading am335x-evm.dtb
>> 5172 bytes read
>> U-Boot# fdt addr 80000000; fdt resize; bootm 82000000 - 80000000
>> ## Booting kernel from Legacy Image at 82000000 ...
>> Image Name: Linux-3.7.0-rc5-00028-g79e979e
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 4222520 Bytes = 4 MiB
>> Load Address: 80008000
>> Entry Point: 80008000
>> Verifying Checksum ... OK
>> ## Flattened Device Tree blob at 80000000
>> Booting using the fdt blob at 0x80000000
>> Loading Kernel Image ... OK
>> OK
>> reserving fdt memory region: addr=80000000 size=2000
>> Loading Device Tree to 8fe64000, end 8fe68fff ... OK
>>
>> Starting kernel ...
>>
>> I force kernel to use default params, so I don't specify them in u-boot. Any idea?
>
> Did you try to set console=ttyO3,115200 in u-boot bootargs settings?
>
Got the stuff working by just invoking make omap2plus_config once again. Perhaps I changed something viable and didn't notice that. Now waiting for MMC device tree support ;-)
Thanks.
Yegor
prev parent reply other threads:[~2012-11-16 12:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 19:30 OMAP baseline test results for v3.7-rc5 Paul Walmsley
2012-11-12 22:58 ` Tony Lindgren
2012-11-14 1:07 ` Kevin Hilman
2012-11-14 23:36 ` Tony Lindgren
2012-11-13 15:59 ` Igor Mazanov
2012-11-13 16:00 ` Igor Mazanov
2012-11-13 16:04 ` Igor Mazanov
2012-11-13 16:05 ` Igor Mazanov
2012-11-16 7:47 ` Richard Cochran
2012-11-16 11:35 ` Igor Mazanov
2012-11-16 10:49 ` Yegor Yefremov
2012-11-16 11:56 ` Igor Mazanov
2012-11-16 12:01 ` Yegor Yefremov [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=50A62B27.8060107@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=i.mazanov@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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