AM3517 fails to boot 3.16-rc5 device tree kernel

AM3517 fails to boot 3.16-rc5 device tree kernel

[mwelling]

I am in the process of porting a device tree compatible version of the
linux kernel to a AM3517 based device.

First I tried 3.10.x and the device tree port appeared to be incomplete.
Neither the LCD or Ethernet were supported.

Next I tried 3.14.x and the Ethernet driver appeared to work but still
no LCD support.

Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
without any messages from the serial COM.

I was using the omap2plus_defconfig and the am3517-evm.dtb from each
kernel build. Is there any reason why the kernel would start hanging
with the newest release?

Are there any versions where the LCD output works?

Looking at the 3.16-rc5 test results just posted it is supposed to be working
but I have not been able to replicate this.

Any suggestions would be greatly appreciated.

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Tony Lindgren]

* mwelling <mwelling@emacinc.com> [140717 16:42]:
> I am in the process of porting a device tree compatible version of the
> linux kernel to a AM3517 based device.
> 
> First I tried 3.10.x and the device tree port appeared to be incomplete.
> Neither the LCD or Ethernet were supported.
> 
> Next I tried 3.14.x and the Ethernet driver appeared to work but still
> no LCD support.
> 
> Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
> without any messages from the serial COM.

For device tree based booting on omap3 I would user v.16-rc4 or later.
There have been multiple issues fixed over past year and PM is working
finally at least for 36xx/37xx. And we do have the DSS panels finally
working too.
 
> I was using the omap2plus_defconfig and the am3517-evm.dtb from each
> kernel build. Is there any reason why the kernel would start hanging
> with the newest release?

No reason that I can think of. AFAIK 3517 has been booting in the test
farms just fine?

Can you please enable debug_ll + earlyprintk and pass also earlyprintk
in the kernel cmdline?
 
> Are there any versions where the LCD output works?

Starting with v3.16-rc1 you should get the LCD working for panel-dpi
based devices. Most of them actually are actually ls037v3dw01, so
see omap3-panel-sharp-ls037v7dw01.dtsi and omap3-evm-common.dtsi
variants if you have similar setup.
 
> Looking at the 3.16-rc5 test results just posted it is supposed to be working
> but I have not been able to replicate this.
> 
> Any suggestions would be greatly appreciated.

Hmm maybe double check your're booting device tree based kernel
instead of legacy machine ID based kernel? The legacy booting should
still work just fine and no changes has been made to it, but it will
get removed shortly.

Regards,

Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Michael Welling]

On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> * mwelling <mwelling@emacinc.com> [140717 16:42]:
>> I am in the process of porting a device tree compatible version of the
>> linux kernel to a AM3517 based device.
>>
>> First I tried 3.10.x and the device tree port appeared to be incomplete.
>> Neither the LCD or Ethernet were supported.
>>
>> Next I tried 3.14.x and the Ethernet driver appeared to work but still
>> no LCD support.
>>
>> Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
>> without any messages from the serial COM.
>
> For device tree based booting on omap3 I would user v.16-rc4 or later.
> There have been multiple issues fixed over past year and PM is working
> finally at least for 36xx/37xx. And we do have the DSS panels finally
> working too.
>
>> I was using the omap2plus_defconfig and the am3517-evm.dtb from each
>> kernel build. Is there any reason why the kernel would start hanging
>> with the newest release?
>
> No reason that I can think of. AFAIK 3517 has been booting in the test
> farms just fine?
>
> Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> in the kernel cmdline?
I will try this.
>
>> Are there any versions where the LCD output works?
>
> Starting with v3.16-rc1 you should get the LCD working for panel-dpi
> based devices. Most of them actually are actually ls037v3dw01, so
> see omap3-panel-sharp-ls037v7dw01.dtsi and omap3-evm-common.dtsi
> variants if you have similar setup.
>
>> Looking at the 3.16-rc5 test results just posted it is supposed to be working
>> but I have not been able to replicate this.
>>
>> Any suggestions would be greatly appreciated.
>
> Hmm maybe double check your're booting device tree based kernel
> instead of legacy machine ID based kernel? The legacy booting should
> still work just fine and no changes has been made to it, but it will
> get removed shortly.
I downloaded the version from the test results and it did boot.
These are combining the uImage and dtb. How do you accomplish this?
>
> Regards,
>
> Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Michael Welling]

