Re: [Kgdb-bugreport] error at start

2014-08-10 Thread Ran Shalit
Hi Jegathesan, I get the following (the same with KGDB config or without): root@dm814x:~# cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:unknown port: irq:0 1: uart:unknown port: irq:0 2: uart:unknown port: irq:0 3: uart:unknown port: irq:0 But I

Re: [Kgdb-bugreport] error at start

2014-08-08 Thread Ran Shalit
Hi Jegathesan, I haven't tested this yet. But in the last try when I compiled modules with KGDB , I noticed error on loading modules after boot. This error at boot is only when kernel is compiled with KGDB. Starting udev udev[117]: starting version 164 tlc59108

Re: [Kgdb-bugreport] error at start

2014-08-05 Thread Ran Shalit
Hi, I'm using the following kernel flags: CONFIG_KGDB CONFIG_KGDB_SERIAL I'm trying to debug remote target. Thanks, Ran On Tue, Aug 5, 2014 at 11:28 AM, Jegathesan Durairaj wrote: > I am using 8250 serial driver. Are you using the same? > > > On Tue, Aug 5, 2014 at 1:40 PM, Jegathesan Durairaj

Re: [Kgdb-bugreport] error at start

2014-08-05 Thread Ran Shalit
Hi, Are you using netconsole ? Anyway, with or without netconsole, I see that CONFIG_CONSOLE_POLL=y when I was trying previously to use KGDB (in Kconfig CONFIG_CONSOLE_POLL depends on CONFIG_KGDB & CONFIG_KGDB_SERIAL). Regards, Ran On Tue, Aug 5, 2014 at 7:59 AM, Jegathesan Durairaj wrote: > H

Re: [Kgdb-bugreport] error at start

2014-08-04 Thread Ran Shalit
Hi, I did not try it yet. I wander why there are patches only for short list of kernel versions, no patch for 2.6.37. I didnt think it will be so difficult to make kgdb work ! -- Infragistics Professional Build stunning Win

Re: [Kgdb-bugreport] error at start

2014-08-03 Thread Ran Shalit
Hi, I found out that debug info was missing from my kernel config. I thought this is it. But I still get same failure, clean compilation does not help... I wander what's the issue. Thanks, Ran On Fri, Aug 1, 2014 at 3:20 PM, Jegathesan Durairaj wrote: > I will also try to get patch for this i

Re: [Kgdb-bugreport] error at start

2014-08-01 Thread Ran Shalit
I still haven't made it yet. The insteresting thing is the SDK linux version (2.6.37) does not have kgdb ethernet support, though it is the method that been documented in TI's docuemnt. I suppost it required some patch, though I don't know where to get it from. Thanks, Ran On Fri, Aug 1, 2014 at

Re: [Kgdb-bugreport] error at start

2014-07-31 Thread Ran Shalit
Hi Jegathesan, I tried to add kgdbwait and tried the 3 oprtions below for kgdboc, but all of the fail in the same way... I thought that maybe this problem is related to using same uart as console. Another thing is that maybe the kgdb in this SDK is mallfunctioning and should be patched for version

Re: [Kgdb-bugreport] error at start

2014-07-31 Thread Ran Shalit
No, It is not set (It does not exist in .config) $ cat .config | grep "SMP" CONFIG_BROKEN_ON_SMP=y # CONFIG_VIDEO_VP27SMPX is not set Thanks, Ran On Thu, Jul 31, 2014 at 11:20 AM, Jegathesan Durairaj wrote: > check CONFIG_SMP in .config file. Is it set or NOT? > > > On Thu, Jul 31, 2014 at 1:

Re: [Kgdb-bugreport] error at start

2014-07-31 Thread Ran Shalit
No, DM8148 Soc has only one ARM Cortex-A8 Core (ARMv7 Architecture). On Thu, Jul 31, 2014 at 10:50 AM, Jegathesan Durairaj wrote: > Is it SMP? > On 31/07/2014 1:18 pm, "Ran Shalit" wrote: > >> Hi Jonathan, >> >> Thanks for the assistance. >> On stty I get: >> root@dm814x:/media/sda1# stty >>

Re: [Kgdb-bugreport] error at start

2014-07-31 Thread Ran Shalit
Hi Jonathan, Thanks for the assistance. On stty I get: root@dm814x:/media/sda1# stty speed 115200 baud; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;

Re: [Kgdb-bugreport] error at start

2014-07-30 Thread Ran Shalit
Hi Jegathesan, I am using TI's DM8148 (armv7 based soc), and I'm using the same UART (ttyS0 for both console and kgdb debugger) Now I get the exception already in tring to set the baud rate, according to the lines below it happens in uart_get_baud_rate. Maybe it is illegal to use same UART for bot