I think there is a fundamental misunderstanding about JTAG and OpenOCD. Let me try to clarify:
JTAG clocks in and out bits, not bytes, so the concept of "big/small-endian" does not enter the picture at the JTAG level. OpenOCD stores the bits clocked in/out as a series of words which happen to be one byte long. The confusion starts when a series of one byte words and little endian representations are identical. Really OpenOCD could have stored the bits as a series of words larger than bytes in the host representation to be more efficient. -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/ _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
