pandaboard not booting

pandaboard not booting

[Radu Moisan]

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

Hi guys,
I tried to start pandaboard with latest from master but it got stuck 
booting the kernel.
This is all I got, do you have any idea what am I missing?


U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
Texas Instruments OMAP4430 ES2.3
Bypassing DPLL failed 4a008180
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)

CPU  : OMAP4430 ES2.3
Board: OMAP4 Panda
I2C:   ready
DRAM:  1 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
reading boot.scr

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

4176612 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 82000000 ...
    Image Name:   Linux-3.1.0
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    4176548 Bytes = 4 MiB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Thanks,
Radu

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

Re: pandaboard not booting

[Radu Moisan]

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

Hi guys,
Can anyone tell me if pandaboard is working with master branch of poky? 
I just don't want to waste my time figuring out what I've done wrong, if 
the build is not working anyway.

Thanks,
Radu

On 09/25/2012 04:43 PM, Radu Moisan wrote:
> Hi guys,
> I tried to start pandaboard with latest from master but it got stuck 
> booting the kernel.
> This is all I got, do you have any idea what am I missing?
>
>
> U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
> Texas Instruments OMAP4430 ES2.3
> Bypassing DPLL failed 4a008180
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)
>
> CPU  : OMAP4430 ES2.3
> Board: OMAP4 Panda
> I2C:   ready
> DRAM:  1 GiB
> MMC:   OMAP SD/MMC: 0
> Using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Hit any key to stop autoboot:  0
> reading boot.scr
>
> ** Unable to read "boot.scr" from mmc 0:1 **
> reading uImage
>
> 4176612 bytes read
> Booting from mmc0 ...
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   Linux-3.1.0
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4176548 Bytes = 4 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
>
> Thanks,
> Radu
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


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

Re: pandaboard not booting

[Enrico]

On Wed, Sep 26, 2012 at 10:02 AM, Radu Moisan <radu.moisan@intel.com> wrote:
> Hi guys,
> Can anyone tell me if pandaboard is working with master branch of poky? I
> just don't want to waste my time figuring out what I've done wrong, if the
> build is not working anyway.

It's a long time since i tried it but it was working, can you post
your bootloader env? Maybe you are just missing the console=ttyO2...
part.

Enrico

Re: pandaboard not booting

[Radu Moisan]

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

Hi Enrico,
I'm not sure what are you reffering to when you say bootloader env, but 
here's what I get on my console:

U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
Texas Instruments OMAP4430 ES2.3
Bypassing DPLL failed 4a008180
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)

CPU  : OMAP4430 ES2.3
Board: OMAP4 Panda
I2C:   ready
DRAM:  1 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
reading boot.scr

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

4176612 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 82000000 ...
    Image Name:   Linux-3.1.0
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    4176548 Bytes = 4 MiB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

All I did to build it, was to add meta-ti to my bblayers.conf and try 
bitbake with MACHINE=pandaboard. The build was screaming about some QA 
errors, which I had to disable to get the build finish. I'm assuming 
those are the reason for my failure. However, I did not investigate 
further into these.

Thanks,
Radu

On 09/26/2012 12:20 PM, Enrico wrote:
> On Wed, Sep 26, 2012 at 10:02 AM, Radu Moisan <radu.moisan@intel.com> wrote:
>> Hi guys,
>> Can anyone tell me if pandaboard is working with master branch of poky? I
>> just don't want to waste my time figuring out what I've done wrong, if the
>> build is not working anyway.
> It's a long time since i tried it but it was working, can you post
> your bootloader env? Maybe you are just missing the console=ttyO2...
> part.
>
> Enrico


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

Re: pandaboard not booting

[Gary Thomas]

On 2012-09-26 04:44, Radu Moisan wrote:
> Hi Enrico,
> I'm not sure what are you reffering to when you say bootloader env, but here's what I get on my console:
>
> U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
> Texas Instruments OMAP4430 ES2.3
> Bypassing DPLL failed 4a008180
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)
>
> CPU  : OMAP4430 ES2.3
> Board: OMAP4 Panda
> I2C:   ready
> DRAM:  1 GiB
> MMC:   OMAP SD/MMC: 0
> Using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Hit any key to stop autoboot:  0
> reading boot.scr
>
> ** Unable to read "boot.scr" from mmc 0:1 **
> reading uImage
>
> 4176612 bytes read
> Booting from mmc0 ...
> ## Booting kernel from Legacy Image at 82000000 ...
>     Image Name:   Linux-3.1.0
>     Image Type:   ARM Linux Kernel Image (uncompressed)
>     Data Size:    4176548 Bytes = 4 MiB
>     Load Address: 80008000
>     Entry Point:  80008000
>     Verifying Checksum ... OK
>     Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> All I did to build it, was to add meta-ti to my bblayers.conf and try bitbake with MACHINE=pandaboard. The build was screaming about some QA errors, which I had to disable to get
> the build finish. I'm assuming those are the reason for my failure. However, I did not investigate further into these.

Break into U-Boot during the boot process and show us what you get from
the 'printenv' command.  This will show the default value of 'bootargs'
which is what is being used since you don't have a 'boot.scr' script

> On 09/26/2012 12:20 PM, Enrico wrote:
>> On Wed, Sep 26, 2012 at 10:02 AM, Radu Moisan<radu.moisan@intel.com>  wrote:
>>> Hi guys,
>>> Can anyone tell me if pandaboard is working with master branch of poky? I
>>> just don't want to waste my time figuring out what I've done wrong, if the
>>> build is not working anyway.
>> It's a long time since i tried it but it was working, can you post
>> your bootloader env? Maybe you are just missing the console=ttyO2...
>> part.
>>
>> Enrico

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: pandaboard not booting

