* AM335x EVM and core-image-sato
@ 2013-10-17 21:29 Rudolf Streif
2013-10-17 21:45 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-17 21:29 UTC (permalink / raw)
To: meta-ti
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
I built a core-image-sato for the AM335x EVM. The image boots into the
command line. X does not work. There is no frame buffer device (/dev/fb0).
/lib/modules/3.12.0-rc3/kernel/dirvers/video/omap2/omapfb contains an
omapfb kernel module. However, "modprobing" it results in ERROR: Could not
insert 'omapfb': No such device.
I suppose I am missing something here but what?
Thanks,
Rudi
[-- Attachment #2: Type: text/html, Size: 535 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-17 21:29 AM335x EVM and core-image-sato Rudolf Streif
@ 2013-10-17 21:45 ` Denys Dmytriyenko
2013-10-19 1:09 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-17 21:45 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
On Thu, Oct 17, 2013 at 02:29:49PM -0700, Rudolf Streif wrote:
> I built a core-image-sato for the AM335x EVM. The image boots into the
> command line. X does not work. There is no frame buffer device (/dev/fb0).
I haven't tried X here, but I was able to get the framebuffer working on a
more recent build of 3.12-rc4 and there was /dev/fb0 available. I was running
Qt5-based app on it using linuxfb QPA output plugin.
> /lib/modules/3.12.0-rc3/kernel/dirvers/video/omap2/omapfb contains an
> omapfb kernel module. However, "modprobing" it results in ERROR: Could not
> insert 'omapfb': No such device.
>
> I suppose I am missing something here but what?
>
> Thanks,
> Rudi
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-17 21:45 ` Denys Dmytriyenko
@ 2013-10-19 1:09 ` Rudolf Streif
2013-10-19 2:39 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-19 1:09 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Well, I rebuilt with a newer version of meta-ti
(master, b3df09902da0d2469a02e9975d404e26c4c5ec0e). Now the /dev/fb0 device
is in the root file system. However:
- Kernel image is now zImage but u-boot environment still looks for
uImage; work around that and then
- kernel panic - not syncing: Attempting to kill init! exitcode=0x0b.
One step forward, two steps back. Pulled again, and this time build fails
because branch ti-linux-312.y is not available.
What branch of meta-ti and what commit is working?
Thanks,
:rjs
[-- Attachment #2: Type: text/html, Size: 655 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-19 1:09 ` Rudolf Streif
@ 2013-10-19 2:39 ` Denys Dmytriyenko
2013-10-19 18:53 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-19 2:39 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
On Fri, Oct 18, 2013 at 06:09:23PM -0700, Rudolf Streif wrote:
> Well, I rebuilt with a newer version of meta-ti
> (master, b3df09902da0d2469a02e9975d404e26c4c5ec0e). Now the /dev/fb0 device
> is in the root file system. However:
>
> - Kernel image is now zImage but u-boot environment still looks for
> uImage; work around that and then
u-boot has changed the preferred default from uImage to zImage somewhere
between 2013.10-rc4 and the final 2013.10 release. The kernel now builds
zImage by default and there's corresponding u-boot update:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=3f3bad888972776b4740f7210e709b74362631f5
Looks like you hit it at the wrong time... Sorry, that sometimes happens
when there are multiple components being actively developed and the API
between them changes...
> - kernel panic - not syncing: Attempting to kill init! exitcode=0x0b.
Have you tried the latest update to 3.12-rc5? That combination seems to be
building and booting fine, according to our automated reports:
http://article.gmane.org/gmane.linux.embedded.yocto.meta-arago/1245
> One step forward, two steps back. Pulled again, and this time build fails
> because branch ti-linux-312.y is not available.
The branch was and is called ti-linux-3.12.y and it hasn't changed since the
beginning of 3.12 integration and is still there:
http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.12.y
> What branch of meta-ti and what commit is working?
Both master and dylan are currently in sync and always are, when it comes to
3.12-rc5 kernel and 2013.10 u-boot. Other recipes can differ between master
and dylan, but the integration trees are the same. The above link to automated
build and test report used dylan branch of meta-ti and the latest commit ID of
f61008a20340373247ebfd8f381e377b21f11afe. If you want to use meta-ti master,
then the corresponding commit ID is c11504664990f007c3903d349e7cc135a904f8e2.
--
Denys
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-19 2:39 ` Denys Dmytriyenko
@ 2013-10-19 18:53 ` Rudolf Streif
2013-10-21 8:16 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-19 18:53 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
Thanks, Denys.
Have you tried the latest update to 3.12-rc5? That combination seems to be
> building and booting fine, according to our automated reports:
>
> http://article.gmane.org/gmane.linux.embedded.yocto.meta-arago/1245
>
> Yes, I tried 3.12-rc3 which worked, 3.12-rc4 which did not, as well as
3.12-rc5 which does not work either.
>
> > One step forward, two steps back. Pulled again, and this time build fails
> > because branch ti-linux-312.y is not available
> The branch was and is called ti-linux-3.12.y and it hasn't changed since
> the
> beginning of 3.12 integration and is still there:
>
>
> http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.12.y
>
>
> Fetcher failed on it during the day yesterday. But it worked again at
night. Maybe a glitch. Although the Gitorious web frontend responds with an
error message when trying to explore the branch tree.
> If you want to use meta-ti master,
> then the corresponding commit ID is
> c11504664990f007c3903d349e7cc135a904f8e2.
>
> I used the master branch and the exact commit you mentioned above. See
[1]. I will try again.
Thanks,
Rudi
[1]
Build Configuration:
BB_VERSION = "1.21.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Fedora-18"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "am335x-evm"
DISTRO = "poky"
DISTRO_VERSION = "1.5+snapshot-20131019"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
[-- Attachment #2: Type: text/html, Size: 3362 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-19 18:53 ` Rudolf Streif
@ 2013-10-21 8:16 ` Rudolf Streif
2013-10-21 17:42 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-21 8:16 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]
Denys,
I recompiled the 3.12-rc5 kernel again but it still stalls during
initialization. I attached the boot log. I don't know much about the
platform details but maybe that's an issue you know about.
Thanks,
Rudi
>
> [1]
> Build Configuration:
> BB_VERSION = "1.21.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "Fedora-18"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "am335x-evm"
> DISTRO = "poky"
> DISTRO_VERSION = "1.5+snapshot-20131019"
> TUNE_FEATURES = "armv7a vfp neon"
> TARGET_FPU = "vfp-neon"
> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
>
>
[-- Attachment #1.2: Type: text/html, Size: 1887 bytes --]
[-- Attachment #2: am335x-evm.log --]
[-- Type: application/octet-stream, Size: 1469 bytes --]
[ 2.607910] [<c02f8994>] (gpio_debounce+0x78/0x12c) from [<c02f6180>] (gpio_set_debounce+0x94/0x118)
[ 2.617516] [<c02f6180>] (gpio_set_debounce+0x94/0x118) from [<c045b828>] (gpio_keys_probe+0x3c4/0x7c4)
[ 2.627403] [<c045b828>] (gpio_keys_probe+0x3c4/0x7c4) from [<c035331c>] (platform_drv_probe+0x18/0x1c)
[ 2.637279] [<c035331c>] (platform_drv_probe+0x18/0x1c) from [<c0352114>] (driver_probe_device+0x108/0x224)
[ 2.647519] [<c0352114>] (driver_probe_device+0x108/0x224) from [<c0352308>] (__driver_attach+0x94/0x98)
[ 2.657486] [<c0352308>] (__driver_attach+0x94/0x98) from [<c0350598>] (bus_for_each_dev+0x60/0x94)
[ 2.666995] [<c0350598>] (bus_for_each_dev+0x60/0x94) from [<c0351898>] (bus_add_driver+0x1d4/0x284)
[ 2.676597] [<c0351898>] (bus_add_driver+0x1d4/0x284) from [<c03528e0>] (driver_register+0x78/0xf8)
[ 2.686112] [<c03528e0>] (driver_register+0x78/0xf8) from [<c0008848>] (do_one_initcall+0xe8/0x14c)
[ 2.695627] [<c0008848>] (do_one_initcall+0xe8/0x14c) from [<c07fcbbc>] (kernel_init_freeable+0x104/0x1c8)
[ 2.705789] [<c07fcbbc>] (kernel_init_freeable+0x104/0x1c8) from [<c0584b58>] (kernel_init+0x8/0x150)
[ 2.715494] [<c0584b58>] (kernel_init+0x8/0x150) from [<c0013bc8>] (ret_from_fork+0x14/0x2c)
[ 2.724364] Code: e594309c e5142070 e1d331be e0823003 (e5932000)
[ 2.730784] ---[ end trace 3bceeb7e3873ca62 ]---
[ 2.735954] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 8:16 ` Rudolf Streif
@ 2013-10-21 17:42 ` Rudolf Streif
2013-10-21 21:15 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-21 17:42 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 2633 bytes --]
Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel a
try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot environment
has now moved on to using zImage which consequently means u-boot will not
find the kernel file.
I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
linux-ti-staging_3.8.bb recipe but whoever did it did not think about
u-boot. Does zImage not work with 3.8? I did not try it but it should
normally have no effect. Since there is no dependency of the u-boot recipes
on the kernel image types changes to the kernel image type for newer
versions of the kernel then automatically means that it must be changed for
the previous versions too.
I mocked around with the u-boot environment and booted the 3.8 uImage
kernel. To my surprise the 3.8 kernel from the TI staging repository fails
with the exact same problem and stops booting with a kernel not syncing
message during the init calls. Apparently a patch must have been applied to
the kernel repo that breaks it. It has nothing possibly to do with the
build system.
I would appreciate any hints to get this kernel built and boot on the board.
Thanks,
Rudi
On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
<rstreif@linuxfoundation.org>wrote:
> Denys,
>
> I recompiled the 3.12-rc5 kernel again but it still stalls during
> initialization. I attached the boot log. I don't know much about the
> platform details but maybe that's an issue you know about.
>
> Thanks,
> Rudi
>
>
>
>>
>> [1]
>> Build Configuration:
>> BB_VERSION = "1.21.0"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING = "Fedora-18"
>> TARGET_SYS = "arm-poky-linux-gnueabi"
>> MACHINE = "am335x-evm"
>> DISTRO = "poky"
>> DISTRO_VERSION = "1.5+snapshot-20131019"
>> TUNE_FEATURES = "armv7a vfp neon"
>> TARGET_FPU = "vfp-neon"
>> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
>> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
>> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
>> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
>>
>>
>
>
>
>
>
--
--
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation
rudolf.streif@linux.com
Phone: +1.619.537.6646
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B
Linux Foundation Events Schedule: events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
[-- Attachment #2: Type: text/html, Size: 5394 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 17:42 ` Rudolf Streif
@ 2013-10-21 21:15 ` Denys Dmytriyenko
2013-10-21 22:19 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-21 21:15 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
Rudi,
As we discussed earlier today, let my send you my binaries for the kernel and
u-boot to try on your board. I just wanted to ask you about the toolchain that
you used to build yours. In our builds we use Linaro gcc-4.7 hardfp toolchain
and I vaguely remember hearing about some problems with the recent gcc-4.8
toolchain from oe-core... I'm wondering if you are having the same issue.
--
Denys
On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel a
> try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot environment
> has now moved on to using zImage which consequently means u-boot will not
> find the kernel file.
>
> I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> u-boot. Does zImage not work with 3.8? I did not try it but it should
> normally have no effect. Since there is no dependency of the u-boot recipes
> on the kernel image types changes to the kernel image type for newer
> versions of the kernel then automatically means that it must be changed for
> the previous versions too.
>
> I mocked around with the u-boot environment and booted the 3.8 uImage
> kernel. To my surprise the 3.8 kernel from the TI staging repository fails
> with the exact same problem and stops booting with a kernel not syncing
> message during the init calls. Apparently a patch must have been applied to
> the kernel repo that breaks it. It has nothing possibly to do with the
> build system.
>
> I would appreciate any hints to get this kernel built and boot on the board.
>
> Thanks,
> Rudi
>
>
> On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> <rstreif@linuxfoundation.org>wrote:
>
> > Denys,
> >
> > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > initialization. I attached the boot log. I don't know much about the
> > platform details but maybe that's an issue you know about.
> >
> > Thanks,
> > Rudi
> >
> >
> >
> >>
> >> [1]
> >> Build Configuration:
> >> BB_VERSION = "1.21.0"
> >> BUILD_SYS = "x86_64-linux"
> >> NATIVELSBSTRING = "Fedora-18"
> >> TARGET_SYS = "arm-poky-linux-gnueabi"
> >> MACHINE = "am335x-evm"
> >> DISTRO = "poky"
> >> DISTRO_VERSION = "1.5+snapshot-20131019"
> >> TUNE_FEATURES = "armv7a vfp neon"
> >> TARGET_FPU = "vfp-neon"
> >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> >>
> >>
> >
> >
> >
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 21:15 ` Denys Dmytriyenko
@ 2013-10-21 22:19 ` Rudolf Streif
2013-10-21 23:19 ` Denys Dmytriyenko
2013-10-22 19:37 ` Denys Dmytriyenko
0 siblings, 2 replies; 21+ messages in thread
From: Rudolf Streif @ 2013-10-21 22:19 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1.1: Type: text/plain, Size: 4964 bytes --]
Thanks, Denys.
Interesting point about gcc. It's version 4.8.1 which is the default for
poky master. Which is what I used all along.
Thanks for sending your binaries. They fail too with the exact same
problem. See attached log. I found [1] on gmane which exactly describes the
problem I am seeing.
If that is the case then I was wondering why my earlier builds with
3.12-rc3 actually worked. And I tried them again and they are now failing
too. Of course I don't know anything about the specifics of the gpio and
the timers on the chip but it looks like a weird hardware initialization
condition. And I don't know if the proposed patch in [1] was ever
incorporated in your kernel tree.
I don't think it's the hardware (or at least not alone) because the SD that
ships with it with the 3.2 kernel works just fine.
Cheers,
Rudi
[1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> Rudi,
>
> As we discussed earlier today, let my send you my binaries for the kernel
> and
> u-boot to try on your board. I just wanted to ask you about the toolchain
> that
> you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> toolchain
> and I vaguely remember hearing about some problems with the recent gcc-4.8
> toolchain from oe-core... I'm wondering if you are having the same issue.
>
> --
> Denys
>
>
> On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> a
> > try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> environment
> > has now moved on to using zImage which consequently means u-boot will not
> > find the kernel file.
> >
> > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > normally have no effect. Since there is no dependency of the u-boot
> recipes
> > on the kernel image types changes to the kernel image type for newer
> > versions of the kernel then automatically means that it must be changed
> for
> > the previous versions too.
> >
> > I mocked around with the u-boot environment and booted the 3.8 uImage
> > kernel. To my surprise the 3.8 kernel from the TI staging repository
> fails
> > with the exact same problem and stops booting with a kernel not syncing
> > message during the init calls. Apparently a patch must have been applied
> to
> > the kernel repo that breaks it. It has nothing possibly to do with the
> > build system.
> >
> > I would appreciate any hints to get this kernel built and boot on the
> board.
> >
> > Thanks,
> > Rudi
> >
> >
> > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > <rstreif@linuxfoundation.org>wrote:
> >
> > > Denys,
> > >
> > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > initialization. I attached the boot log. I don't know much about the
> > > platform details but maybe that's an issue you know about.
> > >
> > > Thanks,
> > > Rudi
> > >
> > >
> > >
> > >>
> > >> [1]
> > >> Build Configuration:
> > >> BB_VERSION = "1.21.0"
> > >> BUILD_SYS = "x86_64-linux"
> > >> NATIVELSBSTRING = "Fedora-18"
> > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > >> MACHINE = "am335x-evm"
> > >> DISTRO = "poky"
> > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > >> TUNE_FEATURES = "armv7a vfp neon"
> > >> TARGET_FPU = "vfp-neon"
> > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > >>
> > >>
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
>
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
>
>
--
--
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation
rudolf.streif@linux.com
Phone: +1.619.537.6646
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B
Linux Foundation Events Schedule: events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
[-- Attachment #1.2: Type: text/html, Size: 8172 bytes --]
[-- Attachment #2: boot-am335x-evmsk.log --]
[-- Type: application/octet-stream, Size: 15846 bytes --]
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.12.0-rc5-geb765a3 (jenkins@puget) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP Fri Oct 18 12:52:18 E
DT 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x EVM-SK
[ 0.000000] cma: CMA: reserved 16 MiB at 8e800000
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] AM335X ES1.0 (sgx neon )
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c119d000 s14656 r8192 d14016 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64512
[ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 226516K/260096K available (5818K kernel code, 679K rwdata, 2268K rodata, 422K init, 5528K bss, 33580K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07edbbc (8087 kB)
[ 0.000000] .init : 0xc07ee000 - 0xc0857940 ( 423 kB)
[ 0.000000] .data : 0xc0858000 - 0xc0901e20 ( 680 kB)
[ 0.000000] .bss : 0xc0901e20 - 0xc0e680b0 (5529 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: timer1 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 0.000000] ... MAX_LOCK_DEPTH: 48
[ 0.000000] ... MAX_LOCKDEP_KEYS: 8191
[ 0.000000] ... CLASSHASH_SIZE: 4096
[ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384
[ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768
[ 0.000000] ... CHAINHASH_SIZE: 16384
[ 0.000000] memory used by lock dependency info: 3695 kB
[ 0.000000] per task-struct memory footprint: 1152 bytes
[ 0.001209] Calibrating delay loop... 476.77 BogoMIPS (lpj=2383872)
[ 0.109438] pid_max: default: 32768 minimum: 301
[ 0.109947] Security Framework initialized
[ 0.110105] Mount-cache hash table entries: 512
[ 0.138580] CPU: Testing write buffer coherency: ok
[ 0.140290] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.140375] Setting up static identity map for 0xc0583f40 - 0xc0583fb0
[ 0.143823] Brought up 1 CPUs
[ 0.143847] SMP: Total of 1 processors activated.
[ 0.143860] CPU: All CPU(s) started in SVC mode.
[ 0.147095] devtmpfs: initialized
[ 0.158322] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 0.238061] omap_hwmod: debugss: _wait_target_disable failed
[ 0.244117] pinctrl core: initialized pinctrl subsystem
[ 0.248951] regulator-dummy: no parameters
[ 0.253074] NET: Registered protocol family 16
[ 0.260087] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.277066] platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt!
[ 0.280712] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt!
[ 0.286113] OMAP GPIO hardware version 0.1
[ 0.299380] platform 48060000.mmc: FIXME: clock-name 'fck' DOES NOT exist in dt!
[ 0.316601] platform 4803c000.mcasp: FIXME: clock-name 'fck' DOES NOT exist in dt!
[ 0.321478] DSS not supported on this SoC
[ 0.321507] No ATAGs?
[ 0.321522] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.405293] bio: create slab <bio-0> at 0
[ 0.452783] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[ 0.455266] vbat: 5000 mV
[ 0.456621] lis3_reg: no parameters
[ 0.466534] SCSI subsystem initialized
[ 0.471551] usbcore: registered new interface driver usbfs
[ 0.472092] usbcore: registered new interface driver hub
[ 0.472921] usbcore: registered new device driver usb
[ 0.475742] omap_i2c 44e0b000.i2c: could not find pctldev for node /pinmux@44e10800/pinmux_i2c0_pins, deferring probe
[ 0.475798] platform 44e0b000.i2c: Driver omap_i2c requests probe deferral
[ 0.485534] Switched to clocksource timer1
[ 0.651596] NET: Registered protocol family 2
[ 0.653762] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.653980] TCP bind hash table entries: 2048 (order: 4, 73728 bytes)
[ 0.654932] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.655167] TCP: reno registered
[ 0.655203] UDP hash table entries: 256 (order: 2, 20480 bytes)
[ 0.655682] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes)
[ 0.657159] NET: Registered protocol family 1
[ 0.658928] RPC: Registered named UNIX socket transport module.
[ 0.658954] RPC: Registered udp transport module.
[ 0.658967] RPC: Registered tcp transport module.
[ 0.658980] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.661633] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.662999] PM: Loading am335x-pm-firmware.bin
[ 0.867506] VFS: Disk quotas dquot_6.5.2
[ 0.867797] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.870634] NFS: Registering the id_resolver key type
[ 0.871117] Key type id_resolver registered
[ 0.871138] Key type id_legacy registered
[ 0.871278] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
[ 0.871830] msgmni has been set to 474
[ 0.878386] io scheduler noop registered
[ 0.878415] io scheduler deadline registered
[ 0.878496] io scheduler cfq registered (default)
[ 0.882787] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.909452] Console: switching to colour frame buffer device 60x34
[ 0.918116] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.927465] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000) is a OMAP UART0
[ 1.584204] console [ttyO0] enabled
[ 1.594339] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[ 1.636805] brd: module loaded
[ 1.661004] loop: module loaded
[ 1.674000] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 1.693377] usbcore: registered new interface driver asix
[ 1.700120] usbcore: registered new interface driver ax88179_178a
[ 1.707611] usbcore: registered new interface driver cdc_ether
[ 1.714303] usbcore: registered new interface driver r815x
[ 1.721101] usbcore: registered new interface driver smsc95xx
[ 1.728006] usbcore: registered new interface driver net1080
[ 1.734454] usbcore: registered new interface driver cdc_subset
[ 1.741338] usbcore: registered new interface driver zaurus
[ 1.747942] usbcore: registered new interface driver cdc_ncm
[ 1.757973] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.765009] ehci-omap: OMAP-EHCI Host Controller driver
[ 1.772787] usbcore: registered new interface driver cdc_wdm
[ 1.779786] usbcore: registered new interface driver usb-storage
[ 1.786978] usbcore: registered new interface driver usbtest
[ 1.797618] mousedev: PS/2 mouse device common for all mice
[ 1.810686] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 1.818459] 44e3e000.rtc: already running
[ 1.824531] i2c /dev entries driver
[ 1.829080] Driver for 1-wire Dallas network protocol.
[ 1.840739] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 1.853337] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 1.860812] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 1.868183] omap_hsmmc 48060000.mmc: vmmc regulator missing
[ 1.874445] edma-dma-engine edma-dma-engine.0: freeing channel for 24
[ 1.881305] edma-dma-engine edma-dma-engine.0: freeing channel for 25
[ 1.888254] platform 48060000.mmc: Driver omap_hsmmc requests probe deferral
[ 1.903083] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.910310] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[ 1.917653] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 1.928554] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 1.934670] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[ 1.941991] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[ 1.953788] usbcore: registered new interface driver usbhid
[ 1.959888] usbhid: USB HID core driver
[ 1.970122] oprofile: no performance counters
[ 1.977955] oprofile: using timer interrupt.
[ 1.983276] TCP: cubic registered
[ 1.986991] Initializing XFRM netlink socket
[ 1.991750] NET: Registered protocol family 17
[ 1.996622] NET: Registered protocol family 15
[ 2.001764] Key type dns_resolver registered
[ 2.007762] cpu cpu0: cpu0 regulator not ready, retry
[ 2.013128] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral
[ 2.021424] ThumbEE CPU extension supported.
[ 2.040266] tps65910 0-002d: No interrupt support, no core IRQ
[ 2.055286] vrtc: 1800 mV
[ 2.059244] vrtc: supplied by vbat
[ 2.066851] vio: at 1500 mV
[ 2.070098] vio: supplied by vbat
[ 2.077049] vdd_mpu: 912 <--> 1312 mV at 1137 mV
[ 2.082206] vdd_mpu: supplied by vbat
[ 2.089478] vdd_core: 912 <--> 1150 mV at 1137 mV
[ 2.094700] vdd_core: supplied by vbat
[ 2.101496] vdd3: 5000 mV
[ 2.107296] vdig1: at 1800 mV
[ 2.110709] vdig1: supplied by vbat
[ 2.117676] vdig2: at 1800 mV
[ 2.121063] vdig2: supplied by vbat
[ 2.127924] vpll: at 1800 mV
[ 2.131220] vpll: supplied by vbat
[ 2.137999] vdac: at 1800 mV
[ 2.141298] vdac: supplied by vbat
[ 2.148047] vaux1: at 1800 mV
[ 2.151449] vaux1: supplied by vbat
[ 2.158297] vaux2: at 3300 mV
[ 2.161688] vaux2: supplied by vbat
[ 2.168485] vaux33: at 3300 mV
[ 2.171959] vaux33: supplied by vbat
[ 2.178812] vmmc: 1800 <--> 3300 mV at 3300 mV
[ 2.183751] vmmc: supplied by vbat
[ 2.193206] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[ 2.200759] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 2.208095] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 2.216655] omap_hsmmc 48060000.mmc: pins are not configured from the driver
[ 2.335513] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.341942] davinci_mdio 4a101000.mdio: detected phy mask fffffffc
[ 2.353892] libphy: 4a101000.mdio: probed
[ 2.358277] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver Atheros 8031 ethernet
[ 2.368430] davinci_mdio 4a101000.mdio: phy[1]: device 4a101000.mdio:01, driver Atheros 8031 ethernet
[ 2.378614] Detected MACID = d4:94:a1:89:2b:a6
[ 2.389947] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa1ac150
[ 2.398014] Internal error: : 1028 [#1] SMP ARM
[ 2.402777] Modules linked in:
[ 2.406005] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.0-rc5-geb765a3 #1
[ 2.413412] task: ce081440 ti: ce082000 task.ti: ce082000
[ 2.419102] PC is at gpio_debounce+0x78/0x12c
[ 2.423690] LR is at _raw_spin_unlock_irqrestore+0x40/0x44
[ 2.429455] pc : [<c02f0224>] lr : [<c057e8bc>] psr: 60000193
[ 2.429455] sp : ce083e00 ip : 60000193 fp : 00000028
[ 2.441513] r10: 00000002 r9 : ce33ac00 r8 : 20000113
[ 2.447000] r7 : 000000a0 r6 : 00000004 r5 : ce150c68 r4 : ce150c88
[ 2.453859] r3 : fa1ac150 r2 : fa1ac000 r1 : ce083dd8 r0 : 00000000
[ 2.460718] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 2.468486] Control: 10c5387d Table: 80004019 DAC: 00000017
[ 2.474523] Process swapper/0 (pid: 1, stack limit = 0xce082248)
[ 2.480833] Stack: (0xce083e00 to 0xce084000)
[ 2.485419] 3e00: c02f01ac ce150c88 00000006 00000000 a0000113 00001388 ce33d800 c02edd70
[ 2.494013] 3e20: ce3550e8 ce33ac44 c0f87fb0 ce355000 00000001 c044ebb8 ce355050 00000000
[ 2.502606] 3e40: 00000000 00000003 c044f0f4 00000000 ce13e410 ce13e400 ce13fdb0 00000000
[ 2.511201] 3e60: ce13e410 c0e55334 ce13e410 00000000 c0901e40 c08e6828 ce082000 000000bd
[ 2.519794] 3e80: 00000000 c0348e7c c0348e64 c0347cf8 ce13e410 c08e6828 ce13e444 c0901e40
[ 2.528387] 3ea0: 00000000 c0347ea8 00000000 c08e6828 c0347e14 c03462bc ce02a2a8 ce115710
[ 2.536981] 3ec0: c08e6828 ce339cc0 c08d3f50 c03473a8 c070e0d0 c08e6828 c08e6828 00000007
[ 2.545575] 3ee0: c0838168 c0901e40 c0829d90 c03484d0 00000000 c0852eb4 00000007 c0008838
[ 2.554168] 3f00: 00000004 c08b59a0 c08b59a0 60000113 c02cb400 00000000 00000000 00000000
[ 2.562761] 3f20: 00000000 c057e3cc 00000002 ce082000 c119a2fe c05cb5a8 000000bd c0062ce8
[ 2.571355] 3f40: c07ba490 00000007 c119a306 00000007 60000113 c0852eb4 00000007 c0838168
[ 2.579948] 3f60: c0901e40 c07ee458 c0838170 000000bd 00000000 c07eebbc 00000007 00000007
[ 2.588541] 3f80: c07ee458 00000000 00000000 c0574084 00000000 00000000 00000000 00000000
[ 2.597135] 3fa0: 00000000 c057408c 00000000 c0013e68 00000000 00000000 00000000 00000000
[ 2.605729] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 2.614322] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 37e7773f fcfbbfea
[ 2.622926] [<c02f0224>] (gpio_debounce+0x78/0x12c) from [<c02edd70>] (gpio_set_debounce+0x94/0x120)
[ 2.632535] [<c02edd70>] (gpio_set_debounce+0x94/0x120) from [<c044ebb8>] (gpio_keys_probe+0x384/0x734)
[ 2.642414] [<c044ebb8>] (gpio_keys_probe+0x384/0x734) from [<c0348e7c>] (platform_drv_probe+0x18/0x1c)
[ 2.652299] [<c0348e7c>] (platform_drv_probe+0x18/0x1c) from [<c0347cf8>] (driver_probe_device+0x108/0x224)
[ 2.662539] [<c0347cf8>] (driver_probe_device+0x108/0x224) from [<c0347ea8>] (__driver_attach+0x94/0x98)
[ 2.672503] [<c0347ea8>] (__driver_attach+0x94/0x98) from [<c03462bc>] (bus_for_each_dev+0x54/0x88)
[ 2.682010] [<c03462bc>] (bus_for_each_dev+0x54/0x88) from [<c03473a8>] (bus_add_driver+0xd8/0x26c)
[ 2.691518] [<c03473a8>] (bus_add_driver+0xd8/0x26c) from [<c03484d0>] (driver_register+0x78/0xf4)
[ 2.700940] [<c03484d0>] (driver_register+0x78/0xf4) from [<c0008838>] (do_one_initcall+0xe4/0x148)
[ 2.710452] [<c0008838>] (do_one_initcall+0xe4/0x148) from [<c07eebbc>] (kernel_init_freeable+0xfc/0x1cc)
[ 2.720511] [<c07eebbc>] (kernel_init_freeable+0xfc/0x1cc) from [<c057408c>] (kernel_init+0x8/0xe4)
[ 2.730031] [<c057408c>] (kernel_init+0x8/0xe4) from [<c0013e68>] (ret_from_fork+0x14/0x2c)
[ 2.738808] Code: e594309c e5142070 e1d331be e0823003 (e5932000)
[ 2.745226] ---[ end trace a0c72887f520c3a6 ]---
[ 2.750388] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.750388]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 22:19 ` Rudolf Streif
@ 2013-10-21 23:19 ` Denys Dmytriyenko
2013-10-22 7:57 ` Rudolf Streif
2013-10-22 19:37 ` Denys Dmytriyenko
1 sibling, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-21 23:19 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
Now I'm just wondering what PG version of the board you've got, if it fails in
the same way with our 3.8 kernel and a known good set of 3.12 images...
On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> Thanks, Denys.
>
> Interesting point about gcc. It's version 4.8.1 which is the default for
> poky master. Which is what I used all along.
>
> Thanks for sending your binaries. They fail too with the exact same
> problem. See attached log. I found [1] on gmane which exactly describes the
> problem I am seeing.
>
> If that is the case then I was wondering why my earlier builds with
> 3.12-rc3 actually worked. And I tried them again and they are now failing
> too. Of course I don't know anything about the specifics of the gpio and
> the timers on the chip but it looks like a weird hardware initialization
> condition. And I don't know if the proposed patch in [1] was ever
> incorporated in your kernel tree.
>
> I don't think it's the hardware (or at least not alone) because the SD that
> ships with it with the 3.2 kernel works just fine.
>
> Cheers,
> Rudi
>
>
> [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org> wrote:
>
> > Rudi,
> >
> > As we discussed earlier today, let my send you my binaries for the kernel
> > and
> > u-boot to try on your board. I just wanted to ask you about the toolchain
> > that
> > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > toolchain
> > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > toolchain from oe-core... I'm wondering if you are having the same issue.
> >
> > --
> > Denys
> >
> >
> > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > a
> > > try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > environment
> > > has now moved on to using zImage which consequently means u-boot will not
> > > find the kernel file.
> > >
> > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > normally have no effect. Since there is no dependency of the u-boot
> > recipes
> > > on the kernel image types changes to the kernel image type for newer
> > > versions of the kernel then automatically means that it must be changed
> > for
> > > the previous versions too.
> > >
> > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > fails
> > > with the exact same problem and stops booting with a kernel not syncing
> > > message during the init calls. Apparently a patch must have been applied
> > to
> > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > build system.
> > >
> > > I would appreciate any hints to get this kernel built and boot on the
> > board.
> > >
> > > Thanks,
> > > Rudi
> > >
> > >
> > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > <rstreif@linuxfoundation.org>wrote:
> > >
> > > > Denys,
> > > >
> > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > initialization. I attached the boot log. I don't know much about the
> > > > platform details but maybe that's an issue you know about.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > >
> > > >>
> > > >> [1]
> > > >> Build Configuration:
> > > >> BB_VERSION = "1.21.0"
> > > >> BUILD_SYS = "x86_64-linux"
> > > >> NATIVELSBSTRING = "Fedora-18"
> > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > >> MACHINE = "am335x-evm"
> > > >> DISTRO = "poky"
> > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > >> TARGET_FPU = "vfp-neon"
> > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 23:19 ` Denys Dmytriyenko
@ 2013-10-22 7:57 ` Rudolf Streif
2013-10-22 19:36 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-22 7:57 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti
[-- Attachment #1: Type: text/plain, Size: 6348 bytes --]
Where do I find the PG version of the board? The barcode sticker on the
board says rev 1.2.
On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
> Now I'm just wondering what PG version of the board you've got, if it
> fails in
> the same way with our 3.8 kernel and a known good set of 3.12 images...
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes
> the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD
> that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the
> kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the
> toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent
> gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same
> issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot
> will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be
> changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not
> syncing
> > > > message during the init calls. Apparently a patch must have been
> applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with
> the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about
> the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto =
> "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti =
> "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe =
> "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta =
> "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
>
>
>
--
--
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation
rudolf.streif@linux.com
Phone: +1.619.537.6646
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B
Linux Foundation Events Schedule: events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
[-- Attachment #2: Type: text/html, Size: 10509 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 7:57 ` Rudolf Streif
@ 2013-10-22 19:36 ` Denys Dmytriyenko
2013-10-22 20:16 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-22 19:36 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
versions of the silicon and I believe those are the latest ones. Need to
double-check that.
Denys
On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> Where do I find the PG version of the board? The barcode sticker on the
> board says rev 1.2.
>
>
> On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
>
> > Now I'm just wondering what PG version of the board you've got, if it
> > fails in
> > the same way with our 3.8 kernel and a known good set of 3.12 images...
> >
> >
> > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > Thanks, Denys.
> > >
> > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > poky master. Which is what I used all along.
> > >
> > > Thanks for sending your binaries. They fail too with the exact same
> > > problem. See attached log. I found [1] on gmane which exactly describes
> > the
> > > problem I am seeing.
> > >
> > > If that is the case then I was wondering why my earlier builds with
> > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > too. Of course I don't know anything about the specifics of the gpio and
> > > the timers on the chip but it looks like a weird hardware initialization
> > > condition. And I don't know if the proposed patch in [1] was ever
> > > incorporated in your kernel tree.
> > >
> > > I don't think it's the hardware (or at least not alone) because the SD
> > that
> > > ships with it with the 3.2 kernel works just fine.
> > >
> > > Cheers,
> > > Rudi
> > >
> > >
> > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > wrote:
> > >
> > > > Rudi,
> > > >
> > > > As we discussed earlier today, let my send you my binaries for the
> > kernel
> > > > and
> > > > u-boot to try on your board. I just wanted to ask you about the
> > toolchain
> > > > that
> > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > toolchain
> > > > and I vaguely remember hearing about some problems with the recent
> > gcc-4.8
> > > > toolchain from oe-core... I'm wondering if you are having the same
> > issue.
> > > >
> > > > --
> > > > Denys
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > kernel
> > > > a
> > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > environment
> > > > > has now moved on to using zImage which consequently means u-boot
> > will not
> > > > > find the kernel file.
> > > > >
> > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > about
> > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > recipes
> > > > > on the kernel image types changes to the kernel image type for newer
> > > > > versions of the kernel then automatically means that it must be
> > changed
> > > > for
> > > > > the previous versions too.
> > > > >
> > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > fails
> > > > > with the exact same problem and stops booting with a kernel not
> > syncing
> > > > > message during the init calls. Apparently a patch must have been
> > applied
> > > > to
> > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > the
> > > > > build system.
> > > > >
> > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > board.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > <rstreif@linuxfoundation.org>wrote:
> > > > >
> > > > > > Denys,
> > > > > >
> > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > initialization. I attached the boot log. I don't know much about
> > the
> > > > > > platform details but maybe that's an issue you know about.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > >
> > > > > >>
> > > > > >> [1]
> > > > > >> Build Configuration:
> > > > > >> BB_VERSION = "1.21.0"
> > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > >> MACHINE = "am335x-evm"
> > > > > >> DISTRO = "poky"
> > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > >> TARGET_FPU = "vfp-neon"
> > > > > >> meta-yocto =
> > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >> meta-ti =
> > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > >> meta-oe =
> > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > >> meta =
> > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com
> > > > > Phone: +1.619.537.6646
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > >
> > > > > _______________________________________________
> > > > > meta-ti mailing list
> > > > > meta-ti@yoctoproject.org
> > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-21 22:19 ` Rudolf Streif
2013-10-21 23:19 ` Denys Dmytriyenko
@ 2013-10-22 19:37 ` Denys Dmytriyenko
1 sibling, 0 replies; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-22 19:37 UTC (permalink / raw)
To: Rudolf Streif; +Cc: meta-ti
And just to double-check here as well - you did try all the binaries I sent
you, including MLO, u-boot, zImage and DTB, right?
Denys
On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> Thanks, Denys.
>
> Interesting point about gcc. It's version 4.8.1 which is the default for
> poky master. Which is what I used all along.
>
> Thanks for sending your binaries. They fail too with the exact same
> problem. See attached log. I found [1] on gmane which exactly describes the
> problem I am seeing.
>
> If that is the case then I was wondering why my earlier builds with
> 3.12-rc3 actually worked. And I tried them again and they are now failing
> too. Of course I don't know anything about the specifics of the gpio and
> the timers on the chip but it looks like a weird hardware initialization
> condition. And I don't know if the proposed patch in [1] was ever
> incorporated in your kernel tree.
>
> I don't think it's the hardware (or at least not alone) because the SD that
> ships with it with the 3.2 kernel works just fine.
>
> Cheers,
> Rudi
>
>
> [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org> wrote:
>
> > Rudi,
> >
> > As we discussed earlier today, let my send you my binaries for the kernel
> > and
> > u-boot to try on your board. I just wanted to ask you about the toolchain
> > that
> > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > toolchain
> > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > toolchain from oe-core... I'm wondering if you are having the same issue.
> >
> > --
> > Denys
> >
> >
> > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > a
> > > try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > environment
> > > has now moved on to using zImage which consequently means u-boot will not
> > > find the kernel file.
> > >
> > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > normally have no effect. Since there is no dependency of the u-boot
> > recipes
> > > on the kernel image types changes to the kernel image type for newer
> > > versions of the kernel then automatically means that it must be changed
> > for
> > > the previous versions too.
> > >
> > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > fails
> > > with the exact same problem and stops booting with a kernel not syncing
> > > message during the init calls. Apparently a patch must have been applied
> > to
> > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > build system.
> > >
> > > I would appreciate any hints to get this kernel built and boot on the
> > board.
> > >
> > > Thanks,
> > > Rudi
> > >
> > >
> > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > <rstreif@linuxfoundation.org>wrote:
> > >
> > > > Denys,
> > > >
> > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > initialization. I attached the boot log. I don't know much about the
> > > > platform details but maybe that's an issue you know about.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > >
> > > >>
> > > >> [1]
> > > >> Build Configuration:
> > > >> BB_VERSION = "1.21.0"
> > > >> BUILD_SYS = "x86_64-linux"
> > > >> NATIVELSBSTRING = "Fedora-18"
> > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > >> MACHINE = "am335x-evm"
> > > >> DISTRO = "poky"
> > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > >> TARGET_FPU = "vfp-neon"
> > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 19:36 ` Denys Dmytriyenko
@ 2013-10-22 20:16 ` Denys Dmytriyenko
0 siblings, 0 replies; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-22 20:16 UTC (permalink / raw)
To: Rudolf Streif, meta-ti
Hey, Rudi,
Just one more quick check about your board - are you sure yours is an EVM? Or
is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
board - is it green (EVM) or purple (SK)?
For example, here's the EVM:
https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
--
Denys
On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com
> > > > > > Phone: +1.619.537.6646
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
@ 2013-10-22 20:36 Vanderpool Josh
2013-10-22 22:28 ` Denys Dmytriyenko
0 siblings, 1 reply; 21+ messages in thread
From: Vanderpool Josh @ 2013-10-22 20:36 UTC (permalink / raw)
To: meta-ti@yoctoproject.org
It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or B after the AM335x.
________________________________________
From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of meta-ti-request@yoctoproject.org [meta-ti-request@yoctoproject.org]
Sent: Tuesday, October 22, 2013 4:17 PM
To: meta-ti@yoctoproject.org
Subject: meta-ti Digest, Vol 25, Issue 36
Send meta-ti mailing list submissions to
meta-ti@yoctoproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.yoctoproject.org/listinfo/meta-ti
or, via email, send a message with subject or body 'help' to
meta-ti-request@yoctoproject.org
You can reach the person managing the list at
meta-ti-owner@yoctoproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of meta-ti digest..."
Today's Topics:
1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
core-image-base (Vanderpool Josh)
4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
----------------------------------------------------------------------
Message: 1
Date: Tue, 22 Oct 2013 15:36:21 -0400
From: Denys Dmytriyenko <denys@ti.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Message-ID: <20131022193620.GB9301@edge>
Content-Type: text/plain; charset="us-ascii"
Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
versions of the silicon and I believe those are the latest ones. Need to
double-check that.
Denys
On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> Where do I find the PG version of the board? The barcode sticker on the
> board says rev 1.2.
>
>
> On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
>
> > Now I'm just wondering what PG version of the board you've got, if it
> > fails in
> > the same way with our 3.8 kernel and a known good set of 3.12 images...
> >
> >
> > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > Thanks, Denys.
> > >
> > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > poky master. Which is what I used all along.
> > >
> > > Thanks for sending your binaries. They fail too with the exact same
> > > problem. See attached log. I found [1] on gmane which exactly describes
> > the
> > > problem I am seeing.
> > >
> > > If that is the case then I was wondering why my earlier builds with
> > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > too. Of course I don't know anything about the specifics of the gpio and
> > > the timers on the chip but it looks like a weird hardware initialization
> > > condition. And I don't know if the proposed patch in [1] was ever
> > > incorporated in your kernel tree.
> > >
> > > I don't think it's the hardware (or at least not alone) because the SD
> > that
> > > ships with it with the 3.2 kernel works just fine.
> > >
> > > Cheers,
> > > Rudi
> > >
> > >
> > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > wrote:
> > >
> > > > Rudi,
> > > >
> > > > As we discussed earlier today, let my send you my binaries for the
> > kernel
> > > > and
> > > > u-boot to try on your board. I just wanted to ask you about the
> > toolchain
> > > > that
> > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > toolchain
> > > > and I vaguely remember hearing about some problems with the recent
> > gcc-4.8
> > > > toolchain from oe-core... I'm wondering if you are having the same
> > issue.
> > > >
> > > > --
> > > > Denys
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > kernel
> > > > a
> > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > environment
> > > > > has now moved on to using zImage which consequently means u-boot
> > will not
> > > > > find the kernel file.
> > > > >
> > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > about
> > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > recipes
> > > > > on the kernel image types changes to the kernel image type for newer
> > > > > versions of the kernel then automatically means that it must be
> > changed
> > > > for
> > > > > the previous versions too.
> > > > >
> > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > fails
> > > > > with the exact same problem and stops booting with a kernel not
> > syncing
> > > > > message during the init calls. Apparently a patch must have been
> > applied
> > > > to
> > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > the
> > > > > build system.
> > > > >
> > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > board.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > <rstreif@linuxfoundation.org>wrote:
> > > > >
> > > > > > Denys,
> > > > > >
> > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > initialization. I attached the boot log. I don't know much about
> > the
> > > > > > platform details but maybe that's an issue you know about.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > >
> > > > > >>
> > > > > >> [1]
> > > > > >> Build Configuration:
> > > > > >> BB_VERSION = "1.21.0"
> > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > >> MACHINE = "am335x-evm"
> > > > > >> DISTRO = "poky"
> > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > >> TARGET_FPU = "vfp-neon"
> > > > > >> meta-yocto =
> > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >> meta-ti =
> > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > >> meta-oe =
> > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > >> meta =
> > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com
> > > > > Phone: +1.619.537.6646
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > >
> > > > > _______________________________________________
> > > > > meta-ti mailing list
> > > > > meta-ti@yoctoproject.org
> > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
------------------------------
Message: 2
Date: Tue, 22 Oct 2013 15:37:32 -0400
From: Denys Dmytriyenko <denys@ti.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Message-ID: <20131022193732.GC9301@edge>
Content-Type: text/plain; charset="us-ascii"
And just to double-check here as well - you did try all the binaries I sent
you, including MLO, u-boot, zImage and DTB, right?
Denys
On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> Thanks, Denys.
>
> Interesting point about gcc. It's version 4.8.1 which is the default for
> poky master. Which is what I used all along.
>
> Thanks for sending your binaries. They fail too with the exact same
> problem. See attached log. I found [1] on gmane which exactly describes the
> problem I am seeing.
>
> If that is the case then I was wondering why my earlier builds with
> 3.12-rc3 actually worked. And I tried them again and they are now failing
> too. Of course I don't know anything about the specifics of the gpio and
> the timers on the chip but it looks like a weird hardware initialization
> condition. And I don't know if the proposed patch in [1] was ever
> incorporated in your kernel tree.
>
> I don't think it's the hardware (or at least not alone) because the SD that
> ships with it with the 3.2 kernel works just fine.
>
> Cheers,
> Rudi
>
>
> [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org> wrote:
>
> > Rudi,
> >
> > As we discussed earlier today, let my send you my binaries for the kernel
> > and
> > u-boot to try on your board. I just wanted to ask you about the toolchain
> > that
> > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > toolchain
> > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > toolchain from oe-core... I'm wondering if you are having the same issue.
> >
> > --
> > Denys
> >
> >
> > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > a
> > > try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > environment
> > > has now moved on to using zImage which consequently means u-boot will not
> > > find the kernel file.
> > >
> > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > normally have no effect. Since there is no dependency of the u-boot
> > recipes
> > > on the kernel image types changes to the kernel image type for newer
> > > versions of the kernel then automatically means that it must be changed
> > for
> > > the previous versions too.
> > >
> > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > fails
> > > with the exact same problem and stops booting with a kernel not syncing
> > > message during the init calls. Apparently a patch must have been applied
> > to
> > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > build system.
> > >
> > > I would appreciate any hints to get this kernel built and boot on the
> > board.
> > >
> > > Thanks,
> > > Rudi
> > >
> > >
> > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > <rstreif@linuxfoundation.org>wrote:
> > >
> > > > Denys,
> > > >
> > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > initialization. I attached the boot log. I don't know much about the
> > > > platform details but maybe that's an issue you know about.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > >
> > > >>
> > > >> [1]
> > > >> Build Configuration:
> > > >> BB_VERSION = "1.21.0"
> > > >> BUILD_SYS = "x86_64-linux"
> > > >> NATIVELSBSTRING = "Fedora-18"
> > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > >> MACHINE = "am335x-evm"
> > > >> DISTRO = "poky"
> > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > >> TARGET_FPU = "vfp-neon"
> > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
>
>
> --
> --
> *Rudolf J. Streif*
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@linux.com
> Phone: +1.619.537.6646
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
------------------------------
Message: 3
Date: Tue, 22 Oct 2013 19:52:13 +0000
From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
meta-ti(master) core-image-base
Message-ID:
<7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
Content-Type: text/plain; charset="us-ascii"
Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
Regards,
Josh
________________________________________
From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of meta-ti-request@yoctoproject.org [meta-ti-request@yoctoproject.org]
Sent: Tuesday, October 22, 2013 3:00 PM
To: meta-ti@yoctoproject.org
Subject: meta-ti Digest, Vol 25, Issue 35
Send meta-ti mailing list submissions to
meta-ti@yoctoproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.yoctoproject.org/listinfo/meta-ti
or, via email, send a message with subject or body 'help' to
meta-ti-request@yoctoproject.org
You can reach the person managing the list at
meta-ti-owner@yoctoproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of meta-ti digest..."
Today's Topics:
1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
core-image-base (Rudolf Streif)
----------------------------------------------------------------------
Message: 1
Date: Tue, 22 Oct 2013 18:18:29 +0100
From: Rudolf Streif <rstreif@linuxfoundation.org>
To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
meta-ti(master) core-image-base
Message-ID:
<CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Josh,
I am seeing the exact same problem with my am335x-evmsk and the latest
meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
This problem looks like the one posted here [2].
The bad news is I don't have a solution for it. The good news is that Denys
and I are attending the same conference and I keep harassing him about it.
:)
Cheers,
Rudi
[1]
https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
[2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
Joshua.Vanderpool@raymondcorp.com> wrote:
> I am having a similar issue as Rudi.
> Attached is the bootLog.
>
>
> Build Configuration:
> BB_VERSION = "1.21.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "Ubuntu-12.04"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "am335x-evm"
> DISTRO = "poky"
> DISTRO_VERSION = "1.5+snapshot-20131022"
> TUNE_FEATURES = "armv7a vfp neon"
> TARGET_FPU = "vfp-neon"
> meta
> meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
>
> Josh Vanderpool
> Electrical Engineer
> Control Systems
> The Raymond Corporation
> 20 South Canal Street
> Greene, New York 13778-0130
> Phone: 607-656-2617
> Fax: 607-656-4845
> joshua.vanderpool@raymondcorp.com
> http://www.raymondcorp.com
>
>
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains
> information that may be confidential, protected by applicable legal
> privileges, or constitute non-public information. It is intended to be
> conveyed only to the designated recipient(s). If you are not an intended
> recipient of this message, please notify the sender by replying to this
> message and then delete it from your system. Use, dissemination,
> distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
------------------------------
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti
End of meta-ti Digest, Vol 25, Issue 35
***************************************
Confidentiality Notice:
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
------------------------------
Message: 4
Date: Tue, 22 Oct 2013 16:16:52 -0400
From: Denys Dmytriyenko <denys@ti.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>,
meta-ti@yoctoproject.org
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Message-ID: <20131022201652.GB404@denix.org>
Content-Type: text/plain; charset=us-ascii
Hey, Rudi,
Just one more quick check about your board - are you sure yours is an EVM? Or
is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
board - is it green (EVM) or purple (SK)?
For example, here's the EVM:
https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
--
Denys
On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com
> > > > > > Phone: +1.619.537.6646
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
> _______________________________________________
> 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
End of meta-ti Digest, Vol 25, Issue 36
***************************************
Confidentiality Notice:
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 20:36 Vanderpool Josh
@ 2013-10-22 22:28 ` Denys Dmytriyenko
2013-10-22 23:47 ` Rudolf Streif
0 siblings, 1 reply; 21+ messages in thread
From: Denys Dmytriyenko @ 2013-10-22 22:28 UTC (permalink / raw)
To: Vanderpool Josh; +Cc: meta-ti@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 31994 bytes --]
Josh,
Yes, in your case it was clear from the beginning you had a problem with SK
and it is kind of known... In Rudi's case he was saying he had an actual EVM,
which is known to boot fine at the moment, hence I was confirming with him.
For your case, please try the DTB file attached. Thanks.
--
Denys
On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or
> B after the AM335x.
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of meta-ti-request@yoctoproject.org [meta-ti-request@yoctoproject.org]
> Sent: Tuesday, October 22, 2013 4:17 PM
> To: meta-ti@yoctoproject.org
> Subject: meta-ti Digest, Vol 25, Issue 36
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Vanderpool Josh)
> 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 15:36:21 -0400
> From: Denys Dmytriyenko <denys@ti.com>
> To: Rudolf Streif <rstreif@linuxfoundation.org>
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193620.GB9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com
> > > > > > Phone: +1.619.537.6646
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Oct 2013 15:37:32 -0400
> From: Denys Dmytriyenko <denys@ti.com>
> To: Rudolf Streif <rstreif@linuxfoundation.org>
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193732.GC9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> And just to double-check here as well - you did try all the binaries I sent
> you, including MLO, u-boot, zImage and DTB, right?
>
> Denys
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bb recipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not syncing
> > > > message during the init calls. Apparently a patch must have been applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com
> > Phone: +1.619.537.6646
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org
> > Linux Foundation Training Schedule: training.linuxfoundation.org
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Oct 2013 19:52:13 +0000
> From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
> To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
>
> There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
>
> however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
>
> So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
>
> So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
>
> Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
>
> Regards,
> Josh
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org] on behalf of meta-ti-request@yoctoproject.org [meta-ti-request@yoctoproject.org]
> Sent: Tuesday, October 22, 2013 3:00 PM
> To: meta-ti@yoctoproject.org
> Subject: meta-ti Digest, Vol 25, Issue 35
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Rudolf Streif)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 18:18:29 +0100
> From: Rudolf Streif <rstreif@linuxfoundation.org>
> To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
> Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Josh,
>
> I am seeing the exact same problem with my am335x-evmsk and the latest
> meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
>
> This problem looks like the one posted here [2].
>
> The bad news is I don't have a solution for it. The good news is that Denys
> and I are attending the same conference and I keep harassing him about it.
> :)
>
> Cheers,
> Rudi
>
>
> [1]
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> Joshua.Vanderpool@raymondcorp.com> wrote:
>
> > I am having a similar issue as Rudi.
> > Attached is the bootLog.
> >
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Ubuntu-12.04"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "am335x-evm"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.5+snapshot-20131022"
> > TUNE_FEATURES = "armv7a vfp neon"
> > TARGET_FPU = "vfp-neon"
> > meta
> > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> >
> > Josh Vanderpool
> > Electrical Engineer
> > Control Systems
> > The Raymond Corporation
> > 20 South Canal Street
> > Greene, New York 13778-0130
> > Phone: 607-656-2617
> > Fax: 607-656-4845
> > joshua.vanderpool@raymondcorp.com
> > http://www.raymondcorp.com
> >
> >
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> > information that may be confidential, protected by applicable legal
> > privileges, or constitute non-public information. It is intended to be
> > conveyed only to the designated recipient(s). If you are not an intended
> > recipient of this message, please notify the sender by replying to this
> > message and then delete it from your system. Use, dissemination,
> > distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 35
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Oct 2013 16:16:52 -0400
> From: Denys Dmytriyenko <denys@ti.com>
> To: Rudolf Streif <rstreif@linuxfoundation.org>,
> meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022201652.GB404@denix.org>
> Content-Type: text/plain; charset=us-ascii
>
> Hey, Rudi,
>
> Just one more quick check about your board - are you sure yours is an EVM? Or
> is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
> board - is it green (EVM) or purple (SK)?
>
> For example, here's the EVM:
> https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
>
> --
> Denys
>
>
>
> On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > > the timers on the chip but it looks like a weird hardware initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > > initialization. I attached the boot log. I don't know much about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com
> > > > > > > Phone: +1.619.537.6646
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com
> > > > > Phone: +1.619.537.6646
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > _______________________________________________
> > 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
>
>
> End of meta-ti Digest, Vol 25, Issue 36
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
[-- Attachment #2: am335x-evmsk.dtb --]
[-- Type: application/octet-stream, Size: 34722 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 22:28 ` Denys Dmytriyenko
@ 2013-10-22 23:47 ` Rudolf Streif
2013-10-22 23:54 ` Dmytriyenko, Denys
0 siblings, 1 reply; 21+ messages in thread
From: Rudolf Streif @ 2013-10-22 23:47 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti@yoctoproject.org, Vanderpool Josh
[-- Attachment #1: Type: text/plain, Size: 35676 bytes --]
Denys,
Sorry, yes, the board I have is a am335x_evmsk. I forgot to write it out
correctly in the subject line. it's a purple board. I have been using the
correct device tree file all along.
The board revision is 1.2B. The CPU is XAM3359ZCZ. On boot the kernel
reports:
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instruction cache
[ 0.000000] Machine: am335xevm
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (sgx neon )
Maybe that helps you to determine what CPU revision that is.
I built a 3.2.0 kernel with core-image-sato and it works just fine (after
enabling tmpdevfs support in the kernel).
It may will be a combination of that hardware with the newer kernel
versions. I just bought the board a couple of weeks ago from DigiKey. If it
is an older CPU revision then they are apparently selling older stock.
If the CPU revision not being supported by the newer kernel is indeed the
root cause of the issue then this may become frustrating for more users.
There is no way that a user can reasonably find out that the kernel does
not boot because of the CPU revision. I don't know what has changed between
the CPU revisions but I would think that the kernel should support all of
them.
Cheers,
Rudi
On Tue, Oct 22, 2013 at 11:28 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> Josh,
>
> Yes, in your case it was clear from the beginning you had a problem with SK
> and it is kind of known... In Rudi's case he was saying he had an actual
> EVM,
> which is known to boot fine at the moment, hence I was confirming with him.
>
> For your case, please try the DTB file attached. Thanks.
>
> --
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> > It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A
> or
> > B after the AM335x.
> >
> > ________________________________________
> > From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org]
> on behalf of meta-ti-request@yoctoproject.org [
> meta-ti-request@yoctoproject.org]
> > Sent: Tuesday, October 22, 2013 4:17 PM
> > To: meta-ti@yoctoproject.org
> > Subject: meta-ti Digest, Vol 25, Issue 36
> >
> > Send meta-ti mailing list submissions to
> > meta-ti@yoctoproject.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.yoctoproject.org/listinfo/meta-ti
> > or, via email, send a message with subject or body 'help' to
> > meta-ti-request@yoctoproject.org
> >
> > You can reach the person managing the list at
> > meta-ti-owner@yoctoproject.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of meta-ti digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> > 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> > 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> > core-image-base (Vanderpool Josh)
> > 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 22 Oct 2013 15:36:21 -0400
> > From: Denys Dmytriyenko <denys@ti.com>
> > To: Rudolf Streif <rstreif@linuxfoundation.org>
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> > Message-ID: <20131022193620.GB9301@edge>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com>
> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12
> images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the
> default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly
> describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now
> failing
> > > > > too. Of course I don't know anything about the specifics of the
> gpio and
> > > > > the timers on the chip but it looks like a weird hardware
> initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because
> the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <
> denis@denix.org>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for
> the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7
> hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the
> recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the
> same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the
> 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the
> linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means
> u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into
> the
> > > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not
> think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it
> should
> > > > > > > normally have no effect. Since there is no dependency of the
> u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for
> newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8
> uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging
> repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have
> been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do
> with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot
> on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls
> during
> > > > > > > > initialization. I attached the boot log. I don't know much
> about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com
> > > > > > > Phone: +1.619.537.6646
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > > Linux Foundation Training Schedule:
> training.linuxfoundation.org
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com
> > > > > Phone: +1.619.537.6646
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Tue, 22 Oct 2013 15:37:32 -0400
> > From: Denys Dmytriyenko <denys@ti.com>
> > To: Rudolf Streif <rstreif@linuxfoundation.org>
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> > Message-ID: <20131022193732.GC9301@edge>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > And just to double-check here as well - you did try all the binaries I
> sent
> > you, including MLO, u-boot, zImage and DTB, right?
> >
> > Denys
> >
> >
> > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > Thanks, Denys.
> > >
> > > Interesting point about gcc. It's version 4.8.1 which is the default
> for
> > > poky master. Which is what I used all along.
> > >
> > > Thanks for sending your binaries. They fail too with the exact same
> > > problem. See attached log. I found [1] on gmane which exactly
> describes the
> > > problem I am seeing.
> > >
> > > If that is the case then I was wondering why my earlier builds with
> > > 3.12-rc3 actually worked. And I tried them again and they are now
> failing
> > > too. Of course I don't know anything about the specifics of the gpio
> and
> > > the timers on the chip but it looks like a weird hardware
> initialization
> > > condition. And I don't know if the proposed patch in [1] was ever
> > > incorporated in your kernel tree.
> > >
> > > I don't think it's the hardware (or at least not alone) because the SD
> that
> > > ships with it with the 3.2 kernel works just fine.
> > >
> > > Cheers,
> > > Rudi
> > >
> > >
> > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org>
> wrote:
> > >
> > > > Rudi,
> > > >
> > > > As we discussed earlier today, let my send you my binaries for the
> kernel
> > > > and
> > > > u-boot to try on your board. I just wanted to ask you about the
> toolchain
> > > > that
> > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > toolchain
> > > > and I vaguely remember hearing about some problems with the recent
> gcc-4.8
> > > > toolchain from oe-core... I'm wondering if you are having the same
> issue.
> > > >
> > > > --
> > > > Denys
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> kernel
> > > > a
> > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > environment
> > > > > has now moved on to using zImage which consequently means u-boot
> will not
> > > > > find the kernel file.
> > > > >
> > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not think
> about
> > > > > u-boot. Does zImage not work with 3.8? I did not try it but it
> should
> > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > recipes
> > > > > on the kernel image types changes to the kernel image type for
> newer
> > > > > versions of the kernel then automatically means that it must be
> changed
> > > > for
> > > > > the previous versions too.
> > > > >
> > > > > I mocked around with the u-boot environment and booted the 3.8
> uImage
> > > > > kernel. To my surprise the 3.8 kernel from the TI staging
> repository
> > > > fails
> > > > > with the exact same problem and stops booting with a kernel not
> syncing
> > > > > message during the init calls. Apparently a patch must have been
> applied
> > > > to
> > > > > the kernel repo that breaks it. It has nothing possibly to do with
> the
> > > > > build system.
> > > > >
> > > > > I would appreciate any hints to get this kernel built and boot on
> the
> > > > board.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > <rstreif@linuxfoundation.org>wrote:
> > > > >
> > > > > > Denys,
> > > > > >
> > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > initialization. I attached the boot log. I don't know much about
> the
> > > > > > platform details but maybe that's an issue you know about.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > >
> > > > > >>
> > > > > >> [1]
> > > > > >> Build Configuration:
> > > > > >> BB_VERSION = "1.21.0"
> > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > >> MACHINE = "am335x-evm"
> > > > > >> DISTRO = "poky"
> > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > >> TARGET_FPU = "vfp-neon"
> > > > > >> meta-yocto =
> "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >> meta-ti =
> "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > >> meta-oe =
> "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > >> meta =
> "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com
> > > > > Phone: +1.619.537.6646
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > >
> > > > > _______________________________________________
> > > > > meta-ti mailing list
> > > > > meta-ti@yoctoproject.org
> > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com
> > > Phone: +1.619.537.6646
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > Linux Foundation Training Schedule: training.linuxfoundation.org
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Tue, 22 Oct 2013 19:52:13 +0000
> > From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
> > To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
> > Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> > meta-ti(master) core-image-base
> > Message-ID:
> >
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
> >
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Thanks for the links Rudi, I looked for the file referenced in [2]
> "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
> >
> > There is no cclock33xx_data.c rather there is in
> tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
> >
> > however a search I found
> tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
> >
> > So it appears there is mis-match as the patch is in the 3.10 files that
> re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
> >
> > So is this something that is just lost from the 3.12-rc5 kernel and
> shouldn't the linux-linc-headers be the version being built?
> >
> > Unfortunately being inexperienced with the project I am at a loss at how
> to fix this but hope this help point someone to the solution.
> >
> > Regards,
> > Josh
> >
> > ________________________________________
> > From: meta-ti-bounces@yoctoproject.org [meta-ti-bounces@yoctoproject.org]
> on behalf of meta-ti-request@yoctoproject.org [
> meta-ti-request@yoctoproject.org]
> > Sent: Tuesday, October 22, 2013 3:00 PM
> > To: meta-ti@yoctoproject.org
> > Subject: meta-ti Digest, Vol 25, Issue 35
> >
> > Send meta-ti mailing list submissions to
> > meta-ti@yoctoproject.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.yoctoproject.org/listinfo/meta-ti
> > or, via email, send a message with subject or body 'help' to
> > meta-ti-request@yoctoproject.org
> >
> > You can reach the person managing the list at
> > meta-ti-owner@yoctoproject.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of meta-ti digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> > core-image-base (Rudolf Streif)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 22 Oct 2013 18:18:29 +0100
> > From: Rudolf Streif <rstreif@linuxfoundation.org>
> > To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com>
> > Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
> > Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> > meta-ti(master) core-image-base
> > Message-ID:
> > <
> CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi Josh,
> >
> > I am seeing the exact same problem with my am335x-evmsk and the latest
> > meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
> >
> > This problem looks like the one posted here [2].
> >
> > The bad news is I don't have a solution for it. The good news is that
> Denys
> > and I are attending the same conference and I keep harassing him about
> it.
> > :)
> >
> > Cheers,
> > Rudi
> >
> >
> > [1]
> >
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> > [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> > Joshua.Vanderpool@raymondcorp.com> wrote:
> >
> > > I am having a similar issue as Rudi.
> > > Attached is the bootLog.
> > >
> > >
> > > Build Configuration:
> > > BB_VERSION = "1.21.0"
> > > BUILD_SYS = "x86_64-linux"
> > > NATIVELSBSTRING = "Ubuntu-12.04"
> > > TARGET_SYS = "arm-poky-linux-gnueabi"
> > > MACHINE = "am335x-evm"
> > > DISTRO = "poky"
> > > DISTRO_VERSION = "1.5+snapshot-20131022"
> > > TUNE_FEATURES = "armv7a vfp neon"
> > > TARGET_FPU = "vfp-neon"
> > > meta
> > > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> > >
> > > Josh Vanderpool
> > > Electrical Engineer
> > > Control Systems
> > > The Raymond Corporation
> > > 20 South Canal Street
> > > Greene, New York 13778-0130
> > > Phone: 607-656-2617
> > > Fax: 607-656-4845
> > > joshua.vanderpool@raymondcorp.com
> > > http://www.raymondcorp.com
> > >
> > >
> > > Confidentiality Notice:
> > >
> > > The preceding e-mail message (including any attachments) contains
> > > information that may be confidential, protected by applicable legal
> > > privileges, or constitute non-public information. It is intended to be
> > > conveyed only to the designated recipient(s). If you are not an
> intended
> > > recipient of this message, please notify the sender by replying to this
> > > message and then delete it from your system. Use, dissemination,
> > > distribution or reproduction of this message by unintended recipients
> is
> > > not authorized and may be unlawful.
> > >
> > >
> > >
> > > _______________________________________________
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> > End of meta-ti Digest, Vol 25, Issue 35
> > ***************************************
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> information that may be confidential, protected by applicable legal
> privileges, or constitute non-public information. It is intended to be
> conveyed only to the designated recipient(s). If you are not an intended
> recipient of this message, please notify the sender by replying to this
> message and then delete it from your system. Use, dissemination,
> distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Tue, 22 Oct 2013 16:16:52 -0400
> > From: Denys Dmytriyenko <denys@ti.com>
> > To: Rudolf Streif <rstreif@linuxfoundation.org>,
> > meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> > Message-ID: <20131022201652.GB404@denix.org>
> > Content-Type: text/plain; charset=us-ascii
> >
> > Hey, Rudi,
> >
> > Just one more quick check about your board - are you sure yours is an
> EVM? Or
> > is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB
> of your
> > board - is it green (EVM) or purple (SK)?
> >
> > For example, here's the EVM:
> > https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
> >
> > --
> > Denys
> >
> >
> >
> > On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > > versions of the silicon and I believe those are the latest ones. Need
> to
> > > double-check that.
> > >
> > > Denys
> > >
> > >
> > > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > > Where do I find the PG version of the board? The barcode sticker on
> the
> > > > board says rev 1.2.
> > > >
> > > >
> > > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com>
> wrote:
> > > >
> > > > > Now I'm just wondering what PG version of the board you've got, if
> it
> > > > > fails in
> > > > > the same way with our 3.8 kernel and a known good set of 3.12
> images...
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > > Thanks, Denys.
> > > > > >
> > > > > > Interesting point about gcc. It's version 4.8.1 which is the
> default for
> > > > > > poky master. Which is what I used all along.
> > > > > >
> > > > > > Thanks for sending your binaries. They fail too with the exact
> same
> > > > > > problem. See attached log. I found [1] on gmane which exactly
> describes
> > > > > the
> > > > > > problem I am seeing.
> > > > > >
> > > > > > If that is the case then I was wondering why my earlier builds
> with
> > > > > > 3.12-rc3 actually worked. And I tried them again and they are
> now failing
> > > > > > too. Of course I don't know anything about the specifics of the
> gpio and
> > > > > > the timers on the chip but it looks like a weird hardware
> initialization
> > > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > > incorporated in your kernel tree.
> > > > > >
> > > > > > I don't think it's the hardware (or at least not alone) because
> the SD
> > > > > that
> > > > > > ships with it with the 3.2 kernel works just fine.
> > > > > >
> > > > > > Cheers,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <
> denis@denix.org>
> > > > > wrote:
> > > > > >
> > > > > > > Rudi,
> > > > > > >
> > > > > > > As we discussed earlier today, let my send you my binaries for
> the
> > > > > kernel
> > > > > > > and
> > > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > > toolchain
> > > > > > > that
> > > > > > > you used to build yours. In our builds we use Linaro gcc-4.7
> hardfp
> > > > > > > toolchain
> > > > > > > and I vaguely remember hearing about some problems with the
> recent
> > > > > gcc-4.8
> > > > > > > toolchain from oe-core... I'm wondering if you are having the
> same
> > > > > issue.
> > > > > > >
> > > > > > > --
> > > > > > > Denys
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > > Since the 3.12-rc5 kernel does not work I decided to give
> the 3.8
> > > > > kernel
> > > > > > > a
> > > > > > > > try. The issue with this one is that the
> linux-ti-staging_3.8.bbrecipe
> > > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the
> u-boot
> > > > > > > environment
> > > > > > > > has now moved on to using zImage which consequently means
> u-boot
> > > > > will not
> > > > > > > > find the kernel file.
> > > > > > > >
> > > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked
> into the
> > > > > > > > linux-ti-staging_3.8.bb recipe but whoever did it did not
> think
> > > > > about
> > > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but
> it should
> > > > > > > > normally have no effect. Since there is no dependency of the
> u-boot
> > > > > > > recipes
> > > > > > > > on the kernel image types changes to the kernel image type
> for newer
> > > > > > > > versions of the kernel then automatically means that it must
> be
> > > > > changed
> > > > > > > for
> > > > > > > > the previous versions too.
> > > > > > > >
> > > > > > > > I mocked around with the u-boot environment and booted the
> 3.8 uImage
> > > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging
> repository
> > > > > > > fails
> > > > > > > > with the exact same problem and stops booting with a kernel
> not
> > > > > syncing
> > > > > > > > message during the init calls. Apparently a patch must have
> been
> > > > > applied
> > > > > > > to
> > > > > > > > the kernel repo that breaks it. It has nothing possibly to
> do with
> > > > > the
> > > > > > > > build system.
> > > > > > > >
> > > > > > > > I would appreciate any hints to get this kernel built and
> boot on the
> > > > > > > board.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > > <rstreif@linuxfoundation.org>wrote:
> > > > > > > >
> > > > > > > > > Denys,
> > > > > > > > >
> > > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls
> during
> > > > > > > > > initialization. I attached the boot log. I don't know much
> about
> > > > > the
> > > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Rudi
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >>
> > > > > > > > >> [1]
> > > > > > > > >> Build Configuration:
> > > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > > >> DISTRO = "poky"
> > > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > > >> meta-yocto =
> > > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > > >> meta-ti =
> > > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > > >> meta-oe =
> > > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > > >> meta =
> > > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > --
> > > > > > > > *Rudolf J. Streif*
> > > > > > > > Director of Embedded Solutions
> > > > > > > > The Linux Foundation
> > > > > > > >
> > > > > > > > rudolf.streif@linux.com
> > > > > > > > Phone: +1.619.537.6646
> > > > > > > > Skype: rudolfstreif
> > > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > > >
> > > > > > > > Linux Foundation Events Schedule:
> events.linuxfoundation.org
> > > > > > > > Linux Foundation Training Schedule:
> training.linuxfoundation.org
> > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > meta-ti mailing list
> > > > > > > > meta-ti@yoctoproject.org
> > > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com
> > > > > > Phone: +1.619.537.6646
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com
> > > > Phone: +1.619.537.6646
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org
> > > _______________________________________________
> > > 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
> >
> >
> > End of meta-ti Digest, Vol 25, Issue 36
> > ***************************************
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> information that may be confidential, protected by applicable legal
> privileges, or constitute non-public information. It is intended to be
> conveyed only to the designated recipient(s). If you are not an intended
> recipient of this message, please notify the sender by replying to this
> message and then delete it from your system. Use, dissemination,
> distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > 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
>
>
[-- Attachment #2: Type: text/html, Size: 54186 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 23:47 ` Rudolf Streif
@ 2013-10-22 23:54 ` Dmytriyenko, Denys
2013-10-23 16:32 ` Vanderpool Josh
0 siblings, 1 reply; 21+ messages in thread
From: Dmytriyenko, Denys @ 2013-10-22 23:54 UTC (permalink / raw)
To: rstreif@linuxfoundation.org
Cc: meta-ti@yoctoproject.org, Joshua.Vanderpool@raymondcorp.com
[-- Attachment #1: Type: text/plain, Size: 36924 bytes --]
I sent a different DTB...
Denys
-----Original Message-----
From: Rudolf Streif [rstreif@linuxfoundation.org]
Received: Wednesday, 23 Oct 2013, 0:48
To: Dmytriyenko, Denys [denys@ti.com]
CC: Vanderpool Josh [Joshua.Vanderpool@raymondcorp.com]; meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Denys,
Sorry, yes, the board I have is a am335x_evmsk. I forgot to write it out correctly in the subject line. it's a purple board. I have been using the correct device tree file all along.
The board revision is 1.2B. The CPU is XAM3359ZCZ. On boot the kernel reports:
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: am335xevm
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (sgx neon )
Maybe that helps you to determine what CPU revision that is.
I built a 3.2.0 kernel with core-image-sato and it works just fine (after enabling tmpdevfs support in the kernel).
It may will be a combination of that hardware with the newer kernel versions. I just bought the board a couple of weeks ago from DigiKey. If it is an older CPU revision then they are apparently selling older stock.
If the CPU revision not being supported by the newer kernel is indeed the root cause of the issue then this may become frustrating for more users. There is no way that a user can reasonably find out that the kernel does not boot because of the CPU revision. I don't know what has changed between the CPU revisions but I would think that the kernel should support all of them.
Cheers,
Rudi
On Tue, Oct 22, 2013 at 11:28 PM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
Josh,
Yes, in your case it was clear from the beginning you had a problem with SK
and it is kind of known... In Rudi's case he was saying he had an actual EVM,
which is known to boot fine at the moment, hence I was confirming with him.
For your case, please try the DTB file attached. Thanks.
--
Denys
On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or
> B after the AM335x.
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 4:17 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 36
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Vanderpool Josh)
> 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 15:36:21 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193620.GB9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Oct 2013 15:37:32 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193732.GC9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> And just to double-check here as well - you did try all the binaries I sent
> you, including MLO, u-boot, zImage and DTB, right?
>
> Denys
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not syncing
> > > > message during the init calls. Apparently a patch must have been applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Oct 2013 19:52:13 +0000
> From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> To: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
>
> There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
>
> however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
>
> So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
>
> So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
>
> Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
>
> Regards,
> Josh
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 3:00 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 35
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Rudolf Streif)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 18:18:29 +0100
> From: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> Cc: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com<mailto:CA%2BgsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Josh,
>
> I am seeing the exact same problem with my am335x-evmsk and the latest
> meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
>
> This problem looks like the one posted here [2].
>
> The bad news is I don't have a solution for it. The good news is that Denys
> and I are attending the same conference and I keep harassing him about it.
> :)
>
> Cheers,
> Rudi
>
>
> [1]
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>> wrote:
>
> > I am having a similar issue as Rudi.
> > Attached is the bootLog.
> >
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Ubuntu-12.04"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "am335x-evm"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.5+snapshot-20131022"
> > TUNE_FEATURES = "armv7a vfp neon"
> > TARGET_FPU = "vfp-neon"
> > meta
> > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> >
> > Josh Vanderpool
> > Electrical Engineer
> > Control Systems
> > The Raymond Corporation
> > 20 South Canal Street
> > Greene, New York 13778-0130
> > Phone: 607-656-2617
> > Fax: 607-656-4845
> > joshua.vanderpool@raymondcorp.com<mailto:joshua.vanderpool@raymondcorp.com>
> > http://www.raymondcorp.com
> >
> >
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> > information that may be confidential, protected by applicable legal
> > privileges, or constitute non-public information. It is intended to be
> > conveyed only to the designated recipient(s). If you are not an intended
> > recipient of this message, please notify the sender by replying to this
> > message and then delete it from your system. Use, dissemination,
> > distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 35
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Oct 2013 16:16:52 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>,
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022201652.GB404@denix.org<mailto:20131022201652.GB404@denix.org>>
> Content-Type: text/plain; charset=us-ascii
>
> Hey, Rudi,
>
> Just one more quick check about your board - are you sure yours is an EVM? Or
> is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
> board - is it green (EVM) or purple (SK)?
>
> For example, here's the EVM:
> https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
>
> --
> Denys
>
>
>
> On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > > the timers on the chip but it looks like a weird hardware initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > > initialization. I attached the boot log. I don't know much about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 36
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-ti
[-- Attachment #2: Type: text/html, Size: 56471 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-22 23:54 ` Dmytriyenko, Denys
@ 2013-10-23 16:32 ` Vanderpool Josh
2013-10-25 12:07 ` Vanderpool Josh
0 siblings, 1 reply; 21+ messages in thread
From: Vanderpool Josh @ 2013-10-23 16:32 UTC (permalink / raw)
To: Dmytriyenko, Denys, rstreif@linuxfoundation.org; +Cc: meta-ti@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 37955 bytes --]
Attached is a boot log from a working version done back the 7th of October 3.12.rc3.
This was using the master branch of poky, meta-ti and meta-qt5.
I hope plan on getting the commit tag shortly.
-Josh
________________________________________
From: Dmytriyenko, Denys [denys@ti.com]
Sent: Tuesday, October 22, 2013 7:54 PM
To: rstreif@linuxfoundation.org
Cc: Vanderpool Josh; meta-ti@yoctoproject.org
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
I sent a different DTB...
Denys
-----Original Message-----
From: Rudolf Streif [rstreif@linuxfoundation.org]
Received: Wednesday, 23 Oct 2013, 0:48
To: Dmytriyenko, Denys [denys@ti.com]
CC: Vanderpool Josh [Joshua.Vanderpool@raymondcorp.com]; meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Denys,
Sorry, yes, the board I have is a am335x_evmsk. I forgot to write it out correctly in the subject line. it's a purple board. I have been using the correct device tree file all along.
The board revision is 1.2B. The CPU is XAM3359ZCZ. On boot the kernel reports:
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: am335xevm
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (sgx neon )
Maybe that helps you to determine what CPU revision that is.
I built a 3.2.0 kernel with core-image-sato and it works just fine (after enabling tmpdevfs support in the kernel).
It may will be a combination of that hardware with the newer kernel versions. I just bought the board a couple of weeks ago from DigiKey. If it is an older CPU revision then they are apparently selling older stock.
If the CPU revision not being supported by the newer kernel is indeed the root cause of the issue then this may become frustrating for more users. There is no way that a user can reasonably find out that the kernel does not boot because of the CPU revision. I don't know what has changed between the CPU revisions but I would think that the kernel should support all of them.
Cheers,
Rudi
On Tue, Oct 22, 2013 at 11:28 PM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
Josh,
Yes, in your case it was clear from the beginning you had a problem with SK
and it is kind of known... In Rudi's case he was saying he had an actual EVM,
which is known to boot fine at the moment, hence I was confirming with him.
For your case, please try the DTB file attached. Thanks.
--
Denys
On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or
> B after the AM335x.
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 4:17 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 36
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Vanderpool Josh)
> 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 15:36:21 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193620.GB9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Oct 2013 15:37:32 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193732.GC9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> And just to double-check here as well - you did try all the binaries I sent
> you, including MLO, u-boot, zImage and DTB, right?
>
> Denys
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not syncing
> > > > message during the init calls. Apparently a patch must have been applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Oct 2013 19:52:13 +0000
> From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> To: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
>
> There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
>
> however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
>
> So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
>
> So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
>
> Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
>
> Regards,
> Josh
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 3:00 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 35
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Rudolf Streif)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 18:18:29 +0100
> From: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> Cc: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com<mailto:CA%2BgsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Josh,
>
> I am seeing the exact same problem with my am335x-evmsk and the latest
> meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
>
> This problem looks like the one posted here [2].
>
> The bad news is I don't have a solution for it. The good news is that Denys
> and I are attending the same conference and I keep harassing him about it.
> :)
>
> Cheers,
> Rudi
>
>
> [1]
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>> wrote:
>
> > I am having a similar issue as Rudi.
> > Attached is the bootLog.
> >
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Ubuntu-12.04"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "am335x-evm"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.5+snapshot-20131022"
> > TUNE_FEATURES = "armv7a vfp neon"
> > TARGET_FPU = "vfp-neon"
> > meta
> > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> >
> > Josh Vanderpool
> > Electrical Engineer
> > Control Systems
> > The Raymond Corporation
> > 20 South Canal Street
> > Greene, New York 13778-0130
> > Phone: 607-656-2617
> > Fax: 607-656-4845
> > joshua.vanderpool@raymondcorp.com<mailto:joshua.vanderpool@raymondcorp.com>
> > http://www.raymondcorp.com
> >
> >
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> > information that may be confidential, protected by applicable legal
> > privileges, or constitute non-public information. It is intended to be
> > conveyed only to the designated recipient(s). If you are not an intended
> > recipient of this message, please notify the sender by replying to this
> > message and then delete it from your system. Use, dissemination,
> > distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 35
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Oct 2013 16:16:52 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>,
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022201652.GB404@denix.org<mailto:20131022201652.GB404@denix.org>>
> Content-Type: text/plain; charset=us-ascii
>
> Hey, Rudi,
>
> Just one more quick check about your board - are you sure yours is an EVM? Or
> is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
> board - is it green (EVM) or purple (SK)?
>
> For example, here's the EVM:
> https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
>
> --
> Denys
>
>
>
> On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > > the timers on the chip but it looks like a weird hardware initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > > initialization. I attached the boot log. I don't know much about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 36
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-ti
Confidentiality Notice:
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
[-- Attachment #2: bootLog 1.5 --]
[-- Type: application/octet-stream, Size: 15335 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-23 16:32 ` Vanderpool Josh
@ 2013-10-25 12:07 ` Vanderpool Josh
2013-10-25 14:11 ` Dmytriyenko, Denys
0 siblings, 1 reply; 21+ messages in thread
From: Vanderpool Josh @ 2013-10-25 12:07 UTC (permalink / raw)
To: Dmytriyenko, Denys, rstreif@linuxfoundation.org; +Cc: meta-ti@yoctoproject.org
Denys,
This is the commit of meta-ti that works with the AM335x-SK.
meta-ti = "(nobranch):b739286d690bdaada952a2376bd7aa1ba221badd"
-Josh
________________________________________
From: Vanderpool Josh
Sent: Wednesday, October 23, 2013 12:32 PM
To: Dmytriyenko, Denys; rstreif@linuxfoundation.org
Cc: meta-ti@yoctoproject.org
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
Attached is a boot log from a working version done back the 7th of October 3.12.rc3.
This was using the master branch of poky, meta-ti and meta-qt5.
I hope plan on getting the commit tag shortly.
-Josh
________________________________________
From: Dmytriyenko, Denys [denys@ti.com]
Sent: Tuesday, October 22, 2013 7:54 PM
To: rstreif@linuxfoundation.org
Cc: Vanderpool Josh; meta-ti@yoctoproject.org
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
I sent a different DTB...
Denys
-----Original Message-----
From: Rudolf Streif [rstreif@linuxfoundation.org]
Received: Wednesday, 23 Oct 2013, 0:48
To: Dmytriyenko, Denys [denys@ti.com]
CC: Vanderpool Josh [Joshua.Vanderpool@raymondcorp.com]; meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Denys,
Sorry, yes, the board I have is a am335x_evmsk. I forgot to write it out correctly in the subject line. it's a purple board. I have been using the correct device tree file all along.
The board revision is 1.2B. The CPU is XAM3359ZCZ. On boot the kernel reports:
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: am335xevm
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (sgx neon )
Maybe that helps you to determine what CPU revision that is.
I built a 3.2.0 kernel with core-image-sato and it works just fine (after enabling tmpdevfs support in the kernel).
It may will be a combination of that hardware with the newer kernel versions. I just bought the board a couple of weeks ago from DigiKey. If it is an older CPU revision then they are apparently selling older stock.
If the CPU revision not being supported by the newer kernel is indeed the root cause of the issue then this may become frustrating for more users. There is no way that a user can reasonably find out that the kernel does not boot because of the CPU revision. I don't know what has changed between the CPU revisions but I would think that the kernel should support all of them.
Cheers,
Rudi
On Tue, Oct 22, 2013 at 11:28 PM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
Josh,
Yes, in your case it was clear from the beginning you had a problem with SK
and it is kind of known... In Rudi's case he was saying he had an actual EVM,
which is known to boot fine at the moment, hence I was confirming with him.
For your case, please try the DTB file attached. Thanks.
--
Denys
On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or
> B after the AM335x.
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 4:17 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 36
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Vanderpool Josh)
> 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 15:36:21 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193620.GB9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Oct 2013 15:37:32 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193732.GC9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> And just to double-check here as well - you did try all the binaries I sent
> you, including MLO, u-boot, zImage and DTB, right?
>
> Denys
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not syncing
> > > > message during the init calls. Apparently a patch must have been applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Oct 2013 19:52:13 +0000
> From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> To: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
>
> There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
>
> however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
>
> So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
>
> So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
>
> Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
>
> Regards,
> Josh
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 3:00 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 35
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Rudolf Streif)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 18:18:29 +0100
> From: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> Cc: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com<mailto:CA%2BgsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Josh,
>
> I am seeing the exact same problem with my am335x-evmsk and the latest
> meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
>
> This problem looks like the one posted here [2].
>
> The bad news is I don't have a solution for it. The good news is that Denys
> and I are attending the same conference and I keep harassing him about it.
> :)
>
> Cheers,
> Rudi
>
>
> [1]
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>> wrote:
>
> > I am having a similar issue as Rudi.
> > Attached is the bootLog.
> >
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Ubuntu-12.04"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "am335x-evm"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.5+snapshot-20131022"
> > TUNE_FEATURES = "armv7a vfp neon"
> > TARGET_FPU = "vfp-neon"
> > meta
> > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> >
> > Josh Vanderpool
> > Electrical Engineer
> > Control Systems
> > The Raymond Corporation
> > 20 South Canal Street
> > Greene, New York 13778-0130
> > Phone: 607-656-2617
> > Fax: 607-656-4845
> > joshua.vanderpool@raymondcorp.com<mailto:joshua.vanderpool@raymondcorp.com>
> > http://www.raymondcorp.com
> >
> >
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> > information that may be confidential, protected by applicable legal
> > privileges, or constitute non-public information. It is intended to be
> > conveyed only to the designated recipient(s). If you are not an intended
> > recipient of this message, please notify the sender by replying to this
> > message and then delete it from your system. Use, dissemination,
> > distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 35
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Oct 2013 16:16:52 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>,
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022201652.GB404@denix.org<mailto:20131022201652.GB404@denix.org>>
> Content-Type: text/plain; charset=us-ascii
>
> Hey, Rudi,
>
> Just one more quick check about your board - are you sure yours is an EVM? Or
> is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
> board - is it green (EVM) or purple (SK)?
>
> For example, here's the EVM:
> https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
>
> --
> Denys
>
>
>
> On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > > the timers on the chip but it looks like a weird hardware initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > > initialization. I attached the boot log. I don't know much about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 36
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-ti
Confidentiality Notice:
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: AM335x EVM and core-image-sato
2013-10-25 12:07 ` Vanderpool Josh
@ 2013-10-25 14:11 ` Dmytriyenko, Denys
0 siblings, 0 replies; 21+ messages in thread
From: Dmytriyenko, Denys @ 2013-10-25 14:11 UTC (permalink / raw)
To: rstreif@linuxfoundation.org, Joshua.Vanderpool@RAYMONDCORP.COM
Cc: meta-ti@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 38722 bytes --]
Thanks!
Denys
-----Original Message-----
From: Vanderpool Josh [Joshua.Vanderpool@RAYMONDCORP.COM]
Received: Friday, 25 Oct 2013, 13:09
To: Dmytriyenko, Denys [denys@ti.com]; rstreif@linuxfoundation.org [rstreif@linuxfoundation.org]
CC: meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
Denys,
This is the commit of meta-ti that works with the AM335x-SK.
meta-ti = "(nobranch):b739286d690bdaada952a2376bd7aa1ba221badd"
-Josh
________________________________________
From: Vanderpool Josh
Sent: Wednesday, October 23, 2013 12:32 PM
To: Dmytriyenko, Denys; rstreif@linuxfoundation.org
Cc: meta-ti@yoctoproject.org
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
Attached is a boot log from a working version done back the 7th of October 3.12.rc3.
This was using the master branch of poky, meta-ti and meta-qt5.
I hope plan on getting the commit tag shortly.
-Josh
________________________________________
From: Dmytriyenko, Denys [denys@ti.com]
Sent: Tuesday, October 22, 2013 7:54 PM
To: rstreif@linuxfoundation.org
Cc: Vanderpool Josh; meta-ti@yoctoproject.org
Subject: RE: [meta-ti] AM335x EVM and core-image-sato
I sent a different DTB...
Denys
-----Original Message-----
From: Rudolf Streif [rstreif@linuxfoundation.org]
Received: Wednesday, 23 Oct 2013, 0:48
To: Dmytriyenko, Denys [denys@ti.com]
CC: Vanderpool Josh [Joshua.Vanderpool@raymondcorp.com]; meta-ti@yoctoproject.org [meta-ti@yoctoproject.org]
Subject: Re: [meta-ti] AM335x EVM and core-image-sato
Denys,
Sorry, yes, the board I have is a am335x_evmsk. I forgot to write it out correctly in the subject line. it's a purple board. I have been using the correct device tree file all along.
The board revision is 1.2B. The CPU is XAM3359ZCZ. On boot the kernel reports:
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: am335xevm
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AM335X ES1.0 (sgx neon )
Maybe that helps you to determine what CPU revision that is.
I built a 3.2.0 kernel with core-image-sato and it works just fine (after enabling tmpdevfs support in the kernel).
It may will be a combination of that hardware with the newer kernel versions. I just bought the board a couple of weeks ago from DigiKey. If it is an older CPU revision then they are apparently selling older stock.
If the CPU revision not being supported by the newer kernel is indeed the root cause of the issue then this may become frustrating for more users. There is no way that a user can reasonably find out that the kernel does not boot because of the CPU revision. I don't know what has changed between the CPU revisions but I would think that the kernel should support all of them.
Cheers,
Rudi
On Tue, Oct 22, 2013 at 11:28 PM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
Josh,
Yes, in your case it was clear from the beginning you had a problem with SK
and it is kind of known... In Rudi's case he was saying he had an actual EVM,
which is known to boot fine at the moment, hence I was confirming with him.
For your case, please try the DTB file attached. Thanks.
--
Denys
On Tue, Oct 22, 2013 at 08:36:13PM +0000, Vanderpool Josh wrote:
> It is a SK and the revision of silicon is 1.0 as it is a XAM3359ZCZ no A or
> B after the AM335x.
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 4:17 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 36
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 2. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
> 3. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Vanderpool Josh)
> 4. Re: AM335x EVM and core-image-sato (Denys Dmytriyenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 15:36:21 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193620.GB9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> versions of the silicon and I believe those are the latest ones. Need to
> double-check that.
>
> Denys
>
>
> On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > Where do I find the PG version of the board? The barcode sticker on the
> > board says rev 1.2.
> >
> >
> > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> >
> > > Now I'm just wondering what PG version of the board you've got, if it
> > > fails in
> > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > >
> > >
> > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > Thanks, Denys.
> > > >
> > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > poky master. Which is what I used all along.
> > > >
> > > > Thanks for sending your binaries. They fail too with the exact same
> > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > the
> > > > problem I am seeing.
> > > >
> > > > If that is the case then I was wondering why my earlier builds with
> > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > the timers on the chip but it looks like a weird hardware initialization
> > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > incorporated in your kernel tree.
> > > >
> > > > I don't think it's the hardware (or at least not alone) because the SD
> > > that
> > > > ships with it with the 3.2 kernel works just fine.
> > > >
> > > > Cheers,
> > > > Rudi
> > > >
> > > >
> > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > wrote:
> > > >
> > > > > Rudi,
> > > > >
> > > > > As we discussed earlier today, let my send you my binaries for the
> > > kernel
> > > > > and
> > > > > u-boot to try on your board. I just wanted to ask you about the
> > > toolchain
> > > > > that
> > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > toolchain
> > > > > and I vaguely remember hearing about some problems with the recent
> > > gcc-4.8
> > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > issue.
> > > > >
> > > > > --
> > > > > Denys
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > kernel
> > > > > a
> > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > environment
> > > > > > has now moved on to using zImage which consequently means u-boot
> > > will not
> > > > > > find the kernel file.
> > > > > >
> > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > about
> > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > recipes
> > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > versions of the kernel then automatically means that it must be
> > > changed
> > > > > for
> > > > > > the previous versions too.
> > > > > >
> > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > fails
> > > > > > with the exact same problem and stops booting with a kernel not
> > > syncing
> > > > > > message during the init calls. Apparently a patch must have been
> > > applied
> > > > > to
> > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > the
> > > > > > build system.
> > > > > >
> > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > board.
> > > > > >
> > > > > > Thanks,
> > > > > > Rudi
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > >
> > > > > > > Denys,
> > > > > > >
> > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > initialization. I attached the boot log. I don't know much about
> > > the
> > > > > > > platform details but maybe that's an issue you know about.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> [1]
> > > > > > >> Build Configuration:
> > > > > > >> BB_VERSION = "1.21.0"
> > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > >> MACHINE = "am335x-evm"
> > > > > > >> DISTRO = "poky"
> > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > >> meta-yocto =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >> meta-ti =
> > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > >> meta-oe =
> > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > >> meta =
> > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > --
> > > > > > *Rudolf J. Streif*
> > > > > > Director of Embedded Solutions
> > > > > > The Linux Foundation
> > > > > >
> > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > Skype: rudolfstreif
> > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > >
> > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > >
> > > > > > _______________________________________________
> > > > > > meta-ti mailing list
> > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Oct 2013 15:37:32 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> Cc: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022193732.GC9301@edge>
> Content-Type: text/plain; charset="us-ascii"
>
> And just to double-check here as well - you did try all the binaries I sent
> you, including MLO, u-boot, zImage and DTB, right?
>
> Denys
>
>
> On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > Thanks, Denys.
> >
> > Interesting point about gcc. It's version 4.8.1 which is the default for
> > poky master. Which is what I used all along.
> >
> > Thanks for sending your binaries. They fail too with the exact same
> > problem. See attached log. I found [1] on gmane which exactly describes the
> > problem I am seeing.
> >
> > If that is the case then I was wondering why my earlier builds with
> > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > too. Of course I don't know anything about the specifics of the gpio and
> > the timers on the chip but it looks like a weird hardware initialization
> > condition. And I don't know if the proposed patch in [1] was ever
> > incorporated in your kernel tree.
> >
> > I don't think it's the hardware (or at least not alone) because the SD that
> > ships with it with the 3.2 kernel works just fine.
> >
> > Cheers,
> > Rudi
> >
> >
> > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> >
> >
> > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>> wrote:
> >
> > > Rudi,
> > >
> > > As we discussed earlier today, let my send you my binaries for the kernel
> > > and
> > > u-boot to try on your board. I just wanted to ask you about the toolchain
> > > that
> > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > toolchain
> > > and I vaguely remember hearing about some problems with the recent gcc-4.8
> > > toolchain from oe-core... I'm wondering if you are having the same issue.
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8 kernel
> > > a
> > > > try. The issue with this one is that the linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe
> > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > environment
> > > > has now moved on to using zImage which consequently means u-boot will not
> > > > find the kernel file.
> > > >
> > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think about
> > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > normally have no effect. Since there is no dependency of the u-boot
> > > recipes
> > > > on the kernel image types changes to the kernel image type for newer
> > > > versions of the kernel then automatically means that it must be changed
> > > for
> > > > the previous versions too.
> > > >
> > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > fails
> > > > with the exact same problem and stops booting with a kernel not syncing
> > > > message during the init calls. Apparently a patch must have been applied
> > > to
> > > > the kernel repo that breaks it. It has nothing possibly to do with the
> > > > build system.
> > > >
> > > > I would appreciate any hints to get this kernel built and boot on the
> > > board.
> > > >
> > > > Thanks,
> > > > Rudi
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > >
> > > > > Denys,
> > > > >
> > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > initialization. I attached the boot log. I don't know much about the
> > > > > platform details but maybe that's an issue you know about.
> > > > >
> > > > > Thanks,
> > > > > Rudi
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> [1]
> > > > >> Build Configuration:
> > > > >> BB_VERSION = "1.21.0"
> > > > >> BUILD_SYS = "x86_64-linux"
> > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > >> MACHINE = "am335x-evm"
> > > > >> DISTRO = "poky"
> > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > >> TARGET_FPU = "vfp-neon"
> > > > >> meta-yocto = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >> meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > >> meta-oe = "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > >> meta = "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > --
> > > > *Rudolf J. Streif*
> > > > Director of Embedded Solutions
> > > > The Linux Foundation
> > > >
> > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > Skype: rudolfstreif
> > > > PGP: RSA 2048/2048 D6E7D28B
> > > >
> > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > >
> > > > _______________________________________________
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > >
> > >
> >
> >
> > --
> > --
> > *Rudolf J. Streif*
> > Director of Embedded Solutions
> > The Linux Foundation
> >
> > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > Skype: rudolfstreif
> > PGP: RSA 2048/2048 D6E7D28B
> >
> > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Oct 2013 19:52:13 +0000
> From: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> To: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <7D1F292BE8E4CC4F93079C1A7A58D5622B9FF6D7@USNYGRMBX4.raymondcorp.local>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the links Rudi, I looked for the file referenced in [2] "arch/arm/mach-omap2/cclock33xx_data.c" to see if the patch works but...
>
> There is no cclock33xx_data.c rather there is in tmp/work/am335x_evm-poky-linux-gnueabi/linux-ti-staging/3.11+3.12-rc5-r20a+gitrAUTOINC+eb765a394c/git/arch/arm/mach-omap2/cclock3xxx_data.c.
>
> however a search I found tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/linux-libc-headers/3.10-r0/linux-3.10/arch/arm/mach-omap2/cclock33xx_data.c
>
> So it appears there is mis-match as the patch is in the 3.10 files that re in the armv7a-vfp-neon-poky-linux-gnueabi directory?
>
> So is this something that is just lost from the 3.12-rc5 kernel and shouldn't the linux-linc-headers be the version being built?
>
> Unfortunately being inexperienced with the project I am at a loss at how to fix this but hope this help point someone to the solution.
>
> Regards,
> Josh
>
> ________________________________________
> From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org>] on behalf of meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org> [meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>]
> Sent: Tuesday, October 22, 2013 3:00 PM
> To: meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: meta-ti Digest, Vol 25, Issue 35
>
> Send meta-ti mailing list submissions to
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/meta-ti
> or, via email, send a message with subject or body 'help' to
> meta-ti-request@yoctoproject.org<mailto:meta-ti-request@yoctoproject.org>
>
> You can reach the person managing the list at
> meta-ti-owner@yoctoproject.org<mailto:meta-ti-owner@yoctoproject.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of meta-ti digest..."
>
>
> Today's Topics:
>
> 1. Re: AM335x-SK kernel panic with Poky(master), meta-ti(master)
> core-image-base (Rudolf Streif)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Oct 2013 18:18:29 +0100
> From: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>
> To: Vanderpool Josh <Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>>
> Cc: "meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>" <meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>>
> Subject: Re: [meta-ti] AM335x-SK kernel panic with Poky(master),
> meta-ti(master) core-image-base
> Message-ID:
> <CA+gsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com<mailto:CA%2BgsK-pNkDYCcecOftuopRu9XnxK3Xr9ZbSU23yekqQEczCYeg@mail.gmail.com>>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Josh,
>
> I am seeing the exact same problem with my am335x-evmsk and the latest
> meta-ti with 3.12-rc5 kernel. I posted it on this mailing list [1].
>
> This problem looks like the one posted here [2].
>
> The bad news is I don't have a solution for it. The good news is that Denys
> and I are attending the same conference and I keep harassing him about it.
> :)
>
> Cheers,
> Rudi
>
>
> [1]
> https://lists.yoctoproject.org/pipermail/meta-ti/2013-October/003519.html
> [2] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
>
>
> On Tue, Oct 22, 2013 at 5:28 PM, Vanderpool Josh <
> Joshua.Vanderpool@raymondcorp.com<mailto:Joshua.Vanderpool@raymondcorp.com>> wrote:
>
> > I am having a similar issue as Rudi.
> > Attached is the bootLog.
> >
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Ubuntu-12.04"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "am335x-evm"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.5+snapshot-20131022"
> > TUNE_FEATURES = "armv7a vfp neon"
> > TARGET_FPU = "vfp-neon"
> > meta
> > meta-yocto = "master:505114c13d29799a25379f7ce720d632616d8776"
> > meta-ti = "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > meta-qt5 = "master:84cd4be2491895b0c3a0af64e4c83d58910d1f6c"
> >
> > Josh Vanderpool
> > Electrical Engineer
> > Control Systems
> > The Raymond Corporation
> > 20 South Canal Street
> > Greene, New York 13778-0130
> > Phone: 607-656-2617
> > Fax: 607-656-4845
> > joshua.vanderpool@raymondcorp.com<mailto:joshua.vanderpool@raymondcorp.com>
> > http://www.raymondcorp.com
> >
> >
> > Confidentiality Notice:
> >
> > The preceding e-mail message (including any attachments) contains
> > information that may be confidential, protected by applicable legal
> > privileges, or constitute non-public information. It is intended to be
> > conveyed only to the designated recipient(s). If you are not an intended
> > recipient of this message, please notify the sender by replying to this
> > message and then delete it from your system. Use, dissemination,
> > distribution or reproduction of this message by unintended recipients is
> > not authorized and may be unlawful.
> >
> >
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20131022/34dc4b0c/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 35
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Oct 2013 16:16:52 -0400
> From: Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>
> To: Rudolf Streif <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>,
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> Subject: Re: [meta-ti] AM335x EVM and core-image-sato
> Message-ID: <20131022201652.GB404@denix.org<mailto:20131022201652.GB404@denix.org>>
> Content-Type: text/plain; charset=us-ascii
>
> Hey, Rudi,
>
> Just one more quick check about your board - are you sure yours is an EVM? Or
> is it an SK-EVM i.e. a "Starter Kit"? Basically, what color is the PCB of your
> board - is it green (EVM) or purple (SK)?
>
> For example, here's the EVM:
> https://plus.google.com/u/0/110579591067038943673/posts/SLB35o1JgBu
>
> --
> Denys
>
>
>
> On Tue, Oct 22, 2013 at 03:36:21PM -0400, Denys Dmytriyenko wrote:
> > Huh, I'm wondering if 1.2 is still supported... There were 2.0 and 2.1
> > versions of the silicon and I believe those are the latest ones. Need to
> > double-check that.
> >
> > Denys
> >
> >
> > On Tue, Oct 22, 2013 at 08:57:51AM +0100, Rudolf Streif wrote:
> > > Where do I find the PG version of the board? The barcode sticker on the
> > > board says rev 1.2.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 12:19 AM, Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>> wrote:
> > >
> > > > Now I'm just wondering what PG version of the board you've got, if it
> > > > fails in
> > > > the same way with our 3.8 kernel and a known good set of 3.12 images...
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 11:19:35PM +0100, Rudolf Streif wrote:
> > > > > Thanks, Denys.
> > > > >
> > > > > Interesting point about gcc. It's version 4.8.1 which is the default for
> > > > > poky master. Which is what I used all along.
> > > > >
> > > > > Thanks for sending your binaries. They fail too with the exact same
> > > > > problem. See attached log. I found [1] on gmane which exactly describes
> > > > the
> > > > > problem I am seeing.
> > > > >
> > > > > If that is the case then I was wondering why my earlier builds with
> > > > > 3.12-rc3 actually worked. And I tried them again and they are now failing
> > > > > too. Of course I don't know anything about the specifics of the gpio and
> > > > > the timers on the chip but it looks like a weird hardware initialization
> > > > > condition. And I don't know if the proposed patch in [1] was ever
> > > > > incorporated in your kernel tree.
> > > > >
> > > > > I don't think it's the hardware (or at least not alone) because the SD
> > > > that
> > > > > ships with it with the 3.2 kernel works just fine.
> > > > >
> > > > > Cheers,
> > > > > Rudi
> > > > >
> > > > >
> > > > > [1] http://permalink.gmane.org/gmane.linux.ports.arm.omap/96044
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 10:15 PM, Denys Dmytriyenko <denis@denix.org<mailto:denis@denix.org>>
> > > > wrote:
> > > > >
> > > > > > Rudi,
> > > > > >
> > > > > > As we discussed earlier today, let my send you my binaries for the
> > > > kernel
> > > > > > and
> > > > > > u-boot to try on your board. I just wanted to ask you about the
> > > > toolchain
> > > > > > that
> > > > > > you used to build yours. In our builds we use Linaro gcc-4.7 hardfp
> > > > > > toolchain
> > > > > > and I vaguely remember hearing about some problems with the recent
> > > > gcc-4.8
> > > > > > toolchain from oe-core... I'm wondering if you are having the same
> > > > issue.
> > > > > >
> > > > > > --
> > > > > > Denys
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 21, 2013 at 10:42:35AM -0700, Rudolf Streif wrote:
> > > > > > > Since the 3.12-rc5 kernel does not work I decided to give the 3.8
> > > > kernel
> > > > > > a
> > > > > > > try. The issue with this one is that the linux-ti-staging_3.8.bbrecipe
> > > > > > > explicitly sets KERNEL_IMAGETYPE="uImage". However, the u-boot
> > > > > > environment
> > > > > > > has now moved on to using zImage which consequently means u-boot
> > > > will not
> > > > > > > find the kernel file.
> > > > > > >
> > > > > > > I do not know why KERNEL_IMAGETYPE = "uImage" was hacked into the
> > > > > > > linux-ti-staging_3.8.bb<http://linux-ti-staging_3.8.bb> recipe but whoever did it did not think
> > > > about
> > > > > > > u-boot. Does zImage not work with 3.8? I did not try it but it should
> > > > > > > normally have no effect. Since there is no dependency of the u-boot
> > > > > > recipes
> > > > > > > on the kernel image types changes to the kernel image type for newer
> > > > > > > versions of the kernel then automatically means that it must be
> > > > changed
> > > > > > for
> > > > > > > the previous versions too.
> > > > > > >
> > > > > > > I mocked around with the u-boot environment and booted the 3.8 uImage
> > > > > > > kernel. To my surprise the 3.8 kernel from the TI staging repository
> > > > > > fails
> > > > > > > with the exact same problem and stops booting with a kernel not
> > > > syncing
> > > > > > > message during the init calls. Apparently a patch must have been
> > > > applied
> > > > > > to
> > > > > > > the kernel repo that breaks it. It has nothing possibly to do with
> > > > the
> > > > > > > build system.
> > > > > > >
> > > > > > > I would appreciate any hints to get this kernel built and boot on the
> > > > > > board.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rudi
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 21, 2013 at 1:16 AM, Rudolf Streif
> > > > > > > <rstreif@linuxfoundation.org<mailto:rstreif@linuxfoundation.org>>wrote:
> > > > > > >
> > > > > > > > Denys,
> > > > > > > >
> > > > > > > > I recompiled the 3.12-rc5 kernel again but it still stalls during
> > > > > > > > initialization. I attached the boot log. I don't know much about
> > > > the
> > > > > > > > platform details but maybe that's an issue you know about.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rudi
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>
> > > > > > > >> [1]
> > > > > > > >> Build Configuration:
> > > > > > > >> BB_VERSION = "1.21.0"
> > > > > > > >> BUILD_SYS = "x86_64-linux"
> > > > > > > >> NATIVELSBSTRING = "Fedora-18"
> > > > > > > >> TARGET_SYS = "arm-poky-linux-gnueabi"
> > > > > > > >> MACHINE = "am335x-evm"
> > > > > > > >> DISTRO = "poky"
> > > > > > > >> DISTRO_VERSION = "1.5+snapshot-20131019"
> > > > > > > >> TUNE_FEATURES = "armv7a vfp neon"
> > > > > > > >> TARGET_FPU = "vfp-neon"
> > > > > > > >> meta-yocto =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >> meta-ti =
> > > > "master:c11504664990f007c3903d349e7cc135a904f8e2"
> > > > > > > >> meta-oe =
> > > > "master:f8903f53db717294d63a8d79b5ef7ca34b3c189e"
> > > > > > > >> meta =
> > > > "master:9a1dce10bdc9254bb38e0e54199f23ae55e209a4"
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > --
> > > > > > > *Rudolf J. Streif*
> > > > > > > Director of Embedded Solutions
> > > > > > > The Linux Foundation
> > > > > > >
> > > > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > > > Skype: rudolfstreif
> > > > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > > > >
> > > > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-ti mailing list
> > > > > > > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > *Rudolf J. Streif*
> > > > > Director of Embedded Solutions
> > > > > The Linux Foundation
> > > > >
> > > > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > > > Skype: rudolfstreif
> > > > > PGP: RSA 2048/2048 D6E7D28B
> > > > >
> > > > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > --
> > > *Rudolf J. Streif*
> > > Director of Embedded Solutions
> > > The Linux Foundation
> > >
> > > rudolf.streif@linux.com<mailto:rudolf.streif@linux.com>
> > > Phone: +1.619.537.6646<tel:%2B1.619.537.6646>
> > > Skype: rudolfstreif
> > > PGP: RSA 2048/2048 D6E7D28B
> > >
> > > Linux Foundation Events Schedule: events.linuxfoundation.org<http://events.linuxfoundation.org>
> > > Linux Foundation Training Schedule: training.linuxfoundation.org<http://training.linuxfoundation.org>
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-ti
> >
>
>
> ------------------------------
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
>
>
> End of meta-ti Digest, Vol 25, Issue 36
> ***************************************
> Confidentiality Notice:
>
> The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
> not authorized and may be unlawful.
>
>
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-ti
Confidentiality Notice:
The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
[-- Attachment #2: Type: text/html, Size: 58014 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2013-10-25 14:11 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-17 21:29 AM335x EVM and core-image-sato Rudolf Streif
2013-10-17 21:45 ` Denys Dmytriyenko
2013-10-19 1:09 ` Rudolf Streif
2013-10-19 2:39 ` Denys Dmytriyenko
2013-10-19 18:53 ` Rudolf Streif
2013-10-21 8:16 ` Rudolf Streif
2013-10-21 17:42 ` Rudolf Streif
2013-10-21 21:15 ` Denys Dmytriyenko
2013-10-21 22:19 ` Rudolf Streif
2013-10-21 23:19 ` Denys Dmytriyenko
2013-10-22 7:57 ` Rudolf Streif
2013-10-22 19:36 ` Denys Dmytriyenko
2013-10-22 20:16 ` Denys Dmytriyenko
2013-10-22 19:37 ` Denys Dmytriyenko
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 20:36 Vanderpool Josh
2013-10-22 22:28 ` Denys Dmytriyenko
2013-10-22 23:47 ` Rudolf Streif
2013-10-22 23:54 ` Dmytriyenko, Denys
2013-10-23 16:32 ` Vanderpool Josh
2013-10-25 12:07 ` Vanderpool Josh
2013-10-25 14:11 ` Dmytriyenko, Denys
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.