maybe the Cygwin ioperm package wasn't installed when you did ./configure? Furthermore, the output looks as if readline isn't installed. I suggest to install at least ioperm, re-configure, and if that solves the problem, please update this tracker item
Kolja
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, "UrJTAG.txt" _is_ included in the bz2 (in doc/ subdirectory). What do you mean by "it doesn't do any thing"? After you type the "cable..." command, most probably the next required step is to type "detect". What's the output of UrJTAG after "detect"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah - well, the UrJTAG.txt is online at http://urjtag.org/book/index.html - however, it's probably not easy to find - it's not obvious they're the same text (and sometimes the UrJTAG.txt in SVN repository is more up to date).
If "detect" returns without any output, that maybe indicates a cable/connection problem. Is it a ready-made cable or "flying leads" (homebrew) type? Do you have an oscilloscope for debugging?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made this cable myself. But made it ina good way and tested by the multimeter. I don't have oscilloscpe.
Is there any way to test the cable and the connections. Is there any other way to test the signals between the PC and the device.
Thanks for the help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, unfortunately, there is almost no other way. You could add some printf()s in the cable driver to display the actual value read from TDO. It should at least change between 0 and 1 and NOT remain stable during "detect". Are you sure you selected the right driver/pin mapping for your (Intel?) cable?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know where to add the printf statement. Could you please guide me where to add the printf statement or add for me so that I can rebuild the urjtag.
Thanks for taking the interest.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=478715
Originator: NO
Hi Ajit,
maybe the Cygwin ioperm package wasn't installed when you did ./configure? Furthermore, the output looks as if readline isn't installed. I suggest to install at least ioperm, re-configure, and if that solves the problem, please update this tracker item
Kolja
Logged In: YES
user_id=1981123
Originator: YES
Thx for the prompt response.
I installed ioperm and now the error is:
Initializing parallel port at 0x378
Error: Cable Initialization failed
Any more tips:
Thx
Logged In: YES
user_id=1981123
Originator: YES
I am sorry I didn't read the urjtag.txt file. I think this file should be with the bz2 file.
I then installed ioperm -i.
Now I don't get any error. But it doesn't do any thing either.
If you have time I was following the http://www.seattlewireless.net/LinksysWrv54g website for jtag. But this is not working for me.
You can close this case now.
Any way thx
Logged In: YES
user_id=478715
Originator: NO
Hi, "UrJTAG.txt" _is_ included in the bz2 (in doc/ subdirectory). What do you mean by "it doesn't do any thing"? After you type the "cable..." command, most probably the next required step is to type "detect". What's the output of UrJTAG after "detect"?
Logged In: YES
user_id=1981123
Originator: YES
Hi,
I know it is included in the Doc subdirectory. But my suggestion it to also include seperately so that people can read it.
Anyway for my problem. Detect doesn't do anything.
Thx.
Logged In: YES
user_id=478715
Originator: NO
Ah - well, the UrJTAG.txt is online at http://urjtag.org/book/index.html - however, it's probably not easy to find - it's not obvious they're the same text (and sometimes the UrJTAG.txt in SVN repository is more up to date).
If "detect" returns without any output, that maybe indicates a cable/connection problem. Is it a ready-made cable or "flying leads" (homebrew) type? Do you have an oscilloscope for debugging?
Logged In: YES
user_id=1981123
Originator: YES
I made this cable myself. But made it ina good way and tested by the multimeter. I don't have oscilloscpe.
Is there any way to test the cable and the connections. Is there any other way to test the signals between the PC and the device.
Thanks for the help.
Logged In: YES
user_id=478715
Originator: NO
Hi, unfortunately, there is almost no other way. You could add some printf()s in the cable driver to display the actual value read from TDO. It should at least change between 0 and 1 and NOT remain stable during "detect". Are you sure you selected the right driver/pin mapping for your (Intel?) cable?
Logged In: YES
user_id=1981123
Originator: YES
I don't know where to add the printf statement. Could you please guide me where to add the printf statement or add for me so that I can rebuild the urjtag.
Thanks for taking the interest.
Logged In: YES
user_id=478715
Originator: NO
Hi,
let's move our conversation over to the new User Forum. My actual reply is there:
http://sourceforge.net/forum/message.php?msg_id=4735999
Regards,
Kolja