Other Parts Discussed in Thread: AM3352
Tool/software: Linux
Hi,
Using SDK version 4.02.00.09. We have a custom board with AM3358 Soc and USB hub chip USB2512 connected to USB0 port but it doesn't seem to be detected at all. In fact, I don't believe the drivers, particularly the musb_hdrc, are not loading and configuring properly since there are no port related entries entries under /sys/bus/platform/musb_hdrc to be able to read status as per similar issue discussed in e2e.ti.com/.../333490:
/ # ls /sys/bus/platform/drivers
alarmtimer omap-aes pbias-regulator
armv7-pmu omap-control-phy pinctrl-single
cadence-qspi omap-des poweroff-gpio
cppi41-dma-engine omap-dma-engine pwmss
cpsw omap-elm pwrseq_emmc
cpsw-phy-sel omap-gpmc pwrseq_simple
cpufreq-dt omap-mailbox reg-dummy
davinci_mdio omap-sham reg-fixed-voltage
ecap omap2-nand restart-gpio
edma omap2_mcspi serial8250
edma3-tptc omap8250 simple-framebuffer
ehrpwm omap_dma_system sram
fsl-edma omap_gpio syscon
gpio-clk omap_hsmmc syscon-reboot
gpio-fan omap_hwspinlock ti-cpufreq
gpio-regulator omap_i2c ti-dma-crossbar
gpio-syscon omap_rng ti-iodelay
iio_hwmon omap_timer ti-qspi
mmci-omap omap_uart ti-soc-thermal
musb-hdrc palmas-clk ti-syscon-reset
of_fixed_clk palmas-gpio ti_abb
of_fixed_factor_clk palmas-pinctrl ti_opp_supply
of_serial palmas-pmic tps65217-pmic
/ # ls /sys/bus/platform/drivers/musb-hdrc/
bind module uevent unbind
despite the fact that the drivers loaded properly using the modprobe musb_hdrc command (note that log level 7 is set):
[ 746.006591] bus: 'usb': registered
[ 746.006655] bus: 'usb': add driver usbfs
[ 746.007037] usbcore: registered new interface driver usbfs
[ 746.039879] bus: 'usb': add driver hub
[ 746.040410] usbcore: registered new interface driver hub
[ 746.049891] bus: 'usb': add driver usb
[ 746.050340] usbcore: registered new device driver usb
[ 746.079805] device class 'udc': registering
[ 746.120171] bus: 'platform': add driver musb-hdrc
For this test, I am using the original tisdk_am335x-evm_defconfig to build the kernel and modules and with the following entries in device tree related to usb:
&usb {
status = "okay";
};
&usb_ctrl_mod {
status = "okay";
};
&usb0_phy {
status = "okay";
};
&usb1_phy {
status = "okay";
};
&usb0 {
status = "okay";
dr_mode = "host";
};
&usb1 {
status = "okay";
dr_mode = "host";
};
The USB2512 chip that is connected to USB0 is properly powered and configured over I2C. Yet when programmed and the usb drivers loaded, it is not detected and enumerated at all.