• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 557 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.

Unable to load firmware for RDK.4

Vaibhav Dhingani
Expert 1540 points

Hi,

We have a customize board, which contains DM8148 & we are using RDK-4.0.

We are able to boot the kernel,

Also I am able to run init.sh script of RDK,

But when I run load.sh , I am getting following error

root@dm814x:/opt/dvr_rdk/ti814x# ./load.sh
Attached to slave procId 2.
Unable to handle kernel NULL pointer dereference at virtual address 0000000e
pgd = ea5f4000
[0000000e] *pgd=aaa6e031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
last sysfs file: /sys/devices/virtual/syslinkipc/syslinkipc_GateMP/uevent
Modules linked in: syslink
CPU: 0    Tainted: G        W    (2.6.37 #1)
PC is at OsalKfile_open+0xac/0x190 [syslink]
LR is at path_put+0x30/0x34
pc : [<bf021010>]    lr : [<c00d7458>]    psr: 20000013
sp : ea6b7d70  ip : ea6b7c80  fp : ea6b7dac
r10: 00000000  r9 : 00000000  r8 : 00000000
r7 : ea6b7dc4  r6 : ee5fb000  r5 : ee5fe000  r4 : fffffffe
r3 : eb37e900  r2 : 0000007d  r1 : 0000007e  r0 : fffffffe
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5387d  Table: aa5f4019  DAC: 00000017
Process fw_load.out (pid: 1026, stack limit = 0xea6b62e8)
Stack: (0xea6b7d70 to 0xea6b8000)
7d60:                                     bf05b1fd ea6b7dc4 00000001 bf000000
7d80: ea6b7dc4 ea6b7dc4 ee5fb000 ee58d000 00000000 00000000 00000000 bf0ae2bc
7da0: ea6b7dec ea6b7db0 bf009c00 bf020f70 ee5fb000 00000000 00000000 00000000
7dc0: ec429000 ee5fe000 ee58d000 ee5fb000 00000000 00000000 bf0ae2bc 00000000
7de0: ea6b7e24 ea6b7df0 bf001d4c bf009ba8 00000000 ea6b7ec8 00000000 00000000
7e00: ee59f000 00000000 ee5fb000 00000000 ea6b7ec8 00000000 ea6b7e64 ea6b7e28
7e20: bf002db0 bf001cf4 00000000 ea6b7ec8 00000000 00000000 00000025 befd3b40
7e40: 00000000 c020e0a2 ee5fb000 00000000 ea6b6000 00000000 ea6b7efc ea6b7e68
7e60: bf0051dc bf002d34 00000000 ea6b7ec8 ea6b7e94 ea6b7e80 c0220714 c02206b8
7e80: 00000000 60000013 ea8a3280 eb2c9890 ea6b6000 0000001c 4009b000 00000000
7ea0: ea6b7ecc ea6b7eb0 c0070764 0485f000 ee59f000 befd3e4d 00000025 00000000
7ec0: 00000000 00000000 00000000 ea6b7ed8 c00f9e84 c00917f4 ea6b7ef4 eae00e00
7ee0: 00000008 befd3b40 00000008 00000000 ea6b7f74 ea6b7f00 c00dc4c4 bf00492c
7f00: ea8a3280 00000000 00000000 00000000 00000000 0000001c eabc7588 00000002
7f20: eb2c9830 00000000 00000002 00000000 fffffffe 00000000 ea6b7f6c ea6b7f48
7f40: c041f5bc c00479ec ffffffff eb08e01c ea9a7400 befd3b40 c020e0a2 00000008
7f60: 00000000 ea6b6000 ea6b7fa4 ea6b7f78 c00dc590 c00dc000 ea6b7fac 00000001
7f80: c041be30 00000000 0007f334 000521d4 00000036 c004c568 00000000 ea6b7fa8
7fa0: c004c3c0 c00dc544 00000000 0007f334 00000008 c020e0a2 befd3b40 00000001
7fc0: 00000000 0007f334 000521d4 00000036 befd3b40 c020e0a2 00000000 00000000
7fe0: 0007f64c befd3b08 0002b1c0 402a81cc 60000010 00000008 00000000 00000000
Backtrace:
[<bf020f64>] (OsalKfile_open+0x0/0x190 [syslink]) from [<bf009c00>] (ElfLoader_load+0x64/0xfc [syslink])
[<bf009b9c>] (ElfLoader_load+0x0/0xfc [syslink]) from [<bf001d4c>] (Loader_load+0x64/0x94 [syslink])
[<bf001ce8>] (Loader_load+0x0/0x94 [syslink]) from [<bf002db0>] (ProcMgr_load+0x88/0xe8 [syslink])
[<bf002d28>] (ProcMgr_load+0x0/0xe8 [syslink]) from [<bf0051dc>] (ProcMgrDrv_ioctl+0x8bc/0x14d4 [syslink])
[<bf004920>] (ProcMgrDrv_ioctl+0x0/0x14d4 [syslink]) from [<c00dc4c4>] (do_vfs_ioctl+0x4d0/0x544)
 r8:00000000 r7:00000008 r6:befd3b40 r5:00000008 r4:eae00e00
[<c00dbff4>] (do_vfs_ioctl+0x0/0x544) from [<c00dc590>] (sys_ioctl+0x58/0x7c)
 r9:ea6b6000 r8:00000000 r7:00000008 r6:c020e0a2 r5:befd3b40
r4:ea9a7400
[<c00dc538>] (sys_ioctl+0x0/0x7c) from [<c004c3c0>] (ret_fast_syscall+0x0/0x30)
 r8:c004c568 r7:00000036 r6:000521d4 r5:0007f334 r4:00000000
Code: e3a09000 e1a04000 e9850050 e5875000 (e5903010)
---[ end trace 1b75b31a2719ed1e ]---

Please help me in this.

  • 0
    TI__Expert 6950 points


    1. Are you trying pre-built binaries or your own compiled version?

    2. What is your file system? Are the firmware present in the root file system?

    3. Have you done your h/w (custom board) specific changes (if any) in uboot, kernel?

    4. Attach the complete log from uboot.

     

  • 0
    TI__Expert 7765 points

    This can happen if firmware binary is not present in the file system is or the path provided to firmwareloader is wrong. Kindly confirm firmware binaries are there in /opt/dvr_rdk/ti814x/firmware folder. Also please confirm bootargs.

  • 0 in reply to Yogesh Marathe
    Expert 1540 points

    Thanks for the help

    I solved this issue. I have one more issue

    While booting kernel I am getting following error prints, though kernel is up & i am able to run demo.

    What is this?

    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 GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    ti8148_evm_init: 1072: 0x4814 0934: e0001
    omap_mux_init: Add partition: #1: core, flags: 4
    _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
    Setting pinmux for i2c2 gpio
    Register board info - i2c2
    Platform device register - i2c2
    ------------[ cut here ]------------
    WARNING: at kernel/resource.c:491 __insert_resource+0x4c/0x12c()
    Modules linked in:
    Backtrace:
    [<c0050020>] (dump_backtrace+0x0/0x110) from [<c041b608>] (dump_stack+0x18/0x1c)
     r6:c0502ffc r5:000001eb r4:00000000 r3:60000013
    [<c041b5f0>] (dump_stack+0x0/0x1c) from [<c00760f0>] (warn_slowpath_common+0x54/0x6c)
    [<c007609c>] (warn_slowpath_common+0x0/0x6c) from [<c007612c>] (warn_slowpath_null+0x24/0x2c)
     r8:00000000 r7:c000b794 r6:c05a562c r5:c058e988 r4:c058e988
    r3:00000009
    [<c0076108>] (warn_slowpath_null+0x0/0x2c) from [<c007b8fc>] (__insert_resource+0x4c/0x12c)
    [<c007b8b0>] (__insert_resource+0x0/0x12c) from [<c007c084>] (insert_resource+0x10/0x1c)
     r6:00000000 r5:00000000 r4:c058e3d0 r3:c04f802f
    [<c007c074>] (insert_resource+0x0/0x1c) from [<c022f640>] (platform_device_add+0xc0/0x16c)
    [<c022f580>] (platform_device_add+0x0/0x16c) from [<c022f70c>] (platform_device_register+0x20/0x24)
     r7:c000b794 r6:c0078d24 r5:c002ff1c r4:c058e3d0
    [<c022f6ec>] (platform_device_register+0x0/0x24) from [<c0010ca0>] (ti81xx_register_mcasp+0x60/0x80)
     r4:c05d8c90 r3:60000013
    [<c0010c40>] (ti81xx_register_mcasp+0x0/0x80) from [<c0013720>] (ti8148_evm_init+0xe8/0x1a4)
    [<c0013638>] (ti8148_evm_init+0x0/0x1a4) from [<c000b7b4>] (customize_machine+0x20/0x2c)
     r4:c002fa48 r3:c0013638
    [<c000b794>] (customize_machine+0x0/0x2c) from [<c00424f8>] (do_one_initcall+0xbc/0x190)
    [<c004243c>] (do_one_initcall+0x0/0x190) from [<c0008cfc>] (kernel_init+0xa0/0x154)
     r8:00000000 r7:00000013 r6:c0078d24 r5:c002ff1c r4:c002fa48
    [<c0008c5c>] (kernel_init+0x0/0x154) from [<c0078d24>] (do_exit+0x0/0x5d0)
     r5:c0008c5c r4:00000000
    ---[ end trace 1b75b31a2719ed1c ]---
    davinci-mcasp.1: failed to claim resource 0
    clk get on i2c3 fck failed
    Cannot clk_get ck_32
    Changing Mux registers for DS3
    _omap_mux_get_by_name: Multiple signal paths (2) for vin0_d10.gpio2_15
    Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    ti81xx_init_vpss: 525: 0x4814 0934: e0001
    registered ti81xx_vpss device
    registered ti81xx_vidout device
    ti81xx_init_vpss: 531: 0x4814 0934: e0001
    registered ti81xx on-chip HDMI device
    ti81xx_init_vpss: 535: 0x4814 0934: e0001

  • 0 in reply to Vaibhav Dhingani
    TI__Expert 7765 points

    Are you able to run demo with audio? looks like some issue with Mcasp device registration with kernel.

  • 0 in reply to Vaibhav Dhingani
    Prodigy 230 points

    Dear Vaibhav,

     

    I have exactly the same problem as in your original post. Would you please explain how you solved it?

     

    Best regards

    Gleb

     

  • 0 in reply to Gleb Feigstein
    Prodigy 230 points

    I have found the problem: the correct *.xem3 file was missing from the firmware directory in the root file system.