Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Shinkyu Kang]

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

Using  IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. C,
the kernel 3.4.34  works correctly, but Rev D doesn't work.

What is the deferences between Rev. C and Rev. D. of hardware?

Best Regards,
Shinkyu
2013/5/2 Fabio Estevam <festevam@gmail.com>

> On Tue, Apr 30, 2013 at 8:02 PM, Shinkyu Kang <ksk4097@gmail.com> wrote:
> > Hi,
> > My name is Shinkyu, working for Realtimewave in South Korea.
> > This is first time to write a mail to yocktoproject.org.
> > I'm testing with IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. D,
> > WindRiver Linux 5 which supports to Yockto project and Linux 3.4.34.
> >
> > When I try to boot with kernel 3.4.34, it loops infinitly at
> "while(ticks ==
>
> As you are using a 3.x kernel, why don't you use the latest stable
> release (3.8.11) instead?
>

[-- Attachment #2: Type: text/html, Size: 1421 bytes --]

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Eric Nelson]

Hi Shikyu,

On 05/02/2013 10:32 PM, Shinkyu Kang wrote:
> Using  IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. C,
> the kernel 3.4.34  works correctly, but Rev D doesn't work.
> What is the deferences between Rev. C and Rev. D. of hardware?
> Best Regards,
> Shinkyu

We switched CAN transceivers from the Freescale MC33902 to
the NXP TJA1040 (Freescale announced EOL on theirs):

We have code to detect the two here:
	https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_1.1.1/arch/arm/mach-mx6/board-mx6q_sabrelite.c#L1289

Regards,


Eric

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Eric Nelson]

On 05/02/2013 10:32 PM, Shinkyu Kang wrote:
> Using  IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. C,
> the kernel 3.4.34  works correctly, but Rev D doesn't work.
> What is the deferences between Rev. C and Rev. D. of hardware?
> Best Regards,
> Shinkyu

Hi Shinkyu,

Thinking about this, it seems that a CPU revision change is
more likely to be an issue than the board rev.

Does your Rev D board have 1.2 silicon?

You can see this during U-Boot startup:
	CPU:   Freescale i.MX6Q rev1.2 at 792 MHz

Please advise,


Eric

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Shinkyu Kang]

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

Hi, Eric,

Thank you for the hint.

>> Does your Rev D board have 1.2 silicon?
>> You can see this during U-Boot startup:
>> CPU: Freescale i.MX6Q rev1.2 at 792 MHz


Yes. I can see the message.

Also, when I using the kernel 3.0.35-gb0b02db-dirty,
the debug message shows "CPU identified as i.MX6Q, silicon rev 1.2".

But, in 3.4.34 kernel, I couldn't find the mesage.

Is there any initalization code for "i.MX6Q, silicon rev 1.2".

Thanks again.
Best Regards,
Shinkyu.



2013/5/4 Eric Nelson <eric.nelson@boundarydevices.com>

> On 05/02/2013 10:32 PM, Shinkyu Kang wrote:
>
>> Using  IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. C,
>> the kernel 3.4.34  works correctly, but Rev D doesn't work.
>> What is the deferences between Rev. C and Rev. D. of hardware?
>> Best Regards,
>> Shinkyu
>>
>
> Hi Shinkyu,
>
> Thinking about this, it seems that a CPU revision change is
> more likely to be an issue than the board rev.
>
> Does your Rev D board have 1.2 silicon?
>
> You can see this during U-Boot startup:
>         CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
>
> Please advise,
>
>
> Eric
>
>

[-- Attachment #2: Type: text/html, Size: 1991 bytes --]

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Eric Nelson]

Hi Shinkyu,

On 05/03/2013 12:46 PM, Shinkyu Kang wrote:
> Hi, Eric,
> Thank you for the hint.
>  >> Does your Rev D board have 1.2 silicon?
>  >> You can see this during U-Boot startup:
>  >> CPU: Freescale i.MX6Q rev1.2 at 792 MHz
 >
> Yes. I can see the message.
> Also, when I using the kernel 3.0.35-gb0b02db-dirty,
> the debug message shows "CPU identified as i.MX6Q, silicon rev 1.2".

That's what I thought.

> But, in 3.4.34 kernel, I couldn't find the mesage.
> Is there any initalization code for "i.MX6Q, silicon rev 1.2".

These are off-topic for the meta-freescale list.

Please contact me privately, and bring in the WRS support
team.

There are a variety of conditionals for CPU revisions
in the kernel startup, and either Freescale's git
repository or ours are the places to start reviewing
them vs. the Wind River kernel.

Regards,


Eric

[IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Shinkyu Kang]

