Hello, if there is not something else wrong this error means AP ERROR on the SWD interface.
Regards, Mathias Am 01.06.2012 12:25, schrieb Sergey A. Borshch: > Greetings, developers. > > I have some problem with my STLink-v2 and STM32F100: seems like after gdb > connecting and loading image (target running or halted, doesn't matter), I'm > getting the message: > > jtag status contains invalid mode value - communication failure > Polling target failed, GDB will be halted. Polling again in 100ms > > Digging into sources and dumping some values shows that problem arises from > stlink_usb_v2_read_debug_reg() > > res = stlink_usb_xfer(handle, h->databuf, 8); > > if (res != ERROR_OK) > return res; > > *val = le_to_h_u32(h->databuf + 4); > return h->databuf[0] == STLINK_DEBUG_ERR_OK ? ERROR_OK : ERROR_FAIL; > > where h->databuf[0] takes walue not STLINK_DEBUG_ERR_OK (0x80) and not > STLINK_DEBUG_ERR_FAULT(0x81), but 0x12. As far as I read early in this list, > Spencer Oliver has STLink-v2 protocol description from ST. Spencer, can you > tell, what does this value mean? > > I don't think it's really communication failure, because same target hardware > with the same firmware, same OpenOCD, same JTAG and USB cables works fine > when > debugging with JLink clone. > > I think OpenOCD need to handle this response code somehow, but don't know > what > does this code mean. > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
