rick> Don't use _DEBUG_USB_COMMS_ and _DEBUG_JTAG_IO_. rick> LOG_DEBUG ensures that they are only output if rick> someone uses 'debug_level 3'.
SimonQian wrote: > In my opinion, '-d3' is used when debugging OpenOCD. > But there is no debug_level to use when debugging JTAG tools. Rick - I agree with Simon. This problem has came up earlier in a slightly different forms. When there was much discussion about debug logs from the SVF file processor And ... I know this also came up in another thread about debugging some tap state stuff. See: https://lists.berlios.de/pipermail/openocd-development/2008-December/003846.html the problem is generally: What are you debugging - and what do you need the log info for? A single "global debug level" is simply not a solution. Perhaps we should: 1) add a "-j3" type option? J for jtag debug, or maybe "-T3" for "tap" debug... 2) Add a "J_LOG_DEBUG()" macro... or something to that effect. -Duane. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
