[Buildroot] new TI kernel version for beaglebone black

[Buildroot] new TI kernel version for beaglebone black

[Dan Pattison]

Hello All,

I have a question that is probably not 100% buildroot related, but was 
hoping to get some help. I am using buildroot to build a kernel and 
rootFS for a beaglebone black. Buildroot is awesome and builds 
everything fine. The board boots up and all packages work properly. 
Unfortunately, USB seems to be badly broken. In the kernel I have USB 
driver enabled and USB Announce New Devices turned on. Googling around I 
find several people with the same problem, hotplug does not work at all, 
and no device I have tried shows up in dmesg or lsusb on cold or warm 
boot. A band aid is to use a powered USB hub (have not tried that). Some 
guys on the beagleboard.org IRC say to try a newer kernel version (3.14 
or >) because beaglebone USB is fixed in newer kernel versions. Current 
buildroot beaglebone black kernel version is 3.12.10

In buildroot I used make beaglebone_defconfig.
Under the Kernel menu, Custom Git repository is selected.
The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
The def config is board/beaglebone/linux-3.12.config

How was the custom repository number 
(7f280334068b7c875ade51f8f3921ab311f0c824) derived? Looking on the TI 
gitorious site, I see they are working on kernel 3.15. How can I make 
buildroot use the newer version? How do I find the newer custom 
repository version? I tried to find my answer with google, but I must 
not be using the correct search term. Please excuse the newbish questions.

Thank you,

-- 
Dan Pattison
Ethertek Circuits

[Buildroot] new TI kernel version for beaglebone black

[Hadrien Boutteville]

Hello Dan,

On Fri, 30 May 2014 14:18:26 -0700, Dan Pattison wrote:
> I have a question that is probably not 100% buildroot related, but was 
> hoping to get some help. I am using buildroot to build a kernel and 
> rootFS for a beaglebone black. Buildroot is awesome and builds 
> everything fine. The board boots up and all packages work properly. 
> Unfortunately, USB seems to be badly broken. In the kernel I have USB 
> driver enabled and USB Announce New Devices turned on. Googling around I 
> find several people with the same problem, hotplug does not work at all, 
> and no device I have tried shows up in dmesg or lsusb on cold or warm 
> boot. A band aid is to use a powered USB hub (have not tried that). Some 
> guys on the beagleboard.org IRC say to try a newer kernel version (3.14 
> or >) because beaglebone USB is fixed in newer kernel versions. Current 
> buildroot beaglebone black kernel version is 3.12.10
> 
> In buildroot I used make beaglebone_defconfig.
> Under the Kernel menu, Custom Git repository is selected.
> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
> The def config is board/beaglebone/linux-3.12.config

I'm using the default beaglebone_defconfig on BBB and USB hotplug works
fine. In the default kernel config the options are selected as modules,
so you have to load them:

  $ modprobe musb_am335x
  $ modprobe musb_dsps

After that, outputs in dmesg will tell you that the USB port is found
(short version) and USB hotplug will work (I just tested).

> How was the custom repository number 
> (7f280334068b7c875ade51f8f3921ab311f0c824) derived? Looking on the TI 
> gitorious site, I see they are working on kernel 3.15. How can I make 
> buildroot use the newer version? How do I find the newer custom 
> repository version? I tried to find my answer with google, but I must 
> not be using the correct search term. Please excuse the newbish questions.

Regards,

Hadrien

[Buildroot] new TI kernel version for beaglebone black

[Dan Pattison]

On 5/31/2014 5:40 AM, Hadrien Boutteville wrote:
> Hello Dan,
>
> On Fri, 30 May 2014 14:18:26 -0700, Dan Pattison wrote:
>> I have a question that is probably not 100% buildroot related, but was
>> hoping to get some help. I am using buildroot to build a kernel and
>> rootFS for a beaglebone black. Buildroot is awesome and builds
>> everything fine. The board boots up and all packages work properly.
>> Unfortunately, USB seems to be badly broken. In the kernel I have USB
>> driver enabled and USB Announce New Devices turned on. Googling around I
>> find several people with the same problem, hotplug does not work at all,
>> and no device I have tried shows up in dmesg or lsusb on cold or warm
>> boot. A band aid is to use a powered USB hub (have not tried that). Some
>> guys on the beagleboard.org IRC say to try a newer kernel version (3.14
>> or >) because beaglebone USB is fixed in newer kernel versions. Current
>> buildroot beaglebone black kernel version is 3.12.10
>>
>> In buildroot I used make beaglebone_defconfig.
>> Under the Kernel menu, Custom Git repository is selected.
>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
>> The def config is board/beaglebone/linux-3.12.config
> I'm using the default beaglebone_defconfig on BBB and USB hotplug works
> fine. In the default kernel config the options are selected as modules,
> so you have to load them:
>
>    $ modprobe musb_am335x
>    $ modprobe musb_dsps
>
> After that, outputs in dmesg will tell you that the USB port is found
> (short version) and USB hotplug will work (I just tested).
>
>> How was the custom repository number
>> (7f280334068b7c875ade51f8f3921ab311f0c824) derived? Looking on the TI
>> gitorious site, I see they are working on kernel 3.15. How can I make
>> buildroot use the newer version? How do I find the newer custom
>> repository version? I tried to find my answer with google, but I must
>> not be using the correct search term. Please excuse the newbish questions.
> Regards,
>
> Hadrien
>
Hello Hadrien,

