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.

error in capture demo on DM355

Hi,

I tried to run the ./capture_prev_rsz_ss_raw_

bayer -t1 -f0  -p1 -i1 command but i am getting following errors:

input_std_params: name = V4L2_STD_MT9P031_VGA
input_std_params: output width = 640
calling cmem utilities for allocating frame buffers
CMEM Error: init: Failed to open /dev/cmem: 'No such device or address'
CMEM Error: CMEM file descriptor -1 (failed 'open()'), ensure CMEMK kernel module cmemk.ko has been installed with 'insml
Unable to Allocate user buffers


On running loadmodules.sh i am getting the following error:
insmod: can't insert 'cmemk.ko': unknown symbol in module, or unknown parameter
./loadmodules.sh: line 6: ./mapdmaq: not found
insmod: can't insert 'dm350mmap.ko': unknown symbol in module, or unknown parameter
BusyBox v1.14.2 (2011-06-21 10:17:07 IST) multi-call binary

Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR

Somewhere on the net i found that that i need to compile the cmem with the version of the kernel i am using but i couldn't understand this,
should i have to run make command in DM355SDK again.I tried doing that but i am getting errors in gpio_test.c file.

I am facing this cmem issue for almost 1 day,could anyone send me the cmem.ko file and the procedure to install cmem driver.

Thanks and Regards,
Mayank
  • MAYANK AGARWAL said:
    Somewhere on the net i found that that i need to compile the cmem with the version of the kernel i am using

    That's correct, cmemk.ko must be rebuilt.  Also dm350mmap.ko.  I don't know about your other error with mapdmaq.

    MAYANK AGARWAL said:
    could anyone send me the cmem.ko file and the procedure to install cmem driver.

    .

    Since you need to build cmemk.ko against your Linux kernel source files, only you can build it (or someone who has the exact same kernel sources).

    Somewhere in your system's build files should be a file named Rules.make.  This file specifies paths to various components that are needed for the build.  For Linux device driver modules (*.ko files) compiling there is a variable named LINUXKERNEL_INSTALL_DIR that points to the base of the Linux kernel source tree.  You will need to change this to your Linux kernel location.  As a clue that you're pointing to the right place, this directory will have subdirectories such as kernel, drivers, arch, fs, among others).

    There should be a top-level Makefile that rebuilds everything, but I'm not familiar with your SDK not the problem with errors on gpio_test.c

    Regards,

    - Rob