[Radu Moisan]

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


On 09/26/2012 01:49 PM, Gary Thomas wrote:
> On 2012-09-26 04:44, Radu Moisan wrote:
>> Hi Enrico,
>> I'm not sure what are you reffering to when you say bootloader env, 
>> but here's what I get on my console:
>>
>> U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
>> Texas Instruments OMAP4430 ES2.3
>> Bypassing DPLL failed 4a008180
>> OMAP SD/MMC: 0
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)
>>
>> CPU  : OMAP4430 ES2.3
>> Board: OMAP4 Panda
>> I2C:   ready
>> DRAM:  1 GiB
>> MMC:   OMAP SD/MMC: 0
>> Using default environment
>>
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Hit any key to stop autoboot:  0
>> reading boot.scr
>>
>> ** Unable to read "boot.scr" from mmc 0:1 **
>> reading uImage
>>
>> 4176612 bytes read
>> Booting from mmc0 ...
>> ## Booting kernel from Legacy Image at 82000000 ...
>>     Image Name:   Linux-3.1.0
>>     Image Type:   ARM Linux Kernel Image (uncompressed)
>>     Data Size:    4176548 Bytes = 4 MiB
>>     Load Address: 80008000
>>     Entry Point:  80008000
>>     Verifying Checksum ... OK
>>     Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>>
>> All I did to build it, was to add meta-ti to my bblayers.conf and try 
>> bitbake with MACHINE=pandaboard. The build was screaming about some 
>> QA errors, which I had to disable to get
>> the build finish. I'm assuming those are the reason for my failure. 
>> However, I did not investigate further into these.
>
> Break into U-Boot during the boot process and show us what you get from
> the 'printenv' command.  This will show the default value of 'bootargs'
> which is what is being used since you don't have a 'boot.scr' script
>
Panda # printenv
baudrate=115200
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run 
bootscript; else if run loaduimage; then run mmcboot; fi; fi; fi
bootdelay=3
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyO2,115200n8
loadaddr=0x82000000
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} vram=${vram} root=${mmcroot} 
rootfstype=${mmcrootfstype}
mmcboot=echo Booting from mmc${mmcdev} ...; run mmcargs; bootm ${loadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext4 rootwait
usbtty=cdc_acm
vram=16M

Environment size: 686/131068 bytes

Thanks,
Radu


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

Re: pandaboard not booting

[Gary Thomas]

On 2012-09-26 06:42, Radu Moisan wrote:
>
> On 09/26/2012 01:49 PM, Gary Thomas wrote:
>> On 2012-09-26 04:44, Radu Moisan wrote:
>>> Hi Enrico,
>>> I'm not sure what are you reffering to when you say bootloader env, but here's what I get on my console:
>>>
>>> U-Boot SPL 2011.12-dirty (Sep 24 2012 - 17:18:42)
>>> Texas Instruments OMAP4430 ES2.3
>>> Bypassing DPLL failed 4a008180
>>> OMAP SD/MMC: 0
>>> reading u-boot.img
>>> reading u-boot.img
>>>
>>>
>>> U-Boot 2011.12-dirty (Sep 24 2012 - 17:18:42)
>>>
>>> CPU  : OMAP4430 ES2.3
>>> Board: OMAP4 Panda
>>> I2C:   ready
>>> DRAM:  1 GiB
>>> MMC:   OMAP SD/MMC: 0
>>> Using default environment
>>>
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Hit any key to stop autoboot:  0
>>> reading boot.scr
>>>
>>> ** Unable to read "boot.scr" from mmc 0:1 **
>>> reading uImage
>>>
>>> 4176612 bytes read
>>> Booting from mmc0 ...
>>> ## Booting kernel from Legacy Image at 82000000 ...
>>>     Image Name:   Linux-3.1.0
>>>     Image Type:   ARM Linux Kernel Image (uncompressed)
>>>     Data Size:    4176548 Bytes = 4 MiB
>>>     Load Address: 80008000
>>>     Entry Point:  80008000
>>>     Verifying Checksum ... OK
>>>     Loading Kernel Image ... OK
>>> OK
>>>
>>> Starting kernel ...
>>>
>>> Uncompressing Linux... done, booting the kernel.
>>>
>>> All I did to build it, was to add meta-ti to my bblayers.conf and try bitbake with MACHINE=pandaboard. The build was screaming about some QA errors, which I had to disable to get
>>> the build finish. I'm assuming those are the reason for my failure. However, I did not investigate further into these.
>>
>> Break into U-Boot during the boot process and show us what you get from
>> the 'printenv' command.  This will show the default value of 'bootargs'
>> which is what is being used since you don't have a 'boot.scr' script
>>
> Panda # printenv
> baudrate=115200
> bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; fi; fi; fi
> bootdelay=3
> bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
> console=ttyO2,115200n8
> loadaddr=0x82000000
> loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
> loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
> mmcargs=setenv bootargs console=${console} vram=${vram} root=${mmcroot} rootfstype=${mmcrootfstype}
> mmcboot=echo Booting from mmc${mmcdev} ...; run mmcargs; bootm ${loadaddr}
> mmcdev=0
> mmcroot=/dev/mmcblk0p2 ro
> mmcrootfstype=ext4 rootwait
> usbtty=cdc_acm
> vram=16M
>
> Environment size: 686/131068 bytes

This looks correct - the important bit is that console=ttyO2

Diagnosing why this doesn't come up may be a bit trickier.  One thing that you
can do is to look at the kernel messages (which are not being printed!).  Thankfully,
those are kept buffered in memory and you should be able to print them manually.

Give these steps a go:
   * Boot as you have been, letting it hang after starting the kernel
   * Press the RESET button on the PandaBoard
   * Break into U-Boot
   * Dump the kernel messages via:
       U-Boot> md LOG_BUF_ADDRESS
     This will display 256 bytes at LOG_BUF_ADDRESS.  If you just press return, you'll
     get to see the next 256 bytes, etc.  Keep doing this until the messages stop...

To find the LOG_BUF_ADDRESS, search for __log_buf in the System.map which was created
when you built your kernel.  This will be in your Yocto build tree .../tmp/work/pandaboard*/linux*/git
(I think - I don't have a build for this machine handy)  You'll see something like this:
    $ grep __log_buf tmp/work/panda*/linux*/git/System.map
    c06d66e9 b __log_buf
That's a virtual address which corresponds to 0x806d66e9 in physical RAM.  Truncate
the address to a longword value, i.e. 0x806d66e8 - that's LOG_BUF_ADDRESS

See what you get, it may provide a clue where the kernel is crashing.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: pandaboard not booting

[Radu Moisan]

> This looks correct - the important bit is that console=ttyO2
>
> Diagnosing why this doesn't come up may be a bit trickier.  One thing 
> that you
> can do is to look at the kernel messages (which are not being 
> printed!).  Thankfully,
> those are kept buffered in memory and you should be able to print them 
> manually.
>
> Give these steps a go:
>   * Boot as you have been, letting it hang after starting the kernel
>   * Press the RESET button on the PandaBoard
>   * Break into U-Boot
>   * Dump the kernel messages via:
>       U-Boot> md LOG_BUF_ADDRESS
>     This will display 256 bytes at LOG_BUF_ADDRESS.  If you just press 
> return, you'll
>     get to see the next 256 bytes, etc.  Keep doing this until the 
> messages stop...
>
> To find the LOG_BUF_ADDRESS, search for __log_buf in the System.map 
> which was created
> when you built your kernel.  This will be in your Yocto build tree 
> .../tmp/work/pandaboard*/linux*/git
> (I think - I don't have a build for this machine handy)  You'll see 
> something like this:
>    $ grep __log_buf tmp/work/panda*/linux*/git/System.map
>    c06d66e9 b __log_buf
> That's a virtual address which corresponds to 0x806d66e9 in physical 
> RAM.  Truncate
> the address to a longword value, i.e. 0x806d66e8 - that's LOG_BUF_ADDRESS
>
> See what you get, it may provide a clue where the kernel is crashing.
>
Everything went ok, except the board doesn't reset when I press the 
reset button, or at least I can't see that in the serial console, it 
stays stuck at line "booting kernel..."

Radu

Re: pandaboard not booting

[Christian.Schulenberg]

Hi,

I would like to jump into this discussion, as I'm facing exact the same problem. I try to build the meta-ivi System. Therefore, I have setup my system with the following layers:

- meta-ivi
- meta-systemd
- poky
- meta-ti

bblayers.conf looks like this:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/csb/yocto-excalibur/yocto-ivi/meta-ti \
  /home/csb/yocto-excalibur/yocto-ivi/poky/meta \
  /home/csb /yocto-excalibur/yocto-ivi/poky/meta-yocto \
  /home/csb /yocto-excalibur/yocto-ivi/meta-ivi \
  /home/csb /yocto-excalibur/yocto-ivi/meta-systemd \
  "

The meta-ti misc subdir is excluded from build via BBMASK = "meta-ti/recipes-misc" in local.conf. MACHINE is set to pandabaord -> MACHINE ??= "pandaboard"

The build process went through without any suspicious warnings. But in the end, I stuck with the same problem as Radu, except the fact, that I'm using a boot.scr. Here is my console output:

U-Boot SPL 2011.12-dirty (Sep 27 2012 - 07:42:14)
Texas Instruments OMAP4460 ES1.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.12-dirty (Sep 27 2012 - 07:42:14)

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
Hit any key to stop autoboot:  0
reading boot.scr

390 bytes read
Running bootscript from mmc0 ...
## Executing script at 82000000
reading uImage

4176496 bytes read
## Booting kernel from Legacy Image at 80000000 ...
   Image Name:   Linux-3.1.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4176432 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

At the end, both LED's on Pandaboard (D1 and D2) are switched on. Pressing reset does not help, only LED D1 is switched off.

I used the meta.ivi layer in combination with meta-ti before in a much older version, which worked fine for me, but at the moment I have no idea what's wrong with my configuration.


Best regards,
Christian

-----Ursprüngliche Nachricht-----
Von: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] Im Auftrag von Radu Moisan
Gesendet: Mittwoch, 26. September 2012 15:50
An: meta-ti@yoctoproject.org
Betreff: Re: [meta-ti] pandaboard not booting


> This looks correct - the important bit is that console=ttyO2
>
> Diagnosing why this doesn't come up may be a bit trickier.  One thing 
> that you
> can do is to look at the kernel messages (which are not being 
> printed!).  Thankfully,
> those are kept buffered in memory and you should be able to print them 
> manually.
>
> Give these steps a go:
>   * Boot as you have been, letting it hang after starting the kernel
>   * Press the RESET button on the PandaBoard
>   * Break into U-Boot
>   * Dump the kernel messages via:
>       U-Boot> md LOG_BUF_ADDRESS
>     This will display 256 bytes at LOG_BUF_ADDRESS.  If you just press 
> return, you'll
>     get to see the next 256 bytes, etc.  Keep doing this until the 
> messages stop...
>
> To find the LOG_BUF_ADDRESS, search for __log_buf in the System.map 
> which was created
> when you built your kernel.  This will be in your Yocto build tree 
> .../tmp/work/pandaboard*/linux*/git
> (I think - I don't have a build for this machine handy)  You'll see 
> something like this:
>    $ grep __log_buf tmp/work/panda*/linux*/git/System.map
>    c06d66e9 b __log_buf
> That's a virtual address which corresponds to 0x806d66e9 in physical 
> RAM.  Truncate
> the address to a longword value, i.e. 0x806d66e8 - that's LOG_BUF_ADDRESS
>
> See what you get, it may provide a clue where the kernel is crashing.
>
Everything went ok, except the board doesn't reset when I press the 
reset button, or at least I can't see that in the serial console, it 
stays stuck at line "booting kernel..."

Radu
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: pandaboard not booting

[Radu Moisan]

Same led story on my side as well.

Radu

On 09/27/2012 10:25 AM, Christian.Schulenberg@bmw.de wrote:
> Hi,
>
> I would like to jump into this discussion, as I'm facing exact the same problem. I try to build the meta-ivi System. Therefore, I have setup my system with the following layers:
>
> - meta-ivi
> - meta-systemd
> - poky
> - meta-ti
>
> bblayers.conf looks like this:
>
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> # changes incompatibly
> LCONF_VERSION = "5"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
>    /home/csb/yocto-excalibur/yocto-ivi/meta-ti \
>    /home/csb/yocto-excalibur/yocto-ivi/poky/meta \
>    /home/csb /yocto-excalibur/yocto-ivi/poky/meta-yocto \
>    /home/csb /yocto-excalibur/yocto-ivi/meta-ivi \
>    /home/csb /yocto-excalibur/yocto-ivi/meta-systemd \
>    "
>
> The meta-ti misc subdir is excluded from build via BBMASK = "meta-ti/recipes-misc" in local.conf. MACHINE is set to pandabaord -> MACHINE ??= "pandaboard"
>
> The build process went through without any suspicious warnings. But in the end, I stuck with the same problem as Radu, except the fact, that I'm using a boot.scr. Here is my console output:
>
> U-Boot SPL 2011.12-dirty (Sep 27 2012 - 07:42:14)
> Texas Instruments OMAP4460 ES1.1
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2011.12-dirty (Sep 27 2012 - 07:42:14)
>
> 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
> Hit any key to stop autoboot:  0
> reading boot.scr
>
> 390 bytes read
> Running bootscript from mmc0 ...
> ## Executing script at 82000000
> reading uImage
>
> 4176496 bytes read
> ## Booting kernel from Legacy Image at 80000000 ...
>     Image Name:   Linux-3.1.0
>     Image Type:   ARM Linux Kernel Image (uncompressed)
>     Data Size:    4176432 Bytes = 4 MiB
>     Load Address: 80008000
>     Entry Point:  80008000
>     Verifying Checksum ... OK
>     Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> At the end, both LED's on Pandaboard (D1 and D2) are switched on. Pressing reset does not help, only LED D1 is switched off.
>
> I used the meta.ivi layer in combination with meta-ti before in a much older version, which worked fine for me, but at the moment I have no idea what's wrong with my configuration.
>
>
> Best regards,
> Christian
>
> -----Ursprüngliche Nachricht-----
> Von: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] Im Auftrag von Radu Moisan
> Gesendet: Mittwoch, 26. September 2012 15:50
> An: meta-ti@yoctoproject.org
> Betreff: Re: [meta-ti] pandaboard not booting
>
>
>> This looks correct - the important bit is that console=ttyO2
>>
>> Diagnosing why this doesn't come up may be a bit trickier.  One thing
>> that you
>> can do is to look at the kernel messages (which are not being
>> printed!).  Thankfully,
>> those are kept buffered in memory and you should be able to print them
>> manually.
>>
>> Give these steps a go:
>>    * Boot as you have been, letting it hang after starting the kernel
>>    * Press the RESET button on the PandaBoard
>>    * Break into U-Boot
>>    * Dump the kernel messages via:
>>        U-Boot> md LOG_BUF_ADDRESS
>>      This will display 256 bytes at LOG_BUF_ADDRESS.  If you just press
>> return, you'll
>>      get to see the next 256 bytes, etc.  Keep doing this until the
>> messages stop...
>>
>> To find the LOG_BUF_ADDRESS, search for __log_buf in the System.map
>> which was created
>> when you built your kernel.  This will be in your Yocto build tree
>> .../tmp/work/pandaboard*/linux*/git
>> (I think - I don't have a build for this machine handy)  You'll see
>> something like this:
>>     $ grep __log_buf tmp/work/panda*/linux*/git/System.map
>>     c06d66e9 b __log_buf
>> That's a virtual address which corresponds to 0x806d66e9 in physical
>> RAM.  Truncate
>> the address to a longword value, i.e. 0x806d66e8 - that's LOG_BUF_ADDRESS
>>
>> See what you get, it may provide a clue where the kernel is crashing.
>>
> Everything went ok, except the board doesn't reset when I press the
> reset button, or at least I can't see that in the serial console, it
> stays stuck at line "booting kernel..."
>
> Radu
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: pandaboard not booting

[Enrico]

On Thu, Sep 27, 2012 at 9:25 AM,  <Christian.Schulenberg@bmw.de> wrote:
> I used the meta.ivi layer in combination with meta-ti before in a much older version, which worked fine for me, but at the moment I have no idea what's wrong with my configuration.

Maybe it's not a problem with your config but just a kernel bug or a
faulty toolchain+kernel combination.

You can try to manually build a (recent) kernel and see if it boots,
if you need directions just ask.

Enrico

Re: pandaboard not booting

[Christian.Schulenberg]

I'm using the same kernel version as I did before. It's the default kernel 3.1 as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision: a5c60c099296fcfc0c8fa8085c40883971486512

Do you really think it makes sense to switch to a more recent one?




-----Ursprüngliche Nachricht-----
Von: ebutera@gmail.com [mailto:ebutera@gmail.com] Im Auftrag von Enrico
Gesendet: Donnerstag, 27. September 2012 10:48
An: Schulenberg Christian, EI-42
Cc: radu.moisan@intel.com; meta-ti@yoctoproject.org
Betreff: Re: [meta-ti] pandaboard not booting

On Thu, Sep 27, 2012 at 9:25 AM,  <Christian.Schulenberg@bmw.de> wrote:
> I used the meta.ivi layer in combination with meta-ti before in a much older version, which worked fine for me, but at the moment I have no idea what's wrong with my configuration.

Maybe it's not a problem with your config but just a kernel bug or a
faulty toolchain+kernel combination.

You can try to manually build a (recent) kernel and see if it boots,
if you need directions just ask.

Enrico

Re: pandaboard not booting

[Enrico]

On Thu, Sep 27, 2012 at 1:16 PM,  <Christian.Schulenberg@bmw.de> wrote:
> I'm using the same kernel version as I did before. It's the default kernel 3.1 as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision: a5c60c099296fcfc0c8fa8085c40883971486512
>
> Do you really think it makes sense to switch to a more recent one?

No, but i have no better ideas right now...

You could check if it's a known toolchain bug with that kernel, but i
think it would be faster to try a newer kernel (from the same
repository, ti ubuntu integration).

Enrico

Re: pandaboard not booting

[Christian.Schulenberg]

Hi,

as I wrote before, I have an older version. I used the kernel version of that one to start up my new meta-ivi build. It crashed later with a kernel panic, but at least the kernel is running.

After that I compared the two kernel version I have, with mkimage -l.

1. Kernel version that is working quite well:

mkimage -l uImage
Image Name:   Linux-3.1.0
Created:      Fri Sep 21 11:25:32 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    4144744 Bytes = 4047.60 kB = 3.95 MB
Load Address: 80008000
Entry Point:  80008000

2. Kernel version that fails after uncompression:

mkimage -l uImage
Image Name:   Linux-3.1.0
Created:      Thu Sep 27 07:07:25 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    4176432 Bytes = 4078.55 kB = 3.98 MB
Load Address: 80008000
Entry Point:  80008000

I don't see any major issues here, so I guess I need to check the toolchain as proposed by Enrico.

Christian

-----Ursprüngliche Nachricht-----
Von: ebutera@gmail.com [mailto:ebutera@gmail.com] Im Auftrag von Enrico
Gesendet: Donnerstag, 27. September 2012 14:07
An: Schulenberg Christian, EI-42
Cc: meta-ti@yoctoproject.org
Betreff: Re: [meta-ti] pandaboard not booting

On Thu, Sep 27, 2012 at 1:16 PM,  <Christian.Schulenberg@bmw.de> wrote:
> I'm using the same kernel version as I did before. It's the default kernel 3.1 as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision: a5c60c099296fcfc0c8fa8085c40883971486512
>
> Do you really think it makes sense to switch to a more recent one?

No, but i have no better ideas right now...

You could check if it's a known toolchain bug with that kernel, but i
think it would be faster to try a newer kernel (from the same
repository, ti ubuntu integration).

Enrico

Re: pandaboard not booting

[Khem Raj]

On Thu, Sep 27, 2012 at 6:47 AM,  <Christian.Schulenberg@bmw.de> wrote:
> Hi,
>
> as I wrote before, I have an older version. I used the kernel version of that one to start up my new meta-ivi build. It crashed later with a kernel panic, but at least the kernel is running.
>
> After that I compared the two kernel version I have, with mkimage -l.
>
> 1. Kernel version that is working quite well:
>
> mkimage -l uImage
> Image Name:   Linux-3.1.0
> Created:      Fri Sep 21 11:25:32 2012
> Image Type:   ARM Linux Kernel Image (uncompressed)
> Data Size:    4144744 Bytes = 4047.60 kB = 3.95 MB
> Load Address: 80008000
> Entry Point:  80008000
>
> 2. Kernel version that fails after uncompression:
>
> mkimage -l uImage
> Image Name:   Linux-3.1.0
> Created:      Thu Sep 27 07:07:25 2012
> Image Type:   ARM Linux Kernel Image (uncompressed)
> Data Size:    4176432 Bytes = 4078.55 kB = 3.98 MB
> Load Address: 80008000
> Entry Point:  80008000
>
> I don't see any major issues here, so I guess I need to check the toolchain as proposed by Enrico.
>

Download denzil SDK for arm which is gcc 4.6 based and compile kernel
using that and see if that boots. There could be some kernel+toolchain
interaction w.r.t gcc 4.7 which is what is
default in current master/(would be 1.3) release, sometimes gcc
exposes latent bugs in kernel
and at times its wise versa

> Christian
>
> -----Ursprüngliche Nachricht-----
> Von: ebutera@gmail.com [mailto:ebutera@gmail.com] Im Auftrag von Enrico
> Gesendet: Donnerstag, 27. September 2012 14:07
> An: Schulenberg Christian, EI-42
> Cc: meta-ti@yoctoproject.org
> Betreff: Re: [meta-ti] pandaboard not booting
>
> On Thu, Sep 27, 2012 at 1:16 PM,  <Christian.Schulenberg@bmw.de> wrote:
>> I'm using the same kernel version as I did before. It's the default kernel 3.1 as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision: a5c60c099296fcfc0c8fa8085c40883971486512
>>
>> Do you really think it makes sense to switch to a more recent one?
>
> No, but i have no better ideas right now...
>
> You could check if it's a known toolchain bug with that kernel, but i
> think it would be faster to try a newer kernel (from the same
> repository, ti ubuntu integration).
>
> Enrico
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: pandaboard not booting

[Gary Thomas]

On 2012-09-27 07:55, Khem Raj wrote:
> On Thu, Sep 27, 2012 at 6:47 AM,  <Christian.Schulenberg@bmw.de> wrote:
>> Hi,
>>
>> as I wrote before, I have an older version. I used the kernel version of that one to start up my new meta-ivi build. It crashed later with a kernel panic, but at least the kernel is running.
>>
>> After that I compared the two kernel version I have, with mkimage -l.
>>
>> 1. Kernel version that is working quite well:
>>
>> mkimage -l uImage
>> Image Name:   Linux-3.1.0
>> Created:      Fri Sep 21 11:25:32 2012
>> Image Type:   ARM Linux Kernel Image (uncompressed)
>> Data Size:    4144744 Bytes = 4047.60 kB = 3.95 MB
>> Load Address: 80008000
>> Entry Point:  80008000
>>
>> 2. Kernel version that fails after uncompression:
>>
>> mkimage -l uImage
>> Image Name:   Linux-3.1.0
>> Created:      Thu Sep 27 07:07:25 2012
>> Image Type:   ARM Linux Kernel Image (uncompressed)
>> Data Size:    4176432 Bytes = 4078.55 kB = 3.98 MB
>> Load Address: 80008000
>> Entry Point:  80008000
>>
>> I don't see any major issues here, so I guess I need to check the toolchain as proposed by Enrico.
>>
>
> Download denzil SDK for arm which is gcc 4.6 based and compile kernel
> using that and see if that boots. There could be some kernel+toolchain
> interaction w.r.t gcc 4.7 which is what is
> default in current master/(would be 1.3) release, sometimes gcc
> exposes latent bugs in kernel
> and at times its wise versa

I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest master)
and GCC-4.6.3 (~denzil).  Both fail during to come up.

The next step would be to diagnose this with a JTAG.  Sadly, I've not been able
to get my XDS100v2 to work with the PandaBoard yet, so it'll have to be someone
else to carry this torch.

>
>> Christian
>>
>> -----Ursprüngliche Nachricht-----
>> Von: ebutera@gmail.com [mailto:ebutera@gmail.com] Im Auftrag von Enrico
>> Gesendet: Donnerstag, 27. September 2012 14:07
>> An: Schulenberg Christian, EI-42
>> Cc: meta-ti@yoctoproject.org
>> Betreff: Re: [meta-ti] pandaboard not booting
>>
>> On Thu, Sep 27, 2012 at 1:16 PM,  <Christian.Schulenberg@bmw.de> wrote:
>>> I'm using the same kernel version as I did before. It's the default kernel 3.1 as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision: a5c60c099296fcfc0c8fa8085c40883971486512
>>>
>>> Do you really think it makes sense to switch to a more recent one?
>>
>> No, but i have no better ideas right now...
>>
>> You could check if it's a known toolchain bug with that kernel, but i
>> think it would be faster to try a newer kernel (from the same
>> repository, ti ubuntu integration).
>>
>> Enrico
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: pandaboard not booting

[Khem Raj]

On Thu, Sep 27, 2012 at 9:08 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2012-09-27 07:55, Khem Raj wrote:
>>
>> On Thu, Sep 27, 2012 at 6:47 AM,  <Christian.Schulenberg@bmw.de> wrote:
>>>
>>> Hi,
>>>
>>> as I wrote before, I have an older version. I used the kernel version of
>>> that one to start up my new meta-ivi build. It crashed later with a kernel
>>> panic, but at least the kernel is running.
>>>
>>> After that I compared the two kernel version I have, with mkimage -l.
>>>
>>> 1. Kernel version that is working quite well:
>>>
>>> mkimage -l uImage
>>> Image Name:   Linux-3.1.0
>>> Created:      Fri Sep 21 11:25:32 2012
>>> Image Type:   ARM Linux Kernel Image (uncompressed)
>>> Data Size:    4144744 Bytes = 4047.60 kB = 3.95 MB
>>> Load Address: 80008000
>>> Entry Point:  80008000
>>>
>>> 2. Kernel version that fails after uncompression:
>>>
>>> mkimage -l uImage
>>> Image Name:   Linux-3.1.0
>>> Created:      Thu Sep 27 07:07:25 2012
>>> Image Type:   ARM Linux Kernel Image (uncompressed)
>>> Data Size:    4176432 Bytes = 4078.55 kB = 3.98 MB
>>> Load Address: 80008000
>>> Entry Point:  80008000
>>>
>>> I don't see any major issues here, so I guess I need to check the
>>> toolchain as proposed by Enrico.
>>>
>>
>> Download denzil SDK for arm which is gcc 4.6 based and compile kernel
>> using that and see if that boots. There could be some kernel+toolchain
>> interaction w.r.t gcc 4.7 which is what is
>> default in current master/(would be 1.3) release, sometimes gcc
>> exposes latent bugs in kernel
>> and at times its wise versa
>
>
> I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest
> master)
> and GCC-4.6.3 (~denzil).  Both fail during to come up.

OK you can take further step back and use edison SDK which has gcc 4.5
which then can _kind_ of eliminate the compiler if it fails with all 3

Re: pandaboard not booting

[Enrico]

On Thu, Sep 27, 2012 at 6:10 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Thu, Sep 27, 2012 at 9:08 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest
>> master)
>> and GCC-4.6.3 (~denzil).  Both fail during to come up.
>
> OK you can take further step back and use edison SDK which has gcc 4.5
> which then can _kind_ of eliminate the compiler if it fails with all 3

