Da Vinci record

Source: Internet
Author: User
Tags sdo

The uboot variable is applicable to dm3730 omap3530.

Setenv bootargs console = ttys2, 115200n8 ubi. MTD = 4 root = ubi0: rootfs rootfstype = ubifs Video = omapfb: Mode: 4. 3inch _ LCD mem = 80 m

Setenv bootcmd NAND read. I 80300000 280000 300000 \; bootm 80300000

Error in Porting dvsdk onto devkit8000. error his "insmod: cannot insert 'dsplinkk. ko': Unknown symbol in module, or unknown parameter"

Hello Sanjeev premi, let me explain the procedure I followed in breif.

We have purchased devkit8000 borad from timll, which use
Omap3530 processor. They have just a provided dvsdk demo version which has precomplied files in it.

We thought of porting Ti dvsdk onto devkit8000, so that we can use encoders. to port Ti dvsdk onto devkit8000, We need to generate MLO, u-boot.bin, and uimage for devkit8000. when I searched how to generate and I got some patch files for devkit8000, which
Has 2 patch files in it one to generate uboot. Bin and another to generate uimage

Http://code.google.com/p/devkit8000-unofficial-patches/downloads/list

Uboot patch file was for DVSDK-3.01 and uimage patch file was for DVSDK-3.00.

In DVSDK-3.00 there was no configuration file only for devkit 8000 So again I downloaded DVSDK-3.01 and extracted the U-boot source code which has configuration file for devkit8000 and used it. I just used the MLO file which I got in dvsdk demo version only

Steps I used to rebuilt U-boot (from dvsdk 3.00)
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm distclean
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm devkit8000_config
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm
U-boot.bin was generated without any errors.

Steps I used to rebuilt the Linux kernel (from dvsdks 3.01)
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm distclean
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm omap3_devkit8000_defconfig
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm menuconfig
Host $ make cross_compile = arm-None-Linux-gnueabi-arch = arm uimage modules
Uimage was generated successfully without any errors.

Then steps I used to rebuilt the dvsdk software for the target (from dvsdk 3.01)
Host $ CD/home/<useracct>/dvsdk/dvsdk_3_00_02_44
Host $ make check
Host $ make info
Host $ make clean
Host $ make all

All files were generated without error.

Then copied MLO, u-boot.bin and uimage to one partition of the memory card and NFS to another partition of the memory card, then finally I did
Host $ make install.
It replaced some files in the memory card as follows
Root @ cedt-desktop:/home/cedt/dvsdk/dvsdk_3_00_02_44 # make install

 

Creating/Media/file/opt/dvsdk/omap3530
Installing dvsdk demos ..
Make-C/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530 install
Make [1]: Entering directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530'

Executing make install in subdirectory deCODE /...
Make [2]: Entering directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530/decode'

Installed decode binaries to/Media/file/opt/dvsdk/omap3530 ..
Make [2]: Leaving directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530/decode'

Executing make install in subdirectory interface /...
Make [2]: Entering directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530/interface'

Installed interface binaries to/Media/file/opt/dvsdk/omap3530 ..
Make [2]: Leaving directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530/interface'

Make [2]: Entering directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/data'

Installing fonts in/Media/file/opt/dvsdk/omap3530/data/fonts...

Installing pictures in/Media/file/opt/dvsdk/omap3530/data/pics...

Installing sounds in/Media/file/opt/dvsdk/omap3530/data/sounds...

Installing sounds in/Media/file/opt/dvsdk/omap3530/data/videos...
Make [2]: Leaving directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/data'
Make [1]: Leaving directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/dvsdk_demos_3_00_01_13/omap3530'
Installing clips ..
Make-C clips install
Make [1]: Entering directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/clips'

Installing sounds in/Media/file/opt/dvsdk/omap3530/data/sounds...

Installing sounds in/Media/file/opt/dvsdk/omap3530/data/videos...

Installing sounds in/Media/file/opt/dvsdk/omap3530/data/images...
Make [1]: Leaving directory '/home/cedt/dvsdk/dvsdk_3_00_02_44/clips'

Copying kernel modules to target file system:/Media/file/opt/dvsdk/omap3530/
Copying cmemk. Ko
Copying dsplinkk. Ko
Copying lpm_omap3530.ko
Copying sdmak. Ko
Copying codec servers from/home/cedt/dvsdk/dvsdk_3_00_02_44/cs1omap1__000000_01

