2010-02-10
jerry_xjtu
发件人： David Brownell
发送时间： 2010-02-05 02:19:40
收件人： openocd-development
抄送： jerry_xjtu
主题： Re: [Openocd-development] Fw: For JLink Support
On Thursday 04 February 2010, jerry_xjtu wrote:
> So my question is:
> Can we take full control of JLink by using OpenOC
] Fw: For JLink Support
On Thursday 04 February 2010, jerry_xjtu wrote:
> So my question is:
> Can we take full control of JLink by using OpenOCD and generate the simulate
> timing for Flash program?(using boundary scan)
Have you tried using the SVF or XSVF support to do that?
That'
Hi Jerry,
"jerry_xjtu" writes:
>
> I am reading src\jtag\drivers\jlink.c
> From JLink USB protocol manual there is 3 x 2048 Bytes
> buffer to store tdi/tms/tdo data.
> Any one knows why it have changed to 256Bytes from the code?
>
>
> //#define JLINK_TAP_BUFFER_SIZE 2048
> #define JLINK_TAP_BU
On Thursday 04 February 2010, jerry_xjtu wrote:
> So my question is:
> Can we take full control of JLink by using OpenOCD and generate the simulate
> timing for Flash program?(using boundary scan)
Have you tried using the SVF or XSVF support to do that?
That's the only way to do it for now; we d
For question:
>hi ALL:
>I am using a WIGGLER board to program flash by using boundary scan.
>It's too slow as here are 734 CellNum on the chip MPC8247, and the TCK is only
>about 100KHz to 200KHz.
>I found JLink can works at 12MHz TCK.
>So my question is:
>Can we take full control of JLink by u
hi ALL:
I am reading src\jtag\drivers\jlink.c
From JLink USB protocol manual there is 3 x 2048 Bytes buffer to store
tdi/tms/tdo data.
Any one knows why it have changed to 256Bytes from the code?
//#define JLINK_TAP_BUFFER_SIZE 2048
#define JLINK_TAP_BUFFER_SIZE 256
//#define JLINK_TAP_BUFFER_S
hi ALL:
From code :
+/* We use the maximal value observed */
+#define JLINK_TAP_BUFFER_SIZE 390
+
+static int tap_length;
+static u8 tms_buffer[JLINK_TAP_BUFFER_SIZE];
+static u8 tdi_buffer[JLINK_TAP_BUFFER_SIZE];
+static u8 tdo_buffer[JLINK_TAP_BUFFER_SIZE];
+
Does it means SAMPLE op will
