• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 309 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RDK missing files

Cullum Baldwin
Prodigy 210 points
Other Parts Discussed in Thread: TVP5158, TVP5151

We have the DM368 DVR RDK, the instructions state when we should load the kernal named "uImage_DM368_DVR", unfortunately the /bin folder only has a file named uImage_DM365_DVR. I built the kernel, but it also generates a file of the incorrect name.  I suspect I may have the "target" set incorrectly.  Is this really an issue, do I need to set the target correctly?  How do I do this in the RDK?  I do not see any compile fields that can be set to DM368.

In the interest of being diligent, I tried loading this kernel file, but I get a kernel panic during boot:

layer=c3bee800,layer->video_dev=c3bee960
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
i2c /dev entries driver
MDIN200 default input NTSC
Unable to handle kernel NULL pointer dereference at virtual address 00000008
pgd = c0004000
[00000008] *pgd=00000000
Internal error: Oops: 5 [#1]
Modules linked in:
CPU: 0
PC is at mdin200_i2c_read_reg+0x10/0x9c
LR is at mdin200_probe+0x40/0xf74
pc : [<c02f23fc>]    lr : [<c02f2e30>]    Not tainted
sp : c05a1c50  ip : c05a1c90  fp : c05a1c8c
r10: 00000000  r9 : c045dcf8  r8 : c0460108
r7 : c0460004  r6 : 00000000  r5 : c04600a0  r4 : c05a1dee
r3 : 00000080  r2 : c05a1dee  r1 : 00000004  r0 : 00000000
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  Segment kernel
Control: 5317F
Table: 80004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc05a0258)
Stack: (0xc05a1c50 to 0xc05a2000)
1c40:                                     c00fdba4 c05a1dee c04600a0 00000000
1c60: c0460004 c0460108 c045dcf8 00000000 c05a1c8c c05a1dee c04600a0 00000000
1c80: c05a1e1c c05a1c90 c02f2e30 c02f23fc c0460098 00000000 c05a1cc4 c05a1ca8
1ca0: c00efba4 c010afe4 c05a0000 ffffffff fbc48000 c044f048 c03dbed8 c05a1d28
1cc0: c05a1d0c c05a1cd0 c04c7280 c05b4640 c05a1cf4 c05a1ce0 c00ff0b8 c00fefcc
1ce0: c05b4640 c04c7280 c05a1d14 c05a1cf8 c00ff158 c00ff0a0 00000001 c05b4640
1d00: c04c7280 00000007 c05a1d44 c05a0000 c058dbc0 00000017 c05a1d3c c05a1d28
1d20: c01151f4 c0114610 c05d201c c058dbc0 c05a1d7c c05a1d40 c03dbc6c c03de130
1d40: c01001ac c00fffd4 00000001 c058dcd0 c00feb44 c05a0000 c058dbc0 c05a0000
1d60: c05a1e2c c0458d54 00000000 c3bd4ca0 c05a1d94 c05a1d80 c03dbed8 c03db570
1d80: c010043c 00000004 c05a1dcc c05a1d98 c03dc228 c03dbe2c c05a1dbc 00000001
1da0: c058dbc0 c0100190 00100100 00200200 00000000 c05a1e84 c05a1ddc c05a1e2c
1dc0: c05a1e64 c05a1dd0 c0117518 c03dc178 c05a1df4 c05be640 c05f59e0 00000000
1de0: c05a1de0 c05a1de0 c0117530 00001e0c c05966e0 00000000 c04600a0 00000000
1e00: c0460004 c0460108 c045dcf8 00000000 c05a1e2c c05a1e20 c02d14b8 c02f2e00
1e20: c05a1e4c c05a1e30 c02cfae8 c02d14a8 00000000 c02cfb38 c04600a0 c05a1e64
1e40: c05a1e5c c05a1e50 c02cfb48 c02cfa7c c05a1e8c c05a1e60 c02cf314 c02cfb48
1e60: c028ed60 c045df30 c045df30 c0460064 c0460170 c04600a0 c0460144 00000000
1e80: c05a1ea4 c05a1e90 c02cfbac c02cf2d4 c02cf2b0 c045de20 c05a1ebc c05a1ea8
1ea0: c02ceff4 c02cfb5c 00000000 c04600a0 c05a1ef4 c05a1ec0 c02cdff4 c02cefe4
1ec0: c0418874 00000000 c05a1fa0 00000000 c0460098 00000000 c0460144 c044e094
1ee0: 00000000 c044e0b0 c05a1f24 c05a1ef8 c02d1860 c02cdda0 00000000 c04600a0
1f00: c0460098 00000000 c04e7758 00000000 c05a1fa0 c0030c40 c05a1f3c c05a1f28
1f20: c02d18d8 c02d1768 c02d16e0 c040cdfc c05a1f9c c05a1f40 c0027d94 c02d18c4
1f40: c041832c c040cdfc 00000001 00000001 00000001 000002e0 000001e0 00007530
1f60: 000003e9 00000079 00000000 00000010 00000000 00000000 00000000 00000000
1f80: c0027c6c 00000000 c0030abc c05a0000 c05a1ff4 c05a1fa0 c00ee0c0 c0027ce8
1fa0: 00000000 c05a1fb0 c00eee88 c00f1208 00000000 00000000 c00ee028 c0107f24
1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
1fe0: 00000000 00000000 00000000 c05a1ff8 c0107f24 c00ee038 e5933008 e3530000
Backtrace:
[<c02f23ec>] (mdin200_i2c_read_reg+0x0/0x9c) from [<c02f2e30>] (mdin200_probe+0x40/0xf74)
 r6 = 00000000  r5 = C04600A0  r4 = C05A1DEE