Or take a step forward and try a newer kernel ;)

Enrico

Re: pandaboard not booting

[Denys Dmytriyenko]

On Thu, Sep 27, 2012 at 06:22:42PM +0200, Enrico wrote:
> On Thu, Sep 27, 2012 at 6:10 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Thu, Sep 27, 2012 at 9:08 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> >> I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest
> >> master)
> >> and GCC-4.6.3 (~denzil).  Both fail during to come up.
> >
> > OK you can take further step back and use edison SDK which has gcc 4.5
> > which then can _kind_ of eliminate the compiler if it fails with all 3
> 
> Or take a step forward and try a newer kernel ;)

Well, the current kernel used to work at least on Pandaboard ES...

-- 
Denys

Re: pandaboard not booting

[Gary Thomas]

On 2012-09-27 10:24, Denys Dmytriyenko wrote:
> On Thu, Sep 27, 2012 at 06:22:42PM +0200, Enrico wrote:
>> On Thu, Sep 27, 2012 at 6:10 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> On Thu, Sep 27, 2012 at 9:08 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest
>>>> master)
>>>> and GCC-4.6.3 (~denzil).  Both fail during to come up.
>>>
>>> OK you can take further step back and use edison SDK which has gcc 4.5
>>> which then can _kind_ of eliminate the compiler if it fails with all 3
>>
>> Or take a step forward and try a newer kernel ;)
>
> Well, the current kernel used to work at least on Pandaboard ES...

