• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 1502 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.

Kernel boot crashes in ezsdk 5.02.02.60 on DM8148 EVM

Mitul Chokshi
Intellectual 405 points


Hi,

I'm trying to boot DM8148 evm with EZSDK 5.02.02.60. The boot process hangs halfway, with default bootargs.

Bootargs: 'console=ttyO0,115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=10.10.38.39:/home/admin1/targetfs/ ip=dhcp'

Bootlog: See attachment [[View:http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/717/0247.with_5F00_notifyk.txt]]

 

If I remove notifyk command from bootargs, then boot process goes further but crashes while loading hdvpss.

Bootargs: 'console=ttyO0,115200n8 rootwait rw mem=256M earlyprintk vram=50M ti814xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=10.10.38.39:/home/admin1/targetfs/ ip=dhcp'

Bootloag: See attachment [[View:http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/717/7853.without_5F00_notifyk.txt]]

 

Regards,

Mitul

 

 

  • 0
    TI__Mastermind 20245 points

    Hi,

    Are you running on 512MB DDR memory board of 1GB memory board. It will work with only 1GB memory board.

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 405 points
    Hi Hardik, 

    I'm using 512MB board. But I've made changes in EZSDK memory map as mentioned on this wiki page.

    http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map#Changing_Memory_Map_For_512MB_Board

    Please let me know if any other change I need to make.

    Regards,

    Mitul

  • 0 in reply to Mitul Chokshi
    TI__Mastermind 20245 points

    Hi,

    You wont be able to allocated 256MB for 512MB board. Try setting it to say 80MB.  rw mem=256M mem=80M

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    TI__Mastermind 20245 points

    Hi,

    512MB memory map says 176 MB memory for Linux so you should change mem=176M instead of 256M

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 405 points

    I checked with 80M, 128M & 176M. But the result is same.

    If I keep notifyk command in boorargs, then it hangs during kernel boot. What could be the issue?

     

    Regards,

    Mitul

  • 0 in reply to Mitul Chokshi
    TI__Mastermind 20245 points

    Hi,

    With 512MB memory map notifyk.vpssm3_sva=0xBF900000 0x9F900000. Its mentioned in same 512MB memory map document.

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 405 points

    HardikShah said:
    notifyk.vpssm3_sva=0xBF900000 0x9F900000

    Yes I tried with that also, but it does not make any difference. Result is same.

  • 0 in reply to Mitul Chokshi
    TI__Mastermind 20245 points

    Hi,

    You have modified uboot for 512MB right?

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 405 points

    Yes, but let me confirm if correct u-boot is being used or not.

  • 0 in reply to HardikShah
    Intellectual 405 points

    I modified u-boot for 512MB and the crash issue is gone. Thanks.

     

    But still the kernel boot fails. Please see this log file.

    Fullscreen 7610.bootlog_512M.txt Download 
    Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (admin1@admin1-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #2 Fri Sep 30 20:01:34 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 1.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 31904
Kernel command line: console=ttyO0,115200n8 rootwait rw mem=176M earlyprintk notifyk.vpssm3_sva=0x9F900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M root=/dev/
nfs nfsroot=10.10.38.39:/home/admin1/targetfs/ ip=dhcp
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 126MB = 126MB total
Memory: 122260k/122260k available, 57964k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xcb800000 - 0xf8000000   ( 712 MB)
    lowmem  : 0xc0000000 - 0xcb000000   ( 176 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0037000   ( 188 kB)
      .text : 0xc0037000 - 0xc049e000   (4508 kB)
      .data : 0xc049e000 - 0xc04e0d00   ( 268 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
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 IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
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
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy: 
NET: Registered protocol family 16
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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x: probe of 1-0021 failed with error -121
i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)
i2c i2c-1: Can't create device at 0x21
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
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
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 cb80c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
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 cb81e800 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: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
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
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 238
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, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
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 ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
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-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, 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
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0x9f900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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
Detected MACID=0:0:0:0:0:0
ata1: SATA link down (SStatus 0 SControl 300)
mmc0: new SD card at address e624
mmcblk0: mmc0:e624 SD01G 968 MiB 
 mmcblk0: p1 p2

CPSW phy found : id is : 0x282f014
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
....., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.10.38.56
IP-Config: Complete:
     device=eth0, addr=10.10.38.56, mask=255.255.255.0, gw=10.10.38.1,
     host=10.10.38.56, domain=kpit.com, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.10.38.39, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 188K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (77): /proc/77/oom_adj is deprecated, please use /proc/77/oom_score_adj instead.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
ISOFS: Unable to identify CD-ROM format.
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
Root filesystem already rw, not remounting
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card EVM
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
hwclock: can't open '/dev/misc/rtc': No such file or directory
Thu Sep  8 17:37:00 UTC 2011
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
        PRCM for IVHD0 is in Progress, Please wait.....  
                        BW Phy Addr : 0x48180600 Data : 0x00000002
                        AW Phy Addr : 0x48180600 Data : 0x00000002
                        Phy Addr : 0x48180c04 Data : 0x00000037
                        BW Phy Addr : 0x48180620 Data : 0x00070000
                        AW Phy Addr : 0x48180620 Data : 0x00070002
                        BW Phy Addr : 0x48180624 Data : 0x00030000
                        AW Phy Addr : 0x48180624 Data : 0x00010002
                        Phy Addr : 0x48180600 Data : 0x00000102
                        BW Phy Addr : 0x48180c10 Data : 0x00000007
                        AW Phy Addr : 0x48180c10 Data : 0x00000003
                        Phy Addr : 0x48180c14 Data : 0x00000004
                        BW Phy Addr : 0x58088000 Data : 0x7f5adc32
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0x0cc6bac1
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : 0x00000003
                        AW Phy Addr : 0x48180c10 Data : 0x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed 
FATAL: Module syslink not found.
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directory
/dev/syslinkipc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP: No such file or directory
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffff8
Starting telnet daemon.
Loading HDVPSS Firmware
FATAL: Module syslink not found.
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directory
/dev/syslinkipc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP: No such file or directory
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffff8
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
ti81xxfb ti81xxfb: no grpxs
ti81xxfb: probe of ti81xxfb failed with error -22
Configuring fb0 to LCD
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sys/devices/platform/vpss/graphics0/nodes: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sys/devices/platform/vpss/display1/enabled: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sys/devices/platform/vpss/display1/timings: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sys/devices/platform/vpss/display1/output: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sys/devices/platform/vpss/display1/enabled: nonexistent directory
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
cat: write error: No space left on device
cat: write error: No space left on device

  • 0 in reply to Mitul Chokshi
    TI__Mastermind 20245 points

    Hi,

    I have forwarded your query to concerned team. They will respond.

     

    Regards,

    Hardik shah

  • 0 in reply to HardikShah
    TI__Intellectual 2785 points

    Mitul,

        Just for your info"This question is answered" thread may not get attention.

       I think there is only small correction required. The kernel crash is due to the notify address in bootargs (notifyk.vpssm3_sva=0x9F900000) is wrong. This address is same for both 1G and 512M, refer 512M memory map.

      But i want to emphasis that.

        The steps mentioned in http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map#Changing_Memory_Map_For_512MB_Board section is perfectly fine to change the system for 512MB.

         Ensure to use the LISA setting as mentioned in the 512M memory map. and all the parameters are updated as per the required memory map in this doc.

    Best regards

    Velan

  • 0 in reply to Velan
    Intellectual 405 points

    Thanks Velan,

    I checked with notifyk.vpssm3_sva=0xBF900000 also; but the result is same.

    I also verified the LISA settings.

    I've posted the same question on different thread: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/140714/507265.aspx

     

    In the boot log I see following:

    "Error opening /dev/fb0: No such file or directory"

    But /dev/fb0 is present in my targetfs (i.e. /home/admin1/targetfs/dev/fb0)

     

    Boot log also say:

    FATAL: Module syslink not found.

    But syslink module is present in fs.


  • 0 in reply to Mitul Chokshi
    TI__Intellectual 2785 points

    I missed to recognize syslink module missing issue.

    So there are two issues here.

    1. FATAL: Module syslink not found.

    2. notify_shm_drv_sendevent failed! status = 0xfffffff0

        My suggestion had only 2nd issue in mind. But the 2nd issue might happen as a side effect of 1st issue also.

    Even with the prebuilt binaries & Out of box demos) you must not have 1st issue.

    Please use all prebuilt once and see first issue does not happen. you can also

    1. manually try'modprobe syslink'

    2. try lsmod

    3. introduce delay between insmod syslink and next command

    Best Regards

    Velan

  • 0 in reply to Velan
    Intellectual 405 points

    Hi Velan,

     

    I checked with prebuilt uImage but still I get the same error. (FATAL: Module syslink not found.)

    modprobe syslink command also gives same error. But "insmod /lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko" command works correctly.

     

    I don't understand why modprobe fails when syslink module is available in filesystem.

     

  • 0 in reply to Mitul Chokshi
    Intellectual 405 points

    Hi Velan,

    I replaced "modprobe syslink" to "insmod /lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko" in /etc/init.d/load-hdv* files in targetfs. After that kernel is booting fine. See boot log

    Fullscreen 1680.boot_success.txt Download 
    Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@admin1-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #6 Mon Oct 17 16:50:33 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 1.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 31904
Kernel command line: console=ttyO0,115200n8 rootwait rw mem=176M earlyprintk notifyk.vpssm3_sva=0x9F900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M root=/dev/
nfs nfsroot=10.10.38.39:/home/admin1/targetfs/ ip=dhcp
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 126MB = 126MB total
Memory: 122228k/122228k available, 57996k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xcb800000 - 0xf8000000   ( 712 MB)
    lowmem  : 0xc0000000 - 0xcb000000   ( 176 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0037000   ( 188 kB)
      .text : 0xc0037000 - 0xc04a6000   (4540 kB)
      .data : 0xc04a6000 - 0xc04e9400   ( 269 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
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 IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
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
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy: 
NET: Registered protocol family 16
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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x: probe of 1-0021 failed with error -121
i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)
i2c i2c-1: Can't create device at 0x21
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
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
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 cb80c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
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 cb81e800 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: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
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
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 238
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, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
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 ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
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-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, 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
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
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 0x9f900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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
Detected MACID=0:0:0:0:0:0
ata1: SATA link down (SStatus 0 SControl 300)
mmc0: new SD card at address e624
mmcblk0: mmc0:e624 SD01G 968 MiB 
 mmcblk0: p1 p2

CPSW phy found : id is : 0x282f014
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
....., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.10.38.71
IP-Config: Complete:
     device=eth0, addr=10.10.38.71, mask=255.255.255.0, gw=10.10.38.1,
     host=10.10.38.71, domain=kpit.com, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.10.38.39, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 188K
INIT: version 2.86 booting
Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (80): /proc/80/oom_adj is deprecated, please use /proc/80/oom_score_adj instead.
udev: starting version 141
Root filesystem already rw, not remounting
Caching udev devnodes
Populating dev cachetar: dev/.udev/queue/683: No such file or directory
tar: dev/.udev/queue/680: No such file or directory
tar: dev/.udev/queue/671: No such file or directory
tar: dev/.udev/queue/669: No such file or directory
tar: dev/.udev/queue/665: No such file or directory
tar: dev/.udev/queue/663: No such file or directory
tar: dev/.udev/queue/661: No such file or directory
tar: dev/.udev/queue/657: No such file or directory
tar: dev/.udev/queue/654: No such file or directory
tar: error exit delayed from previous errors
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
mv: cannot rename '/tmp/devices': No such file or directory
ISOFS: Unable to identify CD-ROM format.
NET: Registered protocol family 10
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
hwclock: can't open '/dev/misc/rtc': No such file or directory
Thu Sep  8 17:38:00 UTC 2011
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
        PRCM for IVHD0 is in Progress, Please wait.....  
                        BW Phy Addr : 0x48180600 Data : 0x00000002
                        AW Phy Addr : 0x48180600 Data : 0x00000002
                        Phy Addr : 0x48180c04 Data : 0x00000037
                        BW Phy Addr : 0x48180620 Data : 0x00070000
                        AW Phy Addr : 0x48180620 Data : 0x00070002
                        BW Phy Addr : 0x48180624 Data : 0x00030000
                        AW Phy Addr : 0x48180624 Data : 0x00010002
                        Phy Addr : 0x48180600 Data : 0x00000102
                        BW Phy Addr : 0x48180c10 Data : 0x00000007
                        AW Phy Addr : 0x48180c10 Data : 0x00000003
                        Phy Addr : 0x48180c14 Data : 0x00000004
                        BW Phy Addr : 0x58088000 Data : 0x7d5adc33
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0x0ccfbac3
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : 0x00000003
                        AW Phy Addr : 0x48180c10 Data : 0x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed 
SysLink version : 2.00.02.80
SysLink module created on Date:Oct 10 2011 Time:14:36:18
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Starting telnet daemon.
Loading HDVPSS Firmware
insmod: error inserting '/lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko': -1 File exists
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
Configuring fb0 to LCD
cat: write error: No space left on device
cat: write error: No space left on device
HDMI W1 rev 4.0
Starting syslogd/klogd: done
Starting thttpd.
Calibrating touchscreen (first time only)ts_open: No such file or directory
.
Starting Matrix GUI application.

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

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

Arago 2011.05 dm814x-evm ttyO0

dm814x-evm login:
    .

    But still i'm not clear why modprobe syslink fails.

    Also note that "cat /dev/zero > /dev/fb0" gives following error.

    cat: write error: No space left on device

    What could be reason for this?

     

    Regards,

    Mitul

  • 0 in reply to Mitul Chokshi
    TI__Intellectual 2785 points

    Mitul

       It is very strange that modprobe could not fing syslink.ko from /lib/modules directory.

       I suspect that your filesystem is changed compared to the one in the EZSDK release. you could notice SD card boot and nfs boot of EZSDK works if you follow the userguide to setup these.

       The man page for mod probe says

        'modprobe  looks  in  the  module  directory  /lib/modules/`uname  -r`  for  all  the modules and other files, except for the optional  /etc/modprobe.conf  configuration  file  and  /etc/modprobe.d directory'

        You could check your /etc/modprobe.conf and /etc/modprobe.d files if there are any misconfigurations in your filesystem

        I think the error 'cat: write error: No space left on device' during booting is just warning, & you can ignore them, But once booted it should work fine. I think the issue here is due to this command executed before HDVPSS firmware gets loaded.

     

    Best Regards

    Velan


  • 0 in reply to Velan
    Intellectual 405 points

    Hi Velan,

    I checked /etc/modules.conf & /etc/modeprobe.d files, but they looks okay. I'll setup the filesystem again & check.

    cat /dev/zero > /dev/fb0 gives same error even after system is booted and HDVPSS firmware is loaded. But during loading HDVPSS firmware I get following warning.

    "FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
    FIRMWARE: Memory Configuration status : In Progress
    FIRMWARE: 2 start Successful
    cat: write error: No space left on device
    cat: write error: No space left on device"

    Can this warning cause any problem?

     

    Regards,

    Mitul

     

  • 0 in reply to Velan
    Intellectual 405 points

    Velan said:
    It is very strange that modprobe could not fing syslink.ko from /lib/modules directory.

    I ran "depmod -a" and after this modeprobe works properly.