From: softwizz <ad...@is...> - 2011-06-01 09:26:16
|
Just noticed in your writeup that you are using g_ether gadget to enable a USB connectioon with the host. I'd missed that, because it sounded counterintuitive, so I assumed you were implementing an ethernet device. Are you saying that all OTG peripheral-side functionality is based on ethernet? Cheers, Mike softwizz wrote: > > Hi Scott, > > As you may have noted, I found the USB_MODE setting in the kernel recipe > ahead of your last posting. > > I can confirm that the GADGET_OMAP change *is* in place. > > I am now testing, and I've discovered some operationa problems :- > > * USB_MODE="host" produces a build which recognises peripheral devices > * USB_MODE="otg" produces a build which fails to recognise anything, be it > peripheral or host > > I'm in the process of rebuilding with USB_MODE=""peripheral" to see if > that enables the target to connect to my devhost, but I only have an OTG > port available to me - I assume this should still operate in peripheral > mode. > > Do you have any idea why OTG should simply not work at all? > > Cheers, > > Mike > > > > jumpnowdev wrote: >> >> First make sure your defconfig has this change. It applies to all OMAP3 >> kernels. >> >> -CONFIG_USB_GADGET_OMAP=y >> -CONFIG_USB_OMAP=y >> +# CONFIG_USB_GADGET_OMAP is not set >> >> >> Then look at the recipe for the kernel, for example >> linux-omap3_2.6.34.bb >> >> There is an OE MUSB_MODE variable that is there to simplify setting the >> musb mode for the omap3 kernels. I did a little write up on it here >> >> http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=53&Itemid=65 >> >> Those recipe script sed lines get applied after the defconfig is copied >> to the OE working directory so it clobbers any changes to MUSB config >> vars you made in defconfig. >> >> I would let the recipe do the work for you. The changes were added >> because it is not very intuitive how to get the config file set up >> correctly for musb modes using menuconfig. >> >> >> On Mon, 2011-05-30 at 00:38 -0700, softwizz wrote: >>> Hi Scott, >>> >>> I've been trying to get USB functionality into your minimal build, and >>> imy >>> efforts are foundering on a very bitbake type of rock :-) >>> >>> When I followed youir advice to add UBIFS etc to the kernel config it >>> all >>> went smoothly, but on this occasion there is something lingering in the >>> config that is not controlled by the menuconfig. What I am finding is >>> that >>> the settings of CONFIG_USB_MUSB_HOST, CONFIG_USB_MUSB_PERIPHERAL, >>> CONFIG_USB_MUSB_OTG and CONFIG_USB_GADGET_MUSB_HDRC are conflicting, >>> causing >>> a compile error at drivers/usb/musb_core.h:103. When I correct the >>> config, >>> I can prove that the .config file as written out does contain the >>> correct >>> values, but after I run 'bitbake -c clean virtual/kernel' and 'bitbake >>> virtual/kernel', the latter crashes as described above and the .config >>> file >>> is seen to have changed back. >>> >>> What am I missing here? >>> >>> Cheers, >>> >>> Mike >>> >>> >>> >>> jumpnowdev wrote: >>> > >>> > [...] >>> > 2. A more generic way to do it is invoke the kernel menuconfig >>> utility. >>> > >>> > $ bitbake -c menuconfig virtual/kernel >>> > >>> > You should get the standard linux ncurses config editor. Make the >>> changes >>> > to >>> > enable UBIFS and then save it. The UBIFS section is under >>> > Filesystems|Miscellaneous filesystems. >>> > >>> > When you are done it saves a .config file here >>> > >>> > >>> $OETMP/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.34-r97/git/.config >>> > >>> > Copy that file to >>> > >>> > >>> $OVEROTOP/org.openembedded.dev/recipes/linux/linux-omap3-2.6.34/overo/defconfig >>> > >>> > >>> > Whichever way you chose to edit the defconfig, you now want to rebuild >>> > the kernel AND rootfs. >>> > >>> > $ bitbake -c clean virtual/kernel >>> > $ bitbake virtual/kernel >>> > [...] >>> > >>> >> >> -- >> Sent from my Linux box >> >> >> ------------------------------------------------------------------------------ >> Simplify data backup and recovery for your virtual environment with >> vRanger. >> Installation's a snap, and flexible recovery options mean your data is >> safe, >> secure and there when you need it. Data protection magic? >> Nope - It's vRanger. Get your free trial download today. >> http://p.sf.net/sfu/quest-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/Help-with-rebuilding-using-bitbake-tp26382370p31747915.html Sent from the Gumstix mailing list archive at Nabble.com. |