| 06:07.09 | *** join/#openjtag muasch|swiss2 (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 06:34.17 | *** join/#openjtag bullet (n=bullet@216-12.0-85.cust.bluewin.ch) |
| 07:21.41 | *** join/#openjtag Bitmaster (n=Bitmaste@c-8963e253.325-1-64736c12.cust.bredbandsbolaget.se) |
| 07:28.29 | *** join/#openjtag muasch|swiss (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 07:31.26 | *** join/#openjtag muasch|swiss3 (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 07:32.29 | *** join/#openjtag muasch|swiss4 (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 08:13.13 | *** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby) |
| 08:44.11 | *** join/#openjtag key2 (n=key2@251.9.39-62.rev.gaoland.net) |
| 08:52.37 | *** join/#openjtag muasch|swiss5 (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 08:58.13 | *** join/#openjtag twok (n=key2@251.9.39-62.rev.gaoland.net) |
| 09:44.22 | *** join/#openjtag vmaster_ (n=vmaster@p549B6538.dip.t-dialin.net) |
| 10:43.46 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 12:28.49 | *** join/#openjtag muasch|swiss5 (n=muasch@31.14.3.213.fix.bluewin.ch) |
| 13:52.47 | *** join/#openjtag key2 (n=key2@251.9.39-62.rev.gaoland.net) |
| 14:38.58 | *** join/#openjtag prpplague (n=billybob@72.22.153.65) |
| 14:39.02 | vmaster | hey prpplague |
| 14:41.32 | prpplague | vmaster: hey hey |
| 14:41.56 | prpplague | whats cookin? |
| 14:43.48 | vmaster | prpplague: you had a problem with the FT2232 not returning data on a read, and told me that you've had that problem before |
| 14:43.59 | vmaster | prpplague: have you been able to solve this? |
| 14:44.25 | prpplague | vmaster: yes, it was based on two issues |
| 14:44.49 | prpplague | vmaster: first the max current setting for the ft2232 device in eprom was set at 90mA |
| 14:45.21 | prpplague | vmaster: with the buffers and leds we were pulling around 150mA |
| 14:45.33 | prpplague | vmaster: this basically cause the usb device to shutdown due to over current |
| 14:45.52 | prpplague | vmaster: after changing the value to 200mA it worked |
| 14:46.06 | vmaster | prpplague: oh, it really uses this setting for anything other than USB enumeration? |
| 14:46.20 | vmaster | prpplague: thanks, never knew that |
| 14:46.38 | prpplague | vmaster: yea the host controller and the ft2232 seem to work together on that |
| 14:47.41 | prpplague | vmaster: the device would initialize but the first time i tried to turn on a led or enable the buffers, the device would cut off |
| 14:48.48 | vmaster | prpplague: ok, and what was the other issue? |
| 14:50.13 | prpplague | vmaster: well, sorta related, the leds i was using were pulling way too much current for the ft2232 |
| 14:50.23 | prpplague | vmaster: we replaced them with smaller leds |
| 14:50.31 | prpplague | vmaster: basically all current related |
| 14:51.27 | vmaster | prpplague: okay, thanks a lot. I've just checked the Amontec JTAGkey (I have two problem reports with it), and it specifies 100mA - could be they're running into a similar issue |
| 14:51.53 | prpplague | vmaster: yea, our device is very similiar to theirs |
| 14:52.22 | prpplague | vmaster: i'd try adjusting the current rating to around 250mA as a test |
| 14:52.42 | prpplague | vmaster: are you turning on any leds ? |
| 14:56.04 | vmaster | prpplague: the JTAGkey has one LED to indicate a USB connection, one to indicate targt power-on, and one to indicate an active-low nSRST, so at least two leds are always powered |
| 14:58.19 | prpplague | vmaster: yea, i'd guess that it might be that |
| 14:59.08 | prpplague | vmaster: average led current is about 20mA |
| 14:59.19 | prpplague | vmaster: so you are already down to just 60mA available to you |
| 15:05.33 | vmaster | prpplague: yeah, the FT2232L uses 30mA itself, leaving only 30mA for the buffers |
| 17:31.58 | *** join/#openjtag muasch|swiss5 (n=muasch@31.14.3.213.fix.bluewin.ch) |