Thanks for the help. I had the drivers compiled into he kernel not as 
modules. When I reverted my changes back to module and added depmod to 
busybox, then things started to happen. Again, thanks for the help.

Best Regards,

Dan Pattison
Ethertek Circuits

[Buildroot] new TI kernel version for beaglebone black

[Hadrien Boutteville]

Dan,

On Sat, 31 May 2014 08:42:28 -0700, Dan Pattison wrote:
> On 5/31/2014 5:40 AM, Hadrien Boutteville wrote:
>> Hello Dan,
>>
>> On Fri, 30 May 2014 14:18:26 -0700, Dan Pattison wrote:
>>> I have a question that is probably not 100% buildroot related, but was
>>> hoping to get some help. I am using buildroot to build a kernel and
>>> rootFS for a beaglebone black. Buildroot is awesome and builds
>>> everything fine. The board boots up and all packages work properly.
>>> Unfortunately, USB seems to be badly broken. In the kernel I have USB
>>> driver enabled and USB Announce New Devices turned on. Googling around I
>>> find several people with the same problem, hotplug does not work at all,
>>> and no device I have tried shows up in dmesg or lsusb on cold or warm
>>> boot. A band aid is to use a powered USB hub (have not tried that). Some
>>> guys on the beagleboard.org IRC say to try a newer kernel version (3.14
>>> or >) because beaglebone USB is fixed in newer kernel versions. Current
>>> buildroot beaglebone black kernel version is 3.12.10
>>>
>>> In buildroot I used make beaglebone_defconfig.
>>> Under the Kernel menu, Custom Git repository is selected.
>>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>>> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
>>> The def config is board/beaglebone/linux-3.12.config
>> I'm using the default beaglebone_defconfig on BBB and USB hotplug works
>> fine. In the default kernel config the options are selected as modules,
>> so you have to load them:
>>
>>    $ modprobe musb_am335x
>>    $ modprobe musb_dsps
>>
>> After that, outputs in dmesg will tell you that the USB port is found
>> (short version) and USB hotplug will work (I just tested).
>>
>> Regards,
>>
>> Hadrien
>>
> Hello Hadrien,
> 
> Thanks for the help. I had the drivers compiled into he kernel not as 
> modules. When I reverted my changes back to module and added depmod to 
> busybox, then things started to happen. Again, thanks for the help.

From what you said I understood that you were using the default kernel
config in beaglebone_defconfig almost unchanged ;-).

Well, I'm using the drivers compiled into the kernel and it works fine
too. Make sure you selected those options in your kernel config:

  USB_MUSB_DUAL_ROLE=y
  USB_MUSB_HDRC=y
  USB_MUSB_DSPS=y
  USB_MUSB_AM335X_CHILD=y

Regards,

Hadrien

[Buildroot] new TI kernel version for beaglebone black

[Dan Pattison]

