Duane Ellis schrieb: > 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.
Agreed. > 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. I don't think adding one extra parameter per module which we want do debug is the right way. Other software solves this by having a bitmask, with one bit per module, so the user can set the bits for those modules whose debug messages he wants to see. This can be combined with a global debug/verbosity level like we have now. This requires an additional parameter (the bit number for the current module) in all LOG() calls - which may be hidden by providing a LOG_module() wrapper for each module. cu Michael _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
