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.

Issue in firmware loading on DM8148

Other Parts Discussed in Thread: TCA6424, PMP, TSC2004, TMP75, TVP5158

Hi,

We are trying to port linux BSP on our coustom board of DM8148. We are able to successfully port U-boot and Kernel, but while I run load.sh script, board hangs.

Please see my below log. Could anyone please guide me to resolve this issue?

Starting kernel ...

Linux version 2.6.37 (rakesh@EIDLCPU1013) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #8 Mon Jan 28 17:02:49 IST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148_rigel
vram size = 88080384 at 0x0
ti81xx_reserve: ### Reserved DDR region @87f00000
reserved size = 88080384 at 0x0
FB: Reserving 88080384 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.1
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 10752
Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/nfs nfsroot=10.99.14.35:/home_cvic/shabbir/8148_rdk/DVRRDK_03.00.00.00/target/rfs_814x rw mem=128M notifyk.vpssm3_sva=0xBFD00000 vram=84M ip=dhcp noinitrd
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 42MB 1MB = 43MB total
Memory: 36648k/36648k available, 94424k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xf8000000   ( 760 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0044000   ( 240 kB)
      .text : 0xc0044000 - 0xc0589000   (5396 kB)
      .data : 0xc058a000 - 0xc05dfac0   ( 343 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
omap_hwmod: gpio1: softreset failed (waited 10000 usec)
omap_hwmod: gpio2: softreset failed (waited 10000 usec)
omap_hwmod: gpio3: softreset failed (waited 10000 usec)
omap_hwmod: gpio4: softreset failed (waited 10000 usec)
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 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0x87f00000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
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 GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
clk get on i2c3 fck failed
Cannot clk_get ck_32
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xc8820000
ti81xx_pcie: forcing link width - x1
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
ti81xx_pcie: PCI scan done.
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 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
Found IO-expander TCA6424
Found IO-expander MCP23009
Advanced Linux Sound Architecture Driver Version 1.0.23.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
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
usb2phy: computed values rxcalib(15)DACs(27 13 13)
usb2phy: override computed values rxcalib(15)DACs(27 13 13)
usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f6ddb6e
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 c881e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(31 13 14)
usb2phy: override computed values rxcalib(15)DACs(31 13 14)
usb2phy_config: musb(1) rxcalib done, rxcalib read value 6f6fdb76
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 c8826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
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.
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
msgmni has been set to 71
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
console [ttyO0] enabled
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
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci probe: devid name is ahci
ahci CAP register dump =0x6726ff80
Modified ahci CAP register dump =0x6f26ff80
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci: SSS flag set, parallel bus scan disabled
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Maf ID: 0x2c, Chip ID: 0xdc (Micron, NAND 512MiB 3,3V 8-bit)
 erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000020000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffe
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can: d_can device registered (irq=52, irq_obj=53)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
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
input: gpio-keys as /devices/platform/gpio-keys/input/input0
input: TSC2004 Touchscreen as /devices/virtual/input/input1
input: power-button as /devices/platform/power-button/input/input2
rtc-ds1672 1-0068: chip found, driver version 0.4
rtc-ds1672 1-0068: rtc core: registered rtc-ds1672 as rtc0
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 252
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
lm75 1-0048: hwmon0: sensor 'tmp75'
lm75 1-004c: hwmon1: sensor 'tmp75'
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
Bluetooth: HCIATH3K protocol initialized
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbfd00000
usbcore: registered new interface driver snd-usb-audio
*** Forcing SW CTS!
asoc: tlv320aic3x-hifi <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
asoc: sii9135-codec-dai <-> davinci-mcasp.0 mapping ok
ALSA device list:
  #0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Registering the dns_resolver key type
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.
Detected MACID=0:17:eb:f8:40:94
Detected MACID=0:17:eb:f8:40:95
rtc-ds1672 1-0068: setting system clock to 2037-10-10 05:00:35 UTC (2138763635)
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU04G 3.69 GiB
 mmcblk0: p1 p2
PHY 0:01 not found
ADDRCONF(NETDEV_UP): eth0: link is not ready

CPSW phy found : id is : 0x70431
ADDRCONF(NETDEV_UP): eth1: link is not ready
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: ST9250315AS, 0001SDM1, max UDMA/133
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST9250315AS      0001 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 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
 sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
Sending DHCP requests .
PHY: 0:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
., OK
IP-Config: Got DHCP answer from 192.168.6.59, my address is 10.99.19.211
IP-Config: Complete:
     device=eth1, addr=10.99.19.211, mask=255.255.252.0, gw=10.99.17.1,
     host=10.99.19.211, domain=, nis-domain=(none),
     bootserver=192.168.6.59, rootserver=10.99.14.35, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:15.
devtmpfs: mounted
Freeing init memory: 240K
INIT: version 2.86 booting
Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (86): /proc/86/oom_adj is deprecated, please use /proc/86/oom_score_adj instead.
udev: starting version 141
udev: renamed network interface eth0 to eth2
udevd-event[97]: error changing netif name eth1 to eth3: Device or resource busy

Root filesystem already rw, not remounting
Caching udev devnodes
Populating dev cacheFAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.

EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
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 (sda2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with writeback data mode
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card EVM
INIT: Entering runlevel: 5
Unknown hardware: "" "" "" "" ""
Hardware is initialized using a guess method
/usr/share/alsa/init/default:53: control element not found
/usr/share/alsa/init/default:53: control element not found
No state is present for card EVM
Starting system message bus: dbus.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
Applying sync command

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org dm814x ttyO0

Arago 2010.11 dm814x ttyO0

dm814x login: root

root@dm814x:~#
root@dm814x:~#
root@dm814x:~# cd /opt/dvr_rdk/ti814x/
root@dm814x:/opt/dvr_rdk/ti814x# ls -l
drwxrwxr-x    2 27562    3355         4096 Dec 24  2012 bin
drwxrwxr-x    2 27562    3355         4096 Dec 21  2012 demo_ini
-rwxr-xr-x    1 27562    3355         1038 Dec 25  2012 env.sh
-rwxr-xr-x    1 27562    3355         1038 Sep  5  2012 env_512M_128M.sh
drwxrwxr-x    2 27562    3355         4096 Dec 25  2012 firmware
-rwxr-xr-x    1 27562    3355         1581 Dec 25  2012 init.sh
drwxrwxr-x    2 27562    3355         4096 Jul 11  2012 kermod
-rwxr-xr-x    1 27562    3355          563 Dec 25  2012 load.sh
-rwxr-xr-x    1 27562    3355           32 Dec 25  2012 run.sh
drwxrwxr-x    2 27562    3355         4096 Dec 20  2012 scripts
-rwxr-xr-x    1 27562    3355          522 Dec 25  2012 unload.sh
-rwxr-xr-x    1 27562    3355          568 Dec 25  2012 validate.sh
root@dm814x:/opt/dvr_rdk/ti814x# ./init.sh
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
Kernel bootargs validated
numid=1,iface=MIXER,name='PCM Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
  : values=127,127
  | dBscale-min=-63.50dB,step=0.50dB,mute=0
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
SysLink version : 2.10.02.17
SysLink module created on Date:Dec 20 2012 Time:12:47:20
Trace enabled
Trace SetFailureReason enabled
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )

 *** TVP5158 probe : START ***

 TI VS EVM : TVP5158 device address : 0x58, 0x5a, 0x5c, 0x5e
 TI DVR    : TVP5158 device address : 0x58, 0x59, 0x5a, 0x5b

 Device found     : I2C (0xXX): 0x08 = 0x51
                    I2C (0xXX): 0x09 = 0x58

 Device NOT found : I2C (0xXX): Read ERROR !!! (reg[0x08], count = 2)

 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )
 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )
 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )
 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )
 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )
 ERROR  (osa_i2c.c|OSA_i2cTestMain|263): OSA_i2cOpen( instId = 3 )

 *** TVP5158 probe : END ***

/opt/dvr_rdk/ti814x
root@dm814x:/opt/dvr_rdk/ti814x# ./load.sh
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]
 [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3vpss ] notify_attach  rtnVal  0
 [m3vpss ] initProxyServer  rtnVal  0
 [m3vpss ]
 [m3vpss ]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3vpss ]
 [m3vpss ]  53: SYSTEM  : System Common Init in progress !!!
 [m3vpss ]  53: SYSTEM: IPC init in progress !!!
 [m3vpss ]  53: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1052: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1054: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3vpss ]  1054: 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]
 [m3video] main start on M3 video*******************
 [m3vpss ]  2054: SYSTEM: Attaching to [DSP] ...
 [m3video] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3video]
 [m3video]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3video]
 [m3video]  1320: SYSTEM  : System Common Init in progress !!!
 [m3video]  1320: SYSTEM: IPC init in progress !!!
 [m3video]  1320: SYSTEM: Attaching to [HOST] ...
 [m3video]  2320: SYSTEM: Attaching to [HOST] ...
 [m3video]  2322: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3video]  2323: 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]
 [c6xdsp ] ***** SYSTEM  : Frequency <ORG> - 500000000, <NEW> - 750000000
 [m3video]  3322: SYSTEM: Attaching to [DSP] ...
 [m3vpss ]  3054: SYSTEM: Attaching to [DSP] ...
 [c6xdsp ]
 [c6xdsp ]  *** UTILS: CPU KHz = 750000 Khz ***
 [c6xdsp ]
 [c6xdsp ]  0: SYSTEM  : System Common Init in progress !!!
 [c6xdsp ]  0: SYSTEM: IPC init in progress !!!
 [c6xdsp ]  0: SYSTEM: Attaching to [HOST] ...
 [c6xdsp ]  667: SYSTEM: Attaching to [HOST] ...
 [c6xdsp ]  669: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [c6xdsp ]  669: SYSTEM: Attaching to [VIDEO-M3] ...