On 5/31/2014 9:38 AM, Hadrien Boutteville wrote:
> Dan,
>
> On Sat, 31 May 2014 08:42:28 -0700, Dan Pattison wrote:
>> On 5/31/2014 5:40 AM, Hadrien Boutteville wrote:
>>> Hello Dan,
>>>
>>> On Fri, 30 May 2014 14:18:26 -0700, Dan Pattison wrote:
>>>> I have a question that is probably not 100% buildroot related, but was
>>>> hoping to get some help. I am using buildroot to build a kernel and
>>>> rootFS for a beaglebone black. Buildroot is awesome and builds
>>>> everything fine. The board boots up and all packages work properly.
>>>> Unfortunately, USB seems to be badly broken. In the kernel I have USB
>>>> driver enabled and USB Announce New Devices turned on. Googling around I
>>>> find several people with the same problem, hotplug does not work at all,
>>>> and no device I have tried shows up in dmesg or lsusb on cold or warm
>>>> boot. A band aid is to use a powered USB hub (have not tried that). Some
>>>> guys on the beagleboard.org IRC say to try a newer kernel version (3.14
>>>> or >) because beaglebone USB is fixed in newer kernel versions. Current
>>>> buildroot beaglebone black kernel version is 3.12.10
>>>>
>>>> In buildroot I used make beaglebone_defconfig.
>>>> Under the Kernel menu, Custom Git repository is selected.
>>>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>>>> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
>>>> The def config is board/beaglebone/linux-3.12.config
>>> I'm using the default beaglebone_defconfig on BBB and USB hotplug works
>>> fine. In the default kernel config the options are selected as modules,
>>> so you have to load them:
>>>
>>>     $ modprobe musb_am335x
>>>     $ modprobe musb_dsps
>>>
>>> After that, outputs in dmesg will tell you that the USB port is found
>>> (short version) and USB hotplug will work (I just tested).
>>>
>>> Regards,
>>>
>>> Hadrien
>>>
>> Hello Hadrien,
>>
>> Thanks for the help. I had the drivers compiled into he kernel not as
>> modules. When I reverted my changes back to module and added depmod to
>> busybox, then things started to happen. Again, thanks for the help.
> >From what you said I understood that you were using the default kernel
> config in beaglebone_defconfig almost unchanged ;-).
>
> Well, I'm using the drivers compiled into the kernel and it works fine
> too. Make sure you selected those options in your kernel config:
>
>    USB_MUSB_DUAL_ROLE=y
>    USB_MUSB_HDRC=y
>    USB_MUSB_DSPS=y
>    USB_MUSB_AM335X_CHILD=y
>
> Regards,
>
> Hadrien
>
Hi Hadrien,

Again you are correct. I think I had the wrong glue layer selected. It 
all works now with the driver compiled into the kernel.

Thanks, you rock!

Dan Pattison
Ethertek Circuits

[Buildroot] new TI kernel version for beaglebone black

[Peter Kümmel]

On 30.05.2014 23:18, Dan Pattison wrote:
> Hello All,
>
> I have a question that is probably not 100% buildroot related, but was hoping to get some help. I am using buildroot to
> build a kernel and rootFS for a beaglebone black. Buildroot is awesome and builds everything fine. The board boots up
> and all packages work properly. Unfortunately, USB seems to be badly broken. In the kernel I have USB driver enabled and
> USB Announce New Devices turned on. Googling around I find several people with the same problem, hotplug does not work
> at all, and no device I have tried shows up in dmesg or lsusb on cold or warm boot. A band aid is to use a powered USB
> hub (have not tried that). Some guys on the beagleboard.org IRC say to try a newer kernel version (3.14 or >) because
> beaglebone USB is fixed in newer kernel versions. Current buildroot beaglebone black kernel version is 3.12.10
>
> In buildroot I used make beaglebone_defconfig.
> Under the Kernel menu, Custom Git repository is selected.
> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

BTW, does someone know how this repository relates to
https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git?

Is the ti-linux-kernel repository _THE_ reference for TI kernels or
are there better starting points?

When looking for kernel sources also the Arago projects pops up and
for sure Linaro.

Does someone have a link or an explanation how all these repositories relate?
That would be great!

Many thanks,
Peter

> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
> The def config is board/beaglebone/linux-3.12.config
>
> How was the custom repository number (7f280334068b7c875ade51f8f3921ab311f0c824) derived? Looking on the TI gitorious
> site, I see they are working on kernel 3.15. How can I make buildroot use the newer version? How do I find the newer
> custom repository version? I tried to find my answer with google, but I must not be using the correct search term.
> Please excuse the newbish questions.
>
> Thank you,
>

[Buildroot] new TI kernel version for beaglebone black

[Jerônimo Lopes]

2014-06-01 5:39 GMT-03:00 Peter K?mmel <syntheticpp@gmx.net>:

> On 30.05.2014 23:18, Dan Pattison wrote:
>
>> Hello All,
>>
>> I have a question that is probably not 100% buildroot related, but was
>> hoping to get some help. I am using buildroot to
>> build a kernel and rootFS for a beaglebone black. Buildroot is awesome
>> and builds everything fine. The board boots up
>> and all packages work properly. Unfortunately, USB seems to be badly
>> broken. In the kernel I have USB driver enabled and
>> USB Announce New Devices turned on. Googling around I find several people
>> with the same problem, hotplug does not work
>> at all, and no device I have tried shows up in dmesg or lsusb on cold or
>> warm boot. A band aid is to use a powered USB
>> hub (have not tried that). Some guys on the beagleboard.org IRC say to
>> try a newer kernel version (3.14 or >) because
>> beaglebone USB is fixed in newer kernel versions. Current buildroot
>> beaglebone black kernel version is 3.12.10
>>
>> In buildroot I used make beaglebone_defconfig.
>> Under the Kernel menu, Custom Git repository is selected.
>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>>
>
> BTW, does someone know how this repository relates to
> https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git?
>
> Is the ti-linux-kernel repository _THE_ reference for TI kernels or
> are there better starting points?
>
> When looking for kernel sources also the Arago projects pops up and
> for sure Linaro.
>
> Does someone have a link or an explanation how all these repositories
> relate?
> That would be great!
>
> Many thanks,
> Peter
>
>
>  The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
>> The def config is board/beaglebone/linux-3.12.config
>>
>> How was the custom repository number (7f280334068b7c875ade51f8f3921ab311f0c824)
>> derived? Looking on the TI gitorious
>> site, I see they are working on kernel 3.15. How can I make buildroot use
>> the newer version? How do I find the newer
>> custom repository version? I tried to find my answer with google, but I
>> must not be using the correct search term.
>> Please excuse the newbish questions.
>>
>> Thank you,
>>
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
?
Hi, I would like to add more questions on the discussion, that again is not
related to buildroot.? First off all I'm really a newbie on embedded linux
development.

