jtag: always configure enabled tap parameter appropriately 61/2261/3
authorPaul Fertser <fercerpav@gmail.com>
Tue, 19 Aug 2014 07:44:42 +0000 (11:44 +0400)
committerSpencer Oliver <spen@spen-soft.co.uk>
Fri, 22 Aug 2014 07:38:42 +0000 (07:38 +0000)
Commit f701c0cb seems to have introduced a regression for non-JTAG
transports as the newly created "tap" (DAP actually) ended up being
disabled, thus resulting in total lack of functionality.

This was exposed by a debug log demonstrating ftdi SWD transport
connection to mdr32f9q2i, the target wasn't examined on init and
couldn't be reset.

Change-Id: If53cbe800d4adc177aa3ac3219860e7fa15b3e49
Reported-by: Хайруллин Эльдар <eldar.khayrullin@mail.ru>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-on: http://openocd.zylin.com/2261
Tested-by: jenkins
Reviewed-by: Angus Gratton <gus@projectgus.com>
Reviewed-by: Nemui Trinomius <nemuisan_kawausogasuki@live.jp>
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
src/jtag/tcl.c

index 647ac70..11687b9 100644 (file)
@@ -556,6 +556,7 @@ static int jim_newtap_cmd(Jim_GetOptInfo *goi)
        if (!transport_is_jtag()) {
                /* SWD or CMSIS-DAP (which is currently SWD-only) doesn't
                   require any JTAG tap parameters */
+               pTap->enabled = true;
                jtag_tap_init(pTap);
                return JIM_OK;
        }