Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #27088
| From | Chris <xxx.syseng.yyy@gfsys.co.uk> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Efficient debug log |
| Date | 2017-07-29 12:47 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <oli059$kqe$1@gioia.aioe.org> (permalink) |
| References | <okpt2m$sok$1@dont-email.me> |
On 07/20/17 09:31, pozz wrote: > I usually prints some messages on a free UART used as a debug port. They > are very useful during debugging to understand the flow of execution. > > Most of the time, I don't compile the debug log facility in release build. > > I sometimes need to disable messages from some modules and enable > messages from other modules under debugging. > Moreover I sometimes need to enable/disable less important messages. > > Do you suggest some efficient implementation of debug log macros that > include all the features above? For any system designed here, some sort of debug and syslog is included at the design stage. To start, always an led or two hanging off spare port lines, then a simple class / value pair syslog facility, with an output to leds or a uart. A simple syslog can be implemented in less than a page of code, with an array of structures for the subsystem class and value pairs. Everything in the system that can have an error condition or other useful info has an entry. Trivial stuff really, but gets the job done... Chris
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Efficient debug log pozz <pozzugno@gmail.com> - 2017-07-20 11:31 +0200
Re: Efficient debug log Anders.Montonen@kapsi.spam.stop.fi.invalid - 2017-07-20 10:35 +0000
Re: Efficient debug log Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2017-07-20 23:14 +0200
Re: Efficient debug log David Brown <david.brown@hesbynett.no> - 2017-07-24 09:40 +0200
Re: Efficient debug log pozz <pozzugno@gmail.com> - 2017-07-26 11:15 +0200
Re: Efficient debug log David Brown <david.brown@hesbynett.no> - 2017-07-26 14:24 +0200
Re: Efficient debug log Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2017-07-27 10:23 +0200
Re: Efficient debug log David Brown <david.brown@hesbynett.no> - 2017-07-27 11:14 +0200
Re: Efficient debug log Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2017-07-27 10:06 +0200
Re: Efficient debug log David Brown <david.brown@hesbynett.no> - 2017-07-27 11:35 +0200
Re: Efficient debug log Clifford Heath <no.spam@please.net> - 2017-07-21 12:57 +1000
Re: Efficient debug log Jack <jack4747@gmail.com> - 2017-07-20 23:17 -0700
Re: Efficient debug log Chris <xxx.syseng.yyy@gfsys.co.uk> - 2017-07-29 12:47 +0000
Re: Efficient debug log pozz <pozzugno@gmail.com> - 2017-07-31 10:45 +0200
Re: Efficient debug log Chris <xxx.syseng.yyy@gfsys.co.uk> - 2017-07-31 16:44 +0000
csiph-web