Linux 3.14-rc7 on Pandaboard ES Rev. B1 doesn't boot

[Juri Lelli]

Hi all,

I'm trying to run Linux 3.14-rc7 on a Pandaboard ES Rev. B1.
After configuring the kernel with omap2plus_defconfig, I also enabled
USB support and low-level debug, and disabled modules (config attached).
dtb is compiled and passed to u-boot at boot.

I'm using linaro u-boot from
git://git.linaro.org/boot/u-boot-linaro-stable.git branch
Linaro-u-boot-2012.04.2, and this is my boot script:

set kaddr 0x80008000
set dtbaddr 0x82000000
set autoload no
set serverip 10.30.3.54
set console ttyO2,115200n8 earlyprintk debug
set bootargs 'console=${console} root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait init=/sbin/init'
set usbethaddr 2E:60:D4:7B:4E:01
usb start
dhcp
tftp ${kaddr} uImage
tftp ${dtbaddr} omap4-panda-es.dtb
bootm ${kaddr} - ${dtbaddr}

The system doesn't boot, it hangs while loading the kernel with this
output printed to the console:

U-Boot SPL 2012.04.01 (Mar 18 2014 - 15:40:22)
OMAP4460 ES1.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2012.04.01 (Mar 18 2014 - 15:40:22)

CPU : OMAP4460 ES1.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
checking for preEnv.txt
reading preEnv.txt

** Unable to read "preEnv.txt" from mmc 0:1 **
Hit any key to stop autoboot: 0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
reading boot.scr

431 bytes read
Loaded script from boot.scr
Running bootscript from mmc0 ...
## Executing script at 82000000
(Re)start USB...
USB: Register 1313 NbrPorts 3
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
scanning bus for ethernet devices... 1 Ethernet Device(s) found
Waiting for Ethernet connection... done.
BOOTP broadcast 1
DHCP client bound to address 10.30.3.139
Waiting for Ethernet connection... done.
Using sms0 device
TFTP from server 10.30.3.54; our IP address is 10.30.3.139
Filename 'uImage'.
Load address: 0x80008000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
######################
done
Bytes transferred = 4768064 (48c140 hex)
Waiting for Ethernet connection... done.
Using sms0 device
TFTP from server 10.30.3.54; our IP address is 10.30.3.139
Filename 'omap4-panda-es.dtb'.
Load address: 0x82000000
Loading: ##########
done
Bytes transferred = 50489 (c539 hex)
## Booting kernel from Legacy Image at 80008000 ...
Image Name: Linux-3.14.0-rc7-00023-g9a15c94
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4768000 Bytes = 4.5 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
XIP Kernel Image ... OK
OK
Loading Device Tree to bfee6000, end bfef5538 ... OK

Starting kernel ...

Then nothing happens. I expect at least something to be printed due to
the earlyprintk boot argument.

How can I further debug what's happening?

Thank in advance.

Best Regards,

- Juri

[Michael Trimarchi]

Hi Juri

On Tue, Mar 18, 2014 at 4:14 PM, Juri Lelli <juri....@gmail.com> wrote:

Hi all,

I'm trying to run Linux 3.14-rc7 on a Pandaboard ES Rev. B1.
After configuring the kernel with omap2plus_defconfig, I also enabled
USB support and low-level debug, and disabled modules (config attached).
dtb is compiled and passed to u-boot at boot.

I'm using linaro u-boot from
git://git.linaro.org/boot/u-boot-linaro-stable.git branch
Linaro-u-boot-2012.04.2, and this is my boot script:

set kaddr 0x80008000
set dtbaddr 0x82000000

set kaddr 0x82000000
set dtbaddr 0x80f80000

Here you have the error I think.

Michael

 

OK
   Loading Device Tree to bfee6000, end bfef5538 ... OK

Starting kernel ...

Then nothing happens. I expect at least something to be printed due to
the earlyprintk boot argument.

