From: Dan Pattison <dan.pattison@ethertek.ca>
To: buildroot@busybox.net
Subject: [Buildroot] new TI kernel version for beaglebone black
Date: Sat, 31 May 2014 17:13:56 -0700 [thread overview]
Message-ID: <538A7044.3030705@ethertek.ca> (raw)
In-Reply-To: <538A0575.8000303@gmail.com>
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
next prev parent reply other threads:[~2014-06-01 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 21:18 [Buildroot] new TI kernel version for beaglebone black Dan Pattison
2014-05-31 12:40 ` Hadrien Boutteville
2014-05-31 15:42 ` Dan Pattison
2014-05-31 16:38 ` Hadrien Boutteville
2014-06-01 0:13 ` Dan Pattison [this message]
2014-06-01 8:39 ` Peter Kümmel
2014-06-02 12:39 ` Jerônimo Lopes
2014-06-02 12:45 ` Yegor Yefremov
2014-06-09 6:12 ` Anders Darander
2014-06-09 6:07 ` Anders Darander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538A7044.3030705@ethertek.ca \
--to=dan.pattison@ethertek.ca \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox