On Sep 23, 2013, at 11:04 AM, Paul Fertser fercer...@gmail.com wrote:
On Wed, Sep 18, 2013 at 04:50:33PM +0200, Damjan Marion wrote:
So to speak 1149.1 with this device special sequence needs to be sent to
this device to switch from cJTAG to JTAG mode.
Sequence is described in the user
On Fri, Oct 11, 2013 at 02:41:31PM +0200, Damjan Marion wrote:
On Sep 23, 2013, at 11:04 AM, Paul Fertser fercer...@gmail.com wrote:
On Wed, Sep 18, 2013 at 04:50:33PM +0200, Damjan Marion wrote:
So to speak 1149.1 with this device special sequence needs to be sent to
this device to switch
On Oct 11, 2013, at 2:57 PM, Paul Fertser fercer...@gmail.com wrote:
On Fri, Oct 11, 2013 at 02:41:31PM +0200, Damjan Marion wrote:
On Sep 23, 2013, at 11:04 AM, Paul Fertser fercer...@gmail.com wrote:
On Wed, Sep 18, 2013 at 04:50:33PM +0200, Damjan Marion wrote:
So to speak 1149.1 with
On Fri, Oct 11, 2013 at 06:12:37PM +0200, Damjan Marion wrote:
I tried to do that with following:
jtag newtap $_CHIPNAME unknown0 -irlen 4
jtag configure $_CHIPNAME.unknown0 -event setup my_proc $_CHIPNAME.unknown0
but my_proc is not called, Instead I'm getting following:
Error: JTAG
On Oct 11, 2013, at 6:27 PM, Paul Fertser fercer...@gmail.com wrote:
On Fri, Oct 11, 2013 at 06:12:37PM +0200, Damjan Marion wrote:
I tried to do that with following:
jtag newtap $_CHIPNAME unknown0 -irlen 4
jtag configure $_CHIPNAME.unknown0 -event setup my_proc $_CHIPNAME.unknown0
but
I'm trying to hook up opened to TI's CC2538 Cortex-M3 SoC and it's not going
smooth.
Problem is that this device supports both 1149.1 and 1149.7 but default mode is
1149.7/cJTAG.
So to speak 1149.1 with this device special sequence needs to be sent to this
device to switch from cJTAG to JTAG
