On Thu, May 24, 2012 at 4:01 AM, Liviu Ionescu <[email protected]> wrote: > > another diff session, this time on the openocd logs, reveled a > difference in the way two firmware versions respond to a > certain EMU_CMD_HW_JTAG3 (0xCF) command issued by openocd: > ... > my first thought is a bug in the new firmware, that in this configuration > fails. > > Q1: any idea where does this long JTAG sequence come from? > can we shorten it? (since other long transactions seem to work, > only this particular one fails).
I am not so familiar with the OpenOCD internals. I contribute mainly by testing. Hopefully others can give you the answer. > > Q2: can you imagine an erroneous condition in our code > (the usb stack?) that could lead to such a situation? I am thinking that OpenOCD codes may be able to be fixed by following what Segger tool does. So you may want to compare the sequences of what Segger tool does and what OpenOCD does. > if not, I will report this to Segger. I think that is a good idea anyway. -- Xiaofan ------------------------------------------------------------------------------ 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
