On Mon, Aug 31, 2015 at 10:11:20AM +0200, Vincent Stehlé wrote: > On 08/28/2015 10:29 AM, Peter Chen wrote: > .. > > Would you supply below: > > 1. The u-boot.bin which you use to reproduce it > > Hi Peter, > > Thank you for looking into this issue. > > I attached u-boot.imx to the ticket for you [1]. > > Due to the environment boot paths being tuned to my setup I can only > recommend that you start from sources instead. > > > 2. The application used to load u-boot.bin from pc, and related > > script > > The binaries are now attached to the ticket for your convenience [3]. > > I fear they will incur additional issues of setting LD_LIBRARY_PATH, due > to absolute paths in the binaries. I therefore recommend that you start > from the sources mentioned in the ticket, in > comment #5 [2]. > > > 3. Instruction how to use the tool to reproduce the failure > > This is what I do: > > 1. Edit the mx6_usb_work.conf config file. > 2. Connect the boart debug UART and USB OTG to the PC USB. > 3. Reset the board. > 4. Run: > > $ sudo ./output/host/usr/bin/imx_usb > --configdir=./output/host/etc/imx-loader.d/ > > (You will need to adapt the paths.) > > .. > > Would you please enable chipidea debug at kernel configuration, and > > add 'debug' at your u-boot command line to run it again, I would > > like to see the log if possible? > > Sure. I updated the log in the ticket [4]. > > Sadly, it seems to make the issue only worse, as the boot is now stuck > even earlier. > > Best regards, > > V. > > [1] https://bugzilla.kernel.org/attachment.cgi?id=186281 > [2] https://bugzilla.kernel.org/show_bug.cgi?id=103461#c5 > [3] https://bugzilla.kernel.org/attachment.cgi?id=186291 > [4] https://bugzilla.kernel.org/attachment.cgi?id=186271 > > Hi Vincent, sorry for late, I can't to reproduce it with your u-boot and v4.2-rc6, and track the activities at bugzilla, let's close it here, and go on debugging this problem at bugzilla. -- Best Regards, Peter Chen -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
