From: Sekhar Nori <nsekhar@ti.com>
To: Yegor Yefremov <yegorslists@googlemail.com>,
Roger Quadros <rogerq@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gupta, Pekon" <pekon@ti.com>
Subject: Re: am335x: system doesn't reboot after flashing NAND
Date: Wed, 4 Jun 2014 15:50:31 +0530 [thread overview]
Message-ID: <538EF2EF.4050709@ti.com> (raw)
In-Reply-To: <CAGm1_kt7BZ7RcbPd51QXhXxQV4SRzeXLzKW43wqK5UnPbYoHBw@mail.gmail.com>
On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros <rogerq@ti.com> wrote:
>> Hi,
>>
>> On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>>>> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
>>>>> On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
>>>>> <yegorslists@googlemail.com> wrote:
>>>>>> Kernel: 3.14, 3.15 (I haven't tried another kernels)
>>>>>>
>>>>>> As soon as I write something to my NAND flash (via cat image >
>>>>>> /dev/mtdblockx or ubiupdatevol) and make reboot or press a reset
>>>>>> button, I see only CCCCC and nothing happens before I make a power
>>>>>> cycle. Any idea?
>>>>>
>>>>> Just forgot to mention, that I was actually booting from MMC (mmc1).
>>>>> The boot sequence is UART0...XIP...MMC0...NAND.
>>
>> Can you try to get XIP out of the boot sequence and see if it works?
>> Maybe try to boot from mmc directly?
>>
>> This would prove that NAND/GPMC driver is leaving some state that doesn't
>> go well with the bootROM XIP.
>
> This configuration is soldered. It won't be easy to change.
Most likely XIP is the issue if sysboot has not changed.
The way ROM works for XIP boot is:
1) Set chip select 0 base address to 0x0800'0000
2) Read memory at 0x0800'0000
3) If something else other than 0x0 or ~0x0 is found, jump to
0x0800'0000 and start executing.
Can you check to see the contents of 0x0800'0000 before and after nand
write using mtdblock?
Thanks,
Sekhar
next prev parent reply other threads:[~2014-06-04 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 7:57 am335x: system doesn't reboot after flashing NAND Yegor Yefremov
2014-06-03 10:48 ` Yegor Yefremov
2014-06-04 6:40 ` Sekhar Nori
2014-06-04 8:25 ` Yegor Yefremov
2014-06-04 8:48 ` Roger Quadros
2014-06-04 9:41 ` Yegor Yefremov
2014-06-04 10:20 ` Sekhar Nori [this message]
2014-06-04 10:30 ` Yegor Yefremov
2014-06-04 10:52 ` Sekhar Nori
2014-06-04 11:49 ` Gupta, Pekon
2014-06-04 12:32 ` Yegor Yefremov
2014-06-04 19:45 ` Yegor Yefremov
2014-06-05 10:02 ` Roger Quadros
2014-06-05 10:07 ` Yegor Yefremov
2014-06-06 9:33 ` Roger Quadros
2014-06-06 9:43 ` jean-philippe francois
2014-07-02 15:45 ` Yegor Yefremov
2014-07-02 21:15 ` Yegor Yefremov
2014-07-03 10:22 ` Sekhar Nori
2014-07-03 8:00 ` Roger Quadros
2014-06-05 10:11 ` Gupta, Pekon
2014-06-05 11:17 ` Gupta, Pekon
2014-06-04 8:54 ` Sekhar Nori
2014-06-04 9:39 ` Yegor Yefremov
2014-06-04 9:49 ` Roger Quadros
2014-06-04 10:07 ` Yegor Yefremov
2014-06-04 10:21 ` Roger Quadros
2014-06-04 12:08 ` Yegor Yefremov
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=538EF2EF.4050709@ti.com \
--to=nsekhar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.com \
--cc=rogerq@ti.com \
--cc=yegorslists@googlemail.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;
as well as URLs for NNTP newsgroup(s).