• Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 226 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.

problem loading DVSDK jffs and uImage obtained by recompiling

M BHARATH
Intellectual 270 points
Other Parts Discussed in Thread: OMAP3530

1)  There are some problems for us in working out DVSDK examples. In DVSDK user guide they given that in order the examples in DVSDK to work we have to flash with the rootfs.jffs2 in DVSDK instead of SDK root.jffs2. We did the same thing and we are getting an error. It is not taking the full root.jffs2 file while booting, after some memory location it is saying as truncating and stopping boot procedure.

    Actually the root.jffs2 file in DVSDK is of 76MB in size where as the file in sdk which we normally use is of size 18MB. We changed the size in reflash_samsung.txt file which is allocated for root.jffs2 from 0x1400000 to 0x6000000. Even then we are facing the same problem. What may be the reason for this?

2) Another thing what we read in DVSDK user guide is about rebuilding the linux kernel to generate uImage. We untared the tar file and followed the procedure as mentioned to create uImage. After reconpiling the kernel an image was generated but it was named as zImage not uImage. We renamed it as uImage and flashed into the OMAP3530 board but it was giving an error after reflashing as  " BAD MAGIC NUMBER". But in the document they are saying that it will generate uImage. Why is this happenig so? Please let us know..

We are using the latest versions of SDK (1_00_02) and DVSDK (3_00_00_29)

Thanks and regards,

M.BHARATH

 

  • Intellectual 270 points

    I am having the same problem

    I think TI is just confusing the Omap EVM users with this jffs2 issue.

    My board has Micro nand, I reflashed the board with sdk1.0.2 with RAMDISK file system, cause we can not use the jffs with Micron Nand.

    When it comes to DVSDK, TI only provides JFFS and NFS file system. at first I tried to use NFS, but I failed, so I turned to jffs,

    first error is that the dvsdk JFFS is too big to be loaded via TFTP, so I have to copy the JFFS to sd card and flashed the NAND.

    then, I started booting the kernel, and after several minutes of bootng , the kernel stoped with error message:

    /sbin/initKernel panic - not syncing: Attempted to kill init!
    : /lib/libpthread.so.0: version `GLIBC_2.4' not found (required by /lib/libcrypt
    .so.1)
    /sbin/init: /lib/libc.so.6: version `GLIBC_PRIVATE' not found (required by /lib/
    libcrypt.so.1)
    /sbin/init: /lib/libc.so.6: version `GLIBC_PRIVATE' not found (required by /lib/
    libpthread.so.0)

    that's really frustrating, if the JFFS doesnt work with Micron, whcih is statdard on al the new EVM ,wdhy do TI bother to include it in the dvsdk PACKAGE INSTAED OF A RAMDISK ?

    also the instruction of using DVSDK NFS filesystem is not very helpful. I alwasy get the

    rpc bind error and can not  mount host NFS.

    can somebody provide some help?

     

    Thanks!