I build the Panda kernel (based on the latest TI/Ubuntu tree ti-ubuntu-3.4-1485.7 branch)
all the time with the Yocto toolchain & it works just fine.

I also tried the off-the-shelf 3.1.0 which worked as well.

There must be something odd about the 3.1 kernel built from the linux-omap4-3.1.0
recipe which is the default when built using Yocto+meta-ti

n.b. this is the end of my experiments on this subject; I was only
trying to help in case it was a toolchain issue since I have the old
tools still around.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: pandaboard not booting

[Nicolas Dechesne]

On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> I build the Panda kernel (based on the latest TI/Ubuntu tree
> ti-ubuntu-3.4-1485.7 branch)
> all the time with the Yocto toolchain & it works just fine.
>
> I also tried the off-the-shelf 3.1.0 which worked as well.
>
> There must be something odd about the 3.1 kernel built from the
> linux-omap4-3.1.0
> recipe which is the default when built using Yocto+meta-ti

i don't think there should be any valid reason to continue with this
old kernel. first there isn't anyone who maintains that branch (my
team maintains that evil vendor tree). For Panda I would either
recommend to use to a more recent branch (like 3.4), in fact we might
even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
(branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
in fact for Panda, just mainline might be another option too..


>
> n.b. this is the end of my experiments on this subject; I was only
> trying to help in case it was a toolchain issue since I have the old
> tools still around.

Re: pandaboard not booting

[Denys Dmytriyenko]

On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
> On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> > I build the Panda kernel (based on the latest TI/Ubuntu tree
> > ti-ubuntu-3.4-1485.7 branch)
> > all the time with the Yocto toolchain & it works just fine.
> >
> > I also tried the off-the-shelf 3.1.0 which worked as well.
> >
> > There must be something odd about the 3.1 kernel built from the
> > linux-omap4-3.1.0
> > recipe which is the default when built using Yocto+meta-ti
> 
> i don't think there should be any valid reason to continue with this
> old kernel. first there isn't anyone who maintains that branch (my
> team maintains that evil vendor tree). For Panda I would either
> recommend to use to a more recent branch (like 3.4), in fact we might
> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
> in fact for Panda, just mainline might be another option too..

