lekernel, before I erasing pod's eeprom info and change VID/PID to a correct one, should I let window Device Manager to know it? i found there're two device found shown "USB<-> Serial Cable" after I changed VID/PID. and surely it can be detected "ID 20b7:0731" by typing 'lsusb' in linux. so i think that pod was changed successfully though. i just curious why my windows Device Manager didn't install ftdibus.inf & ftdiport.inf by I manually point the inf path. switch to Linux asap :-) if you can set the vid/pid with the Windows tool, that's all you need, I would do the whole rest under Linux maybe one day we can even set the vid/pid in Linux, that would be better... yeah..i also think that way... now trying to follow the instructions. :) wolfspraul, http://www.milkymist.org/wiki/index.php?title=Working_ftdi_eeprom do i need to do "Build the libftdi-1.0 and new ftdi_eeprom"? he :-) I didn't think you should try right away... i quite don't know about them. Does it the same thing I did in windows? for now, use the Windows tool to set the vid/pid what's the goal of this page? http://www.milkymist.org/wiki/index.php?title=Build_the_libftdi-1.0_and_new_ftdi_eeprom when you plug it into Linux, /dev/ttyUSB0 should be jtag, and /dev/ttyUSB1 should be serial for serial, you can try: gtkterm -p /dev/ttyUSB1 -s 115200 then you can try commands such as 'help' or 'ls' that should work, if it's plugged into a m1 no, i think it should show /dev/ttyUSB0 and /dev/ttyUSB1 established if I typing 'dmesg' hmm...seems I have to go for that wiki page. :) * Disconnected (Connection timed out). * adamw_ sets mode +i adamw_ * Found your IP: [182.235.72.11] * Now talking on #milkymist * Topic for #milkymist is: Milkymist One, Milkymist SoC & Flickernoise development channel :: Open hardware interactive VJ station :: Early developer kits for sale, see milkymist.org :: Upgrade: http://lekernel.net/blog/?p=1339 * Topic for #milkymist set by lekernel!~lekernel@g225039138.adsl.alicedsl.de at Sat Dec 25 21:03:39 2010 * reeeep (~rep@AMontpellier-257-1-103-181.w86-219.abo.wanadoo.fr) has joined #milkymist * reeeep has quit (Client Quit) * iopluy (~iopluy@rembrandt.weichenberger.at) has joined #milkymist setting the vid/pid works in both windows (using the tool from ftdi) and linux (using something based on http://www.milkymist.org/wiki/index.php?title=Working_ftdi_eeprom which is messy atm) if you don't understand the mess in the wiki just use the windows tool and then use linux to test the cable if you use a recent kernel it should only display a /dev/ttyUSB0 this is the serial port, use gtkterm or other to test then build urjtag to test the jtag part and use "cable milkymist" then "detect" it should find the spartan6 for urjtag you must use the code from the latest official git repository afaik it's not in releases yet it seems his Linux is not creating /dev/ttyUSB devices use the latest kernel then it detects ftdi stuff based on vid/pid those for the milkymist cable are merged in linus tree, but only in very recent releases or you can also pass a parameter to the ftdi module with the vid/pid lekernel: can you run lsusb -v -d 20b7:0731 and paste the results somewhere? it's 0713 re wolfspraul: i'll try to send the 3 cases later today if i manage to get out of the house he sure did you read about this reichl-emv.de thing? yes. lets hope he answers soon * iopluy has quit (Quit: iopluy) * gbraad-c1ina is now known as gbraad-china * Now talking on #milkymist * Topic for #milkymist is: Milkymist One, Milkymist SoC & Flickernoise development channel :: Open hardware interactive VJ station :: Early developer kits for sale, see milkymist.org :: Upgrade: http://lekernel.net/blog/?p=1339 * Topic for #milkymist set by lekernel!~lekernel@g225039138.adsl.alicedsl.de at Sat Dec 25 21:03:39 2010 * bassel (~bassel@178.171.133.151) has joined #milkymist the xilinx sotware doesn't work at all with this cable that's what I suspected lekernel, wow..bad news adam's notebook only has 1.1 external usb - shouldn't that work too? I think there is a big in his kernel that will lead to not creating the ttyUSB devices bug the module to load is ftdi_sio - not usbserial if the cable doesn't create any /dev/ttyUSB* devices, it might just be because his ftdi_sio doesn't have my patch applied yet to make it recognize the vid/pid there's a way to add extra vid/pid to ftdi_sio without recompiling it's in the ftdi_sio documentation mom maybe not in the doc, but in the source at least ;) module_param(vendor, ushort, 0); MODULE_PARM_DESC(vendor, "User specified vendor ID (default=" __MODULE_STRING(FTDI_VID)")"); module_param(product, ushort, 0); MODULE_PARM_DESC(product, "User specified product ID"); try that rmmod ftdi_sio modprobe ftdi_sio vendor=0x... product=0x... sorry, i need step by step commands. :) * bassel has quit (Ping timeout: 272 seconds) and yes the cable should still work with a 1.1 USB hub, but you should test it in high speed as well adamw_: did you try those 2 commands? 1. "rmmod ftdi_sio" 2. "modprobe ftdi_sio vendor=0x20b7 product=0x0713" under ? right yes moment then check with 'dmesg' good, now it shows /dev/ttyUSB0' and ttyUSB1 after dmesg good :-) [28307.090378] usb 5-2: Detected FT2232H [28307.090386] usb 5-2: Number of endpoints 2 [28307.090392] usb 5-2: Endpoint 1 MaxPacketSize 64 [28307.090398] usb 5-2: Endpoint 2 MaxPacketSize 64 [28307.090404] usb 5-2: Setting MaxPacketSize 64 [28307.091965] usb 5-2: FTDI USB Serial Device converter now attached to ttyUSB0 [28307.092435] ftdi_sio 5-2:1.1: FTDI USB Serial Device converter detected [28307.093678] usb 5-2: Detected FT2232H [28307.093687] usb 5-2: Number of endpoints 2 [28307.093693] usb 5-2: Endpoint 1 MaxPacketSize 64 [28307.093699] usb 5-2: Endpoint 2 MaxPacketSize 64 [28307.093704] usb 5-2: Setting MaxPacketSize 64 [28307.095714] usb 5-2: FTDI USB Serial Device converter now attached to ttyUSB1 [28307.095801] usbcore: registered new interface driver ftdi_sio [28307.095807] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver adamw_: ok, this is normal the serial port should be on /dev/ttyUSB1 and ttyUSB0 is the jtag port which is wrongly recongnized as serial because you don't have the kernel patch but this shouldn't be a problem lekernel, thanks a lot ok...i am now trying to test serialboot on testing first..:) if you use urjtag (from git) you should be able to run "cable milkymist" and "detect" it should show the spartan6 device great! thanks lekernel ! :-) lekernel, i'ven't git clone FJMEM...I'll try this you don't need fjmem for now don't bother with it hmm? urjtag get a git snapshot of the latest urjtag tree http://www.milkymist.org/wiki/index.php?title=Flashing_the_Milkymist_One#Using_UrJTAG and use that only for now yes, we don't flash now we test the jtag cable and for this purpose fjmem isn't needed just run the batch file...umm..ok no no no? 1. compile the latest urjtag from git 2. run it (type jtag as root) 3. cable milkymist 4. detect if it show a spartan 6 device, the jtag cable works. no need to test any further hmm...the way to capture Spartan-6 ID? right? yes ok...thanks let me use flterm first. :) pod's serial function now on m1 is ok. lekernel, I must to every time to use those two commands 'rmmod ftdi_sio' and the other when I turn off & tune on my linux latop, right? yeah or upgrade your kernel my patch was merged... not sure in what version exactly though oah..man :) ok or you can add an entry in /etc/modprobe.d echo 'options ftdi_sio vendor=0x20b7 product=0x0713' > /etc/modprobe.d/mm_jtag.conf while I typed './autogen.sh' to install, i got: Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf line 189. Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf line 189. autoreconf: Entering directory `.' what does this meaning? my system missed "libtoolize"? you need to install libtool ok how about "autopoint"? Can't exec "autopoint": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 344. which distro are you using? http://urjtag.git.sourceforge.net/git/gitweb.cgi?p=urjtag/urjtag;a=commit;h=57ac6a345b221ef89d5e39c43cb9b232cc6d3b5b autoreconf: Entering directory `.' autoreconf: running: autopoint --force Can't exec "autopoint": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 344. he's using Ubuntu and discovering the niceties of GNU/Autocrap :) apt-get install gettext (it seems autopoint is in gettext) adamw_: try: apt-get install gettext good, compiled done make[3]: Entering directory `/home/adam/下載/urjtag-57ac6a3/urjtag/src/svf' YACC svf_bison.c ../../tools/ylwrap: line 109: yacc: command not found make[3]: *** [svf_bison.c] Error 1 make[3]: Leaving directory `/home/adam/下載/urjtag-57ac6a3/urjtag/src/svf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/adam/下載/urjtag-57ac6a3/urjtag/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/adam/下載/urjtag-57ac6a3/urjtag' make: *** [all] Error 2 is it ok? or must wrong?! now yacc is missing, one sec try this: apt-get install bison done after 'make' after 'make install', see my log http://pastebin.com/PhCAU0FD is it completely installed? adamw_: seems ok mwalle, ha...thanks you should now have a 'jtag' command which should bring you to urjtags cli root@adam-laptop:/home/adam/下載/urjtag-57ac6a3/urjtag# jtag jtag: error while loading shared libraries: liburjtag.so.0: cannot open shared object file: No such file or directory LD_LIBRARY_PATH=/usr/local/lib jtag maybe just guessing here jtag> cable milkymist Connected to libftdi driver. jtag> detect IR length: 6 Chain length: 1 Device Id: 00100100000000001000000010010011 (0x24008093) Manufacturer: Xilinx (0x093) Part(0): xc6slx45 (0x4008) Stepping: 2 Filename: /usr/local/share/urjtag/xilinx/xc6slx45/xc6slx45 jtag> we MAKE IT! I LOVE YOU all guys here! :) much thanks to all of YOU! well...i have to record all..otherwise I'll quickly forget all. wow...so now 99 pcs of jtag/serial are waiting for me to TOUCH them. thanks you again.