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.

Various Problems with Omap3530Evm

Other Parts Discussed in Thread: OMAP3530

Hi,

Omap3530Evm(Beagle Board): I want to add AACHEENC codec to codecserver  and have a AAC-HEv2 encoding on device. So i download the AAC-HEv2 codec from ti website, add it to codec server and build it. The process of making codec server, get me a new cs.X64P file. 

Then I "make" and "make install" entire dvsdk, dvsdk-demos and codecs. Hence, I have some new files in "targetfs" folder including cmem driver, dvsdk demos, codec server files and others.

Now, there are following problems:

1. When I copied the new made dvsdk-demo  files to file system, and run loadmodules.sh it give  this errors back to me:

Error Details.

# ./loadmodules.sh 

CMEMK module: built on Jul 13 2010 at 09:03:04

  Reference Linux version 2.6.32

             .

             .

dsplinkk: disagrees about version of symbol module_layout

insmod: error inserting 'dsplinkk.ko': -1 Invalid module format

BusyBox v1.16.1 (2010-07-12 18:43:40 JST) 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 include:

        b:      Make a block device

        c lpm_omap3530: Unknown symbol IPS_notify

or u:   Make a character device

        lpm_omap3530: Unknown symbol IPS_register

p:      Make a named pipe (MAJOR and lpm_omap3530: Unknown symbol IPS_unregister

MINOR are ignored)

lpm_omap3530: Unknown symbol LDRV_PROC_setState

lpm_omap3530: Unknown symbol LDRV_PROC_getState

lpm_omap3530: Unknown symbol PMGR_PROC_getSymbolAddress

insmod: error inserting 'lpm_omap3530.ko': -1 Unknown symbol in module


2.I tried to copy a new complete rootfs and boot using mksdboot.sh file and it successfully completed. But boot-loader hangs:

Texas Instruments X-Loader 1.46 (Aug 16 2010 - 16:16:57)
Starting OS Bootloader...

3. I repeat this steps with dvsdk_4_00_02 and 4_03 but it never boots succesfully. When I use old boot files(u-boot,MLO and uImage) with recently made rootfs, following errors is generated and boot process no longer proceeded : 

FATAL: Module omaplfb not found.

FATAL: Module bufferclass_ti not found.

BusyBox v1.13.2 (2011-12-23 00:31:29 IST) 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 include:

        b:      Make a block device

        c or u: Make a character device

        p:      Make a named pipe (MAJOR and MINOR are ignored)

 

chmod: /dev/pvrsrvkm: No such file or directory

Starting SGX fixup for ES5.x

FATAL: Module cmemk not found.

FATAL: Module dsplinkk not found.

FATAL: Module lpm_omap3530 not found.

FATAL: Module sdmak not found.

numid=48,iface=MIXER,name='HeadsetL Mixer AudioL1'

  ; type=BOOLEAN,access=rw------,values=1

  : values=on

numid=45,iface=MIXER,name='HeadsetR Mixer AudioR1'

  ; type=BOOLEAN,access=rw------,values=1

  : values=on

Simple mixer control 'Headset',0

  Capabilities: pvolume penum

  Playback channels: Front Left - Front Right

  Limits: Playback 0 - 3

  Mono:

  Front Left: Playback 3 [100%] [6.00dB]

  Front Right: Playback 3 [100%] [6.00dB]

INIT: Id "S" respawning too fast: disabled for 5 minutes

NOW, Please say me, where I made mistakes and what I must do to? 

How to install the kernel on dvsdk_4_03 psp package on device with appropriate boot files?

And should I updare boot partition of SD card for installing new filesystem files?

Thanks

  • Hi Hamed,

    The described problems seem are not related one by others. I recommend you to start from the beginning. Format the SD card. Copy to it MLO and u-boot. Try to boot. Then copy uImage. Try to boot again. Then copy the whole file system. These steps will help you to find where the problems appear.

    BR

    Tsvetolin Shulev

  • Dear Cvetolin,

    Thanks for your attention.

    I make x-load and u-boot and copied them to boot partition. But when I reset the board nothing happens! When I used the old "mkcard.sh " for creating partitions on the SD Card and copied MLO and u-boot file that are in "DVD\linux\demos\angstrom" it boots successfully. 

    Totally, what is the problem??

  • If you prepare the sd card manually the boot partition must formatted with FAT32 and named "boot" the other partition must be ext3 or ext4 formatted and named "rootfs".

    But if the first step is OK by using the mkcard.sh script use it and continue the preparing of the card.

    BR

    Tsvetolin Sulev

  • Dear Cvetolin,

    The problems is exact here in this point! When I use mkcard.sh script provided on supplied product DVD, I can only boot the device with demo boot and rootfs partition files that are on DVD. But in all of following situations, successful boot became a dream!

    1. Using DVD boot files and new generated filesystem (DVSDK 4.03).

    2.Using mksdboot.sh script on DVSDK 4.03 to create partitions and their content (either default targetfs files or  generated targetfs) leads boot process to errors reported in   main post on part 2. 

    Meanwhile you answer me to solve this problem, please say me " is it possible to I replace new built cs.x64P (codecs sever) files in default filesystem of device (based on DVD demo) and use dvsdk_demos to encode AACHEv2?". I say it because of default dvsdk_demo encoder agree ".aac" file on output file.


    Regards

    Hamed Abbasitabar