On Friday 30 October 2009, Dimitar Dimitrov wrote:
> Working configuration is high-speed USB. I have only two
> patches in my repository and they were attached to my previous
> message. One is trivial interface configs.
Already merged into mainline...
> The other one
> increases (at least I thi
On Friday 30 October 2009, David Brownell wrote:
> On Thursday 29 October 2009, Dimitar Dimitrov wrote:
> > I fixed the issue by disabling dcc memory uploads.
>
> Bizarre. Disabling those let the initial enumeration
> work at full speed?? Or was that caused by some other
> patches in your reposi
On Thursday 29 October 2009, Dimitar Dimitrov wrote:
> I fixed the issue by disabling dcc memory uploads.
Bizarre. Disabling those let the initial enumeration
work at full speed?? Or was that caused by some other
patches in your repository?
Is this still with adaptive clocking enabled?
Where d
Uhh... I forgot to check the log. It does appear like a ft2232 problem...
The symptoms are very much like that other bug though: dcc failing...
Error: 627 36721 ft2232.c:370 ft2232_write(): ftdi_write_data: usb
bulk write failed
Error: 628 36721 ft2232.c:672 ft2232_send_and_recv(): couldn't writ
Please check if you are in fact seeing this problem:
https://lists.berlios.de/pipermail/openocd-development/2009-October/011760.html
Disabling dcc, just means that you have identified that the
bug is in the dcc memory write(s). dcc memory writes are
*much* faster than the alternatives, so we hav
I fixed the issue by disabling dcc memory uploads. Otherwise my setup hasn't
changed:
1. Openocd fetched from latest GIT
2. libftdi-0.16 from the latest release tarball
3. FT2232 timeout/retry-count patch applied (attached).
4. ARM-USB-TINY-H interface config (attached)
After starting openocd I
On Wednesday 28 October 2009, David Brownell wrote:
> > Warn : 262 1093 core.c:986 jtag_examine_chain_end(): Unexpected idcode
> > after end of chain: 481 0x807f8000
> > Warn : 263 1093 core.c:986 jtag_examine_chain_end(): Unexpected idcode
> > after end of chain: 513 0x80003018
>
> And another
If it fails for you with OHCI, I'd expect you have a fairly clean
failure mode and that using a fullspeed hub won't change anything.
Now, one thing that's interesting is that you seem to have gotten
a *different* failure mode at full speed. Suggesting there are
two different bugs associated with
I did "rmmod ehci_hcd" and the OHCI driver took over. In full speed USB mode,
however, OpenOCD could not validate the JTAG chain, let alone reach "reset
init". A complete debug log is attached, containing verbose USB and JTAG
communications messages.
I'll try to test it on another computer and
On Tuesday 27 October 2009, Dimitar Dimitrov wrote:
> I'm trying to debug SAM9-L9260 board /AT91SAM9260 chip/ using
> the latest GIT openocd checkout, FT2232H-based dongle and
> libftdi-0.16. I'm getting the following error when issuing "reset init":
>
> Error: 228 7449 ft2232.c:419 ft2232_read(
Hi,
I'm trying to debug SAM9-L9260 board /AT91SAM9260 chip/ using the latest GIT
openocd checkout, FT2232H-based dongle and libftdi-0.16. I'm getting the
following error when issuing "reset init":
Error: 228 7449 ft2232.c:419 ft2232_read(): couldn't read the requested number
of bytes from FT22
11 matches
Mail list logo