I'm also working on a beaglebone black project using buildroot to build
all. Recently I need to change some pin modes, and every googling about it,
leads to capemanager, witch is provided by 'beagleboard kernel' (
https://github.com/beagleboard/kernel). Also every one saying something
about compile a kernel to beaglebone points to this kernel (the 3.8
version).

So I've decided to change things on my project to build this kernel outside
buildroot. But I'm not sure about this, witch is the recommended kernel to
use with beaglebone black?

Jer?nimo Lopes?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140602/62555503/attachment.html>

[Buildroot] new TI kernel version for beaglebone black

[Yegor Yefremov]

On Mon, Jun 2, 2014 at 2:39 PM, Jer?nimo Lopes <lopesjeronimo@gmail.com> wrote:
> 2014-06-01 5:39 GMT-03:00 Peter K?mmel <syntheticpp@gmx.net>:
>>
>> On 30.05.2014 23:18, Dan Pattison wrote:
>>>
>>> Hello All,
>>>
>>> I have a question that is probably not 100% buildroot related, but was
>>> hoping to get some help. I am using buildroot to
>>> build a kernel and rootFS for a beaglebone black. Buildroot is awesome
>>> and builds everything fine. The board boots up
>>> and all packages work properly. Unfortunately, USB seems to be badly
>>> broken. In the kernel I have USB driver enabled and
>>> USB Announce New Devices turned on. Googling around I find several people
>>> with the same problem, hotplug does not work
>>> at all, and no device I have tried shows up in dmesg or lsusb on cold or
>>> warm boot. A band aid is to use a powered USB
>>> hub (have not tried that). Some guys on the beagleboard.org IRC say to
>>> try a newer kernel version (3.14 or >) because
>>> beaglebone USB is fixed in newer kernel versions. Current buildroot
>>> beaglebone black kernel version is 3.12.10
>>>
>>> In buildroot I used make beaglebone_defconfig.
>>> Under the Kernel menu, Custom Git repository is selected.
>>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>>
>>
>> BTW, does someone know how this repository relates to
>> https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git?
>>
>> Is the ti-linux-kernel repository _THE_ reference for TI kernels or
>> are there better starting points?
>>
>> When looking for kernel sources also the Arago projects pops up and
>> for sure Linaro.
>>
>> Does someone have a link or an explanation how all these repositories
>> relate?
>> That would be great!
>>
>> Many thanks,
>> Peter
>>
>>
>>> The custom repository version is 7f280334068b7c875ade51f8f3921ab311f0c824
>>> The def config is board/beaglebone/linux-3.12.config
>>>
>>> How was the custom repository number
>>> (7f280334068b7c875ade51f8f3921ab311f0c824) derived? Looking on the TI
>>> gitorious
>>> site, I see they are working on kernel 3.15. How can I make buildroot use
>>> the newer version? How do I find the newer
>>> custom repository version? I tried to find my answer with google, but I
>>> must not be using the correct search term.
>>> Please excuse the newbish questions.
>>>
>>> Thank you,
>>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
> Hi, I would like to add more questions on the discussion, that again is not
> related to buildroot. First off all I'm really a newbie on embedded linux
> development.
>
> I'm also working on a beaglebone black project using buildroot to build all.
> Recently I need to change some pin modes, and every googling about it, leads
> to capemanager, witch is provided by 'beagleboard kernel'
> (https://github.com/beagleboard/kernel). Also every one saying something
> about compile a kernel to beaglebone points to this kernel (the 3.8
> version).
>
> So I've decided to change things on my project to build this kernel outside
> buildroot. But I'm not sure about this, witch is the recommended kernel to
> use with beaglebone black?

I'd say, just use the latest kernel
(https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.15-rc8.tar.xz)
and your custom DTS file to reflect your pinmux. Also take a look at
FIT concept (http://elinux.org/images/f/f4/Elc2013_Fernandes.pdf),
where you can embed multiple DTB files for different configurations.

Yegor

[Buildroot] new TI kernel version for beaglebone black

[Anders Darander]

On 1 June 2014 10:39, Peter K?mmel <syntheticpp@gmx.net> wrote:
> On 30.05.2014 23:18, Dan Pattison wrote:
>> In buildroot I used make beaglebone_defconfig.
>> Under the Kernel menu, Custom Git repository is selected.
>> The git URL is https://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
>
>
> BTW, does someone know how this repository relates to
> https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git?

The arm-soc.git repository is the integration repository controlled
the by maintainers
of the arm architecture in the Linux kernel. Thus, this is the last
step before getting your
patches into the mainline kernel. (Linus pulls from arm-soc.git among
other repos).

The TI repo is were TI themselves develops (at least it's the
externally visible point) the
kernels for their own SoC's and BSP's. This means that normally you'll
have better SoC
support (support for more peripherals) in the vendor tree (i.e. the TI
repo). However,
you can'? be sure that when (if) support for these peripherals goes
into the mainline kernel,
that their interface will always be exactly the same as in the TI
repo. The review process
for the mainline kernel might require further changes, that's
currently not reflected in the
TI repo.

> Is the ti-linux-kernel repository _THE_ reference for TI kernels or
> are there better starting points?
>
> When looking for kernel sources also the Arago projects pops up and
> for sure Linaro.

Arago is one of TI's embedded distributions. Currently it's a layer
for OpenEmbedded.

Then there's also the paches that you can find in
https://github.com/beagleboard/kernel. This
is yet another kernel for the SoC's in the Beagle* family of boards.
Instead of keeping a patched
kernel in this repo, they're keeping a set of patches to be applied to
a mainline kernel. This repo,
and their 3.8 branch is likely what you want if you need support for
capemgr etc.

Personally, unless I need some specific perifpheral that I can only
get from a certain tree, I usually
prefer mainline kernels. In this specific case, I've mostly been using
the TI repository (as you can
guess from my occasional updates to the beaglebone_defconfig).

> Does someone have a link or an explanation how all these repositories
> relate?
> That would be great!

Well, not a link but a short summary of what I've learned playing
around with primarily the BeagleBone,
but also a number of other TI SoC's.

Cheers,
Anders

-- 
Anders Darander
EPO guidelines 1978: "If the contribution to the known art resides
solely in a computer program then the subject matter is not
patentable in whatever manner it may be presented in the claims."

[Buildroot] new TI kernel version for beaglebone black

[Anders Darander]

On 2 June 2014 14:39, Jer?nimo Lopes <lopesjeronimo@gmail.com> wrote:
> I'm also working on a beaglebone black project using buildroot to build all.
> Recently I need to change some pin modes, and every googling about it, leads
> to capemanager, witch is provided by 'beagleboard kernel'
> (https://github.com/beagleboard/kernel). Also every one saying something
> about compile a kernel to beaglebone points to this kernel (the 3.8
> version).

> So I've decided to change things on my project to build this kernel outside
> buildroot. But I'm not sure about this, witch is the recommended kernel to
> use with beaglebone black?

I'd be inclined to agree with the previous response that you got.

Try the latest (currently 3.15) from mainline. If you need support for something
that doesn't work there, I'd check the TI tree.

If you want to use / need the capemgr (to more easily support multiple capes,
especially if you like to switch between a number of capes), then the
3.8 version
from https://github.com/beagleboard/kernel is likely your best bet.

There's no need to go to https://github.com/beagleboard/kernel just because of
pinmuxing. For that, just make sure that you customize your DTS to add your
specific configuration.

Cheers,
Anders

-- 
Anders Darander
EPO guidelines 1978: "If the contribution to the known art resides
solely in a computer program then the subject matter is not
patentable in whatever manner it may be presented in the claims."