Hi Peter,
You're right on all points. But....
In my country I can't buy a jtag adapter (and I don't have money to buy
in other country) I think is cheaper do a jtag wiggler2 port to usb and
I have all parts to do this.
I'm using a Osciloscope to meter electronic signals ... and look good,
but I'm not a specialist in the jtag signals.
About the file and the driver, I answer to the list about wath is the
right way to add new drivers and I don't have any answer. I just using
the modified version of parport.c to test, nothing else.
If I can make this work, the next step is make a driver and send it to
the community. (maybe can help someone)
Thank's for your answer and time.
Sergio
El 12/04/2011 10:00 a.m., Peter Stuge escribió:
Sergio wrote:
The USB adapter just make the parallel signals from USB, I do this
with a USB - RS232 converter connected to microcontroller.
Strongly recommend buy a known working JTAG adapter. There are some
really affordable ones that work with OpenOCD.
All signals are generated good.
Did you also look at signalling beyond the electrical level? Is your
JTAG adapter actually generating correct JTAG signalling? Are timings
accurate, and sequences correct? (Probably not.)
But I don't know the source of my problems. When connect the target
board and the usb adapter, run openocd (stable version 0.4)
Please start by using git source.
The parallelport was modify to work over USB connection.
This is obviously not the best approach. If you must, and if you are
confident that the JTAG adapter works, then create a new driver for
it in OpenOCD.
In the attached file are the modified version of the parport.c.
This is very unhelpful, for a couple of reasons. It is unlikely that
any single person knows exactly how the parport.c driver worked and
how it was implemented, especially in the 0.4.0 release which is old.
It is guaranteed that noone will comment or even bother to look at
the file you attached.
A better approach would be to email a diff between the original file
and your modified version, which would show only what you have
changed, and increase the chance that someone will take time to read
the code, because when only changes are shown there is a chance to
understand if and how your changes affect the driver.
The very best approach is that you add a driver for your adapter, and
make sure to add it into the current git source for the project. If
you create a nice and clean patch then it will be included into
OpenOCD immediately.
Some one can helpme?
You have too many unknowns.
Get a known working JTAG adapter if you want to isolate how OpenOCD
works with your target board.
Get a known working target board if you want to isolate how your JTAG
adapter works.
In all circumstances use a known working OpenOCD version; the latest
code from git.
//Peter
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