On Fri, Jul 18, 2014 at 09:40:48AM -0500, Michael Welling wrote:
> On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * mwelling <mwelling@emacinc.com> [140717 16:42]:
> >> I am in the process of porting a device tree compatible version of the
> >> linux kernel to a AM3517 based device.
> >>
> >> First I tried 3.10.x and the device tree port appeared to be incomplete.
> >> Neither the LCD or Ethernet were supported.
> >>
> >> Next I tried 3.14.x and the Ethernet driver appeared to work but still
> >> no LCD support.
> >>
> >> Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
> >> without any messages from the serial COM.
> >
> > For device tree based booting on omap3 I would user v.16-rc4 or later.
> > There have been multiple issues fixed over past year and PM is working
> > finally at least for 36xx/37xx. And we do have the DSS panels finally
> > working too.
> >
> >> I was using the omap2plus_defconfig and the am3517-evm.dtb from each
> >> kernel build. Is there any reason why the kernel would start hanging
> >> with the newest release?
> >
> > No reason that I can think of. AFAIK 3517 has been booting in the test
> > farms just fine?
> >
> > Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> > in the kernel cmdline?
> I will try this.

Adding the earlyprintk did not work. It still hangs without any
messages.

> >
> >> Are there any versions where the LCD output works?
> >
> > Starting with v3.16-rc1 you should get the LCD working for panel-dpi
> > based devices. Most of them actually are actually ls037v3dw01, so
> > see omap3-panel-sharp-ls037v7dw01.dtsi and omap3-evm-common.dtsi
> > variants if you have similar setup.
> >
> >> Looking at the 3.16-rc5 test results just posted it is supposed to be working
> >> but I have not been able to replicate this.
> >>
> >> Any suggestions would be greatly appreciated.
> >
> > Hmm maybe double check your're booting device tree based kernel
> > instead of legacy machine ID based kernel? The legacy booting should
> > still work just fine and no changes has been made to it, but it will
> > get removed shortly.

How do you determine which you are booting?

> I downloaded the version from the test results and it did boot.
> These are combining the uImage and dtb. How do you accomplish this?
> >
> > Regards,
> >
> > Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Michael Welling]

On Fri, Jul 18, 2014 at 09:40:48AM -0500, Michael Welling wrote:
> On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * mwelling <mwelling@emacinc.com> [140717 16:42]:
> >> I am in the process of porting a device tree compatible version of the
> >> linux kernel to a AM3517 based device.
> >>
> >> First I tried 3.10.x and the device tree port appeared to be incomplete.
> >> Neither the LCD or Ethernet were supported.
> >>
> >> Next I tried 3.14.x and the Ethernet driver appeared to work but still
> >> no LCD support.
> >>
> >> Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
> >> without any messages from the serial COM.
> >
> > For device tree based booting on omap3 I would user v.16-rc4 or later.
> > There have been multiple issues fixed over past year and PM is working
> > finally at least for 36xx/37xx. And we do have the DSS panels finally
> > working too.
> >
> >> I was using the omap2plus_defconfig and the am3517-evm.dtb from each
> >> kernel build. Is there any reason why the kernel would start hanging
> >> with the newest release?
> >
> > No reason that I can think of. AFAIK 3517 has been booting in the test
> > farms just fine?
> >
> > Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> > in the kernel cmdline?
> I will try this.
> >
> >> Are there any versions where the LCD output works?
> >
> > Starting with v3.16-rc1 you should get the LCD working for panel-dpi
> > based devices. Most of them actually are actually ls037v3dw01, so
> > see omap3-panel-sharp-ls037v7dw01.dtsi and omap3-evm-common.dtsi
> > variants if you have similar setup.
> >
> >> Looking at the 3.16-rc5 test results just posted it is supposed to be working
> >> but I have not been able to replicate this.
> >>
> >> Any suggestions would be greatly appreciated.
> >
> > Hmm maybe double check your're booting device tree based kernel
> > instead of legacy machine ID based kernel? The legacy booting should
> > still work just fine and no changes has been made to it, but it will
> > get removed shortly.
> I downloaded the version from the test results and it did boot.
> These are combining the uImage and dtb. How do you accomplish this?

It should be noted that when you try to boot the seperate zImage and dtb from
the test build it fails. This replicates my issue.

Here are the two binaries that I used:
http://www.pwsan.com/omap/testlogs/test_v3.16-rc5/20140716140950/build_z/omap2plus_defconfig/zImage
http://www.pwsan.com/omap/testlogs/test_v3.16-rc5/20140716140950/dtbs/am3517-evm.dtb

Here is the boot attempt:
U-Boot> dhcp;set serverip 10.0.2.168;tftp 0x82000000 zImage; tftp 0x80000000 am3517-evm.dtb;bootz 0x82000000 - 0x80000000
BOOTP broadcast 1
DHCP client bound to address 10.0.3.33
Using DaVinci-EMAC device
TFTP from server 10.0.2.168; our IP address is 10.0.3.33
Filename 'zImage'.
Load address: 0x82000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################
         2 MiB/s
done
Bytes transferred = 4360800 (428a60 hex)
Using DaVinci-EMAC device
TFTP from server 10.0.2.168; our IP address is 10.0.3.33
Filename 'am3517-evm.dtb'.
Load address: 0x80000000
Loading: ####
         1.8 MiB/s
done
Bytes transferred = 50145 (c3e1 hex)
Kernel image @ 0x82000000 [ 0x000000 - 0x428a60 ]
## Flattened Device Tree blob at 80000000
   Booting using the fdt blob at 0x80000000
   Loading Device Tree to 9ff05000, end 9ff143e0 ... OK

Starting kernel ...

Using the exact same boot sequence worked for 3.10 and 3.14.

> >
> > Regards,
> >
> > Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Tony Lindgren]

* Michael Welling <mwelling@emacinc.com> [140718 07:42]:
> On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > Hmm maybe double check your're booting device tree based kernel
> > instead of legacy machine ID based kernel? The legacy booting should
> > still work just fine and no changes has been made to it, but it will
> > get removed shortly.
>
> I downloaded the version from the test results and it did boot.

OK that's good to hear.

> These are combining the uImage and dtb. How do you accomplish this?

You need to make sure you have the appended DTB support enabled like
we do in omap2plus_defconfig:

CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y

Then just cat zImage board.dtb > /tmp/zImage-dtba and run
mkimage to convert it to a uImage:

$ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
	-n "Linux" -d /tmp/zImage-dtba /tmp/uImage

Regards,

Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Tony Lindgren]

* Michael Welling <mwelling@emacinc.com> [140718 08:05]:
> On Fri, Jul 18, 2014 at 09:40:48AM -0500, Michael Welling wrote:
> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> > >
> > > Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> > > in the kernel cmdline?
> > I will try this.
> 
> Adding the earlyprintk did not work. It still hangs without any
> messages.

If you have it enabled for the wrong UART it will always hang..
Maybe check you have the right port? 

> > > Hmm maybe double check your're booting device tree based kernel
> > > instead of legacy machine ID based kernel? The legacy booting should
> > > still work just fine and no changes has been made to it, but it will
> > > get removed shortly.
> 
> How do you determine which you are booting?

Looking at the dmesg, the earliest point you'll see it is from
"Machine model: " line, that's most likely different than for
legacy booting :)

And later on you'll see some DT only drivers get initialized
properly like pinctrl-single:

pinctrl-single 48002030.pinmux: 284 pins at pa fa002030 size 568
...

Regards,

Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Tony Lindgren]