Thanks, Nicolas!

I'll give it a try with either of those trees and update the recipe 
accordingly.

-- 
Denys

Re: pandaboard not booting

[Enrico]

On Thu, Sep 27, 2012 at 11:28 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
>> i don't think there should be any valid reason to continue with this
>> old kernel. first there isn't anyone who maintains that branch (my
>> team maintains that evil vendor tree). For Panda I would either
>> recommend to use to a more recent branch (like 3.4), in fact we might
>> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
>> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
>> in fact for Panda, just mainline might be another option too..
>
> Thanks, Nicolas!
>
> I'll give it a try with either of those trees and update the recipe
> accordingly.

Using linaro tilt kernel could be useful to add support for gst-ducati
and friends more easily (using the dce firmware from their repository
instead of building it from sources).

Enrico

Re: pandaboard not booting

[Nicolas Dechesne]

On Fri, Sep 28, 2012 at 10:31 AM, Enrico <ebutera@users.berlios.de> wrote:
> On Thu, Sep 27, 2012 at 11:28 PM, Denys Dmytriyenko <denys@ti.com> wrote:
>> On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
>>> i don't think there should be any valid reason to continue with this
>>> old kernel. first there isn't anyone who maintains that branch (my
>>> team maintains that evil vendor tree). For Panda I would either
>>> recommend to use to a more recent branch (like 3.4), in fact we might
>>> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
>>> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
>>> in fact for Panda, just mainline might be another option too..
>>
>> Thanks, Nicolas!
>>
>> I'll give it a try with either of those trees and update the recipe
>> accordingly.
>
> Using linaro tilt kernel could be useful to add support for gst-ducati
> and friends more easily (using the dce firmware from their repository
> instead of building it from sources).
>

