• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 1036 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.

Error inserting CMEMK->Bad address

Naveen Kumar.S
Intellectual 260 points

Hi, while booting DVSDK-4.01 from SD card onto Beagleboard-xM Rev C, i am facing CMEM error, as mentioned below,

CMEMK module: built on Aug 22 2011 at 18:23:25
  Reference Linux version 2.6.32
  File /home/cedt/DVSDK_Beagle/ti-dvsdk_dm3730-evm_4_01_00_09/linuxutils_2_25_05_11/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x83700000) overlaps kernel (0x80000000 -> 0xa0000000)
CMEMK Error: Failed to request_mem_region(0x83700000, 35651584)
FATAL: Error inserting cmemk (/lib/modules/2.6.32/kernel/drivers/dsp/cmemk.ko): Bad address
DSPLINK Module (1.65.00.02) created on Date: Aug 22 2011 Time: 18:23:46
SDMAK module: built on Aug 22 2011 at 18:23:26
  Reference Linux version 2.6.32
  File /home/cedt/DVSDK_Beagle/ti-dvsdk_dm3730-evm_4_01_00_09/linuxutils_2_25_05_11/packages/ti/sdo/linuxutils/sdma/src/module/sdmak.c
Starting Matrix GUI application.
I have attached the bootarguments file and my bootlog file too.
https://e2e.ti.com/<a target="_blank">http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/447/2705.bootarguments.txt</a>
https://e2e.ti.com/<a target="_blank">http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/447/0045.bootlog.txt</a>
Please, help me out in solving this CMEM error.

I tired changing the bootarguments value, but nothing is working. So, please suggest what should i do to solve this error.

Thankyou,
Naveen
  • 0
    Guru 11260 points

    Hi,

    what are the bootargs value you have set? did you also set the mem value?

    Best Regards

    Prabhakar Lad

  • 0 in reply to Prabhakar Lad
    Intellectual 260 points

    Hello Prabhakar, I have attached the bootargs file and bootlog files

    1781.bootarguments.txt

    0083.bootlog.txt

    There was no any such variable called "mem" in the bootarguments?

    Thank-you,

    Naveen

  • 0 in reply to Naveen Kumar.S
    Guru 11260 points

    Hi 

     

    looks like you are booting from SD card. does the system directly boots up or does the bootloader comes up and waits for passing arguments?

    Best Regards

    Prabhakar Lad 

  • 0 in reply to Prabhakar Lad
    Intellectual 260 points

    Hello,

    Yes i do boot from SD card. The system directly boots up. I have pasted the boot arguments of my beagle board XM C

    baudrate=115200
    beaglerev=xMC
    bootcmd=if mmc rescan ${mmcdev}; then if userbutton; then setenv bootenv user.txt;fi;echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run loaduimage; then run mmcboot;fi;fi;run nandboot;
    bootdelay=3
    bootenv=uEnv.txt
    buddy=none
    camera=lbcm3m1
    console=ttyS2,115200n8
    defaultdisplay=dvi
    dieid#=3ce800029ff800000160a74505018019
    dvimode=640x480MR-16@60
    importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize
    loadaddr=0x80200000
    loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
    loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
    loaduimage=ext2load mmc ${mmcdev}:2 ${loadaddr} /boot/uImage
    loaduimagefat=fatload mmc ${mmcdev} ${loadaddr} uImage
    mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype}
    mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
    mmcdev=0
    mmcroot=/dev/mmcblk0p2 rw
    mmcrootfstype=ext3 rootwait
    mpurate=auto
    nandargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}
    nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
    nandroot=/dev/mtdblock4 rw
    nandrootfstype=jffs2
    ramargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${ramroot} rootfstype=${ramrootfstype}
    ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
    ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=0x81000000,64M
    ramrootfstype=ext2
    rdaddr=0x81000000
    usbtty=cdc_acm
    vram=12M
  • 0
    Expert 1505 points

    Can anyone tell me where this insert cmemk.ko start from phys_start (0x83700000)?

    I checked all the loadmodule*.sh file in the file system, and no one has phys_start from 0x83700000.

     

    Regards

    Touse

  • 0 in reply to Huan Hou
    Expert 1505 points

    I got the location of the initialized script, it's located in /etc/rc5.d/S99loadmodule-rc

    To avoid the overlap error, just modify the phys_start and phys_end address.

    i.e

    modprobe cmemk phys_start=0x83700000 phys_end=0x85900000