[U-Boot] Does usbtty work on omap3?
Hi All
I have usbtty partially working on omap3 (overo board). Unfortunately the byte stream gets corrupted. It looks like some sort of buffer / fifo corruption or similar with old bytes being sent and some bytes being dropped.
Does anyone have this actually working reliably?
I tried to have a hunt around the code, but the musb user guides are unfortunately under NDA.
-- Charles
On Tue, May 10, 2011 at 7:23 PM, Charles Manning manningc2@actrix.gen.nzwrote:
Hi All
I have usbtty partially working on omap3 (overo board). Unfortunately the byte stream gets corrupted. It looks like some sort of buffer / fifo corruption or similar with old bytes being sent and some bytes being dropped.
Does anyone have this actually working reliably?
It is also not reliable for me. There was an alternative implementation, I believe originating from a combination of TI and RidgeRun, for which patches were made public, but the current upstream has data corruption in it. I'm looking into getting the issue staffed by TI, but this is a nice-to-have feature currently so it is at a low priority.
I tried to have a hunt around the code, but the musb user guides are unfortunately under NDA.
-- Charles _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
On Wednesday 11 May 2011 11:47:14 Jason Kridner wrote:
On Tue, May 10, 2011 at 7:23 PM, Charles Manning
manningc2@actrix.gen.nzwrote:
Hi All
I have usbtty partially working on omap3 (overo board). Unfortunately the byte stream gets corrupted. It looks like some sort of buffer / fifo corruption or similar with old bytes being sent and some bytes being dropped.
Does anyone have this actually working reliably?
It is also not reliable for me. There was an alternative implementation, I believe originating from a combination of TI and RidgeRun, for which patches were made public, but the current upstream has data corruption in it.
I hunted around for a bit but could not find those patches. Can you point me at it?
What is somewhat annoying is that the old code (~2008) actually worked well, but that was replaced with broken code from Wind River :-(.
I'm looking into getting the issue staffed by TI, but this is a nice-to-have feature currently so it is at a low priority.
I would argue that it is more than just nice to have. USB is an excellent way to load up data in a manufacturing jig etc and beats any other way to load up software.
Thanks
-- Charles
participants (2)
-
Charles Manning -
Jason Kridner