Unhandled Exception in BIOS

Holger Eberhard102906

Other Parts Discussed in Thread: SYSBIOS, TPS54620

Hi folks,
we use DVR_RDK 03.00.00.00 on Udworks DM8168 platform.
and we get the following unhandled exeption:

Jan 9 20:36:00 10 user.info Remote debug client : [m3video] Unhandled Exception:
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] Exception occurred in ThreadType_Task
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] handle: 0x3dcb96d8.
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] stack base: 0x3ddc0c20.
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] stack size: 0x2000.
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R0 = 0x00000001 R8 = 0x3d527c00
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R1 = 0x00000002 R9 = 0xe5d703a9
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R2 = 0x3d527c24 R10 = 0x5b03d82c
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R3 = 0x00000000 R11 = 0x5b000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R4 = 0x5b03d390 R12 = 0x00000001
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R5 = 0x00000000 SP(R13) = 0x3ddc26f8
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R6 = 0xe59dc000 LR(R14) = 0x00000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] R7 = 0x3d52805c PC(R15) = 0x2000757a
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] PSR = 0x81000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] ICSR = 0x0440f803
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] MMFSR = 0x00
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] BFSR = 0x82
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] UFSR = 0x0000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] HFSR = 0x40000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] DFSR = 0x00000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] MMAR = 0xe59dc001
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] BFAR = 0xe59dc001
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] AFSR = 0x00000000
Jan 9 20:36:00 10 user.info Remote debug client : [m3video] Terminating Execution...

Any idea ?

Best regards
Holger

over 12 years ago

0 Badri Narayanan over 12 years ago

TI__Guru 59700 points

The exception looks like there is jump to NULL address. Can you pls provide the following info:

1. Register for Vsys_registerEventHandler .Pls refer /dvr_rdk/demos/mcfw_api_demos/mcfw_demo/demo.c Vsys_registerEventHandler

2. Pls implement function identical to Demo_eventHandler mainly the handling of slave core exception.

if (eventId == VSYS_EVENT_SLAVE_CORE_EXCEPTION)
    {
        Demo_printSlaveCoreExceptionContext(pPrm);
    }

3. Share the exeception log file and the .xem3 and .xem3.map. You will find them under /dvr_rdk/build/dvr_rdk/bin/ti816x-evm folder.

4. Pls mention under what condition you are gettign exception.

-- Did you make any modification on M3 side ?

-- Are you having a custom usecase ?

-- Is it your custom board or UD DVR

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

Hi Badri,
I prepared the exeption handling for VSYS_EVENT_SLAVE_CORE_EXCEPTION
as You mentioned. Now I am waiting that the excepion occurs.

Your questions:
- Nomodifications on M3 side,
- we use VSYS_USECASE_MULTICHN_PROGRESSIVE_VCAP_VDIS_VENC_VDEC
- Its our own customer hardware based on UD works design Rev. 0.5b

Thanks, best rgrds
Holger

2541.xem.zip

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

This could be a h/w issue. Can you pls confirm the following:

1. Have you done DDR byte wise s/w leveling

2. Do you have heat sink + fan on your board

3. Are you using PMIC on your board.Is it the same as UD DVR reference design/

4. Have you measured voltage ripple on the 1V AVS rail supply to 816x.If so what is the range you are seeing.

5. Do you have a means of monitoring the junction temperature of 816x on your board. Can you monitor it and check the temp at point of failure.

6. How long does it take to recreate the issue.Is it random or does it always happen after a given amount of time.

7. Have you performed DDR stess test for long duration on your board (atleast 12 hrs)

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

Hi Badri,
thanks for Your reply.

I try to answer Your qestions:

- We have not run DDR byte wise leveling, that is on of my next steps I will do,
we only have tested RAM via JTAG test, always successfull

- we have heat sink + fan, the temperature is low

- we use the same power management as UD reference design

- the exeption occurs randomly (after some hours or after some minutes)

Here is the exception, that occured after some minutes running the board

Jan 11 09:51:22 10 user.info Remote debug client : [m3video] Unhandled Exception:
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] Exception occurred in ThreadType_Task
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] handle: 0x3d521c58.
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] stack base: 0x3dd90c20.
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] stack size: 0x8000.
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R0 = 0x3dd987f0 R8 = 0xffffffff
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R1 = 0x3dd98b74 R9 = 0xffffffff
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R2 = 0x00000000 R10 = 0x3db1f000
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R3 = 0x00000000 R11 = 0x00000000
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R4 = 0x00000000 R12 = 0x9d221aa9
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R5 = 0x9d439ecc SP(R13) = 0x3dd987f0
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R6 = 0x00000000 LR(R14) = 0x9d221af3
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] R7 = 0x3db1f000 PC(R15) = 0x9d224b3c
Jan 11 09:51:22 10 user.err DMP : VSYS_EVENT_SLAVE_CORE_EXCEPTION
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] PSR = 0x61000000
Jan 11 09:51:22 10 user.err DMP : 498958:!!!SLAVE CORE DOWN!!!.EXCEPTION INFO DUMP
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] ICSR = 0x00400803
Jan 11 09:51:22 10 user.err DMP : !!HW EXCEPTION ACTIVE (0/1): [1]
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] MMFSR = 0x00
Jan 11 09:51:22 10 user.err DMP : !!EXCEPTION CORE NAME      : [VIDEO-M3]
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] BFSR = 0x00
Jan 11 09:51:22 10 user.err DMP : !!EXCEPTION TASK NAME      : [DEC0   ]
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] UFSR = 0x0008
Jan 11 09:51:22 10 user.err DMP : !!EXCEPTION LOCATION       : []
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] HFSR = 0x40000000
Jan 11 09:51:22 10 user.err DMP : !!EXCEPTION INFO           : [H/W EXCEPTION]
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] DFSR = 0x00000000
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] MMAR = 0xe000ed34
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] BFAR = 0xe000ed38
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] AFSR = 0x00000000
Jan 11 09:51:22 10 user.info Remote debug client : [m3video] Terminating Execution...
Jan 11 09:51:22 10 user.err DMP : !!EXCEPTION CCS CRASH DUMP FORMAT FILE STORED @ .//media/sda1/CCS_CRASH_DUMP_VIDEO-M3.txt