* Michael Welling <mwelling@emacinc.com> [140718 09:15]:
> On Fri, Jul 18, 2014 at 09:40:48AM -0500, Michael Welling wrote:
> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> > > * mwelling <mwelling@emacinc.com> [140717 16:42]:
> > >> I am in the process of porting a device tree compatible version of the
> > >> linux kernel to a AM3517 based device.
> > >>
> > >> First I tried 3.10.x and the device tree port appeared to be incomplete.
> > >> Neither the LCD or Ethernet were supported.
> > >>
> > >> Next I tried 3.14.x and the Ethernet driver appeared to work but still
> > >> no LCD support.
> > >>
> > >> Lastly I tried 3.16-rc5 and found that the kernel hangs in early boot
> > >> without any messages from the serial COM.
> > >
> > > For device tree based booting on omap3 I would user v.16-rc4 or later.
> > > There have been multiple issues fixed over past year and PM is working
> > > finally at least for 36xx/37xx. And we do have the DSS panels finally
> > > working too.
> > >
> > >> I was using the omap2plus_defconfig and the am3517-evm.dtb from each
> > >> kernel build. Is there any reason why the kernel would start hanging
> > >> with the newest release?
> > >
> > > No reason that I can think of. AFAIK 3517 has been booting in the test
> > > farms just fine?
> > >
> > > Can you please enable debug_ll + earlyprintk and pass also earlyprintk
> > > in the kernel cmdline?
> > I will try this.
> > >
> > >> Are there any versions where the LCD output works?
> > >
> > > Starting with v3.16-rc1 you should get the LCD working for panel-dpi
> > > based devices. Most of them actually are actually ls037v3dw01, so
> > > see omap3-panel-sharp-ls037v7dw01.dtsi and omap3-evm-common.dtsi
> > > variants if you have similar setup.
> > >
> > >> Looking at the 3.16-rc5 test results just posted it is supposed to be working
> > >> but I have not been able to replicate this.
> > >>
> > >> Any suggestions would be greatly appreciated.
> > >
> > > Hmm maybe double check your're booting device tree based kernel
> > > instead of legacy machine ID based kernel? The legacy booting should
> > > still work just fine and no changes has been made to it, but it will
> > > get removed shortly.
> > I downloaded the version from the test results and it did boot.
> > These are combining the uImage and dtb. How do you accomplish this?
> 
> It should be noted that when you try to boot the seperate zImage and dtb from
> the test build it fails. This replicates my issue.
> 
> Here are the two binaries that I used:
> http://www.pwsan.com/omap/testlogs/test_v3.16-rc5/20140716140950/build_z/omap2plus_defconfig/zImage
> http://www.pwsan.com/omap/testlogs/test_v3.16-rc5/20140716140950/dtbs/am3517-evm.dtb
> 
> Here is the boot attempt:
> U-Boot> dhcp;set serverip 10.0.2.168;tftp 0x82000000 zImage; tftp 0x80000000 am3517-evm.dtb;bootz 0x82000000 - 0x80000000
> BOOTP broadcast 1
> DHCP client bound to address 10.0.3.33
> Using DaVinci-EMAC device
> TFTP from server 10.0.2.168; our IP address is 10.0.3.33
> Filename 'zImage'.
> Load address: 0x82000000
> Loading: #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          ######################################
>          2 MiB/s
> done
> Bytes transferred = 4360800 (428a60 hex)
> Using DaVinci-EMAC device
> TFTP from server 10.0.2.168; our IP address is 10.0.3.33
> Filename 'am3517-evm.dtb'.
> Load address: 0x80000000
> Loading: ####
>          1.8 MiB/s
> done
> Bytes transferred = 50145 (c3e1 hex)
> Kernel image @ 0x82000000 [ 0x000000 - 0x428a60 ]
> ## Flattened Device Tree blob at 80000000
>    Booting using the fdt blob at 0x80000000
>    Loading Device Tree to 9ff05000, end 9ff143e0 ... OK
> 
> Starting kernel ...
> 
> Using the exact same boot sequence worked for 3.10 and 3.14.

Hmm maybe we still have some relocation issues left and the kernel
or the .dtb size has changed enough to cause trouble. Can you
try with .dtb at a different address?

Regards,

Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Michael Welling]

On Mon, Jul 21, 2014 at 12:09:13AM -0700, Tony Lindgren wrote:
> * Michael Welling <mwelling@emacinc.com> [140718 07:42]:
> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> > >
> > > Hmm maybe double check your're booting device tree based kernel
> > > instead of legacy machine ID based kernel? The legacy booting should
> > > still work just fine and no changes has been made to it, but it will
> > > get removed shortly.
> >
> > I downloaded the version from the test results and it did boot.
> 
> OK that's good to hear.
> 
> > These are combining the uImage and dtb. How do you accomplish this?
> 
> You need to make sure you have the appended DTB support enabled like
> we do in omap2plus_defconfig:
> 
> CONFIG_ARM_APPENDED_DTB=y
> CONFIG_ARM_ATAG_DTB_COMPAT=y
> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
> 
> Then just cat zImage board.dtb > /tmp/zImage-dtba and run
> mkimage to convert it to a uImage:
> 
> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
> 	-n "Linux" -d /tmp/zImage-dtba /tmp/uImage
> 

