**** BEGIN LOGGING AT Wed Aug 08 02:59:58 2012
**** ENDING LOGGING AT Wed Aug 08 20:13:49 2012

**** BEGIN LOGGING AT Wed Aug 08 20:14:16 2012
**** ENDING LOGGING AT Wed Aug 08 20:41:31 2012

**** BEGIN LOGGING AT Wed Aug 08 20:42:22 2012
Aug 09 01:21:45 <vinvl961> I need some clarity in writing a jtag driver for OpenOCD
Aug 09 01:26:09 <vinvl961> Can anuone see my msgs?
Aug 09 01:27:51 <roxfan> yep
Aug 09 01:32:54 <vinvl961> the board has a LPC 43xx with CMSIS DAP firmware on it 
Aug 09 01:33:26 <vinvl961> i need to write a driver which maps ther DAP commands with OpenOCD ApIs
Aug 09 01:34:12 <roxfan> good luck
Aug 09 01:35:47 <vinvl961>  am currently stuck at implementing the .execute_queue JTAG commands 
Aug 09 01:36:11 <vinvl961> mainly JTAG_SCAN
Aug 09 01:36:34 <vinvl961> f you can throuw light on how TDI and TMS values are generated for a scan, it will be of great help 
Aug 09 01:36:53 <vinvl961> *if you can throw light on it
Aug 09 01:41:22 <roxfan> you should write to the mailing list
Aug 09 01:43:13 <vinvl961> I was adviced to look at other drivers
Aug 09 01:44:17 <vinvl961> But since I am an amateur to both OpenOCD and JTAG, it is hard to follow.. there is very less documentation on the OpenOCD APIs
Aug 09 01:52:20 <roxfan> yeah, the only docs are for the users
Aug 09 01:52:28 <roxfan> at least there are _some_
Aug 09 01:53:39 <vinvl961> hmm.. I will have to wait for the the replies on the mailing list then
Aug 09 01:54:37 <vinvl961> is there a way to use a signal analyzer with any of the current working drivers and alyze the signals
Aug 09 01:54:58 <vinvl961> analyze the jtag signals
Aug 09 01:55:22 <vinvl961> Do you think it is a good approach?
Aug 09 02:01:26 <vinvl961> Or is there a way to step through the OpenOCD driver code.. like the currently working onces
Aug 09 02:12:16 <roxfan> it's just a program, you can debug it as any other
**** ENDING LOGGING AT Thu Aug 09 02:59:59 2012