7701.CCS_CRASH_DUMP_VIDEO-M3.txt

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

Can you zip and attach /dvr_rdk/build/dvr_rdk/bin/ti816x-evm folder. I need both the map file and the m3 executable .xem3.

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

7230.ti816x-evm.zip

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

Can you copy paste the code in the file:

/home/heb/Projects/BOP13/build/dvr_rdk/obj/ti816x-evm/m3video/release/dvr_rdk_configuro/package/cfg/MAIN_APP_m3video_pem3.c

line #36075

Crash seems to be happening at link create time. Does this match your observation ?

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

Here comes line 36075:

obj = xdc_runtime_Core_createObject__I(&ti_sysbios_xdcruntime_SemProcessSupport_Object__DESC__C, oa, osz, &prms, (xdc_Ptr)pa, psz, eb);

But it is not clear if the eception occurs at link create time, my log file contains not so deep details.

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

Can you share the full remote debug client log .We can know if it is link create time from that.,Anyhow the place where it is crashing is sysbios code and this is not a s/w issue. THis looks like DDR corruption.Pls try doing s/w leveling and run ddr stree test for long duration to confimr DDR is okay. You can also try clocking DDR slower and check if it improves stability which could give additional data point about DDR issue.

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

Here comes a typical one of my log-files.

One question please:

Can You give me an advice how to bring down the clock slower.

What settings are possible here ?

0844.log.zip

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

From the log it doesnt look like link create time so it is strange it is executing Semaphore_create fucntion. Looks like control came to this function by mistake.

From the logs I see your device is PG1.1. M3 cannot be clocked at 280 in PG1.1 (default uboot setting in DVR RDK). Pls either use PG2.0 or set M3 to 250Mhz.

I will get back to you on uboot modifications to modify freq of M3 and DDR.

0 Sivagamy Govindasamy over 12 years ago in reply to Badri Narayanan

TI__Expert 6950 points

Use these values in arch/arm/include/asm/arch-ti81xx/clocks_ti816x.h for M3 clocking @ 250MHz. Rebuild uboot and reflash.

/* L3 FAST -> 500 MHz, Ducati M3 - 250 MHz, DSS - 250 MHz, L3 Medium - 250 MHz*/

#define MAIN_INTFREQ4 12

#define MAIN_FRACFREQ4 0x189374

#define MAIN_MDIV4 0x2

0 Holger Eberhard102906 over 12 years ago in reply to Sivagamy Govindasamy

Genius 4570 points

I use the following values defined for 250 MHz in clocks_ti816x.h

#define MAIN_INTFREQ4       0x9
#define MAIN_FRACFREQ4       0x55554F
#define MAIN_MDIV4       0x3

and I also changed the values in /mcfw/interfaces/link_api/system_common.h.

It seems a little bit better but the exeption still occurs.

Rgds Holger

0 Sivagamy Govindasamy over 12 years ago in reply to Holger Eberhard102906

TI__Expert 6950 points

There is an issue with DM816x that max FAPLL cannot go beyond 1600MHz. Refer the errata.

Looks like you are using an older uboot settings in which max FAPLL can go to 1728 which is incorrect.

Can you use latest DVR RDK release uboot file which has corrected PLL multiplication factor values to take care of this issue?

Modify the FREQ4 related settings as per my previous reply to clock M3@250MHz.

0 Badri Narayanan over 12 years ago in reply to Sivagamy Govindasamy

TI__Guru 59700 points

Also have you completed DDR byte wisesw leveling for your board

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

Hi all,
my problem still occurs.
After DDR3 SW Leveling, I did put the measured values into Uboot from version DVRRDK_03.00.01.03.

I have running 4 boards parallel in test.
2 of the boards got the exception after running a day.
I also go on stress testing DDR Ram, but I am not finshed for all board.
Until now I found no problem with the Uboot mtest.

At the moment for me it is not clear if I have done all initialization correctly.
I have attached a captured log file and clocks_ti816x.h, ddr_defs_ti816x.h.
Can You please tell me if my settings are OK ?

7444.Files.zip

0 Sivagamy Govindasamy over 12 years ago in reply to Holger Eberhard102906

TI__Expert 6950 points

I still see some discrepancy in macros used for s/w levelling. Eg - WR_DQS_RATIO_BYTE_LANE3 definition in your is not same as the definition from 3.0.1 uboot arago branch.

Could you update your file to be in sync with this - http://arago-project.org/git/projects/?p=u-boot-dvr-rdk-dm81xx.git;a=shortlog;h=refs/heads/dvrrdk_uboot_rel_03.00.01.03?

This update will ensure that s/w levelling configuration is done correctly.

0 Holger Eberhard102906 over 12 years ago in reply to Sivagamy Govindasamy

Genius 4570 points

Hi Sivagamy,

I 'm not shurewhat You meen,

I can not see differences for the 796MHz values that I want to use:

/* For 796 MHz */
#if defined(CONFIG_TI816X_DDR3_796)
#define EMIF_TIM1   0x1779C9FE
#define EMIF_TIM2   0x50608074
#define EMIF_TIM3   0x009F857F
#define EMIF_SDREF 0x10001841
#define EMIF_SDCFG 0x62A73832
#define EMIF_PHYCFG 0x00000110

#if defined(CONFIG_TI816X_DDR3_SW_LEVELING)
/* These values are obtained from the CCS app */
//#define RD_DQS_GATE_LANE3   ((emif == 0) ? 0x1B3 : 0x1B3)
//#define RD_DQS_GATE_LANE2   ((emif == 0) ? 0x1B3 : 0x1B3)
//#define RD_DQS_GATE_LANE1   ((emif == 0) ? 0x1B3 : 0x1B3)
//#define RD_DQS_GATE_LANE0   ((emif == 0) ? 0x1B3 : 0x1B3)

//#define RD_DQS_LANE3       ((emif == 0) ? 0x35 : 0x35)
//#define RD_DQS_LANE2       ((emif == 0) ? 0x35 : 0x35)
//#define RD_DQS_LANE1       ((emif == 0) ? 0x35 : 0x35)
//#define RD_DQS_LANE0       ((emif == 0) ? 0x35 : 0x35)

//#define WR_DQS_LANE3       ((emif == 0) ? 0x93 : 0x93)
//#define WR_DQS_LANE2       ((emif == 0) ? 0x93 : 0x93)
//#define WR_DQS_LANE1       ((emif == 0) ? 0x93 : 0x93)
//#define WR_DQS_LANE0       ((emif == 0) ? 0x93 : 0x93)

// 20130118heb- Values measured for BOP13 with DDR3_SlaveRatio_ByteWiseSearch_TI816x.out
#define RD_DQS_GATE_LANE3   ((emif == 0) ? 0x15d : 0x155)
#define RD_DQS_GATE_LANE2   ((emif == 0) ? 0x17a : 0x174)
#define RD_DQS_GATE_LANE1   ((emif == 0) ? 0x1b4 : 0x1a9)
#define RD_DQS_GATE_LANE0   ((emif == 0) ? 0x1de : 0x1d5)

#define RD_DQS_LANE3       ((emif == 0) ? 0x3c : 0x3a)
#define RD_DQS_LANE2       ((emif == 0) ? 0x40 : 0x41)
#define RD_DQS_LANE1       ((emif == 0) ? 0x3d : 0x3c)
#define RD_DQS_LANE0       ((emif == 0) ? 0x33 : 0x32)

#define WR_DQS_LANE3       ((emif == 0) ? 0xb2 : 0xb1)
#define WR_DQS_LANE2       ((emif == 0) ? 0xb1 : 0xb4)
#define WR_DQS_LANE1       ((emif == 0) ? 0xa4 : 0x9e)
#define WR_DQS_LANE0       ((emif == 0) ? 0x8d : 0x84)
#endif
#endif /* CONFIG_TI816X_DDR_796 */

#if defined(CONFIG_TI816X_DDR3_SW_LEVELING)
#define WR_DQS_RATIO_BYTE_LANE3       ((WR_DQS_LANE3 << 10) | WR_DQS_LANE3)
#define WR_DQS_RATIO_BYTE_LANE2       ((WR_DQS_LANE2 << 10) | WR_DQS_LANE2)
#define WR_DQS_RATIO_BYTE_LANE1       ((WR_DQS_LANE1 << 10) | WR_DQS_LANE1)
#define WR_DQS_RATIO_BYTE_LANE0       ((WR_DQS_LANE0 << 10) | WR_DQS_LANE0)

#define WR_DATA_RATIO_BYTE_LANE3   (((WR_DQS_LANE3 + 0x40) << 10) | (WR_DQS_LANE3 + 0x40))
#define WR_DATA_RATIO_BYTE_LANE2   (((WR_DQS_LANE2 + 0x40) << 10) | (WR_DQS_LANE2 + 0x40))
#define WR_DATA_RATIO_BYTE_LANE1   (((WR_DQS_LANE1 + 0x40) << 10) | (WR_DQS_LANE1 + 0x40))
#define WR_DATA_RATIO_BYTE_LANE0   (((WR_DQS_LANE0 + 0x40) << 10) | (WR_DQS_LANE0 + 0x40))

#define RD_DQS_RATIO_BYTE_LANE3       ((RD_DQS_LANE3 << 10) | RD_DQS_LANE3)
#define RD_DQS_RATIO_BYTE_LANE2       ((RD_DQS_LANE2 << 10) | RD_DQS_LANE2)
#define RD_DQS_RATIO_BYTE_LANE1       ((RD_DQS_LANE1 << 10) | RD_DQS_LANE1)
#define RD_DQS_RATIO_BYTE_LANE0       ((RD_DQS_LANE0 << 10) | RD_DQS_LANE0)

#define RD_DQS_GATE_BYTE_LANE0       ((RD_DQS_GATE_LANE3 << 10) | RD_DQS_GATE_LANE3)
#define RD_DQS_GATE_BYTE_LANE1       ((RD_DQS_GATE_LANE2 << 10) | RD_DQS_GATE_LANE2)
#define RD_DQS_GATE_BYTE_LANE2       ((RD_DQS_GATE_LANE1 << 10) | RD_DQS_GATE_LANE1)
#define RD_DQS_GATE_BYTE_LANE3       ((RD_DQS_GATE_LANE0 << 10) | RD_DQS_GATE_LANE0)
#endif   /* CONFIG_TI816X_DDR3_SW_LEVELING */

#endif   /* CONFIG_TI816X_EVM_DDR3 */

Regards Holger

0 Sivagamy Govindasamy over 12 years ago in reply to Holger Eberhard102906

TI__Expert 6950 points

There is a patch in Uboot for S/W levelling configuration (fix the DDR PHY CONFIG using the a wrong
byte lane s/w leveling parameter) . This was pushed post GA 3.0.1 release. We maintain Uboot, Linux code in Arago Git - externally available.

You can check for updates in Uboot for 3.0.1 branch from the link I mentioned in my previous reply.

I am not too sure if the issue you are seeing is related to this. Still you can get this fix into your uboot code.

I am attaching the file from tip of arago git in case you dont have access to Arago Git. 3618.ddr_defs_ti816x.h

0 Holger Eberhard102906 over 12 years ago in reply to Sivagamy Govindasamy

Genius 4570 points

Sorry, Ok, I undersand, I will try this.

I also made a version for 531 MHz DDR3 clock that I want to test.

Best regards Holger

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

After doing the change Sivagamy mentioned pls share your console logs from uboot prompt onwards till when kernel completes bootup and you get root prompt on your board

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

I have changed uboot ddr_defs_ti816x.h.

Here comes the log file from bootup.

Fullscreen 5148.teraterm.log Download


U-Boot 2010.06-svn169 (Jan 21 2013 - 14:26:17)

TI8168-GP rev 1.1

MAIN_N: 56, MAIN_P: 1, OSC_FREQ: 27, FAPLL_K: 8
ARM clk: 987MHz
DDR clk: 796MHz
HDVICP clk: 600MHz
L3 Fast clk: 500MHz
HDVPSS clk: 250MHz
Ducati M3 clk: 250MHz
DSS clk: 250MHz
DSP clk: 1000MHz

I2C:   ready
DRAM:  2 GiB
NAND:  HW ECC BCH8 Selected
256 MiB
MMC:   OMAP SD/MMC: 0
Net:   Ethernet PHY: GENERIC @ 0x01
DaVinci EMAC
Hit any key to stop autoboot:  1  0 

NAND read: device 0 offset 0x580000, size 0x300000
 3145728 bytes read: OK

NAND read: device 0 offset 0x9c0000, size 0x2800000
Skipping bad block 0x01a40000
 41943040 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37+
   Created:      2013-01-18  14:52:26 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2562420 Bytes = 2.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.37+ (heb@heb) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Fri Jan 18 15:52:20 CET 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168_dvr
vram size = 20971520 at 0x0
reserved size = 20971520 at 0x0
FB: Reserving 20971520 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 1.1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 145488
Kernel command line: console=ttyO2,115200n8 init=/linuxrc root=/dev/ram0 rw initrd=0xC2000000,120M ip=10.30.50.9:192.168.1.20:192.168.1.1:10.255.255.0::eth0:off vram=20M notifyk.vpssm3_sva=0xBEE00000 mem=128M mem=472M@0xC0000000 vmalloc=580M
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 128MB 452MB = 580MB total
Memory: 460296k/460296k available, 154104k reserved, 139264K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd4000000 - 0xf8000000   ( 576 MB)
    lowmem  : 0x80000000 - 0xd3c00000   (1340 MB)
    pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    modules : 0x7f000000 - 0x7fe00000   (  14 MB)
      .init : 0x80008000 - 0x8003b000   ( 204 kB)
      .text : 0x8003b000 - 0x804d9000   (4728 kB)
      .data : 0x804da000 - 0x80522d80   ( 292 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy: 
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
3-wired eeprom init done. (H/W ver:ff)
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
registered ti816x_sr device
pm_dbg_init: only OMAP3 supported
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea20808
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
regulator: pmbus_vr: 800 <--> 1050 mV at 1000 mV 
regulator: tps40400 probe done.
omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d401e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d4028800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 122880K
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
usb 1-1: new high speed USB device using musb-hdrc and address 2
highmem bounce pool size: 64 pages
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 867
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc 
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
omap2-nand driver initializing
NAND device: Maf ID: 0xec, Chip ID: 0xda (Samsung, )
 erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000240000 : "U-Boot"
0x000000240000-0x000000280000 : "U-Boot Env"
0x000000280000-0x000000580000 : "U-Boot Logo"
0x000000580000-0x0000009c0000 : "Kernel"
0x0000009c0000-0x00000d1e0000 : "File System"
0x00000d1e0000-0x000010000000 : "Reserved"
usb 1-1: New USB device found, idVendor=0409, idProduct=005a
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff8
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
rtc-ds1307 1-0068: rtc core: registered ds1337 as rtc0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbee00000
usbcore: registered new interface driver snd-usb-audio
Registered tvp5158 audio codec
asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX DVR
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
smartreflex-ti816x: ti816x_sr_probe done!
rtc-ds1307 1-0068: setting system clock to 2013-01-21 14:41:14 UTC (1358779274)
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=1cc915)
IP-Config: Unable to set interface netmask (-22).
PHY: 0:01 - Link is Up - 100/Full
ata2: link is slow to respond, please be patient (ready=0)
ata1: link is slow to respond, please be patient (ready=0)
ata1: softreset failed (device not ready)
ata2: softreset failed (device not ready)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: TOSHIBA MK5065GSX, GJ003A, max UDMA/100
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MK5065GS GJ00 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: TOSHIBA MK5065GSX, GJ003A, max UDMA/100
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/100
scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA MK5065GS GJ00 PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
 sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI disk
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing init memory: 204K
 Mounting /proc             : [SUCCESS]
 Mounting /sys              : [SUCCESS]
 Mounting /dev              : [SUCCESS]
 Mounting /dev/pts          : [SUCCESS]
 Enabling hot-plug          : [SUCCESS]
 Populating /dev            : EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb1): using internal journal
EXT3-fs (sdb1): recovery complete
EXT3-fs (sdb1): mounted filesystem with writeback data mode
[SUCCESS]
Starting telnet daemon.
Starting syslogd/klogd: done
Starting pure-ftpd daemonJan 21 14:41:32 10 syslog.info syslogd started: BusyBox v1.19.4
Jan 21 14:41:32 10 user.debug kernel: musb-hdrc: setup fifo_mode 4
Jan 21 14:41:32 10 user.debug kernel: musb-hdrc: 28/31 max ep, 16384/16384 memory
Jan 21 14:41:32 10 user.info kernel: musb-hdrc musb-hdrc.1: MUSB HDRC host driver
Jan 21 14:41:32 10 user.info kernel: musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
Jan 21 14:41:32 10 user.info kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jan 21 14:41:32 10 user.info kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan 21 14:41:32 10 user.info kernel: usb usb2: Product: MUSB HDRC host driver
Jan 21 14:41:32 10 user.info kernel: usb usb2: Manufacturer: Linux 2.6.37+ musb-hcd
Jan 21 14:41:32 10 user.info kernel: usb usb2: SerialNumber: musb-hdrc.1
Jan 21 14:41:32 10 user.info kernel: hub 2-0:1.0: USB hub found
Jan 21 14:41:32 10 user.info kernel: hub 2-0:1.0: 1 port detected
Jan 21 14:41:32 10 user.info kernel: musb-hdrc musb-hdrc.1: USB Host mode controller at d4028800 using DMA, IRQ 19
Jan 21 14:41:32 10 user.debug kernel: Registered /proc/driver/musb_hdrc.1
Jan 21 14:41:32 10 user.info kernel: NET: Registered protocol family 2
Jan 21 14:41:32 10 user.info kernel: IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 21 14:41:32 10 user.info kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Jan 21 14:41:32 10 user.info kernel: TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
Jan 21 14:41:32 10 user.info kernel: TCP: Hash tables configured (established 16384 bind 16384)
Jan 21 14:41:32 10 user.info kernel: TCP reno registered
Jan 21 14:41:32 10 user.info kernel: UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 21 14:41:32 10 user.info kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan 21 14:41:32 10 user.info kernel: NET: Registered protocol family 1
Jan 21 14:41:32 10 user.info kernel: RPC: Registered udp transport module.
Jan 21 14:41:32 10 user.info kernel: RPC: Registered tcp transport module.
Jan 21 14:41:32 10 user.info kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 21 14:41:32 10 user.debug kernel: PCI: CLS 0 bytes, default 64
Jan 21 14:41:32 10 user.info kernel: Trying to unpack rootfs image as initramfs...
Jan 21 14:41:32 10 user.info kernel: rootfs image is not initramfs (no cpio magic); looks like an initrd
Jan 21 14:41:32 10 user.info kernel: Freeing initrd memory: 122880K
.
Starting smbd daemonJan 21 14:41:32 10 user.warn kernel: NetWinder Floating Point Emulator V0.97 (double precision)
Jan 21 14:41:32 10 user.info kernel: PMU: registered new PMU device of type 0
Jan 21 14:41:32 10 user.info kernel: omap-iommu omap-iommu.0: ducati registered
Jan 21 14:41:32 10 user.info kernel: omap-iommu omap-iommu.1: sys registered
Jan 21 14:41:32 10 user.info kernel: usb 1-1: new high speed USB device using musb-hdrc and address 2
Jan 21 14:41:32 10 user.warn kernel: highmem bounce pool size: 64 pages
Jan 21 14:41:32 10 user.info kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Jan 21 14:41:32 10 user.info kernel: msgmni has been set to 867
Jan 21 14:41:32 10 user.info kernel: io scheduler noop registered
Jan 21 14:41:32 10 user.info kernel: io scheduler deadline registered
Jan 21 14:41:32 10 user.info kernel: io scheduler cfq registered (default)
Jan 21 14:41:32 10 user.info kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Jan 21 14:41:32 10 user.info kernel: omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
Jan 21 14:41:32 10 user.info kernel: omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
Jan 21 14:41:32 10 user.info kernel: omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
Jan 21 14:41:32 10 user.info kernel: console [ttyO2] enabled
Jan 21 14:41:32 10 user.info kernel: brd: module loaded
Jan 21 14:41:32 10 user.info kernel: loop: module loaded
Jan 21 14:41:32 10 user.warn kernel: ahci ahci.0: forcing PORTS_IMPL to 0x3
Jan 21 14:41:32 10 user.info kernel: ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
Jan 21 14:41:32 10 user.info kernel: ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc 
Jan 21 14:41:32 10 user.info kernel: scsi0 : ahci_platform
Jan 21 14:41:32 10 user.info kernel: scsi1 : ahci_platform
Jan 21 14:41:32 10 user.info kJan 21 14:41:32 Jan 21 14:41:32 10 user.info kernel: usbcore: registered new interface driver dm9601
Jan 21 14:41:32 10 user.info kernel: InitiJan 21 14:41:32 Jan 21 14:41:32 Jan 21 14:41:32 Jan 21 14:41:32 Jan 21 14:41:32 .
Starting nmbd daemon.
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
Kernel bootargs validated
numid=101,iface=MIXER,name='Left DAC Mux'
  ; type=ENUMERATED,access=rw------,values=1,items=3
  ; Item #0 'DAC_L1'
  ; Item #1 'DAC_L3'
  ; Item #2 'DAC_L2'
  : values=2
numid=99,iface=MIXER,name='Right DAC Mux'
  ; type=ENUMERATED,access=rw------,values=1,items=3
  ; Item #0 'DAC_R1'
  ; Item #1 'DAC_R3'
  ; Item #2 'DAC_R2'
  : values=2
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf005020
 [m3vpss ] Remote Debug Shared Memory @ 0xbf00a040
SysLink version : 2.10.02.17
SysLink module created on Date:Jan 14 2013 Time:09:43:36
Trace enabled
Trace SetFailureReason enabled
Jan 21 14:41:34 10 user.alert kernel: SysLink version : 2.10.02.17
Jan 21 14:41:34 10 user.alert kernel: SysLink module created on Date:Jan 14 2013 Time:09:43:36
Jan 21 14:41:34 10 user.alert kernel: Trace enabled
Jan 21 14:41:34 10 user.alert kernel: Trace SetFailureReason enabled
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
 Setting DMM priority for [HDVICP1 ] to [2] ( 0x4e000634 = 0x000a0000 )
 Setting DMM priority for [HDVICP2 ] to [2] ( 0x4e000634 = 0x00a00000 )
 
 *** TVP5158 probe : START ***
 
 TI VS EVM : TVP5158 device address : 0x58, 0x5a, 0x5c, 0x5e
 TI DVR    : TVP5158 device address : 0x5c, 0x5d, 0x5e, 0x5f
 
 Device found     : I2C (0xXX): 0x08 = 0x51
                    I2C (0xXX): 0x09 = 0x58
 
 Device NOT found : I2C (0xXX): Read ERROR !!! (reg[0x08], count = 2)
 
 I2C (0x58): Read ERROR !!! (reg[0x08], count = 2)
 I2C (0x5a): Read ERROR !!! (reg[0x08], count = 2)
 I2C (0x5c): 0x08 = 0x51 
 I2C (0x5c): 0x09 = 0x58 
 I2C (0x5d): 0x08 = 0x51 
 I2C (0x5d): 0x09 = 0x58 
 I2C (0x5e): 0x08 = 0x51 
 I2C (0x5e): 0x09 = 0x58 
 I2C (0x5f): 0x08 = 0x51 
 I2C (0x5f): 0x09 = 0x58 
 
 *** TVP5158 probe : END ***
 
/opt/ti816x
Attached to slave procId 2.
Loaded file ../firmware/dvr_rdk_fw_m3vpss.xem3 on slave procId 2.
Started slave procId 2.
After Ipc_loadcallback status [0x00000000]
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 250000000, <NEW> - 250000000
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ] notify_attach  rtnVal  0
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ] initProxyServer  rtnVal  0
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  *** UTILS: CPU KHz = 500000 Khz ***
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  47: SYSTEM  : System Common Init in progress !!!
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  47: SYSTEM: IPC init in progress !!!
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  47: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  1047: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  1049: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
Jan 21 14:41:36 10 user.info Remote debug client : [m3vpss ]  1049: SYSTEM: Attaching to [DSP] ... 
After Ipc_startcallback status [0x097d2000]
Attached to slave procId 1.
Loaded file ../firmware/dvr_rdk_fw_m3video.xem3 on slave procId 1.
Started slave procId 1.
After Ipc_loadcallback status [0x00000000]
Jan 21 14:41:37 10 user.info Remote debug client : [m3video] ***** SYSTEM  : Frequency <ORG> - 250000000, <NEW> - 250000000
Jan 21 14:41:37 10 user.info Remote debug client : [m3vpss ]  2049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  *** UTILS: CPU KHz = 500000 Khz ***
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  1239: SYSTEM  : System Common Init in progress !!!
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  1239: SYSTEM: IPC init in progress !!!
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  1239: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  2239: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  2241: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
Jan 21 14:41:37 10 user.info Remote debug client : [m3video]  2241: SYSTEM: Attaching to [DSP] ... 
After Ipc_startcallback status [0x00000000]
Attached to slave procId 0.
Loaded file ../firmware/dvr_rdk_fw_c6xdsp.xe674 on slave procId 0.
Started slave procId 0.
After Ipc_loadcallback status [0x00000000]
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ] ***** SYSTEM  : Frequency <ORG> - 800000000, <NEW> - 800000000
Jan 21 14:41:38 10 user.info Remote debug client : [m3video]  3241: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:38 10 user.info Remote debug client : [m3vpss ]  3049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  *** UTILS: CPU KHz = 800000DMA: Module install successful, device major num = 251 
 Khz ***
Jan 21DRV: Module install successful
 14:41:38 10 useDRV: Module built on Jan 14 2013 09:48:43 
r.info Remote debug client : [c6xdsp ]  
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  7: SYSTEM  : System Common Init in progress !!!
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  7: SYSTEM: IPC init in progress !!!
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  7: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  1265: SYSTEM: Attaching to [HOST] ... 
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  1268: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
Jan 21 14:41:38 10 user.info Remote debug client : [c6xdsp ]  1268: SYSTEM: Attaching to [VIDEO-M3] ... 
After Ipc_startcallback status [0x00000000]
Jan 21 14:41:39 10 user.info kernel: DMA: Module install successful, device major num = 251 
Jan 21 14:41:39 10 user.info kernel: DRV: Module install successful
Jan 21 14:41:39 10 user.info kernel: DRV: Module built on Jan 14 2013 09:48:43 
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf005020
 [m3vpss ] Remote Debug Shared Memory @ 0xbf00a040