that's definitely what I had in mind too...

> Enrico

Re: pandaboard not booting

[Christian.Schulenberg]

Hi,

could you give me some advice, what kernel version of 3.4.x to try? Or do you have an idea, when a recipe for a more recent kernel could be available?

BR,
Christian

-----Ursprüngliche Nachricht-----
Von: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] Im Auftrag von Denys Dmytriyenko
Gesendet: Donnerstag, 27. September 2012 23:29
An: Nicolas Dechesne
Cc: meta-ti@yoctoproject.org
Betreff: Re: [meta-ti] pandaboard not booting

On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
> On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> > I build the Panda kernel (based on the latest TI/Ubuntu tree
> > ti-ubuntu-3.4-1485.7 branch)
> > all the time with the Yocto toolchain & it works just fine.
> >
> > I also tried the off-the-shelf 3.1.0 which worked as well.
> >
> > There must be something odd about the 3.1 kernel built from the
> > linux-omap4-3.1.0
> > recipe which is the default when built using Yocto+meta-ti
> 
> i don't think there should be any valid reason to continue with this
> old kernel. first there isn't anyone who maintains that branch (my
> team maintains that evil vendor tree). For Panda I would either
> recommend to use to a more recent branch (like 3.4), in fact we might
> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
> in fact for Panda, just mainline might be another option too..

