On 10/10/2014 2:51 AM, joaoandrefe...@sapo.pt wrote:
> Citando Frank Rowand <frowand.l...@gmail.com>:
>> On 10/9/2014 10:54 AM, joaoandrefe...@sapo.pt wrote:
>>> Citando Frank Rowand <frowand.l...@gmail.com>:
< snip >
>>> I'm running PuTTY on the TARGET (scheme), as the "target console".
>>> Maybe this is not what is supposed to happen, but it was the idea I
>>
>> Ah, that is yet a different picture than I was understanding.
>>
>> That is wrong and will not work.
>>
>> "target console" on the target is the serial device. The kernel on
>> the target should be printing the boot messages to this device, and
>> at the end of boot either a shell show be attached to this device
>> or a login prompt to enter a shell should appear on this device.
>>
>> You probably select the console device by describing it on the
>> kernel boot line (the same place where you put "kgdbwait").
>>
>> When the target console is set to the serial device, you
>> will see the console traffic on minicom on the host. Be
>> sure to start kdmx and minicom before booting so you can
>> see the boot messages.
>>
>
> One interesting detail is that I ran things in the order you
> mentioned above ("./kdmx -n -d -p/dev/ttyS0 -b115200 -DsS" and
> "minicom -o -w -p /dev/pts/1" on the host, and then booting the
> kernel to be debugged in the target - without PuTTY), and I
> got the following output @ kdmx:
>
> serial port: /dev/ttyS0
> Initalizing the serial port to 115200 8n1
> /dev/pts/1 is slave pty for for terminal emulator
> /dev/pts/2 is slave pty for gdb
>
> s< 0x00
>
> This "s< 0X00" isn't coming from the target, or am I wrong?
It is coming from the target. Probably an artifact of the
driver initializing. 0x00 is NULL, which is usually ignored
on a serial port.
< snip >
> I think I got it. Now I'll just have to understand what's
> wrong on the target and change things accordingly.
Reference: kernel source code:
Documentation/kernel-parameters.txt
Documentation/serial-console.txt
On your target kernel boot line, add something like:
console=ttyS0,115200n8
The serial device name you need to use should be the same
name that you earlier connected PuTTY to. I am guessing
that it is ttyS0.
***** Read Documentation/serial-console.txt, especially the
***** 7 step example at the end, for other details you
***** might need, such as setting up getty so you can
***** login on the console (from minicom on the host).
-Frank
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