[<c02f2df0>] (mdin200_probe+0x0/0xf74) from [<c02d14b8>] (platform_drv_probe+0x20/0x24)
[<c02d1498>] (platform_drv_probe+0x0/0x24) from [<c02cfae8>] (driver_probe_device+0x7c/0xcc)
[<c02cfa6c>] (driver_probe_device+0x0/0xcc) from [<c02cfb48>] (__device_attach+0x10/0x14)
 r7 = C05A1E64  r6 = C04600A0  r5 = C02CFB38  r4 = 00000000
[<c02cfb38>] (__device_attach+0x0/0x14) from [<c02cf314>] (bus_for_each_drv+0x50/0x8c)
[<c02cf2c4>] (bus_for_each_drv+0x0/0x8c) from [<c02cfbac>] (device_attach+0x60/0x8c)
 r7 = 00000000  r6 = C0460144  r5 = C04600A0  r4 = C0460170
[<c02cfb4c>] (device_attach+0x0/0x8c) from [<c02ceff4>] (bus_attach_device+0x20/0x30)
 r4 = C045DE20
[<c02cefd4>] (bus_attach_device+0x0/0x30) from [<c02cdff4>] (device_add+0x264/0x3b8)
 r5 = C04600A0  r4 = 00000000
[<c02cdd90>] (device_add+0x0/0x3b8) from [<c02d1860>] (platform_device_add+0x108/0x15c)
[<c02d1758>] (platform_device_add+0x0/0x15c) from [<c02d18d8>] (platform_device_register+0x24/0x28)
[<c02d18b4>] (platform_device_register+0x0/0x28) from [<c0027d94>] (mdin200_i2c_init+0xbc/0x134)
 r4 = C040CDFC
[<c0027cd8>] (mdin200_i2c_init+0x0/0x134) from [<c00ee0c0>] (init+0x98/0x26c)
 r6 = C05A0000  r5 = C0030ABC  r4 = 00000000
[<c00ee028>] (init+0x0/0x26c) from [<c0107f24>] (do_exit+0x0/0xa24)
Code: e1a0c00d e92dd870 e24cb004 e24dd024 (e5903008)
 <0>Kernel panic - not syncing: Attempted to kill init!

 

 

 

  • 0
    TI__Mastermind 19985 points

    Hi,

    which version of DVR RDK are you using? Also, are you testing it on the DM36x DVR RDK hardware or some of your board? The name "DM365" in the uImage is not a problem. It is more of an issue in MakeFile name, which should have been called "DM36x" instead of "DM365"

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Prodigy 210 points

    The version appears to be 2.1 (DM368_DVRRDK_v2.1_Linux.tar.gz).  Is there a newer (better) version?  I do not see a "name" field in any of the Makefiles.  What field/file should I be checking specifically? 

    We are trying to use the RDK on a custom board to do something very simmilar.  However instead of a tvp5158 we have the video coming through a tvp5151.

    Thanks,
    Cullum

  • 0 in reply to Cullum Baldwin
    TI__Mastermind 19985 points

    Hi,

    V2.1 is the latest version for DM36x DVR RDK. In the top level "Makefile", if you look at the "lsp" tag, you can see that we are naming the uImage with "DM365". Anyways, that is not really a concern here.

    Can you confirm that the uImage that you are trying on your custom board, works well on the DM36x DVR RDK hardware?

    If you are trying other board, we need to take care of the board config files which might not be same as our DVR RDK hardware.

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Prodigy 210 points

    Yes, the image does work on the DM368 DVR RDK hardware we have.  You are correct, we are having a collection of boot issues on our custom hardware.  Where can I find the "board configuration" files?  Setting the configuration files sounds much easier.  So far I have resolved the following boot issues:

    *system crash due to not having a mdin200 chip on the i2c
    *system NFS mount failure due to no mac address in EEPROM


    Thanks,
    Cullum