Thanks, Nicolas!

I'll give it a try with either of those trees and update the recipe 
accordingly.

-- 
Denys
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: pandaboard not booting

[Nicolas Dechesne]

On Fri, Sep 28, 2012 at 1:03 PM,  <Christian.Schulenberg@bmw.de> wrote:
> Hi,
>
> could you give me some advice, what kernel version of 3.4.x to try? Or do you have an idea, when a recipe for a more recent kernel could be available?

http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
branch: tilt-3.4
config: omap4plus_defconfig


>
> BR,
> Christian
>
> -----Ursprüngliche Nachricht-----
> Von: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] Im Auftrag von Denys Dmytriyenko
> Gesendet: Donnerstag, 27. September 2012 23:29
> An: Nicolas Dechesne
> Cc: meta-ti@yoctoproject.org
> Betreff: Re: [meta-ti] pandaboard not booting
>
> On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
>> On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> > I build the Panda kernel (based on the latest TI/Ubuntu tree
>> > ti-ubuntu-3.4-1485.7 branch)
>> > all the time with the Yocto toolchain & it works just fine.
>> >
>> > I also tried the off-the-shelf 3.1.0 which worked as well.
>> >
>> > There must be something odd about the 3.1 kernel built from the
>> > linux-omap4-3.1.0
>> > recipe which is the default when built using Yocto+meta-ti
>>
>> i don't think there should be any valid reason to continue with this
>> old kernel. first there isn't anyone who maintains that branch (my
>> team maintains that evil vendor tree). For Panda I would either
>> recommend to use to a more recent branch (like 3.4), in fact we might
>> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
>> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
>> in fact for Panda, just mainline might be another option too..
>
> Thanks, Nicolas!
>
> I'll give it a try with either of those trees and update the recipe
> accordingly.
>
> --
> Denys
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: pandaboard not booting

