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

[2.6.37 - 4.00.00.11] "modprobe vpss" freezes device

Karl Krach
Intellectual 320 points

Hello,

since the USB in peripheral mode is only working with kernel 2.6.37, I try to get the graphics working with this version. According the "SysLink_02.00.00.68_beta1_ReleaseNotes.pdf" I used these software versions:

  • Linux 2.6.37 from tag "TI816XPSP-04.00.00.10" (ARGO git)
  • Syslink in version 2_00_00_68_beta1
  • Ipc in version 1_22_04_25

First I had freezes when downloading the M3 firmware "ti816x_hdvpss.xem3". According Lee's post the new syslink version needs some changes in the M3 code. So I was looking for a new M3 firmware and found the EZSDK for the new evaluation module. I extracted the "dm816xbm_m3vpss.xem3" and the firmware_loader. Now the firmware download works fine - even with the old firmware_loader. But when I insert the vpss module, the device died with the following output:

# modprobe vpss debug=1
VPSS_FVID2: contrl event 0x10040018 timeout
VPSS_DCTRL: failed to get node input status
VPSS_GRPX : failed to set grpx0 nodes
VPSS_CORE : failed to int graphics.

Questions:

  1. Can I use the "dm816xbm_m3vpss.xem3" for my ti816x processor? If not, where do I get the updated "ti816x_hdvpss.xem3" ?
  2. What is the "firmware_loader" binary from the EZSDKs - can I use the progmgrapp instead?

Thanks,

Charly

 

PS: I'm working on the "old C6A816x EMV" with DDR2.

----
UPDATE: I ve attached the terraterm.log, in which I inserted the commands which were executed from a separate SSH session.

  • 0
    Intellectual 320 points

    Yihe,

    thanks a lot for your reply!

    1. I used syslink68, because the "ezsdk 5_01_00_77" contains the 2.6.34 kernel (linux-2.6.37-psp04.00.00.10) and the syslink68. Furthermore the ReleaseNotes (page 3) of syslink68 lists as its dependency the Linux release psp04.00.00.10. So I concluded that they would fit together...
      .
    2. The question "where to get the ti816x_hdvpss.xem3 M3 firmware from?" is one of my major problems. I receive the linux kernel via git from the ARGO project and the syslink and ipc packages from its download pages. But the M3 firmware has no download page - they are contained in the ezsdk, which I don't have...

      At the moment I have only two sources:
      • First the "ezsdk_c6a816x-evm_5_00_00_56_setuplinux" from my SD-card (which only contains a linux-2.6.34-psp04.00.00.07 - and thus a deprecated M3 firmware)
      • Second the "ezsdk_dm816x-evm_5_01_00_77_setuplinux" from this download page which installs files for the "dm816x". But it has a 2.6.37 kernel, and so I hoped to get this running - even on my ti816x board. Do you see a chance?
        .
    3. I recompiled my kernel (and the syslink.ko) with the syslink87 and ipc 1_22_03_23 but now the device freezes when downloading the firmware. I used the procmgrapp_debug from the syslink samples and both, the "ti816x_hdvpss.xem3" from my SD-card and the "dm816xbm_m3vpss.xem3" from the "ezsdk_dm816x-evm_5_01_00_77". If you tell me, that I have a non-matching M3 firmware - can you tell me, where to find a matching one?
      .
    4. Since on the ezsdk download page is written "This is the 5_01_00_77 release of the EZ SDK supporting DM816x/C6A816x/AM389x platforms" it should work with my board. If you tell me, that Linux kernel psp-04.00.00.10 does not work with syslink68 - why are they on this EZSDK?

    Thanks a lot,

    Charly

  • 0
    Intellectual 320 points

    yihe,

    first I tried your suggestion and replaced my linux modules (syslink.ko, vpss.ko and ti81xxfb.ko) with the prebuild ones. And what a surprise - it worked!! Even with the prebuild syslink68 module. So I replaced them one by one - and my custom build system was working, when I use your prebuild vpss.ko - strange, or not?

    The end of the story is:     The linux kernel, available in the EZSDK "linux-2.6.37-psp04.00.00.10" is not the same, as when you checkout the git tag "TI816XPSP04.00.00.10" from ARGO. There were some lines removed - I guess, they brought my system to death before. I ve attached the patch - so you can run it on your ARGO kernel - or take the kernel from the EZSDK 5_01_00_77.

    Regards,

    Charly

    PS: My configuration is

    • kernel "TI816XPSP04.00.00.10" from argo git + attached patch
    • syslink 02_00_00_68_beta1
    • ipc 1_22_04_25
    • dm816xbm_m3vpss.xem3 from EZSDK 5_01_00_77
    • toolchain from crosstool-NG on debian squeeze
    linux-2.6.37-psp04.00.00.10.patch.gz