I actually discovered this and got LCD video working. Now USB host is
not working. The only thing that registers is the OHCI/EHCI hosts.

root@som3517:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Not sure what the problem is. The USB devices that are plugged in are
powered but never detected.

Any hints?

> Regards,
> 
> Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Michael Welling]

On Mon, Jul 21, 2014 at 11:38 AM, Michael Welling <mwelling@emacinc.com> wrote:
> On Mon, Jul 21, 2014 at 12:09:13AM -0700, Tony Lindgren wrote:
>> * Michael Welling <mwelling@emacinc.com> [140718 07:42]:
>> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
>> > >
>> > > Hmm maybe double check your're booting device tree based kernel
>> > > instead of legacy machine ID based kernel? The legacy booting should
>> > > still work just fine and no changes has been made to it, but it will
>> > > get removed shortly.
>> >
>> > I downloaded the version from the test results and it did boot.
>>
>> OK that's good to hear.
>>
>> > These are combining the uImage and dtb. How do you accomplish this?
>>
>> You need to make sure you have the appended DTB support enabled like
>> we do in omap2plus_defconfig:
>>
>> CONFIG_ARM_APPENDED_DTB=y
>> CONFIG_ARM_ATAG_DTB_COMPAT=y
>> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
>>
>> Then just cat zImage board.dtb > /tmp/zImage-dtba and run
>> mkimage to convert it to a uImage:
>>
>> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
>>       -n "Linux" -d /tmp/zImage-dtba /tmp/uImage
>>
>
> I actually discovered this and got LCD video working. Now USB host is
> not working. The only thing that registers is the OHCI/EHCI hosts.
>
> root@som3517:~# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Not sure what the problem is. The USB devices that are plugged in are
> powered but never detected.
>
> Any hints?

So I got the USB host to work on boot with additional entries in the devicetree.
Documentation/devicetree/bindings/omap-usb-host.txt

Though the devices work if plugged in at boot, any time a device is
hotplugged then
the device is not detected. It is powered very briefly and then off
without any kernel messages.

So hints from this point would be good.

>
>> Regards,
>>
>> Tony

Re: AM3517 fails to boot 3.16-rc5 device tree kernel

[Tony Lindgren]

* Michael Welling <mwelling@emacinc.com> [140721 17:17]:
> On Mon, Jul 21, 2014 at 11:38 AM, Michael Welling <mwelling@emacinc.com> wrote:
> > On Mon, Jul 21, 2014 at 12:09:13AM -0700, Tony Lindgren wrote:
> >> * Michael Welling <mwelling@emacinc.com> [140718 07:42]:
> >> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> >> > >
> >> > > Hmm maybe double check your're booting device tree based kernel
> >> > > instead of legacy machine ID based kernel? The legacy booting should
> >> > > still work just fine and no changes has been made to it, but it will
> >> > > get removed shortly.
> >> >
> >> > I downloaded the version from the test results and it did boot.
> >>
> >> OK that's good to hear.
> >>
> >> > These are combining the uImage and dtb. How do you accomplish this?
> >>
> >> You need to make sure you have the appended DTB support enabled like
> >> we do in omap2plus_defconfig:
> >>
> >> CONFIG_ARM_APPENDED_DTB=y
> >> CONFIG_ARM_ATAG_DTB_COMPAT=y
> >> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
> >>
> >> Then just cat zImage board.dtb > /tmp/zImage-dtba and run
> >> mkimage to convert it to a uImage:
> >>
> >> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
> >>       -n "Linux" -d /tmp/zImage-dtba /tmp/uImage
> >>
> >
> > I actually discovered this and got LCD video working. Now USB host is
> > not working. The only thing that registers is the OHCI/EHCI hosts.
> >
> > root@som3517:~# lsusb
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> >
> > Not sure what the problem is. The USB devices that are plugged in are
> > powered but never detected.
> >
> > Any hints?
> 
> So I got the USB host to work on boot with additional entries in the devicetree.
> Documentation/devicetree/bindings/omap-usb-host.txt
> 
> Though the devices work if plugged in at boot, any time a device is
> hotplugged then
> the device is not detected. It is powered very briefly and then off
> without any kernel messages.
> 
> So hints from this point would be good.

Sorry no idea on that, maybe send a separate email about that with
the USB and PHY people in Cc.

Regards,

Tony