[Christian.Schulenberg]

Hi,

thanks for the hint to use kernel 3.4.

I updated my meta-ti layer to use kernel 3.4.11 and it works fine for me now. I tested this with gcc 4.7.1 as well as gcc 4.6.3

Bets regards,
Christian

-----Ursprüngliche Nachricht-----
Von: Nicolas Dechesne [mailto:ndec13@gmail.com] 
Gesendet: Freitag, 28. September 2012 13:54
An: Schulenberg Christian, EI-42
Cc: denys@ti.com; meta-ti@yoctoproject.org
Betreff: Re: [meta-ti] pandaboard not booting

On Fri, Sep 28, 2012 at 1:03 PM,  <Christian.Schulenberg@bmw.de> wrote:
> Hi,
>
> could you give me some advice, what kernel version of 3.4.x to try? Or do you have an idea, when a recipe for a more recent kernel could be available?

http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
branch: tilt-3.4
config: omap4plus_defconfig


>
> BR,
> Christian
>
> -----Ursprüngliche Nachricht-----
> Von: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] Im Auftrag von Denys Dmytriyenko
> Gesendet: Donnerstag, 27. September 2012 23:29
> An: Nicolas Dechesne
> Cc: meta-ti@yoctoproject.org
> Betreff: Re: [meta-ti] pandaboard not booting
>
> On Thu, Sep 27, 2012 at 11:15:55PM +0200, Nicolas Dechesne wrote:
>> On Thu, Sep 27, 2012 at 6:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> > I build the Panda kernel (based on the latest TI/Ubuntu tree
>> > ti-ubuntu-3.4-1485.7 branch)
>> > all the time with the Yocto toolchain & it works just fine.
>> >
>> > I also tried the off-the-shelf 3.1.0 which worked as well.
>> >
>> > There must be something odd about the 3.1 kernel built from the
>> > linux-omap4-3.1.0
>> > recipe which is the default when built using Yocto+meta-ti
>>
>> i don't think there should be any valid reason to continue with this
>> old kernel. first there isn't anyone who maintains that branch (my
>> team maintains that evil vendor tree). For Panda I would either
>> recommend to use to a more recent branch (like 3.4), in fact we might
>> even consider http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git
>> (branch tilt-3.4) as this is the base for our 'ubuntu' derived branch.
>> in fact for Panda, just mainline might be another option too..
>
> Thanks, Nicolas!
>
> I'll give it a try with either of those trees and update the recipe
> accordingly.
>
> --
> Denys
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti