• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 328 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.

DM6446 Modules and Decode demo issues

Wiley Black
Prodigy 90 points

Hello,

I am having some difficulty getting the decode demo to run on our DM6446 EVM.  I had it working with the older version of the DVEVM CDs.  I went through and wiped out (or renamed) folders and installed the latest downloaded CDs, and now am unable to get the decode demo to work.  

1. Installed all the .bin files and decompressed as per the GSG.

2. NFS with TFTP seems to be working ok.

3. Able to build and run the hello world program.

4. Rebuilding the linux kernel had an issue.  The folder in the GSG didn't exist, so as per some posts I'd seen here, I used (GSG Section 4.5):

ti-davinci instead of ti-davinci/linux-2.6.10_mvl401.  

Similarly, my Rules.make in GSG Section 4.6 has:

LINUXKERNEL_INSTALL_DIR=$(HOME)/workdir/lsp/ti-davinci

instead of the ti-davinci/linux-2.6.10_mvl401 from the GSG.

With these changes, the uImage built ok and I copied it to /tftpboot.

5. When I copy the pre-built cmemk.ko and dsplinkk.ko to a folder accessible via the NFS, I am able to loadmodules.sh and they go in ok.  Then when I run the decode demo, it gives no output and just sits there.  I can Ctrl-C back to the prompt, but still nothing from the demo.

6. When I build the cmemk.ko and dsplink.ko using make clean, make, make install, and then run those on the NFS, I get the version error discussed in the FAQ about "disagrees about version of symbol struct_module".  And cannot load the modules.

target $ uname -r

2.6.10_mvl401-davinci_evm

target $ strings cmemk.ko | grep vermagic

vermagic=2.6.10_mvl401 preempt ARMv5 gcc-3.4

My ti-davinci/localversion file contains only "_mvl401".  The ti-davinci/localversion-mvl file does not exist, leaving me to wonder where the vermagic string came from at all.

In any case, the cmemk issue is a strong indicator something is wrong, but the primary problem is that even with the pre-built cmemk.ko, my decode demo won't run.  

I have repeated some sections of the GSG, re-installing etc. to try to ensure that I am using all versions from the same DVSDK version, but to no avail.  I don't know where to look to try to get more troubleshooting information.

My u-boot gives:

U-Boot 1.1.3 (Dec  4 2006 - 12:05:38)

Not sure if that's a new or old version.

My montavista folder is:

/opt/mv_pro_4.0.1

My dvsdk folder is:

/home/wblack/dvsdk_1_30_01_41

Thanks,

Wiley

 

  • 0
    TI__Mastermind 37340 points

    Wiley,

    The main reason for getting "disagrees about version of symbol struct_module" type errors is that one or more of your software components (u-boot, uImage, or file system) are not compatible with the rest of the system.  I see this from time to time when customers upgrade to newer DVSDK.  The first thing I noticed is that the u-boot version you are using is 1.1.3, yet the DVSDK version you are using contains u-boot 1.2.0.  This may not be the source of your problem, but it is worth considering...

    I am using this same DVSDK release (1.30.01.41) and have ran the demos sucessfully when using u-boot 1.2.0, installing per the GSG, and loading my Linux kernel via TFTP and file-system via NFS.  Please note that I did not need to copy anything manually to my file-system.  SImply doing 'make install in the root DVSDK directory (one of the steps in GSG), copies all the necessary files for me.

    I hope this helps.

  • 0 in reply to Juan Gonzales
    Prodigy 90 points

    Thanks Juan, problem solved.  I don't know if it was upgrading u-boot to 1.2.0 that did it, or in following that procedure I came across a pre-built uImage-dm6446 linux kernel image which I put on the TFTP server and configured u-boot to choose as its bootfile.  One or the other solved it.

    I would comment that commands.txt is confusing, had to mix & match with the Getting Started Guide to get it right, and it lacks a DM6446 NOR section.

    Thanks!

    Wiley