How can I further debug what's happening?

Thank in advance.

Best Regards,

- Juri

--
You received this message because you are subscribed to the Google Groups "pandaboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandaboard+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Allan Granados]

Hi Juri,

What version of cross GCC are you using?

Does the LED stop blinking after you receive that message?

Regards 

--Allan Granados Jiménez

[Juri Lelli]

Hi Michael,

On Tue, 18 Mar 2014 23:02:34 +0100
Michael Trimarchi <michaelt...@gmail.com> wrote:

> Hi Juri
>
> On Tue, Mar 18, 2014 at 4:14 PM, Juri Lelli <juri....@gmail.com> wrote:
>
> > Hi all,
> >
> > I'm trying to run Linux 3.14-rc7 on a Pandaboard ES Rev. B1.
> > After configuring the kernel with omap2plus_defconfig, I also enabled
> > USB support and low-level debug, and disabled modules (config attached).
> > dtb is compiled and passed to u-boot at boot.
> >
> > I'm using linaro u-boot from
> > git://git.linaro.org/boot/u-boot-linaro-stable.git branch
> > Linaro-u-boot-2012.04.2, and this is my boot script:
> >
> > set kaddr 0x80008000
> > set dtbaddr 0x82000000
> >
>
> set kaddr 0x82000000
> set dtbaddr 0x80f80000
>
>

Changed that, but quite the same result:

BOOTP broadcast 2

DHCP client bound to address 10.30.3.139
Waiting for Ethernet connection... done.
Using sms0 device
TFTP from server 10.30.3.54; our IP address is 10.30.3.139
Filename 'uImage'.

Load address: 0x82000000

Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###################################################

done
Bytes transferred = 4254496 (40eb20 hex)

Waiting for Ethernet connection... done.
Using sms0 device
TFTP from server 10.30.3.54; our IP address is 10.30.3.139
Filename 'omap4-panda-es.dtb'.

Load address: 0x80f80000
Loading: T ##########

done
Bytes transferred = 50489 (c539 hex)

## Booting kernel from Legacy Image at 82000000 ...

Image Name: Linux-3.14.0-rc7-00023-g9a15c94
Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 4254432 Bytes = 4.1 MiB
Load Address: 82000000
Entry Point: 82000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
Booting using the fdt blob at 0x80f80000

XIP Kernel Image ... OK

OK
Loading Device Tree to bfee6000, end bfef5538 ... OK

Starting kernel ...

It is actually different from below. It seems that DT is loaded
somewhere else than where I said to load it. Do I read it correctly?

Thanks,

- Juri

[Michael Trimarchi]

Hi

On Wed, Mar 19, 2014 at 10:09 AM, Juri Lelli <juri....@gmail.com> wrote:

Hi Michael,

On Tue, 18 Mar 2014 23:02:34 +0100
Michael Trimarchi <michaelt...@gmail.com> wrote:

> Hi Juri
>
> On Tue, Mar 18, 2014 at 4:14 PM, Juri Lelli <juri....@gmail.com> wrote:
>
> > Hi all,
> >
> > I'm trying to run Linux 3.14-rc7 on a Pandaboard ES Rev. B1.
> > After configuring the kernel with omap2plus_defconfig, I also enabled
> > USB support and low-level debug, and disabled modules (config attached).
> > dtb is compiled and passed to u-boot at boot.
> >
> > I'm using linaro u-boot from
> > git://git.linaro.org/boot/u-boot-linaro-stable.git branch
> > Linaro-u-boot-2012.04.2, and this is my boot script:
> >
> > set kaddr 0x80008000
> > set dtbaddr 0x82000000
> >

Can you use bootz ${kaddr} - ${dtbaddr}?

Michael

[Bastian Bittorf]

> > > I'm trying to run Linux 3.14-rc7 on a Pandaboard ES Rev. B1.

seems you forgot to update your *.dts file.
(during building the kernel, the *.dts is also build)

bye, bastian