On Wed, Jan 18, 2012 at 11:37:54PM +0100, Freddie Chopin wrote: > > John - could you send full marking of the chip to the list (especially > date code)? My LPC2103 which works perfectly without srst_pulls_trst is > marked as follows:
Quite new board, but OLD chip. Philips logo LPC2129FBD64 CD2096 02. TPN0437A Looks like 2004 week 37 rev A I wouldn't swear that the "." is a dot. Is this also why it wants CPUTAPID 0x4... instead of 0xc...? --- I have some other LPC boards but they have NXP chips and were OK with the cfg files or worked (as far as I tested): LPC2378 and LPC2919. Chips have 2008 date codes. So those must also have worked OK without the srst_pulls_trst as I checked them before the 2129. I've read openocd.pdf about that setting and have the board schematics plus chip data sheet etc. I don't see much that would have helped me use that setting. Is there a Philips/NXP data sheet that I failed to find and you can point me to that explains what the chip(s) need for their JTAG/etc settings, please? Similar question about the openocd.pdf description of trst_and_srst. They look independent on the schematics so why that setting, i.e. why the _and_? John ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