Then started booting up devkit8000 through memory card.

Boot parameters are as follows

Omap3 devkit8000 # printenv
Bootdelay = 3
Baudrate = 115200
Ipaddr = 192.168.1.177
Serverip = 192.168.1.121
Gatewayip = 192.168.1.1
Netmask = 255.255.255.0
Ethaddr = 02: Fa: 09: 02: 00: 15
Bootargs = console = ttys2, 115200n8 root =/dev/mmcblk0p2 rootdelay = 1 mem = 99 m
Bootcmd = MMC Init; fatload MMC 0 82000000 uimage; bootm 82000000
Bootfile = "uimage"
Stdin = serial
Stdout = serial
Stderr = serial
Dieid # = 148a000400000000040365fa09020015
Ethact = dm9000

Environment size: 389/131068 bytes

 

Omap3 devkit8000 # boot
Mmc1 is available
Reading uimage

2152300 bytes read
# Booting kernel from legacy image at 82000000...
Image name: Linux-2.6.29-rc3-omap1
Image Type: ARM Linux kernel image (uncompressed)
Data size: 2152236 bytes = 2.1 MB
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.29-rc3-omap1 (root @ cedt) (GCC version 4.2.1 (codesourcery sourcery g ++ lite 2007q3-51) #1 Thu May 5 11:54:49 ist 2011
CPU: armv7 processor [411fc083] Revision 3 (armv7), Cr = 10c5387f
CPU: vipt nonaliasing data cache, vipt nonaliasing Instruction Cache
MACHINE: omap3 devkit8000 Board
Memory Policy: ECC disabled, data cache writeback
Omap3430 es3.1 (full speed SGX, iva2)
SRAM: mapped PA 0x40200000 to VA 0xd7000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 25146
Kernel command line: Console = ttys2, 115200n8 root =/dev/mmcblk0p2 rootdelay = 1 mem = 99 m
Clocking rate (Crystal/DPLL/MPU core): 26.0/266/500 MHz
Iva2 clocking rate: 360 MHz
Reprogramming SDRC
Dpll3_m2_clk Rate Change failed:-22
Gpmc revision 5.0
IRQ: found an intc at 0xd8200000 (Revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
Omap34xx gpio hardware version 2.5
PID hash table entries: 512 (Order: 9, 2048 bytes)
OMAP clockevent Source: gptimer12 at 32768Hz
Console: Color dummy device 80x30
Dentry cache hash table entries: 16384 (Order: 4, 65536 bytes)
Inode-Cache hash table entries: 8192 (Order: 3, 32768 bytes)
Memory: 99 MB = 99 MB total
Memory: 95772kb available (3964 K code, 362 K data, 156 K init)
Calibrating delay loop... 515.72 bogomips (lpj = 2015232)
Mount-Cache hash table entries: 512
CPU: Testing write buffer coherency: OK
Net_namespace: 520 bytes
Net: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Omap3evmdc: Driver Registration complete
Omap dma hardware re vision 4.0
USB: no board-specific platform config found
Omap dss Rev. 2.0
OMAP dispc Rev. 3.0
OMAP Venc REV 2
Bio: Create slab <bio-0> at 0
I2c_omap i2c_omap.1: Buses 1 rev3.12 at 2600 kHz
Twl4030: PIH (IRQ 7) chaining irqs 368 .. 375
Twl4030: Power (IRQ 373) chaining irqs 376 .. 383
Twl4030: gpio (IRQ 368) chaining irqs 384 .. 401
I2c_omap i2c_omap.2: Buses 2 rev3.12 at 400 kHz
I2c_omap i2c_omap.3: Bus 3 rev3.12 at 400 kHz
SCSI subsystem initialized
Twl4030_usb twl4030_usb: initialized twl4030 USB Module
Usbcore: registered new interface driver usbfs
Usbcore: registered new interface driver Hub
Usbcore: registered new device driver USB
Musb_hdrc: version 6.0, Musb-DMA, host, DEBUG = 0
Musb_hdrc: USB Host Mode Controller at d80ab000 using DMA, IRQ 92
Musb_hdrc: Musb HDRC host driver
Musb_hdrc: new USB bus registered, assigned bus number 1
USB usb1: configuration #1 chosen from 1 choice
Hub 1-. 0: USB hub found
Hub 1-0: 1 port Detected
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
Net: Registered protocol family 1
Netwinder floating point emulator v0.97 (Double Precision)
VFS: disk quotas dquot_6.5.2
Dquot-Cache hash table entries: 1024 (order 0, 4096 bytes)
Jffs2 Version 2.2. (NAND) 2001-2006 Red Hat, Inc.
Ms gmni has been set to 187
ALG: no test for stdrng (krng)
Io scheduler Noop registered
Io scheduler anticipatory registered (default)
Io scheduler deadline registered
Io scheduler CFQ registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Serial8250.0: ttys0 at mmio 0x4806a000 (IRQ = 72) is a st16654
Serial8250.0: ttys1 at mmio 0x4806c000 (IRQ = 73) is a st16654
Serial8250.0: ttys2 at mmio 0x49020000 (IRQ = 74) is a st16654
Console [ttys2] Enabled
BRD: module loaded
Loop: module loaded
Dm9000 Ethernet driver, v1.31
Eth0: dm9000a at c68ae000, c68b2400 IRQ 185 Mac: 00: 11: 22: 33: 44: 55 (CHIP)
Linux video capture interface: v2.00
I2C/dev entries driver
Driver 'sd' needs updating-Please use bus_type Methods
Omap2-nand driver initializing
Nand device: Manufacturer ID: 0x2c, chip ID: 0xb1 (micron NAND 128mib, 8 V 16-bit)
Cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand ":
0x0000000000000000-0x000000080000: "X-loader"
0x000000080000-0x000000260000: "U-Boot"
0x000000260000-0x000000280000: "U-boot env"
0x000000280000-0x000000680000: "kernel"
0x000000680000-0x000008000000: "File System"
Usbmon: debugfs is not available
Ehci_hcd: USB 2.0 'enabled' host controller (EHCI) Driver
EHCI-OMAP ehci-omap.0: OMAP-EHCI Host Controller
EHCI-OMAP ehci-omap.0: new USB bus registered, assigned bus number 2
EHCI-OMAP ehci-omap.0: IRQ 77, Io mem 0x48064800
EHCI-OMAP ehci-omap.0: USB 2.0 started, EHCI 1.00
USB usb2: configuration #1 chosen from 1 choice
Hub 2-. 0: USB hub found
Hub 2-0: 1. 0: 3 Ports Detected
Initializing USB Mass Storage driver...
Usbcore: registered new interface driver USB-storage
USB Mass Storage support registered.
UDC: omap udc driver, version: 4 October 2004 (ISO) (DMA)
Input: omap_twl4030keypad as/class/input/input0
Input: gpio-keys as/class/input/input1
Ads7846 spi2.0: touchscreen, IRQ 187
Input: ads784x touchscreen as/class/input/input2
Twl4030_rtc twl4030_rtc: RTC core: Registered twl4030_rtc as rtc0
Twl4030_rtc twl4030_rtc: Power Up reset detected.
Twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
Registered LED Device: led1
Registered LED Device: led2
Registered LED Device: ledb
Registered LED Device: led3
Usbcore: registered new interface driver usbhid
Usbhid: v2.6: USB hid Core Driver
Advanced Linux sound architecture driver version 1.0.19.
No device for Dai twl4030
No device for Dai twl4030 voice
No device for Dai omap-mcbsp-dai-0
No device for Dai omap-mcbsp-dai-1
No device for Dai omap-mcbsp-dai-2
No device for Dai omap-mcbsp-dai-3
No device for Dai omap-mcbsp-dai-4
Twl4030 audio codec init
ASOC: twl4030 omap-mcbsp-dai-0 mapping OK
ALSA device list:
#0: omap3evm (twl4030)
TCP cubic registered
Net: Registered protocol family 17
Net: Registered protocol family 15
RPC: Registered UDP Transport module.
RPC: Registered TCP transport module.
VFP support v0.3: implementor 41 architecture 3 part 30 Variant C rev 1
Console: switching to color frame buffer device 60x34
Display already enabled
Display already enabled
Buffer size = 3686400
Omap_vout: registered and initialized video device 0 [v4l2]
Display-> updated
Twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
Waiting 1sec before mounting root device...
Mmc0: New SD card at address AAAA
Mmcblk0: mmc0: AAAA su02g 1.84 Gib
Mmcblk0: P1 P2
Kjournald starting. Commit interval 5 seconds
Ext3 FS on mmcblk0p2, internal journal
EXT3-fs: Recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: mounted root (ext3 filesystem) on device 179: 2.
Freeing init memory: 156 K
Udevd version 124 started
Eth0: link down
Eth0: link up, 100 Mbps, full-duplex, LPA 0x45e1
Init: Entering runlevel: 5
Starting telnet daemon.
Starting syslogd/klogd: Done
Starting thttpd.
/Etc/rc5.d/S99omap-demo: Line 3: Can't create/sys/devices/platform/omapfb/sleep_timeout: nonexistent directory
Cmemk module: built on May 23 2011 at 14:10:16
Reference Linux version 2.6.29
File/home/cedt/dvsdk/dvsdk_3_00_02_44/linuxutils_2_24_02/packages/Ti/SDO/linuxutils/cmem/src/module/cmemk. c
Ioremap_nocache (0x86300000,167 77216) = 0xc9000000
Allocated heap buffer 0xc9000000 of size 0x22000
Cmem initialized 7 pools between 0x86300000 and 0x87300000
Dsplinkk: disagrees about version of symbol _ class_create
Dsplinkk: Unknown symbol _ class_create
Dsplinkk: disagrees about version of symbol class_destroy
Dsplinkk: Unknown symbol class_destroy
Dsplinkk: disagrees about version of symbol set_user_nice
Dsplinkk: Unknown symbol set_user_nice
Dsplinkk: disagrees about version of symbol wake_up_process
Dsplinkk: Unknown symbol wake_up_process
Dsplinkk: disagrees about version of symbol dma_alloc_coherent
Dsplinkk: Unknown symbol dma_alloc_coherent
Dsplinkk: disagrees about version of symbol device_create
Dsplinkk: Unknown symbol device_create
Dsplinkk: disagrees about version of symbol dma_free_coherent
Dsplinkk: Unknown symbol dma_free_coherent
Dsplinkk: disagrees about version of symbol device_destroy
Dsplinkk: Unknown symbol device_destroy
Insmod: cannot insert 'dsplinkk. ko': Unknown symbol in module, or unknown parameter
Busybox v1.13.2 (20:13:58 EDT) Multi-call binary

Usage: mknod [Options] Name type major minor

Create a special file (Block, character, or pipe)

Options:
-M create the special file using the specified mode (default A = RW)
Types includelpm_omap3530: Unknown symbol ips_policy
:
B: Make a block Device
C olpm_omap3530: Unknown symbol ips_register
R u: Make a character device
Plpm_omap3530: Unknown symbol ips_unregister
: Make a named pipe (major and mlpm_omap3530: Unknown symbol ldrv_proc_setstate
Inor are ignored)

Lpm_omap3530: Unknown symbol ldrv_proc_getstate
Lpm_omap3530: Unknown symbol pmgr_proc_getsymboladdress
Insmod: cannot insert 'lpm _ omap3530.ko ': Unknown symbol in module, or unknown parameter
Sdmak module: built on May 23 2011 at 14:10:18
Reference Linux version 2.6.29
File/home/cedt/dvsdk/dvsdk_3_00_02_44/linuxutils_2_24_02/packages/Ti/SDO/linuxutils/sdma/src/module/sdmak. c
/Opt/dvsdk/omap3530/interface: Error while loading shared libraries: libpng12.so. 0: cannot open shared object file: no such
File or directory

.-------.
| .-.
| -----. | .----..-----.-----.
| _ | --- '|' --. |.-'|
| --- | -- '|
'---' --. | -----''----''--''-----'-'-'-'
-'|
'---'

The Angstrom distribution Arago ttys2

Arago 2009.03 Arago ttys2

Arago login: Root
Root @ Arago :~ # Cd ../..
Root @ Arago:/# ls
Bin etc linuxrc MNT sbin TMP
Boot home lost + found opt SRV USR
Dev lib media proc sys VaR
Root @ Arago :/#

Question1: how to solve this DSP link error?
Question2: in latest dvsdk I. e 4.01 version, there is no configuration file provided for devkit8000 to generate uimage.
Question3: Is there any precompiled images for devkit 8000 so that I can just use it for booting?

Thankyou,
Naveen Kumar. s

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.