for simple stuff like lcd drivers, you do not really need a debugger imho, printk'ing will solve most problems i guess,
for the more complex stuff there is always the option of using the kernel debugger. never used it though. but the basic idea is that you hook a host pc to the target system over ttyS and then enable Kdbg etc .. Quoting Geert Vancompernolle <[EMAIL PROTECTED]>: > --- In [email protected], Smtux S <[EMAIL PROTECTED]> wrote: >> >> of course to start writing down a driver I have to look for which is > the right >> instruments... >> My question is which is the right debugger ? > >> I saw in another 3d DDD, is that user friendly? >> >> Does anyone know another debugger? > > If you mean writing a "real" driver in the kernel, then I think > finding a "kernel debugger" will not be that obvious. Kernel drivers > are mainly debugged using printk statements, AFAIK. This is simply > because the kernel has a minimum of tools available (there's no such > thing as a C-library, for instance, hence the use of printk, not > printf). The kernel has its own print routine, simply because the > "normal" printf is not available in kernel space (as is also the case > for many other functionality). > > That said, if you want to write a "driver" alike thing in user space > (which is also possible, by the way), then I can tell you I've started > by using DDD as debug environment, until I bounced (in a positive way) > into a debugger called "Insight" (coming from RedHat). > > I already posted a message in this newsgroup here a while ago, to > "announce" the existence of that debugger. > > So far, I'm very satisfied about it and I would not go back to DDD any > more, unless for very (so far unknown) good reasons! > > You can read more here: > http://tech.groups.yahoo.com/group/foxboard/message/4421 > > I wrote an article on my wiki pages (link is in the above mentioned > thread) on how to build that debugger. > > Really recommended! > > Best rgds, > > --Geert > >