[-- Attachment #1: Type: text/plain, Size: 3777 bytes --]

Hi,
My name is Shinkyu, working for Realtimewave in South Korea.
This is first time to write a mail to yocktoproject.org.
I'm testing with IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. D,
WindRiver Linux 5 which supports to Yockto project and Linux 3.4.34.

When I try to boot with kernel 3.4.34, it loops infinitly at "while(ticks
== jiffies)" in calibrate_delay_converge( ) (Init/calibrate.c)
So, I want to get hints for booting problem from Freescale IMX6Q experts.


===Here is booting log ==================================================
MX6QSABRELITE U-Boot > print bootargs
bootargs=console=ttymxc1,115200
MX6QSABRELITE U-Boot > tftp 10800000 uImage-3.4.34-WR5.0.1.0_standard
Using FEC device
TFTP from server 192.168.0.123; our IP address is 192.168.0.106
Filename 'uImage-3.4.34-WR5.0.1.0_standard'.
Load address: 0x10800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######
done
Bytes transferred = 4853088 (4a0d60 hex)
MX6QSABRELITE U-Boot > bootm
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.4.34-WR5.0.1.0_standard
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4853024 Bytes = 4.6 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.4.34-WR5.0.1.0_standard (silee@silee) (gcc version 4.6.3
(Wind River Linux Sourcery CodeBench 4.6a-99) ) #1 SMP PREEMPT Thu Apr 4
00:02:58 KST 2013
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6Quad Sabre-Lite Board
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 9 pages/cpu @8135f000 s14912 r8192 d13760 u36864
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 227072
Kernel command line: console=ttymxc1,115200
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
allocated 2097152 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Memory: 640MB 256MB = 896MB total
Memory: 894684k/894684k available, 153892k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc0800000 - 0xfb000000   ( 936 MB)
    lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x808e6220   (9081 kB)
      .init : 0x808e7000 - 0x80938a40   ( 327 kB)
      .data : 0x8093a000 - 0x809a8ff0   ( 444 kB)
      .bss : 0x809a9014 - 0x80a577e4   ( 698 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:436
sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
MXC_Early serial console at MMIO 0x21e8000 (options '115200')
bootconsole [ttymxc1] enabled
Console: colour dummy device 80x30
Calibrating delay loop...
====================================================================================

Regards,
Shinkyu

[-- Attachment #2: Type: text/html, Size: 4260 bytes --]

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Eric Nelson]

Hi Shinkyu,

On 04/30/2013 04:02 PM, Shinkyu Kang wrote:
> Hi,
> My name is Shinkyu, working for Realtimewave in South Korea.
> This is first time to write a mail to yocktoproject.org
> <http://yocktoproject.org>.
> I'm testing with IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. D,
> WindRiver Linux 5 which supports to Yockto project and Linux 3.4.34.

Does WRS place the kernel sources on-line for review?

It's impossible to tell the origin of this without some point of
reference.

In the Freescale reference kernel, we've seen similar behaviour
without a flag 'enable_wait_mode=off' flag.

This blog post provides more detail:
	http://boundarydevices.com/wait-a-second-hopefully-less/

Regards,


Eric

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Shinkyu Kang]

[-- Attachment #1: Type: text/plain, Size: 172 bytes --]

Hi, Eric,

Thank you for reply.


> Does WRS place the kernel sources on-line for review?


I'm sorry. They could be only obtained from WRS.

Regards,
Shinkyu.

[-- Attachment #2: Type: text/html, Size: 636 bytes --]

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Otavio Salvador]

On Tue, Apr 30, 2013 at 11:35 PM, Shinkyu Kang <ksk4097@gmail.com> wrote:
> Hi, Eric,
>
> Thank you for reply.
>
>>
>> Does WRS place the kernel sources on-line for review?
>
>
> I'm sorry. They could be only obtained from WRS.

I doubt as the kernel is GPL and the source code needs to be made
available, plus they wouldn't deny access to the code and risk a legal
issue. However it'd be better if you could contact them as they're the
vendor you are using and they know what they changed and why.

Sorry by not being of help.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [IMX6Q Sabre Lite, Linux 3.4.34] Booting is failed in calibrate_delay_converge().

[Fabio Estevam]

On Tue, Apr 30, 2013 at 8:02 PM, Shinkyu Kang <ksk4097@gmail.com> wrote:
> Hi,
> My name is Shinkyu, working for Realtimewave in South Korea.
> This is first time to write a mail to yocktoproject.org.
> I'm testing with IMX6Q SABRE Lite Ev. Board (Boundary Device) Rev. D,
> WindRiver Linux 5 which supports to Yockto project and Linux 3.4.34.
>
> When I try to boot with kernel 3.4.34, it loops infinitly at "while(ticks ==

As you are using a 3.x kernel, why don't you use the latest stable
release (3.8.11) instead?