Hi,
I am trying to acheive a similar goal here. I want to change my USB0 to
host and USB1 to device. I tried to make this change in
arch/arm/boot/dts/am335x-bone-
common.dtsi file but the file structure has changed significantly. It is
now having :
" &usb_otg_hs {
interface_type = <1>;
power = <250>;
status = "okay";
}; " instead of what is posted in your querry.
Also the am33xx.dtsi file is changed in the usb part as:
" usb_otg_hs: usb@47400000 {
compatible = "ti,musb-am33xx";
reg = <0x47400000 0x1000 /* usbss */
0x47401000 0x800 /* musb instance 0
*/
0x47401800 0x800>; /* musb instance 1
*/
interrupts = <17 /* usbss */
18 /* musb instance 0
*/
19>; /* musb instance 1
*/
multipoint = <1>;
num-eps = <16>;
ram-bits = <12>;
port0-mode = <3>;
port1-mode = <1>;
power = <250>;
ti,hwmods = "usb_otg_hs";
status = "disabled";
}; "
Do you have any idea on how to make the USB0 to work as host and USB1 to
work as device with the latest files?
Also do we have to make any change using the 'menuconfig' for achieving
this or the default configuration used for beaglebone is sufficient?
On Thursday, 17 April 2014 15:31:27 UTC+5:30, marc...@gmail.com wrote:
>
> Hello
> I have finally managed to get my hands on an BBB and started to try and
> get my system up and running the way I need by building a kernel (3.14.1).
>
> I am attempting to use the USB client port (USB0) in host mode and think I
> have done all the things necessary to get this working:
>
> Kernel config has EHCI enabled and set to host only
> Hardware mod on the board to short pins 4&5 of micro socket to force
> USB-ID low to indicate host mode.
> Changed the arch/arm/boot/dts/am335x-bone-common.dtsi file to put it into
> host mode
> u...@47401000 <javascript:> {
> status = "okay";
> dr_mode = "host";
> };
> u...@47401800 <javascript:> {
> status = "okay";
> dr_mode = "host";
> };
>
> No matter what I plug in nothing gets identified ???
>
> Plugging into the USB1 host port is fine so the kernel is configured
> correctly.
>
>
> Boot log shows ports being identified:
> [ 2.057294] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
> [ 2.063996] musb-hdrc musb-hdrc.0.auto: new USB bus registered,
> assigned bus number 1
> [ 2.072673] usb usb1: New USB device found, idVendor=1d6b,
> idProduct=0002
> [ 2.079868] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [ 2.087467] usb usb1: Product: MUSB HDRC host driver
> [ 2.092722] usb usb1: Manufacturer: Linux 3.14.1 musb-hcd
> [ 2.098402] usb usb1: SerialNumber: musb-hdrc.0.auto
> [ 2.104856] hub 1-0:1.0: USB hub found
> [ 2.108880] hub 1-0:1.0: 1 port detected
> [ 2.117574] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
> [ 2.124275] musb-hdrc musb-hdrc.1.auto: new USB bus registered,
> assigned bus number 2
> [ 2.133045] usb usb2: New USB device found, idVendor=1d6b,
> idProduct=0002
> [ 2.140253] usb usb2: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [ 2.147851] usb usb2: Product: MUSB HDRC host driver
> [ 2.153105] usb usb2: Manufacturer: Linux 3.14.1 musb-hcd
> [ 2.158786] usb usb2: SerialNumber: musb-hdrc.1.auto
> [ 2.165268] hub 2-0:1.0: USB hub found
> [ 2.169312] hub 2-0:1.0: 1 port detected
>
> Any ideas ???
>
> Thanks
> marc
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
