debug messages

martin at garben.net martin at garben.net
Tue Sep 25 19:32:40 UTC 2007


HI,
I wanted to try the "regular" debug-messages on the firmware.
The firmware is compiled with make DEBUG=1, but there is no additional output on my cutecom. (The output that begins with
DEBUG Interface:
0) Set Pull-up 1) Clear Pull-up 2) Toggle LED1 3) Toggle LED2
9) Reset
is displayed)

When I force the output of the debug messages in dbgu.h with
//#ifdef DEBUG
#if 1
extern void debugp(const char *format, ...);
#define DEBUGP(x, args ...) debugp(x, ## args)
#else
#define DEBUGP(x, args ...) do {} while(0)
#endif

#define DEBUGPCR(x, args ...) DEBUGP(x "\r\n", ## args)
#define DEBUGPCRF(x, args ...) DEBUGPCR("%s(%d): " x, __FUNCTION__, __LINE__, ## args)

it works, but I get spammed with hundreds of "sys_irq END" and some 
"LEN > BYTES_LEFT
WRAP DURING APPEND"
on my cutecom.

I just wanted to test the already implemented AT91F_DBGU_Printk-s, but whats wrong? 
Why are the messages not activated automatically with make DEBUG=1 and why do I get overrun with "sys_irq END" if I force the output?

Best regards, Martin



More information about the openpcd-devel mailing list