Forums

Even if the unbonded PHY is configured improperly, I don't think it should affect the other USB controller.

Could you please provide more details?

- kernel boot log including msg after connected am335x to host PC;
- host PC dmesg after connected am335x (assuming you use Linux Host PC);
- console log of command 'cat /proc/driver/musb_hdrc.0';
- .config

We are running on our own HW design but most of the SW is adapted from the BeagleBone configuration.

The USB entries in the board file are:

/* pinmux for usb0 drvvbus */
static struct pinmux_config usb0_pin_mux[] = {
    {"usb0_drvvbus.usb0_drvvbus",    OMAP_MUX_MODE0 | AM33XX_PIN_OUTPUT},
    {NULL, 0},
};

static struct omap_musb_board_data musb_board_data = {
    .interface_type    = MUSB_INTERFACE_ULPI,
    /*
     * mode[0:3] = USB0PORT's mode
     * mode[4:7] = USB1PORT's mode
     * AM335X beta EVM has USB0 in OTG mode and USB1 in host mode.
     */
    .mode           = (MUSB_HOST << 4) | MUSB_PERIPHERAL,
    .power        = 500,
    .instances    = 0,
};

We are connecting directly to the am335x, so we don't have the FTDI chip, like the BeagleBone.

I have attached the device kernel boot log, the kernel config file and the cat commands from before and after connecting the device to the host PC via USB cable.

When connecting the device and PC, nothing happens in the host PC dmesg.

br.

Nikolaj

7120.device_kernel_boot_log.txt

7674.device_musb_hdrc.o_before_cable_attach.txt

5353.device_musb_hdrc.o_after_cable_attach.txt

Looks like the .config file didn't get attached.

Here it is, renamed so it could be attached:

3162.runmaster_small_defconfig.txt

br.

Nikolaj

Nikolaj,

The log tells the MUSB controller detected VBUS, and SESSION is started, but it is not enumerated by the Host PC. We have some questions regarding your h/w design, and we will send you an email shortly.

ok.

Thanks

Nikolaj