I feel bad for making a Issue on this, but I am trying to use your tool and I have everything to be setup correct I believe. I went through the wiki and set it up . I powered on to firmware and it sat at the BIOS menu. I assume at this point I need to connect the PulseDBG to the machine and choose a boot option?

I launched PulseDBG and it gave me connection options. I chose serial and it closed , no error warnings or anything.(perhaps a cannot connect to serial would be nice) . So I tried using the Pipe option , after all the wiki has me use a named pipe. I try this and it freezed with this.

Available transports for engine "Pulse":
0: Serial port
1: USB 2.0 Debug
2: FireWire (IEEE 1394)
3: Network
4: Pipe
5: Local
Choose your option: 4

No enumerable interfaces found for a given transport
Enter transport address
\.\pipe\com_1
Warning! Cannot query target state
Frozen 0.0:

So obviously this isn't the answer. I don't think my request is anything extraordinary, I just want more documentation for how to use the tool for bios, bootloader, kernel debugging.

Is this already documented? Did I miss this? I will happily read documentation, I feel there isn't any art in figuring out how to make a tool work. There is are in what I do with the tool.

Do you need any more information from me?

If this tool does what I think it will, I would like to contribute to it.

If it is a real debugging machine, does it support multi-core?vmware debugging only supports single core, so if you run a software inside vmware, like FireFox, will it be slow to debug?Also does it support symbols？

Is the source code going to be open ?