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.

DM368更换DDR后问题

Other Parts Discussed in Thread: TVP5150, TVP5158

    公司之前的demo板,基于DM368 + 海力士128M DDR + 三星128M Flash + TVP5150 AD解码器;

    公司自己做的板子,  基于DM368 + 镁光256M DDR + 256M Flash + TVP5158 AD解码器;

    UBL、u-boot中相关DDR的代码已经根据镁光256M DDR作了调整,在开机启动脚本中加载cmem模块等的相关命令如下:

insmod cmemk.ko phys_start=0x83C00000 phys_end=0x90000000 allowOverlap=1 phys_start_1=0x00001000 phys_end_1=0x00008000 pools_1=1x28672 useHeapIfPoolUnavailable=1
    insmod irqk.ko
    insmod edmak.ko
    insmod dm365mmap.ko
    mknod /dev/dm365mmap c `awk "\\$2==\"dm365mmap\" {print \\$1}" /proc/devices` 0

目前系统启动后出现如下问题:

IRQK Error: ioctl(): bad command type 0xfe (should be 0xfc)
IRQK Error: Unknown ioctl received: 65032.
CMEM Error: getVersion: Failed to retrieve version from driver: -1.
CMEM Error: init: major version mismatch between interface and driver.
CMEM Error:     needs driver version 0x3000100, got 0xffffffff
IRQK Error: ioctl(): bad command type 0xfe (should be 0xfc)
IRQK Error: Unknown ioctl received: 65032.
CMEM Error: getVersion: Failed to retrieve version from driver: -1.
CMEM Error: init: major version mismatch between interface and driver.
CMEM Error:     needs driver version 0x3000100, got 0xffffffff
CMEM Error: CMEM_exit() already called, check stderr output for earlier CMEM failure messages (possibly version mismatch).
CMEM Error: CMEM_exit() already called, check stderr output for earlier CMEM failure messages (possibly version mismatch).
CMEM Error: CMEM_exit() already called, check stderr output for earlier CMEM failure messages (possibly version mismatch).
Failed to allocate memory.
Error: Failed to create buftab
Error: Failed to create video encoder: h264enc

之前也会出现“/dev/cmem, no such device"之类的错误,可是在/dev/目录下,是有cmem设备的。

请问会是不是还是DDR配置上有问题?

  • 你可以在uboot里做个内存测试,写进去一个,读出来一个,看是不是一致,把整个ram读写一遍

  • 你好,

    UBL使用新的,Uboot,包括uboot的配置参数都是有老的,看是否能正常使用。

    如果不正常,请降低DDR频率后,再尝试。

  • Chongqing Yuan;

       你的问题解决了吗?  我的新板子也是用256MB DDR2, 目前DM365 跑297M,DDR2 跑240M 没问题, 都能正常工作, 换DM368跑DDR2 340M, 发现每次都nand copy 完成后, UBL交权给UBOOT的时候卡住了,不知道啥原因。

      

    DM36x initialization passed!
    TI UBL Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000008.
       DONE
    Jumping to 22 entry point at 0x81080000.

     DM368_IPNC_UBL_1.0.1

     目前看代码是UBL 从NAND FLASH 把UBOOT 复制到DDR2 是没问题, 但是执行UBOOT的时候卡住了。 很奇怪的问题。

    谢谢

  • 你好,你的ubl代码中相关配置修改了吗?