The windows driver has been installed via zadig as a WINUSB driver. To that
point, please note that we are seeing the device ID come out of the TAP on the
LPC2138, so the driver must be okay, it is establishing TAP contact. When
unplugged, "no TAP is found." I will try the FTDI version of the cfg file. Why
are there two? Only one can be correct for this particular model of OLIMEX? The
equipment has been shipped now and we have two other programmer choices at
install in Wisconsin. I did very much want to conquer this before shipping.
Perhaps, I miswired the equipement via the isolation relay mux to the LPC2138
RESET pin. I don't think so. I will try the FTDI driver when I arrive Thursday
night in WI. Thank you. (stay tuned)
---
** [tickets:#111] LPC2138**
**Status:** new
**Milestone:** 0.9.0
**Created:** Tue Nov 03, 2015 02:21 AM UTC by Kenneth Deitz
**Last Updated:** Tue Nov 03, 2015 09:53 PM UTC
**Owner:** nobody
I have tried everything with OPENOCD nothing works as per the documentation.
Errors, deprecations, invalid commands, sub commands, too few arguments in the
FLASH write_image command, yet I look at the docs and everything seems okay. I
modified the structure for my OLIMEX-ARM-USB-OCD-H shown here:
http://siwawi.bauing.uni-kl.de/avr_projects/arm_projects/openocd_intro/
Nothing works. I simply want to use the programmer unit to load SREC data into
a LPC2138. Nothing more. Why is this so difficult? Anyone got code that will
work?
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
