On Thursday 03 July 2014 02:45 AM, Yegor Yefremov wrote:
> Btw how can I debug the kernel via JTAG? I've read, that one must
> activate JTAG clock or something like this. What is the proper way to
> do this in 3.15 - 3.16?
Please try with Lokesh's patch here:
http://www.spinics.net/lists/arm-kern
+ Nishant.
On 07/02/2014 06:45 PM, Yegor Yefremov wrote:
> On Fri, Jun 6, 2014 at 11:33 AM, Roger Quadros wrote:
>> On 06/05/2014 01:07 PM, Yegor Yefremov wrote:
>>> On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014
On Wed, Jul 2, 2014 at 5:45 PM, Yegor Yefremov
wrote:
> On Fri, Jun 6, 2014 at 11:33 AM, Roger Quadros wrote:
>> On 06/05/2014 01:07 PM, Yegor Yefremov wrote:
>>> On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at
On Fri, Jun 6, 2014 at 11:33 AM, Roger Quadros wrote:
> On 06/05/2014 01:07 PM, Yegor Yefremov wrote:
>> On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
>>> On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
> On Wednesday 04 June 201
2014-06-06 11:33 GMT+02:00 Roger Quadros :
> On 06/05/2014 01:07 PM, Yegor Yefremov wrote:
>> On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
>>> On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
> On Wednesday 04 June 2014 04:00 PM,
On 06/05/2014 01:07 PM, Yegor Yefremov wrote:
> On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
>> On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 a
Hi Yegor,
>From: Gupta, Pekon
>
>However, I don't suspect XIP boot here because even if CPU is detecting
>garbage data while reading from 0x8000 it won't find a valid image
>header there, and so XIP boot should have failed, and boot sequence
>should fall back to MMC. It shouldn't have hung.
>
Hi Roger, Yegor,
>From: Quadros, Roger
>>On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
[...]
>>
>> The 0x8000 address seems to be the beginning of NAND region:
>>
>> ranges = <0 0 0x0800 0x1000>; /* CS0: NAND */
>>
>> I've taken this example from am335x_evm.dts. I have tried to chan
On Thu, Jun 5, 2014 at 12:02 PM, Roger Quadros wrote:
> On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
>>> On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 12:20 PM, Sekhar Nori wrote:
> On Wednesday 0
On 06/04/2014 10:45 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
>> On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 12:20 PM, Sekhar Nori wrote:
On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
> On Wed, Jun
On Wed, Jun 4, 2014 at 12:52 PM, Sekhar Nori wrote:
> On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 12:20 PM, Sekhar Nori wrote:
>>> On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros wrote:
> Hi
On Wed, Jun 4, 2014 at 1:49 PM, Gupta, Pekon wrote:
>>On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
> [...]
>
The way ROM works for XIP boot is:
1) Set chip select 0 base address to 0x0800'
2) Read memory at 0x0800'
3) If something else other than 0x0 o
On Wed, Jun 4, 2014 at 12:21 PM, Roger Quadros wrote:
> On 06/04/2014 01:07 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 11:49 AM, Roger Quadros wrote:
>>> On 06/04/2014 12:39 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 10:54 AM, Sekhar Nori wrote:
> On Wednesday 04 June 201
>On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
[...]
>>> The way ROM works for XIP boot is:
>>>
>>> 1) Set chip select 0 base address to 0x0800'
>>> 2) Read memory at 0x0800'
>>> 3) If something else other than 0x0 or ~0x0 is found, jump to
>>> 0x0800' and start executing.
On Wednesday 04 June 2014 04:00 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 12:20 PM, Sekhar Nori wrote:
>> On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros wrote:
Hi,
On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
>
On Wed, Jun 4, 2014 at 12:20 PM, Sekhar Nori wrote:
> On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
> On
On 06/04/2014 01:07 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 11:49 AM, Roger Quadros wrote:
>> On 06/04/2014 12:39 PM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 10:54 AM, Sekhar Nori wrote:
On Wednesday 04 June 2014 01:55 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 a
On Wednesday 04 June 2014 03:11 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros wrote:
>> Hi,
>>
>> On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
> On
On Wed, Jun 4, 2014 at 11:49 AM, Roger Quadros wrote:
> On 06/04/2014 12:39 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 10:54 AM, Sekhar Nori wrote:
>>> On Wednesday 04 June 2014 01:55 PM, Yegor Yefremov wrote:
On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
> On Tuesday 03 J
On 06/04/2014 12:39 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 10:54 AM, Sekhar Nori wrote:
>> On Wednesday 04 June 2014 01:55 PM, Yegor Yefremov wrote:
>>> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
> On Tue, Jun 3,
On Wed, Jun 4, 2014 at 10:48 AM, Roger Quadros wrote:
> Hi,
>
> On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
>>> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
wrote:
> Ke
On Wed, Jun 4, 2014 at 10:54 AM, Sekhar Nori wrote:
> On Wednesday 04 June 2014 01:55 PM, Yegor Yefremov wrote:
>> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
>>> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
wrote:
>
On Wednesday 04 June 2014 01:55 PM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
>> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
>>> On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
>>> wrote:
Kernel: 3.14, 3.15 (I haven't tried another kernels)
>>
Hi,
On 06/04/2014 11:25 AM, Yegor Yefremov wrote:
> On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
>> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
>>> On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
>>> wrote:
Kernel: 3.14, 3.15 (I haven't tried another kernels)
As s
On Wed, Jun 4, 2014 at 8:40 AM, Sekhar Nori wrote:
> On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
>> On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
>> 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 >
On Tuesday 03 June 2014 04:18 PM, Yegor Yefremov wrote:
> On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
> 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
On Tue, Jun 3, 2014 at 9:57 AM, Yegor Yefremov
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 C and nothing happens before I
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 C and nothing happens before I make a power
cycle. Any idea?
Yegor
--
To unsubscribe from thi
28 matches
Mail list logo