Hello. Today I tried testing with the unmodified images.
(just followed the build instruction on README from https://github.com/Freescale/fsl-community-bsp-platform), and the result was the below. lsusb on imx61sabreauto board: 2.0 (jethro) - OK 2.1 (krogoth) - NG 2.2 (morty) - NG 2.3 (pyro) - NG I am curious since it is OK (lsusb correctly list the USB devices) with jethro, but NG on krogoth and after. I may look into the delta but still not sure where to look into. Any comment/suggestion is welcomed. ________________________________ From: Takashi Matsuzawa Sent: Friday, June 30, 2017 9:03 PM To: meta-freescale@yoctoproject.org Subject: Re: unable to initialize libusb: -99 Hello. I am still looking into this, since without USB working the board is les use. And, I noticed there is an post regarding imx6qdl-sabreauto.dtsi issue regarding pca953x control. https://community.nxp.com/thread/435299 In fact before in the boot log, I see the followings before "Can't register ci_hdrc platform device, err=-517" errors. I an hardly imagine none of the sabreauto board users (on linux-fslc) can use USB. And also I could use USB on NXP release BSP, so board hardware is not broken. If there is a fix patch or workaround known, or if it is my configuration problem, I would like to learn. > pca953x 2-0030: failed reading register > pca953x: probe of 2-0030 failed with error -11 > pca953x 2-0032: failed reading register > pca953x: probe of 2-0032 failed with error -11 > pca953x 2-0034: failed reading register > pca953x: probe of 2-0034 failed with error -11 > CPU PMU: Failed to parse /soc/pmu/interrupt-affinity[0] > Unknown username "adit" in message bus configuration file > mag3110 2-000e: read chip ID 0xfffffff5 is not equal to 0xc4! > mag3110: probe of 2-000e failed with error -22 > mma8451 2-001c: read chip ID 0x1 is not equal to 0x1a or 0x2a! > mma8451: probe of 2-001c failed with error -22 > imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 > imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 > imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 > imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 Any sugestion is highly appreciated. ________________________________ From: Takashi Matsuzawa Sent: Thursday, June 29, 2017 3:09 PM To: meta-freescale@yoctoproject.org Subject: unable to initialize libusb: -99 Hello. I am trying an image based on morty (2.2) fsl communty BSP on sabre-ai board, and see the lsusb -99 error. Any suggestion/comment on which part of the configuration I should be look into! (I already googl'ed and found some old questions/answers on libusb -99 errors, but I could not figure out if they are just the same as my case or not.) My issue is that SB is not working (lsusb gives me error), as below. I checked and make sure CONFIG_USB_EHCI_HCD/CONFIG_USB_XHCI_HCD are there. >root@imx6qsabreauto:~# export LIBUSB_DEBUG=9 >root@imx6qsabreauto:~# lsusb -v >libusb: debug [libusb_init] created default context >libusb: debug [libusb_init] libusb v1.0.20.11004 >libusb: error [op_init] could not find usbfs >unable to initialize libusb: -99 I am also seeing errors like below in journalctl log, but I am not sure what they mean. >Jun 28 12:02:02 imx6qsabreauto kernel[313]: hdm_usb: hdm_usb_init() >Jun 28 12:02:02 imx6qsabreauto kernel[313]: usbcore: registered new interface >driver hdm_usb >Jun 28 12:02:02 imx6qsabreauto kernel[313]: usbcore: registered new interface >driver k2l-mocca >Jun 28 12:02:02 imx6qsabreauto kernel[313]: imx_usb 2184000.usb: Can't >register ci_hdrc platform device, err=-517 >Jun 28 12:02:02 imx6qsabreauto kernel[313]: imx_usb 2184200.usb: Can't >register ci_hdrc platform device, err=-517 >...
-- _______________________________________________ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
