Hi, I am willing to try to build my own uImage to resolve this, but I'm having trouble figuring out what's needed. I looked through these repos: roach2_nfs_uboot: seems to just be binaries uboot_devel: This is the bootloader so should be a step before the uImage is used linux: This would seem logical, but I don't see any USB related changes in the last several months...
Where is the code needed to produce a uImage file? Thanks, Glenn On Fri, Dec 7, 2012 at 1:10 PM, G Jones <[email protected]> wrote: > To answer my own question, it appears the uImage-nousb is also setup for > tcpborphserver3. > > Is there a uImage that has USB disabled and works with tcpborphserver2? We > really need this... > > Thanks, > Glenn > > > On Fri, Dec 7, 2012 at 11:45 AM, G Jones <[email protected]> wrote: > >> Hi, >> In light of the possible issues we're having with tcpborphserver3, we're >> trying to revert to tcpborphserver2. To do so, we tried the uImage-r2borph2 >> but it is freezing at boot at >> >> ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller >> ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1 >> ppc-soc-ohci ppc-soc-ohci.0: irq 21, io mem 0xe0000400 >> >> which I assume is the infamous USB Host problem. I notice on the >> roach2_nfs_uboot github repo there is a uImage-nousb. Is this a >> tcpborphserver2 compatible image? >> >> Thanks, >> Glenn >> > >
