[linux-yocto] Keyboard on Beaglebone Black

[Bruce Ashfield]

On 14-06-24 10:02 AM, Sven Vos wrote:
> If i am right then i have to configure the kernel with the "bitbake
> virtual/kernel -c menuconfig command"? And after that i need to

For iterative testing, that is the right thing to do.

> configure the following modules as built-in:
> - Support for Host-side USB
> - Inventra Highspeed Dual Role Controller
> - Platform Flue Layer (ti DSPS platforms?)
> - MUSB DMA mode (TI CPPI 4.1 (am335x))
>
> i configured it like that right now, but am i missing something because
> it isn't working for me.

To rule out anything non-obvious causing issues (and things that have
all caught me before). You've confirmed that the timestamp on the newly
booted kernel really is the one you rebuilt after changing the config ?
And you've seen it rebuilding ?

If so, can you diff the full .config before and after the menuconfig,
and send it along ? Kevin can compare it to the config he's booting and
testing.

Bruce

>
> Thanks for the good support today!
>
> Sven Vos
>
>
> 2014-06-24 14:56 GMT+02:00 Bruce Ashfield <bruce.ashfield at windriver.com
> <mailto:bruce.ashfield at windriver.com>>:
>
>     On 14-06-24 07:06 AM, Kevin Hao wrote:
>
>         On Tue, Jun 24, 2014 at 10:34:35AM +0800, Kevin Hao wrote:
>
>             On Mon, Jun 23, 2014 at 11:39:57AM -0400, Bruce Ashfield wrote:
>
>                 On 14-06-23 02:59 AM, Sven Vos wrote:
>
>                     Hello,
>
>                     I am trying to get a Keyboard working on a
>                     Beaglebone Black. But after
>                     building a non-custom core-image-minimal and running
>                     it on the
>                     beaglebone black, i saw that the display works, but
>                     my keyboard doesnt.
>                     I think it has something to do with the USB OTG but
>                     i have not a clue
>                     what need to be done to get it work. Does anybody
>                     got it working yet?
>
>
>                 Kevin has been supporting the yocto BSP for us, so
>                 adding him on the
>                 cc'.
>
>                 That being said, I'm not sure if the BBB is in a lab
>                 environment for
>                 him, and hence no physical USB keyboard to use or test.
>
>
>             I do have a BBB in hand. I will take a look at this issue.
>
>
>         It seems that the usb drivers are built as modules by default.
>         But the
>         kernel-modules is not installed by default on core-image-minimal
>         image.
>         That's the reason why the usb keyboard can't work. So we have
>         two options:
>             a) config usb drivers as built-in
>             b) install the kernel-modules on core-image-minimal
>
>         I prefer to option (a) since it makes no sense to build them as
>         modules for
>         a specific BSP. But it seems that many drivers such as sound,
>         display and usb
>         are configured as modules in beaglebone.cfg. Do we have any
>         special reason to
>         do so? Should we convert all of them to built-in?
>
>
>     No special reason that I know of. I'm find with converting them to
>     built-in.
>     Basic/core functionality is fine to include at all times!
>
>     Bruce
>
>
>         Thanks,
>         Kevin
>
>
>