On Wed, Jul 1, 2009 at 12:56 PM, javier Martin<[email protected]> wrote: > We are trying to use openocd with an board which has an i.MX27 > processor and are using a JTAG debugger which runs a GDB server and a > telnet shell with openocd commands on it. > > Every time we try to execute the following command we get the error as > follows: > >> reset > JTAG tap: imx27.bs tap/device found: 0x1b900f0f (Manufacturer: 0x787, > Part: 0xb900, Version: 0x1) > JTAG Tap/device matched > JTAG tap: imx27.cpu tap/device found: 0x07926121 (Manufacturer: 0x090, > Part: 0x7926, Version: 0x0) > JTAG Tap/device matched > BUG: unknown debug reason: 0xe > > I have seen that two more persons have found this problem but no > solution was found yet. > > Does anybody know if this can be safely ignored or what does it mean?
It can be ignored unless you see some unwanted followon behaviour. There are some debug reasons that are not properly documented(marked as "future expansion/not used" in ARM's docs) and it appears that some silicon vendors use these debug reasons for some purpose or other. E.g. Broadcom is exhibiting the same behaviour in some parts. Broadcom never got back to us on what it means, perhaps they even don't know :-) The conclusion so far is that unless we see some bad behaviour then we'll keep it on the watch list, but there is nothing that we can or should try to do with it at this point without further information. If we see some bad behaviour that we can map out, then perhaps we can infer the meaning of this debug reason... If someone has more information to share on this point it would be great to hear from you here on the list! -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
