| 01:51.49 | *** join/#openjtag wookey_ (i=wookey@courthouse.aleph1.co.uk) |
| 02:58.14 | *** join/#openjtag ka6sox-laptop (n=tom@nslu2-linux/ka6sox) |
| 03:37.25 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 06:11.51 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
| 07:28.07 | *** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby) |
| 08:56.36 | *** join/#openjtag bullet (n=bullet@245.212.203.62.cust.bluewin.ch) |
| 10:58.38 | *** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby) |
| 11:03.08 | *** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby) |
| 12:32.02 | *** join/#openjtag vmaster_ (n=vmaster@p549B5D41.dip.t-dialin.net) |
| 13:49.46 | *** join/#openjtag prpplague (n=billybob@216.110.117.117) |
| 18:26.55 | *** join/#openjtag [g2] (n=g2@nslu2-linux/g2) |
| 18:27.16 | [g2] | anybody seen AD around ? |
| 18:36.35 | vmaster | ~seen AchiestDragon |
| 18:36.49 | purl | achiestdragon <n=david@whipy.demon.co.uk> was last seen on IRC in channel #openjtag, 44d 20h 46m 52s ago, saying: 'for debug etc , as sample ram ?'. |
| 18:37.15 | vmaster | hm, i've definitely seen him since then |
| 18:57.26 | prpplague | vmaster: you get my email? |
| 19:04.43 | vmaster | hey prpplague, yeah, got it |
| 19:05.22 | vmaster | we talked about how the output enables your boss wanted didn't make a lot of sense, did we? |
| 19:05.36 | vmaster | at least i hope we did :) |
| 19:06.40 | vmaster | the design is fine as it is, but i'll tie these output enables permanently on in the openocd |
| 19:08.04 | prpplague | vmaster: seems like we discussed it |
| 19:08.35 | prpplague | vmaster: which ones are you refering to? |
| 19:08.44 | prpplague | vmaster: i have the schematic in front of me now |
| 19:09.26 | prpplague | vmaster: ok, yea, i remember now |
| 19:09.46 | prpplague | vmaster: we have specific piece of hardware we want to use with this module |
| 19:09.50 | vmaster | ah, ok |
| 19:10.08 | prpplague | vmaster: so for standard jtag they aren't really needed |
| 19:10.36 | vmaster | yeah, exactly |
| 19:11.32 | prpplague | vmaster: i've started work on a small c app that will jtag on some code, then start it, causing the uart to receive data from the serial port |
| 19:12.30 | prpplague | vmaster: we plan to have 4 to 8 of these devices connected to a single pc for gang loading of main boards |
| 19:12.48 | vmaster | why do you want to use the serial port? |
| 19:13.26 | vmaster | i mean, jtag with the ft2232 is going to faster than 115200 |
| 19:13.30 | prpplague | vmaster: no specific reason than its already on the ft2232 and its easy to code for |
| 19:13.49 | vmaster | ah, ok |
| 19:13.59 | prpplague | vmaster: yea, the key is that we want to use some error checking |
| 19:14.48 | prpplague | vmaster: we'll use xmodem |
| 19:17.21 | prpplague | vmaster: basically we are just doing a flash of about 4mb on some NOR flash |
| 19:17.57 | prpplague | vmaster: what kind of performance do you normally get using a ft2232 to do flashing? |
| 19:20.00 | vmaster | haven't used the CFI flash driver in a while, but RAM download is ~120kb/s, and flash was about half of that, iirc |
| 19:20.34 | prpplague | thats pretty darn good |
| 19:20.44 | prpplague | vmaster: thats using openocd? |
| 19:20.55 | vmaster | yeah |
| 19:21.29 | vmaster | but not with default settings - you'll have to use "arm7_9 fast_memory_access enable" and "arm7_9 dcc_downloads enable" |
| 19:21.55 | vmaster | these are disabled by default to prevent users from outrunning devices running from a slow-clock like 32kHz |
| 19:21.56 | prpplague | vmaster: at 60kp/s that would be just a little over a minute to upload all 4mb |
| 19:22.22 | vmaster | i can write str7 flash at that speed, and the algorithms are comparable |
| 19:22.34 | vmaster | of course, the str7 is done in 4 seconds :) |
| 19:23.01 | prpplague | vmaster: any verification of the data done? |
| 19:23.18 | vmaster | nope, but you can read at >50kb/s |
| 19:23.52 | prpplague | hmm |
| 19:24.55 | vmaster | that's what people are doing |
| 19:25.22 | prpplague | vmaster: question i have is can i run 4 copies at once |
| 19:25.48 | vmaster | you can, but i suspect performance is going to suffer |
| 19:25.57 | prpplague | vmaster: hmm |
| 19:26.10 | prpplague | vmaster: well i should be able to test with openocd for the performance |
| 19:26.27 | prpplague | vmaster: are the changes you made in cvs/svn ? |
| 19:27.21 | vmaster | changes for your ft2232 layout? not yet |
| 19:27.30 | prpplague | ahh ok |
| 19:27.55 | vmaster | brb |
| 19:41.08 | prpplague | vmaster: hmm, openocd doesn't seem to be finding me device |
| 19:41.23 | vmaster | do you use your own vid/pid? |
| 19:42.23 | prpplague | no, right now we are just using the defaults for testing, they match |
| 19:42.37 | prpplague | i think i dont have it enable for ftdi2232, recompiling now |
| 19:43.11 | prpplague | ftdi2232.c:33:18: ftdi.h: No such file or directory |
| 19:43.24 | vmaster | mhh, ftdi2232.c is dead |
| 19:43.43 | vmaster | there was a lot of duplicate code in ftdi2232.c and ftd2xx.c, now everything is in ft2232.c |
| 19:44.05 | prpplague | ahh, guess i need to grab the latest copy then |
| 19:44.36 | vmaster | ah, my performance figures are for FTD2XX, not for libftdi |
| 19:44.44 | vmaster | libftdi is a lot less |
| 19:45.06 | prpplague | ahh |
| 19:45.24 | prpplague | FTD2xx is the FTDI official lib correct? |
| 19:45.28 | vmaster | yes |
| 19:46.33 | prpplague | hmm |
| 19:46.42 | prpplague | lots of errors after svn update :( |
| 19:48.05 | vmaster | mhh, the current code compiles cleanly on linux (ftd2xx and libftdi), windows (ftd2xx) and freebsd (not sure what they're using) |
| 19:48.39 | prpplague | vmaster: yea i think its just it wasn't clean |
| 19:48.53 | vmaster | ok |
| 19:56.04 | prpplague | hmm |
| 19:56.09 | prpplague | compilied properly |
| 19:56.15 | prpplague | still not seeing my device though |
| 19:56.29 | prpplague | Info: openocd.c:82 main(): Open On-Chip Debugger (2006-09-07 20:00 CEST) |
| 19:56.29 | prpplague | Info: configuration.c:50 configuration_output_handler(): Command ft2232_device_desc not found |
| 19:56.29 | prpplague | Info: configuration.c:50 configuration_output_handler(): Command ft2232_layout not found |
| 19:56.29 | prpplague | Info: configuration.c:50 configuration_output_handler(): Command ft2232_vid_pid not found |
| 19:57.31 | vmaster | do you have "interface ft2232" in the .cfg file? |
| 19:58.10 | prpplague | yep |
| 19:59.39 | vmaster | did you configure with --enable-ft2232_ftd2xx or --enable-ft2232_libftdi? |
| 20:00.41 | prpplague | vmaster: with libftdi, changing now, my bad |
| 20:01.40 | vmaster | mhh, no source |
| 20:01.48 | prpplague | lib i mean |
| 20:01.48 | vmaster | that's the problem with ftdi's own driver |
| 20:01.50 | vmaster | ok |
| 20:02.49 | prpplague | hmm |
| 20:02.57 | prpplague | i'm not seeing a place to dl that off hand |
| 20:03.03 | prpplague | thats on the ftdichip.com site? |
| 20:03.17 | vmaster | for 32-bit linux? hold on |
| 20:03.34 | vmaster | http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx0.4.10.tar.gz |
| 20:03.43 | vmaster | the driver page is here: http://www.ftdichip.com/Drivers/D2XX.htm |
| 20:03.53 | prpplague | ahh |
| 20:05.26 | prpplague | argh |
| 20:05.31 | prpplague | someone needs to kick them |
| 20:05.42 | prpplague | don't they know how to make a proper tarball |
| 20:05.50 | vmaster | nope |
| 20:09.44 | prpplague | where do you normally put the ft2xx.h file? |
| 20:11.45 | vmaster | i have it in /usr/local/include |
| 20:12.02 | vmaster | you could also put it into the OpenOCD tree in src/jtag/ |
| 20:12.03 | prpplague | yea thats where i put it as well |
| 20:13.58 | prpplague | vmaster: yea that did the trick |
| 20:15.10 | prpplague | vmaster: a little closer |
| 20:24.37 | vmaster | prpplague: this is what i'd like to include in the OpenOCD code to support your device: http://mmd.ath.cx/ft2232_m5960.diff |
| 20:25.00 | vmaster | i didn't include led handling, as that's not really usable as it is now |
| 20:31.15 | prpplague | Debug: ft2232.c:972 ft2232_init(): 'ft2232' interface using FTD2XX with 'm5960' layout |
| 20:31.15 | prpplague | Error: ft2232.c:997 ft2232_init(): unable to open ftdi device: 2 |
| 20:31.16 | prpplague | Error: ft2232.c:1012 ft2232_init(): ListDevices: 3 |
| 20:32.50 | vmaster | did you specify the right ft2232_device_desc? |
| 20:33.42 | prpplague | i guess not, i just used m5960 as the description |
| 20:35.34 | vmaster | lsusb -v as root, the iProduct |
| 20:35.50 | vmaster | don't remember what the FTDI uses by default |
| 20:39.11 | prpplague | vmaster: ahh didn't catch that |
| 20:39.34 | vmaster | ah, sorry, not iProduct |
| 20:40.22 | vmaster | iInterface - but the OpenOCD should list all the devices it found |
| 20:41.19 | prpplague | yea got it |
| 20:42.20 | prpplague | vmaster: we it recognized the device |
| 20:42.43 | prpplague | Info: ft2232.c:359 ft2232_send_and_recv(): inter: 0.1451, inter2: 0.1451 end: 5.7912 |
| 20:42.43 | prpplague | Error: ft2232.c:367 ft2232_send_and_recv(): ft2232_expect_read (2) != ft2232_buffer_size (0) (0 retries) |
| 20:43.21 | prpplague | vmaster: thanks for the help, i'm gonna have to get at it in the morning |
| 20:43.34 | vmaster | heh, funny, i inserted that timeout just for one windows user |
| 20:43.47 | vmaster | end: 5.7912 means it waited more than 5 seconds for a reply |
| 20:43.51 | prpplague | doh |
| 20:44.16 | vmaster | yeah, just let me know if you need anything |
| 20:44.30 | prpplague | thanks, i'll get to doing some serious work tomorrow |
| 20:44.35 | prpplague | vmaster: later |
| 20:44.38 | vmaster | cya |
| 23:48.22 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |