• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 101 subscribers
  • Views 422 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.

Clarification needed for Syslink FAQs

Alessandro Meliota
Prodigy 80 points
Other Parts Discussed in Thread: AM3874, LINUXEZSDK-SITARA, AM3892, AM3871, AM3894

Hello
I have already posted a question about that here:

http://e2e.ti.com/support/embedded/bios/f/355/t/271771.aspx

I'm trying to solve the problem indicated in the Syslink FAQ as "Ipc_control(STARTCALLBACK) timeouts on TI81XX device when only the VPSS-M3 is used" where it is indicated to modify a .cfg file with some new lines.

What I cannot understand is:

  1. what file should be edited?
  2. how this modification affects compilation of syslink.ko? I found two files with the GateDualCore variable (named RingIO_ti81xx_vpssm3.cfg and Notify_ti81xx_vpssm3.cfg), I modified both as described in the FAQ but nothing changed. Even introducing a syntax error does nothing, so I assume they are not read at compiling time
  3. do I need to run some compilation tools (like xdctools) in order to get new compiling options before running make? or should I use Code Composer studio?

I am able to recompile the syslink.ko module as described in http://processors.wiki.ti.com/index.php/SysLink_Install_Guide, but as already mentioned the problem persists.

Thanks a lot, do not understand how to use the tools starts being annoying...

  • 0
    TI__Expert 7415 points

    This SysLink FAQ provides that troubleshooting hint when you see that error while trying to run SysLink examples. Are you running a specific Syslink example/sample ? If so, which one ?

    The config file that needs the change will correspond to the .cfg file associated with the example/sample you are trying to build and run. Once you tell me what you are trying to run/load i will attemp to figure our which cfg file to modify and how to re-build that particular VPSS-M3 executable.

    Thanks.

  • 0 in reply to Gunjan
    Prodigy 80 points

    Actually I'm not running any example, I am only trying to load the VPSS firmware after inserting the syslink.ko module.

    So the problem reported in the FAQ is not related to the driver itself but to the examples...
    Is there any method to avoid the error reported recompiling the syslink driver?

    I am using the ti-ezsdk_dm814x-evm_5_04_00_11 package.

    Thanks

  • 0 in reply to Alessandro Meliota
    TI__Expert 7415 points

    Alessandro,

    Looks like I might have had it wrong, the config file isn't specifically related to the examples.

    But I discussed with my team, and they seem to think we may find out if we are on the right track by trying to connect to the M3 via CCS (loading the firmware image symbols) and then checking to see if it's stuck in a call to GateDualCore_enter()

    Is that something you could try out ?

  • 0 in reply to Gunjan
    Prodigy 80 points

    Unfortunately not, I have a free version of CCS an any debug/JTAG tool.

    At the moment I found a workaround adding in the 2nd stage u-boot (before loading the kernel) a reset of the HDVPSS and HDVI using the ti814x_set_board() function that is in U-BOOT_DIR/drivers/video/ti814x_logo.c
    Doing so it works well.

    But definitely there is a problem with syslink.

  • 0 in reply to Alessandro Meliota
    TI__Genius 12865 points

    Hi Alessandro,

    When Ipc_control(STARTCALLBACK) timeouts, all it means is that the handshake between the host processor (A8) and the slave processor (M3) did not occur. This could be due to a variety of different reasons - lack of power, wrong drivers, bad code on the slave, etc.. The FAQ that you referred to simply identified one common software initialization problem. But from your posts, this seems more like a lower-level problem where some hardware may not have been initialized properly, causing the M3 to not reach the handshaking code in SysLink.

    I see that you are trying to reuse the software from the EZSDK for TI81xx on a AM3874, which is a similar but slightly different part. There may be differences at the M3 startup sequence between the two devices which are preventing your M3 from booting up properly, which you solved by doing the reset in uboot. Personally I am not familiar with the AM3874 device and am unsure if the TI81xx EZSDK firmware image you are trying to reuse is fully compatible.I will try to get someone from the team who created the firmware image to assist you further.

    Best regards,

    Vincent

  • 0 in reply to Vincent W.
    Prodigy 80 points

    Hi Vincent,

    Thanks for your reply.
    Now what I am wondering is: does a firmware version for the AM3874 exist? Or it would be necessary modify and recompile it from sources?
    If it does not exists, can it be download anywhere? Or has to be requested to TI?

    Speaking more generally, if a user is developing on a CPU that is not exactly that supported by TI (TI81xx vs. AM38xx) how can she/he rely on provided software, knowing nothing about the low level and without any source code? Be aware, I don't want to be polemical, it is only a question if TI (like other competitors, I had similar issues also with Freescale) thinks that the software provided is enough for develop a reliable application, for customers that are not huge consumer electronic devices producers.

    Thanks

  • 0 in reply to Alessandro Meliota
    TI__Mastermind 18320 points

    Alessandro,

    It appears that this thread has veered outside the expertise of the BIOS forum.  I have moved this to the device forum in hopes that you can get a response there.

  • 0 in reply to Alessandro Meliota
    TI__Guru**** 170625 points

    Alessandro,

    DM814x and AM387x devices share the same EZSDK till version 5.04.00.11. And this is the latest version for AM387x. Newer versions are developed and validated only for DM814x device.

    http://www.ti.com/product/am3874 -> http://www.ti.com/tool/linuxezsdk-sitara

    LINUXEZSDK-AM389X-AM387X: Linux EZSDK for AM3871, AM3872, AM3874, AM3894, AM3892 - ALPHA

    http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/5_04_00_11/index_FDS.html

    BR
    Pavel