DM8168 EZSDK 5.02 boot issue.

heming zhang

Other Parts Discussed in Thread: PMP

I download ezsdk5.02.01.59 and use mksdboot.sh to created a SD boot fs. While I use this one to boot DM8168 dev board. I have following issue:

"VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)" , and kernel panic.

I use the same way, same 8GB SD card created in ezsdk 5.01 boot the system successfully. I check the SD card not locked.

Then I do the test:

1,mksdboot.sh in ezsdk 5.01, boot no problem;

2,mksdboot.sh in ezsdk 5.02.01.59, boot with kernel panic and same error infor.

What's the different between ezsdk 5.01 and 5.02?

Thanks

over 14 years ago

0 heming zhang over 14 years ago

Prodigy 190 points

Does anybody have a solution?

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

Can you connect the SD card to a linux host and check if the fileystems is present on partition 2 of the SD card?

0 Marcus Cooksey over 14 years ago in reply to Marcus Cooksey

TI__Genius 9510 points

Also can you include the full console logs.

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

Yes. I can mount partition 2 on ubuntu. Check FS, no problem.

I copy uImage under ezsdk5.01 to replace the uImage on ezsdk5.02, system can boot.

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

0 Jun_Zhang over 14 years ago in reply to heming zhang

Expert 2425 points

I have the exactly same problem with the new SDK5.02, even the same error message

Have you found a solution?

Here is the full console logs:

Net:   Detected MACID:90:d7:eb:35:9f:5c
Ethernet PHY: GENERIC @ 0x01
DaVinci EMAC
Hit any key to stop autoboot: 0
BOOTP broadcast 1
DHCP client bound to address 10.0.1.7
Using DaVinci EMAC device
TFTP from server 10.0.1.38; our IP address is 10.0.1.7
Filename 'uImage'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ################
done
Bytes transferred = 2410756 (24c904 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2410692 Bytes = 2.3 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (jun@muxlab) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Sep 1 11:21:51 EDT 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
reserved size = 52428800 at 0
FB: Reserving 52428800 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: 19712
Kernel command line: console=ttyO2,115200n8 root=/dev/nfs nfsroot=10.0.1.38:/home/jun/targetfs,nolock rw mem=128M
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: 78MB = 78MB total
Memory: 73528k/73528k available, 57544k 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)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0038000   ( 192 kB)
      .text : 0xc0038000 - 0xc0492000   (4456 kB)
      .data : 0xc0492000 - 0xc04d89c0   ( 283 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 GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_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
NOR: Can't request GPMC CS
registered ti816x_vpss device
registered ti816x_gpio_vr device
registered TI816x on-chip HDMI device
registered ti816x_sr device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
ti816x_pcie: Invoking PCI BIOS...
ti816x_pcie: Setting up Host Controller...
ti816x_pcie: Register base mapped @0xc8820000
ti816x_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
regulator: VFB: 800 <--> 1025 mV at 1010 mV
vgaarb: loaded
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
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 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
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
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 c880c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
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 c881e800 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 143
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 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
m25p80 spi1.0: found m25p05-nonjedec, expected w25x32
m25p80 spi1.0: m25p05-nonjedec (64 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
mtd: partition "U-Boot" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
0x000000010000-0x000000012000 : "U-Boot Env"
mtd: partition "U-Boot Env" is out of reach -- disabled
0x000000000000-0x000000280000 : "Kernel"
mtd: partition "Kernel" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
0x000000010000-0x000000010000 : "File System"
mtd: partition "File System" is out of reach -- disabled
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-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 fffffff9
davinci_mdio.0: probed
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
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
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
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
smartreflex smartreflex: Driver initialized
ata2: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00              64 mtdblock0 (driver?)
1f02              64 mtdblock2 (driver?)
1f04            2432 mtdblock4 (driver?)
1f05             128 mtdblock5 (driver?)
1f06            4352 mtdblock6 (driver?)
1f07          204928 mtdblock7 (driver?)
1f08           50304 mtdblock8 (driver?)
b300         7761920 mmcblk0 driver: mmcblk
b301           40131 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302          883575 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
b303         6835657 mmcblk0p3 00000000-0000-0000-0000-000000000mmcblk0p3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0046b44>] (dump_backtrace+0x0/0x110) from [<c0364b48>] (dump_stack+0x18/0x1c)
r7:c4812000 r6:00000000 r5:c002c014 r4:c04d9110
[<c0364b30>] (dump_stack+0x0/0x1c) from [<c0364bac>] (panic+0x60/0x17c)
[<c0364b4c>] (panic+0x0/0x17c) from [<c0009254>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:c4825f58 r0:c041a99c
[<c0009074>] (mount_block_root+0x0/0x220) from [<c0009340>] (mount_root+0xac/0xcc)
[<c0009294>] (mount_root+0x0/0xcc) from [<c00094d0>] (prepare_namespace+0x170/0x1d4)
r4:c04d8a24
[<c0009360>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/0x154)
r5:c0008670 r4:c04d89c0
[<c0008670>] (kernel_init+0x0/0x154) from [<c006aeec>] (do_exit+0x0/0x5e4)
r5:c0008670 r4:00000000

0 Marcus Cooksey over 14 years ago in reply to Jun_Zhang

TI__Genius 9510 points

I'm trying to reproduce the problem on my system.

0 MarcPyne over 14 years ago

TI__Mastermind 25055 points

Please refer to the EZSDK Release Notes for info and differences of each release version.

Regards,
Marc

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

I'm not be able to observed the problems you report. Are you running with the pre-built binaries?

0 Marcus Cooksey over 14 years ago in reply to Marcus Cooksey

TI__Genius 9510 points

Jun Zhang73904

Your issue seems to be related to NFS directory not found. Be sure that you're able to ping the NFS server from your Netra board and that the filesystem is exported in the /etc/exports file (also you must restart on the host machine).

0 heming zhang over 14 years ago in reply to MarcPyne

Prodigy 190 points

in the release notes, it says need to upgrade the u-boot.

Do I have to upgrade the u-boot? It's a little dangerous because I don't have a tools to fix the flash problem in case upgrade u-boot fail.

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

Can you try boot from the SD card?

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

at first, I 'm running the pre-build version.

After it have the problem, I rebuild the kernel and make all. The problem is the same.

Does my SD card have some compatibility problem? Do I have to use a specific SD card?

Thanks,

Heming

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

Still not boot.

I just copy 5.01 uImage to replace 5.02 uImage, it boot successflully. But the system has other error.

I think the uImage in 5.02 has some changes. Any clue?

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

Still not boot.

I just copy 5.01 uImage to replace 5.02 uImage, it boot successflully. But the system has other error.

I think the uImage in 5.02 has some changes. Any clue?

Marcus Cooksey said:

Can you try boot from the SD card?

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

Is you base EVM a DDR3 or DDR2 board?

0 Jun_Zhang over 14 years ago in reply to Marcus Cooksey

Expert 2425 points

after updating the uboot, as suggested by the release note

I cannot boot the EVM anymore:

Bytes transferred = 2410936 (24c9b8 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Arago/2.6.37-psp04.00.00.12/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2410872 Bytes = 2.3 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

(stuck on here)

0 Marcus Cooksey over 14 years ago in reply to Jun_Zhang

TI__Genius 9510 points

Can you also include the uboot logs and dump of the uboot environment variable? BTW - which u-boot images and kernel are you using.

0 Michael Risley over 14 years ago in reply to Marcus Cooksey

TI__Expert 5215 points

Jun,

Could you also try using these bootargs:

setenv bootcmd 'mmc init;fatload mmc 0 0x82000000 uImage;bootm 0x82000000'
setenv bootargs 'console=ttyO2,115200n8 rootwait rw mem=100M earlyprintk root=/dev/mmcblk0p2 rootfstype=ext3 ip=off'
boot

0 Jun_Zhang over 14 years ago in reply to Marcus Cooksey

Expert 2425 points

Thanks Marcus,

As in the EZSDK 5.01, I let the EVM booting from NFS and everything works fine in the EZSDK 5.01.

With the EZSDK 5.02, I have not successfully do this yet. I am using the linux kernel and uboot images generated by the "Make u-boot" and 'Make linux' commands.

I tried difference bootargs, and if i add "notifyk.vpssm3_sva=0xBF900000" into the bootargs,

the booting process will hang on the "Uncompressing Linux... done, booting the kernel.", as shown in my last post.

And if I delete this bootargs, the booting process will be stuck on "unable to mount root fs" .

VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00             256 mtdblock0 (driver?)
1f01               8 mtdblock1 (driver?)
1f02            2560 mtdblock2 (driver?)
1f03            1272 mtdblock3 (driver?)
1f04            2432 mtdblock4 (driver?)
1f05             128 mtdblock5 (driver?)
1f06            4352 mtdblock6 (driver?)
1f07          204928 mtdblock7 (driver?)
1f08           50304 mtdblock8 (driver?)
b300         7823360 mmcblk0 driver: mmcblk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
Backtrace:
[<c0046b44>] (dump_backtrace+0x0/0x110) from [<c0364b48>] (dump_stack+0x18/0x1c)
r7:cc812000 r6:00000000 r5:c002c014 r4:c04d9110
[<c0364b30>] (dump_stack+0x0/0x1c) from [<c0364bac>] (panic+0x60/0x17c)
[<c0364b4c>] (panic+0x0/0x17c) from [<c0009254>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:cc82bf58 r0:c041a9dc
[<c0009074>] (mount_block_root+0x0/0x220) from [<c0009340>] (mount_root+0xac/0xcc)
[<c0009294>] (mount_root+0x0/0xcc) from [<c00094d0>] (prepare_namespace+0x170/0x1d4)
r4:c04d8a24
[<c0009360>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/0x154)
r5:c0008670 r4:c04d89c0
[<c0008670>] (kernel_init+0x0/0x154) from [<c006aeec>] (do_exit+0x0/0x5e4)
r5:c0008670 r4:00000000

0 Jun_Zhang over 14 years ago in reply to Michael Risley

Expert 2425 points

Hi Michael,

With the bootargs you suggested, I can let the evm boot.

However, this is the uImage and kernel stored in the SD card right? I didnot update them after the release of EZSDK 5.02.

0 Michael Risley over 14 years ago in reply to Jun_Zhang

TI__Expert 5215 points

Jun,

Right.

If you have a spare SD card, could you try loading these new images you built from 5.02. This way we could eliminate it down to a kernel / NFS issue.

So if I understand correctly, your 5.01 worked just fine - but you built uImage within 5.02 & replaced the 5.01 uImage over NFS? Did you also update the MLO? Same filesystem?

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

The problem could be that the default AVS settings (configured by GPIO) are not set properly in order to have the correct core voltage level.

Please try the attached uImage which disables the AVS driver.http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/717/7080.uImage_2D00_dm816x_2D00_evm.bin

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

Please see the proposed solution.

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/132039/474551.aspx#474551

0 heming zhang over 14 years ago in reply to Michael Risley

Prodigy 190 points

With the bootargs, I have the same problem. Still cannot boot.

Michael Risley said:

Jun,

Could you also try using these bootargs:

setenv bootcmd 'mmc init;fatload mmc 0 0x82000000 uImage;bootm 0x82000000'
setenv bootargs 'console=ttyO2,115200n8 rootwait rw mem=100M earlyprintk root=/dev/mmcblk0p2 rootfstype=ext3 ip=off'
boot

0 heming zhang over 14 years ago in reply to Marcus Cooksey

Prodigy 190 points

This uImage work fine for me. Could you let me know how I can build my uImage? I did make menuconfig in linux folder, which config I should change?

Thanks a lot!

Marcus Cooksey said:

The problem could be that the default AVS settings (configured by GPIO) are not set properly in order to have the correct core voltage level.

Please try the attached uImage which disables the AVS driver.http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/717/7080.uImage_2D00_dm816x_2D00_evm.bin

0 Marcus Cooksey over 14 years ago in reply to heming zhang

TI__Genius 9510 points

The PSP user guide (under board-support/psp) provides detailed information on how to disable the AVS.

0 pubesh r over 14 years ago in reply to Marcus Cooksey

Prodigy 210 points

Hi Marcus,

We are using DM8168 with DDR3 and EZSDK 5.02, We are trying to load the uImage after tftp done via NFS boot.

the booting process will hang on the "Uncompressing Linux... done, booting the kernel."

Then we tried your uImage also, it is same problem still. anything we missing?

Can you help us?

Thanks & Regards,

Pubesh.R

0 pubesh r over 14 years ago in reply to pubesh r

Prodigy 210 points

Hi All,

We are facing the issue while loading kernel, after TFTP done for uImage.

Currently we are using DDR3 support EVM DM8168 and EZSDK_5_02.

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Mon Aug 29 21:39:54 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
reserved size = 52428800 at 0
FB: Reserving 52428800 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: 79656
Kernel command line: console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=172.17.1.16:/home/cornet/targetfs,udp,v3,rsize=4096,wsi6
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: 314MB = 314MB total
Memory: 313004k/313004k available, 59732k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd7000000 - 0xf8000000   ( 528 MB)
    lowmem : 0xc0000000 - 0xd6c00000   ( 364 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0038000   ( 192 kB)
      .text : 0xc0038000 - 0xc0492000   (4456 kB)
      .data : 0xc0492000 - 0xc04d89c0   ( 283 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 GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_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
NOR: Can't request GPMC CS
registered ti816x_vpss device
registered ti816x_gpio_vr device
registered TI816x on-chip HDMI device
registered ti816x_sr device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
ti816x_pcie: Invoking PCI BIOS...
ti816x_pcie: Setting up Host Controller...
ti816x_pcie: Register base mapped @0xd7020000
ti816x_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
regulator: VFB: 800 <--> 1025 mV at 1010 mV
vgaarb: loaded
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
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 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
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
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 d700c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
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 d701e800 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.
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 611
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 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
m25p80 spi1.0: w25x32 (4096 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000042000 : "U-Boot Env"
0x000000042000-0x0000002c2000 : "Kernel"
0x0000002c2000-0x000000400000 : "File System"
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-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 fffffff9
davinci_mdio.0: probed
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
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
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
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
smartreflex smartreflex: Driver initialized
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP and RARP requests ..
PHY: 0:01 - Link is Up - 1000/Full
DHCP/BOOTP: Reply not for us, op[2] xid[9cf79388]
....
DHCP/BOOTP: Reply not for us, op[2] xid[cc8058a6]
timed out!
IP-Config: Retrying forever (NFS root)...
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP and RARP requests .
PHY: 0:01 - Link is Up - 1000/Full
..
DHCP/BOOTP: Ignoring delayed packet
., OK
IP-Config: Got DHCP answer from 172.17.0.3, my address is 172.17.2.10
IP-Config: Complete:
     device=eth0, addr=172.17.2.10, mask=255.255.0.0, gw=172.17.0.3,
     host=dm8168_streamer1, domain=cornet, nis-domain=(none),
     bootserver=172.17.0.3, rootserver=172.17.1.16, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 192K
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 cachemv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
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.
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
Tue Aug 30 00: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
DM816X 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 : 0x00478d26
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data EXT3-fs: barriers not enabled
: 0x4ba42c0a
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : kjournald starting. Commit interval 5 seconds
0x00000003
                        AEXT3-fs (mmcblk0p2): W Phy Addr : 0x4warning: maximal mount count reached, running e2fsck is recomm0
x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully
        PRCM for IVHD1 is in Progress, Please wait.....
                        BW Phy AddEXT3-fs (mmcblk0p2): r : 0x48180700 Dusing internal journalata : 0x00000002

                        AW Phy AddrEXT3-fs (mmcblk0p2): : 0x48180700 Darecovery completeta : 0x00000002

                        Phy Addr : 0EXT3-fs (mmcblk0p2): x48180d04 Data :mounted filesystem with writeback data mode 0x000007

BW Phy Addr : 0x48180720 Data : 0x00070000
                        AW Phy Addr : 0x48180720 Data : 0x00050002
                        BW Phy Addr : 0x48180724 Data : 0x00030000
                        AW Phy Addr : 0x48180724 Data : 0x00010002
                        Phy Addr : 0x48180700 Data : 0x00000102
                        BW Phy Addr : 0x48180d10EXT3-fs: barriers not enabled
Data : 0x000000kjournald starting. Commit interval 5 seconds
07
                        AW Phy AdEXT3-fs (mmcblk0p3): dr : 0x48180d10 warning: maximal mount count reached, running e2fsck i0
3
                        Phy Addr : 0x48180d14 Data : 0x00000004
                        BW Phy Addr : 0x5a088000 Data : 0x00e7eb33
                        AW Phy Addr : 0x5a088000 Data : 0xeafffffe
                        BW Phy Addr : 0x5a098000 Data : 0xa0431900
                        AW Phy Addr : 0x5a098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180d10 Data : 0x00000003
                        AW Phy Addr : 0x48180d10 Data : 0x00000000
                        Phy Addr : 0x48180d14 Data : 0x00000007
        PRCM for IVHD1 is Done Successfully
        PRCM for IVHD2 is in Progress, Please wait.....
                        BW Phy Addr : 0x48180800 Data : 0x00000002
                        AW Phy Addr : 0x48180800 Data : 0x00000002
                        Phy Addr : 0x48180e04 Data : 0x00000037
                        BW Phy Addr : 0x48180820 Data : 0x00070000
                        AW Phy Addr : 0x48180820 Data : 0x00050002
                        BW Phy Addr : 0x48180824 Data : 0x00030000
                        AW Phy Addr : 0x48180824 Data : 0x00010002
                        Phy AdEXT3-fs (mmcblk0p3): dr : 0x48180800 using internal journalData : 0x0000010
2
                        BW Phy AddEXT3-fs (mmcblk0p3): r : 0x48180e10 Drecovery completeata : 0x00000007

                        AW Phy AddrEXT3-fs (mmcblk0p3): : 0x48180e10 Damounted filesystem with writeback data modeta : 0x003

                        Phy Addr : 0x48180e14 Data : 0x00000004
                        BW Phy Addr : 0x53088000 Data : 0xda3a98ae
                        AW Phy Addr : 0x53088000 Data : 0xeafffffe
                        BW Phy Addr : 0x53098000 Data : 0xb709ddfb
                        AW Phy Addr : 0x53098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180e10 Data : 0x00000003
                        AW Phy Addr : 0x48180e10 Data : 0x00000000
                        Phy Addr : 0x48180e14 Data : 0x00000007
        PRCM for IVHD2 is Done Successfully
PRCM Initialization completed
SysLink version : 2.00.02.80
SysLink module created on Date:Aug 29 2011 Time:22:30:41
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
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
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
open /dev/fb0: No such file or directory
cat: write error: No space left on device
cat: write error: No space left on device
HDMI W1 rev 2.0
Unable to handle kernel NULL pointer dereference at virtual address 00000140
pgd = d2768000
[00000140] *pgd=9277b031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
last sysfs file: /sys/module/vpss/initstate
Modules linked in: ti81xxhdmi(+) ti81xxfb vpss syslink ipv6
CPU: 0    Not tainted (2.6.37 #1)
PC is at TI81xx_register_display_panel+0x44/0xfc [vpss]
LR is at init_module+0x274/0x3b4 [ti81xxhdmi]
pc : [<bf18daec>]    lr : [<bf1b8274>]    psr: a0000013
sp : d2d43f10 ip : d2d43f30 fp : d2d43f2c
r10: 00000000 r9 : d2d42000 r8 : bf1b8000
r7 : 40044000 r6 : 00000000 r5 : bf1b491c r4 : 00000000
r3 : 00000000 r2 : bf198b68 r1 : bf1b491c r0 : bf1b46e0
Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 92768019 DAC: 00000015
Process modprobe (pid: 1089, stack limit = 0xd2d422e8)
Stack: (0xd2d43f10 to 0xd2d44000)
3f00:                                     00000000 bf1b4894 0001b018 40044000
3f20: d2d43f44 d2d43f30 bf1b8274 bf18dab4 00000000 bf1b4770 d2d43f7c d2d43f48
3f40: c00383d8 bf1b800c bf1b4770 0001b018 40044000 c0042f48 00000000 bf1b4770
3f60: 0001b018 40044000 c0042f48 00000000 d2d43fa4 d2d43f80 c0092b5c c0038314
3f80: c00bd750 c00bd668 0001b070 0001b018 00000000 00000080 00000000 d2d43fa8
3fa0: c0042da0 c0092acc 0001b070 0001b018 40044000 00005828 0001b018 0001ac94
3fc0: 0001b070 0001b018 00000000 00000080 0001b008 bee71bf4 00000000 bee71bf4
3fe0: 0001b198 bee718dc 0000b678 401687d4 60000010 40044000 00000000 00010074
Backtrace:
[<bf18daa8>] (TI81xx_register_display_panel+0x0/0xfc [vpss]) from [<bf1b8274>] (init_module+0x274/0x3b4 [ti81xxhdmi])
r7:40044000 r6:0001b018 r5:bf1b4894 r4:00000000
[<bf1b8000>] (init_module+0x0/0x3b4 [ti81xxhdmi]) from [<c00383d8>] (do_one_initcall+0xd0/0x1a4)
r5:bf1b4770 r4:00000000
[<c0038308>] (do_one_initcall+0x0/0x1a4) from [<c0092b5c>] (sys_init_module+0x9c/0x1bc)
[<c0092ac0>] (sys_init_module+0x0/0x1bc) from [<c0042da0>] (ret_fast_syscall+0x0/0x30)
r7:00000080 r6:00000000 r5:0001b018 r4:0001b070
Code: e89da8f0 e59f20b0 e5906000 e5923000 (e5d33140)
---[ end trace c3ae7360285c8983 ]---
Segmentation fault
Starting syslogd/klogd: done
Starting thttpd.
ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device
ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device
expr: syntax error
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven

Usage: fbset [options] [mode]

Valid options:
General options:
    -h, --help         : display this usage information
    --test             : don't change, just test whether the mode is valid
    -s, --show         : display video mode settings
    -i, --info         : display all frame buffer information
    -v, --verbose      : verbose mode
    -V, --version      : print version information
    -x, --xfree86      : XFree86 compatibility mode
    -a, --all          : change all virtual consoles on this device
Frame buffer special device nodes:
    -fb <device>       : processed frame buffer device
                         (default is /dev/fb0)
Video mode database:
    -db <file>         : video mode database file
                         (default is /etc/fb.modes)
Display geometry:
    -xres <value>      : horizontal resolution (in pixels)
    -yres <value>      : vertical resolution (in pixels)
    -vxres <value>     : virtual horizontal resolution (in pixels)
    -vyres <value>     : virtual vertical resolution (in pixels)
    -depth <value>     : display depth (in bits per pixel)
    -nonstd <value>    : select nonstandard video mode
    -g, --geometry ... : set all geometry parameters at once
    -match             : set virtual vertical resolution by virtual resolution
Display timings:
    -pixclock <value> : pixel clock (in picoseconds)
    -left <value>      : left margin (in pixels)
    -right <value>     : right margin (in pixels)
    -upper <value>     : upper margin (in pixel lines)
    -lower <value>     : lower margin (in pixel lines)
    -hslen <value>     : horizontal sync length (in pixels)
    -vslen <value>     : vertical sync length (in pixel lines)
    -t, --timings ... : set all timing parameters at once
Display flags:
    -accel <value>     : haomaplfb: OMAPLFB_Init: OMAPLFBInit failed
rdware text acceleration enable (false or true)
    -hsync <value>     : horizontal sync polarity (low or high)
    -vsync <value>     : vertical sync polarity (low or high)
    -csync <value>     : composite sync polarity (low or high)
    -gsync <value>     : synch on green (false or true)
    -extsync <value>   : external sync enable (false or true)
    -bcast <value>     : broadcast enable (false or true)
    -laced <value>     : interlace enable (false or true)
    -double <value>    : doublescan enable (false or true)
    -rgba <r,g,b,a>    : recommended length of color entries
    -grayscale <value> : grayscale enable (false or true)
Display positioning:
    -move <direction> : move the visible part (left, right, up or down)
    -step <value>      : step increment (in pixels or pixel lines)
                         (default is 8 horizontal, 2 vertical)
Starting PVR
FATAL: Error inserting omaplfb (/lib/modules/2.6.37/kernel/drivers/gpu/pvr/omaplfb.ko): No such device
/dev/mem opened.
Memory mapped at address 0x402c2000.
Read at address 0x48180F04 (0x402c2f04): 0x00000001
Write at address 0x48180F04 (0x402c2f04): 0x00000000, readback 0x00000000
/dev/mem opened.
Memory mapped at address 0x40281000.
Read at address 0x48180900 (0x40281900): 0x00000102
Write at address 0x48180900 (0x40281900): 0x00000002, readback 0x00000002
/dev/mem opened.
Memory mapped at address 0x400d5000.
Read at address 0x48180920 (0x400d5920): 0x00040002
Write at address 0x48180920 (0x400d5920): 0x00000002, readback 0x00000002
Starting Matrix GUI application.

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

Arago Project http://arago-project.org dm816x-evm ttyO2

Arago 2011.05 dm816x-evm ttyO2

dm816x-evm login:

Is it correct uImage or need to check as well u boot also?

Boot Args: (NFS boot Mode)

setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=172.17.1.16:/home/cornet/targetfs,udp,v3,rsize=4096,wsize=1400 ip=172.17.1.10:172.17.1.255:172.17.0.3:255.255.0.0:dm8168_streamer1::off mem=364M mem=324@0x9F900000 mtdparts=davinci-nand.0:512k(ubl),128k(uboot-env),512k(uboot),2m(kernel),-(app) eth=$(ethaddr),notifyk.vpssm3_sva=0xBF900000 insmod vpss.ko sbufaddr=0xBFB00000 insmod cmemk.ko phys_start=0x96C00000 phys_end=0x98000000 pools=20x4096'

When run the ./capture_encode_a8host_debug.xv5T -o sample.h264 -m 1080p -f 60 -b 1000000 -n 1000

Getting the following errors.

root@dm816x-evm:~# ./capture_encode_a8host_debug.xv5T -o sample_memissue.h264 -m
1080p -f 60 -b 1000000 -n 1000
output file: sample_memissue.h264
bit_rate: 1000000
frame_rate: 60
num_frames: 1000
mode: 1080p
Capture-Encode example
===============================
OMX_Init complenotify_shm_drv_sendevent failed! status = 0xfffffff0ted

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

Please any one help us...

Thanks & Regards,

Pubesh.R

0 DaveB123 over 13 years ago in reply to pubesh r

TI__Expert 4745 points

This thread is marked as the "Question was answered."

I have the same issue as the post immediately preceding...wondering what was the resolution?

0 heming zhang over 13 years ago in reply to DaveB123

Prodigy 190 points

1, configure linux kernel disable AVS;

2, recompile linux kernel;

After this, it works.

DaveB123 said:

This thread is marked as the "Question was answered."

I have the same issue as the post immediately preceding...wondering what was the resolution?

0 I Jeffray over 13 years ago in reply to DaveB123

Intellectual 700 points

DaveB123 said:

This thread is marked as the "Question was answered."

I have the same issue as the post immediately preceding...wondering what was the resolution?

For me, the error with "notify_shm_drv_sendevent failed! status = 0xfffffff0" was resolved by adding a delay after loading the M3 firmware to the HDVPSS before inserting the hdvpss Linux kernel module. I guess the M3 needs an (unspecified?) amount of time to start up.

0 hutchman over 13 years ago in reply to I Jeffray

Expert 1100 points

I have DDR2 EVM and with the newer PSP's (psp04.00.00.10 & 04.00.00.12 for example) I am not able to boot from the SD Card if I update MLO and u-boot.

Before you say MLO is the problem not being first file in FAT ... I already know that one (been using BeagleBoard since 2008 so I've been around the block a few times).

First, I modified u-boot according to the release notes to make u-boot work with DDR2:

This section described how to modify the U-Boot source to enable DDR2 support.
• Open the file arch/arm/include/asm/arch-

ti81xx/clocks_ti816x.h and
modify the #define as shown below
#define DDR_PLL_400
/* Values supported 400,531,675,796 */
• Open the file include/configs/ti8168_evm.h and make sure that the
config option for DDR2 is not commented and
that for DDR3 is commented out as shown below
[...]
//#define CONFIG_TI816X_EVM_DDR3
U-Boot */
#define CONFIG_TI816X_EVM_DDR2
U-Boot */
[...]
/* Configure DDR3 in
/* Configure DDR2 in

I built MLO first (1st stage loader)

Used NAND u-boot build for 2nd stage loader

Copied my new MLO, u-boot.bin (from NAND build), and rootfs to a directory on my Ubuntu box and ran the mksd-ti816x.sh on a brand new virgin SD Card.

Verified boot & rootfs were setup right. The script doesn't create a boot.scr so I created one and also tried to use the boot.scr that came with the DDR3 EVM SD Card (I have both DDR2 & DDR3 EVM).

Verified dip switches are all correct and this is what I get when I try to boot from SD Card:

U-Boot 2010.06 (Oct 28 2011 - 16:28:13)

DRAM: 2 GiB
Using default environment

Hit any key to stop autoboot: 0

I've tried all I can think of. I'm starting to think that getting the DDR2 EVM to run with new u-boot requires more than what the release notes say!

I can run DDR3 based board from NOR flash just fine but can't use this new code (even though it is modified for DDR2) in a DDR2 EVM for some reason.

Regards,

Brian

0 Faiyaz Pisuwala over 13 years ago in reply to Marcus Cooksey

Prodigy 60 points

Hi Marcus,

We are using DM8168 in our product and we have set the Core AVS voltage at 0.955V (P.S. we have used a different Core Voltage regulator than EVM, which controls Core AVS via PMBus).

When we tried to boot our system from SD card, we faced the same mmc I/O errors as reported by heming zhang in this post. We found this post and lifted the Core AVS voltage by some 35 mV, and then found that the mmc errors were gone. I am trying to find out what is the relating between Core AVS voltage of 8168 and SD Card interface performance? Could there be any relation between performance of other interfaces/modules with 1V Core AVS or 1V Constant supply values?

Our ARM core is running at 987 MHz and DDR3 is running at ~800 MHz. What vaule of 1V Core AVS and 1V constant should we set for best performance?

Thanks

Faiyaz

0 InCheol Park over 12 years ago

Prodigy 20 points

Please, Check your SD-Card Lock key.

In my case, SD-Card write protection key is locked.

Processors

Processors forum

DM8168 EZSDK 5.02 boot issue.