After Ipc_startcallback status [0x00000000]
DMA: Module install successful, device major num = 250
DRV: Module install successful
DRV: Module built on Dec 24 2012 11:35:31
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040

  • Of 128M linux memory VRAM is allocated 84M leaving only 42M avalable for apps.Although this may not be the issue pls first try with small vram size such as vram=4M. ALso I dont see any failure log. Have you share the full log

  • Hi Badri,

    Thanks for your answer. I have shared full log from starting of kernel. I have tried to run by keeping vram=20M, in that case also firmware load fails at same point.

    So I doubt vram should be the issue.

    Thanks & Regards,

    Rakesh Modi

  • WHen you say fail what is exactly happening ? Is A8 console frozen ? Have you made any changes to the default memory map ? Is this your own board or EVM  ?

  • Yes, my A8 console get frozen, while it fails. I am using my coustom board, which has 512 MB DDR on each emif.

    I have not done any changes in memory map.

  • The most likely causes are your DMM_LISA setting is wrong causing the same memory to be reflected in different physical address. You can check this by first wirting a different pattern at various addresses like 0x8000_0000/0x8800_0000/0x9000_0000 so on for 1GB and reading them back to confirm they are unmodified.You can also run mtest on full 1GB to confirm all 1GB is accessible.

    Another cause could be the voltage level is not set correctly for the required OPP. Pls refer theDVR RDK documentation for 814x bootargs. The PMIC is configured with correct voltage level for different domains.Similar configuration needs to be done on your board.

  • The most likely causes are your DMM_LISA setting is wrong causing the same memory to be reflected in different physical address. You can check this by first wirting a different pattern at various addresses like 0x8000_0000/0x8800_0000/0x9000_0000 so on for 1GB and reading them back to confirm they are unmodified.You can also run mtest on full 1GB to confirm all 1GB is accessible.

    Ronak : On our custom board we have two 512 MBs DDR banks, one starting from 0x8000000 and second starting from 0xA0000000. So following is the configurations we did in uboot. We verified that both the banks are accessible by performing write tests.

    #define CONFIG_NR_DRAM_BANKS            2

    #define PHYS_DRAM_1                     0x80000000
    #define PHYS_DRAM_1_SIZE                0x20000000      /* 512 MB */
    #define PHYS_DRAM_2                     0xA0000000      /* DRAM Bank #2 */
    #define PHYS_DRAM_2_SIZE                0x20000000      /* 512 MB */

    Another cause could be the voltage level is not set correctly for the required OPP. Pls refer theDVR RDK documentation for 814x bootargs. The PMIC is configured with correct voltage level for different domains.Similar configuration needs to be done on your board.

    Ronak : We are clocking A8 on 600 MHz and core voltage is of 1.2 V, so I think OPP settings are proper in terms of voltage requirements.

    Following is our end goal, it may help you to understand the issue.

    1) On our custom board there is 1G DDR available.

    2) We want to use default 512 MB memory map but wanted to use another 512 MB in linux.

    3) To reflect the same changes we modified "config_512M.bld"  and did following changes to reflect our actual physical address.

    var DDR3_ADDR_REG0_START = 0x80000000;
    var DDR3_ADDR_REG0_END   = 0x90000000; /* 256 MB */
    var DDR3_ADDR_REG1_START = 0x90000000;
    var DDR3_ADDR_REG1_END   = 0xA0000000; /* 256 MB */

    4) We use following bootargs

    setenv ipaddr 10.99.19.215;setenv serverip 10.99.19.216;setenv gatewayip 10.99.19.1; setenv netmask 255.255.255.0; setenv bootargs 'console=ttyO0,115200n8 rootwait root=/dev/nfs rw nfsroot=10.99.19.216:/opt/target/rfs_814x rw mem=128M mem=256@0xA0000000 notifyk.vpssm3_sva=0xbfd00000 vram=20M ddr_mem=512M noinitrd muxsel=sd'; setenv bootcmd 'tftp 0x81000000 uImage_DM814X_TI_EVM;bootm 0x81000000'; boot

    5) But when we load the firmware using ./load.sh after running ./init.sh we get the print on console "SYSTEM: Attaching to [DSP] ..." and after that A8 gets hang.

    Would you please let us know where we are missing.

    Thanks,

    Ronak

  • I am confused as you previously mentioned there were no changes in default RDK memory map. Anyhow if you modified config_512M with changes mentioned above it will not work. There are a number of restrictions in terms of notify address,cacheability of memory regions which get broken when you change the DDR1 reg from

    var DDR3_ADDR_REG1_START = 0xB0000000;
    var DDR3_ADDR_REG1_END   = 0xC0000000;

    Is the app working if you dont modify the memory map and dont change the uboot . Pls check if that works first.We can then try modifications to enable 1GB usage.

    Also setting ARM to 600 is not the only factor determining voltage. IVA HD /DSP/M3 have also to be clocked to correct values. TO elimintate voltage as a factor pls check if board is stable with 512 MB configuration and you are able to run the app for long duration.

  • Hi Badri,

    We performed both the experiments i) without changing default memory map and ii) with changing default memory map as described above. But in both cases we got errors in loading the firmware. But during both the experiments we changes the uboot for following memory changes,

    #define PHYS_DRAM_2                     0xA0000000      /* DRAM Bank
    #define PHYS_DRAM_2_SIZE                0x20000000      /* 512 MB */

    Followings are our LISA register configurations and core frequencies. 

    /*     
     * TI814X PG2.1 DMM LISA MAPPING
     * 1G contiguous section with 128-byte interleaving
     */
    #define PG2_1_DMM_LISA_MAP__0       0x0
    #define PG2_1_DMM_LISA_MAP__1       0x0
    #define PG2_1_DMM_LISA_MAP__2       0x0
    #define PG2_1_DMM_LISA_MAP__3       0x80640300

    CLK For 
    TI8148 :-
    --------------------------
    CPU CLK [ARM] -600MHz
    DDR Freq -400MHz
    DSP CLK -500MHz
    ISS CLK -400MHz
    IVA CLK -306 MHz
    DSS CLK -200MHz

    Badri : "Is the app working if you dont modify the memory map and dont change the uboot . Pls check if that works first.We can then try modifications to enable 1GB usage."

    Here, I don't understand the point of not changing uboot. We have 2nd DDR bank starting from address 0XA0000000 so that's why I think we have to change the physical DDR mapping in uboot.

    Just as a sideline, we are successfully running EZSDK 5.5 on this custom board with following bootargs, there we are utilizing 1 GB memory

    setenv bootargs 'console=ttyO0,115200n8 rootwait root=/dev/nfs nfsroot=10.99.18.170:/opttargetfs rw mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 ip=dhcp vram=84M noinitrd muxsel=sd';dhcp;setenv serverip 10.99.18.170;tftpboot uImage.1212;bootm

    -Thanks,

    Ronak