ollie lho ollie@sis.com.tw writes:
On Fri, 2003-05-16 at 01:23, jarcher wrote:
To add to Ron's message.
It varies a lot with your experience and how dirty you want to get.
A simple POST card and a lot of creative POST code bread crumbs is the cheap and dirty way to go, until you get the serial port debugger up and running. But it requires you to be really creative in crawling through the code. And takes a lot of time.
But you can move up the a logic analyzer looking at bus cycles or an ICE (in circuit emulator) looking at CPU activity These two are expensive (lots of $10K), but you can often rent them. Setup is usually the time burner here. But with a LA you can take selective pictures of events chained together in time. I don't know if SIS has an ICE for their SOC products.
Jordan
PS: Has anyone done a USB interface low level debugger? Early BIOS or at least just prior to payload decompress.
BTW, why didn't we come up with a GDB stub in LinuxBIOS ??
Primarily no one submitted it?. Someone reportedly wrote one a while ago.
Admittedly I don't think I would every use it, as I don't see the point. Except for the resource allocation code practically everything in LinuxBIOS is pretty trivial straight forward code. And it should remain so.
Eric