Jan 21 14:41:39 10 user.info Remote debug client : [m3vpss ]  4049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:39 10 user.info Remote debug client : [m3video]  4241: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:39 10 user.info Remote debug client : [c6xdsp ]  2527: SYSTEM: Attaching to [VIDEO-M3] ... 
Jan 21 14:41:40 10 user.info Remote debug client : [m3vpss ]  5049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:40 10 user.info Remote debug client : [c6xdsp ]  3639: SYSTEM: Attaching to [VIDEO-M3] ... SUCCESS !!!
Jan 21 14:41:40 10 user.info Remote debug client : [m3video]  5241: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:40 10 user.info Remote debug client : [c6xdsp ]  3639: SYSTEM: Attaching to [VPSS-M3] ... 
Jan 21 14:41:40 10 user.info Remote debug client : [m3video]  5241: SYSTEM: Attaching to [DSP] ... SUCCESS !!!
Jan 21 14:41:40 10 user.info Remote debug client : [m3video]  5242: SYSTEM: Attaching to [VPSS-M3] ... 
Jan 21 14:41:41 10 user.info Remote debug client : [m3vpss ]  6049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:41 10 user.info Remote debug client : [m3video]  6241: SYSTEM: Attaching to [VPSS-M3] ... 
Jan 21 14:41:41 10 user.info Remote debug client : [c6xdsp ]  4897: SYSTEM: Attaching to [VPSS-M3] ... 
Jan 21 14:41:42 10 user.info Remote debug client : [c6xdsp ]  5899: SYSTEM: Attaching to [VPSS-M3] ... SUCCESS !!!
Jan 21 14:41:42 10 user.info Remote debug client : [m3vpss ]  7049: SYSTEM: Attaching to [DSP] ... 
Jan 21 14:41:42 10 user.info Remote debug client : [c6xdsp ]  5899: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
Jan 21 14:41:42 10 user.info Remote debug client : [m3vpss ]  7050: SYSTEM: Attaching to [DSP] ... SUCCESS !!!
Jan 21 14:41:42 10 user.info Remote debug client : [m3vpss ]  7050: SYSTEM: Attaching to [VIDEO-M3] ... 
Jan 21 14:41:42 10 user.info Remote debug client : [m3video]  7241: SYSTEM: Attaching to [VPSS-M3] ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8050: SYSTEM: Attaching to [VPSS-M3] ... SUCCESS !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8049: SYSTEM: Attaching to [VIDEO-M3] ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8050: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8050: SYSTEM: Attaching to [VIDEO-M3] ... SUCCESS !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8050: SYSTEM: Creating MsgQ [VIDEO-M3_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8050: SYSTEM: Creating MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8051: SYSTEM: Creating MsgQ [VIDEO-M3_ACK_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8050: SYSTEM: Creating MsgQ [VPSS-M3_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8052: SYSTEM: Notify register to [HOST] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8050: SYSTEM: Creating MsgQ [VPSS-M3_ACK_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8052: SYSTEM: Notify register to [DSP] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8052: SYSTEM: Notify register to [HOST] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8053: SYSTEM: Notify register to [VPSS-M3] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8052: SYSTEM: Notify register to [DSP] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8053: SYSTEM: IPC init DONE !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8053: SYSTEM: Notify register to [VIDEO-M3] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8053: SYSTEM: IPC init DONE !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7158: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8059: MEM: Shared Region 2: Base = 0xb0000000, Length = 0x0e9c0000 (233 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8059: MEM: Shared Region 2: Base = 0xb0000000, Length = 0x0e9c0000 (233 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7158: SYSTEM: Creating MsgQ [DSP_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8059: MEM: Shared Region 1: Base = 0x88000000, Length = 0x15000000 (336 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8059: MEM: Shared Region 1: Base = 0x88000000, Length = 0x15000000 (336 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7158: SYSTEM: Creating MsgQ [DSP_ACK_MSGQ] ...
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7159: SYSTEM: Notify register to [HOST] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8061: SYSTEM  : System Common Init Done !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7159: SYSTEM: Notify register to [VIDEO-M3] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8061: SYSTEM  : System VPSS Init in progress !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7159: SYSTEM: Notify register to [VPSS-M3] line 0, event 15 ... 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8061: SYSTEM  : System Common Init Done !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7159: SYSTEM: IPC init DONE !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8061: SYSTEM  : System Video Init in progress !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7161: MEM: Shared Region 2: Base = 0xb0000000, Length = 0x0e9c0000 (233 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  8061: SYSTEM  : System Video Init Done !!!
Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  7161: MEM: Shared Region 1: Base = 0x88000000, Length = 0x15000000 (336 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [mJan 21 14:41:43 Jan 21 14:41:43 Jan 21 14:41:43 Jan 21 14:41:43 10 user.info Remote debug client : [c6xdsp ]  71Jan 21 14:41:43 Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  80Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 1[module] vpss probe done.
0 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug clientJan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug client : [m3video]  80Jan 21 14:41:43 10 user.info Remote debug clientJan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8169: SYSTEM  : FVI[module] ti81xxfb probe done.
D2 Init in progress DONE !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8169: SYSTEM  : Device Init in progress !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ] initPrms.isI2cInitReq = 0
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ] initPrms.isI2cInitReq = 0
Jan 21 HDMI W1 rev 2.0
14:41:43 10 user.info Remote debug client : [m3vpss ]  8171: SYSTEM  : Device Init in progress DONE !!!
Jan 21 14:41:43 10 user[module] ti81xx_hdmi probe done.
.info Remote debug client : [m3vpss ]  8304: SYSTEM  : System VPSS Init Done !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8304: UTILS: DMA: HWI Create for INT63 !!!
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8304: SYSTEM  : Initializing Links !!! 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : System Heap      = 13024 B, Mbx = 10240 msgs) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : SR0 Heap         = 13452672 B (12 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : Frame Buffer     = 240794496 B (229 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : Bitstream Buffer = 352321408 B (335 MB) 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : Tiler 8-bit      = 134217728 B (128 MB)  - TILER ON 
Jan 21 14:41:43 10 user.info Remote debug client : [m3vpss ]  8305: SYSTEM  : FREE SPACE : Tiler 16-bit     = 134217728 B (128 MB)  - TILER ON 
Jan 21 14:41:44 10 user.info Remote debug client : [m3vpss ]  8415: SYSTEM  : Initializing Links ... DONE !!! 
 [m3vpss ] Received character 's'
Jan 21 14:41:44 10 user.info Remote debug client : [m3vpss ]  8415: SYSTEM  : Set Static L3 pressure for HDVPSS as High
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf005020
 [m3vpss ] Remote Debug Shared Memory @ 0xbf00a040
 [m3video] Received character 's'
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf005020
 [m3vpss ] Remote Debug Shared Memory @ 0xbf00a040
 [c6xdsp ] Received character 's'
/opt/ti816x
Jan 21 14:41:44 10 user.warn kernel: [module] vpss probe done.
Jan 21 14:41:44 10 user.warn kernel: [module] ti81xxfb probe done.
Jan 21 14:41:44 10 user.info kernel: HDMI W1 rev 2.0
Jan 21 14:41:44 10 user.warn kernel: [module] ti81xx_hdmi probe done.
I2C No Ack
Jan 21 14:41:44 10 user.warn kernel: I2C No Ack
 
 ORG 0x46c00524: 0
 NEW 0x46c00524: 2
 
Jan 21 14:41:45 10 daemon.info linuxrc: starting pid 201, tty '': '/opt/ti816x/bin/launcher.out'
Jan 21 14:41:45 10 daemon.info linuxrc: starting pid 202, tty '': '/sbin/syslogd -n'
Jan 21 14:41:45 10 daemon.info linuxrc: starting pid 203, tty '': '/sbin/klogd -n'
Jan 21 14:41:45 10 daemon.info linuxrc: starting pid 204, tty '': '-/bin/sh'
Jan 21 14:41:45 10 user.notice kernel: klogd started: BusyBox v1.19.4 (2012-11-27 09:06:50 CET)
Jan 21 14:41:45 10 syslog.info syslogd started: BusyBox v1.19.4

0 Holger Eberhard102906 over 12 years ago in reply to Holger Eberhard102906

Genius 4570 points

The behavior seems to be better since I have made the changes Sivagamy mentioned.

But after 2 days I have got another exception on one board.

I am not sure if this belongs to a DDR3 RAM problem or not.

Jan 23 05:03:02 10 user.info Remote debug client : [m3vpss ] 132915880: Assertion @ Line: 218 in links_common/merge/mergeLink_tsk.c: inQue < pCreateArgs->numInQue : failed !!!
Jan 23 05:03:02 10 user.err DMP : VSYS_EVENT_SLAVE_CORE_EXCEPTION
Jan 23 05:03:02 10 user.err DMP : 132905634:!!!SLAVE CORE DOWN!!!.EXCEPTION INFO DUMP
Jan 23 05:03:02 10 user.err DMP : !!HW EXCEPTION ACTIVE (0/1): [0]
Jan 23 05:03:02 10 user.err DMP : !!EXCEPTION CORE NAME      : [VPSS-M3]
Jan 23 05:03:02 10 user.err DMP : !!EXCEPTION TASK NAME      : [IPC_OUT_M30]
Jan 23 05:03:02 10 user.err DMP : !!EXCEPTION LOCATION       : [links_common/merge/mergeLink_tsk.c:218]
Jan 23 05:03:02 10 user.err DMP : !!EXCEPTION INFO           : [inQue < pCreateArgs->numInQue]
Jan 23 05:03:02 10 user.err DMP : !!EXCEPTION CCS CRASH DUMP FORMAT FILE STORED @ .//media/sda1/CCS_CRASH_DUMP_VPSS-M3.txt

7167.CCS_CRASH_DUMP_VPSS-M3.txt.

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

From exception dump looks like FVID2_Frame channel number is corrupted. This still points to DDR issue. Can you migrate to RDK 3.5 .The uboot and kernel had several fixes and some important fix may get missed if you backport individual patches.Have you done s/w leveling on different boards. Are you getting the same values on all boards. We have seen variation from board to board in some cases. Can you get the s/w leveling on the failing board and check if you get the same value.Another thing altough may not be directly related to the issue you are seeing is UD DVR 0.5b version is designed for max current of 13A.This is may be insufficient for the 16 ch DVR usecase.Pls refer UD DVR 0.6 and above schematics where the design is modified to support upto 18A peak current.Is the failing board using PG1.1 sample ? Did you see any VIP overflow logs during your run ? VIP overflow on PG1.1 can cause DDR memory corruption.

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

1.) Here come the results of my sw leveling.

Fullscreen 0333.Results SW Leveling.txt Download

DDR3 SW Leveling							
									
	EMIF 0					EMIF 1			
Nr.	Byte 0	Byte 1	Byte 2	Byte 3		Byte 0	Byte 1	Byte 2	Byte 3
									
Read DQS OPT									
#1	37 	3f 	43 	3d		35 	3b 	42 	3c
#2	31 	3d 	3f 	3d		32 	3c 	43 	3b
#4	34 	42 	41 	3c		25 	39 	41 	3c
#5	33 	3f 	3f 	39		30 	3b 	41 	38
#6	32 	3c 	40 	3d		32 	3d 	41 	3c
#8	24 	3a 	41 	3b		32 	3e 	42 	3b
#9	35 	3d 	44 	40		2e 	42 	48 	3d
Udworks	33 	3b 	3e 	3a		36 	39 	41 	36
									
DQS GATE OPT									
#1	1e1	1b8 	186 	157		1ce	1b0 	175 	154
#2	1e0	1b7 	179 	159		1da	1ab 	173 	15d
#4	1e1	1c5 	180 	16c		1da	1b8 	174 	14a
#5	1da	1b0 	170 	15e		1c9	19b 	179 	15a
#6	1dd	1ba 	17b 	15c		1db	1b5 	174 	165
#8	1d5	1b0 	173 	144		1ee	1b1 	18e 	163
#9	1be	18c 	15a 	146		1bf	196 	16d 	141
Udworks	1e3	1bd 	183 	160		1dd	1b4 	185 	15e
									
Write DQS OPT									
#1	b2 	b2 	a7 	8e		b0 	b4 	9e 	83
#2	af 	b6 	a4 	8e		b1 	b4 	9c 	86
#4	b2 	b0 	a5 	8c		b5 	b5 	9f 	83
#5	b3 	b0 	a2 	8a		ad 	b2 	9b 	82
#6	b7 	b3 	a6 	8c		b4 	b9 	a1 	83
#8	af 	b5 	a1 	8d		b2 	b4 	9e 	84
#9	b2 	ae 	ab 	91		b0 	b5 	a1 	86
Udworks	b2 	b0 	a4 	8b		b1 	b3 	a0 	84

I tested 7 of our boards and also the

In my opinion, the values are nearly equal for all boards.

2.) we will check the power supply of our board.

3.) I contacted our FAE to get version 3.5.

4.) You are right, I have overflow on VIP in the following way:

Jan 23 06:56:40 10 user.info Remote debug client : [m3vpss ] 83216457: CAPTURE: Overflow detected on VIP1, Total Resets = 1

Jan 23 06:56:40 10 user.info Remote debug client : [m3vpss ] 83216479: DEI : Loading Up-scaling Co-effs

Jan 23 06:56:40 10 user.info Remote debug client : [m3vpss ] 83216480: DEI : Co-effs Loading ... DONE !!!

But the overflow occurs not directly before the exception occurs.

What can I do against this overflow ?

0 Badri Narayanan over 12 years ago in reply to Holger Eberhard102906

TI__Guru 59700 points

I dont think this VIP overflow is causing the memory corruption.It is only one overflow and oevrflow seems to have occured after exception occured (based on timestamp in your log). Have you run DDR stress test on your board for long duration (typically atleast 16 hours) after the sw leveling.

0 Holger Eberhard102906 over 12 years ago in reply to Badri Narayanan

Genius 4570 points

I am not finished running stress test for all of the boards,

but I have not seen any problems with the boards I tested.

By the way, all our boards have version PG1.1.

0 Holger Eberhard102906 over 12 years ago in reply to Holger Eberhard102906

Genius 4570 points

After some unsuccessful attempts using software parameters, we decided to go back to check the hardware. It soon became apparent that all was not well on the 1.5V DDR3 power supply. The output was definitely ringing, with a p-p of 200mV. After some investigation we found that the switch mode regulator U95, TPS54620 has too much frequency compensation, and therefore starts to ring. R633 should be around 1.5K to reduce the compensation, and stop the ringing effects. This is in fact the preferred value stated in the TI data sheet. The same can be said for U96 and R701.

Thanks Badi and Sivagami for the support !

Processors

Processors forum

Unhandled Exception in BIOS