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.

Port DSPLink to DM814x

Other Parts Discussed in Thread: OMAP-L138, OMAP3530

Hello,

We have DSPLink running successfully on our OMAP-L138 system but it appears  that it does not run on DM814x.

I know that the newer SYSLink will run on both OMAP-L138 and DM814x.

How  difficult would it be to port DSPLink over to the DM814x?

Thanks,

Victor

  • Very.

    SysLink supports more use cases (HW and SW) than DSP Link - use cases that the DM814X architecture requires.  You're welcome to try, but I warned ya'.  :)

    Chris

  • Hello,


    I should have made it clear that I am only interested in keeping the same GPP-DSP functionality for the DM814x.  I understand that the DM814x has additional processors that are not DSP and thus DSPLink will not work.  However, I am not interested in interfacing to those other processors and just need the GPP  interfaced to DSP just like the OMAP-L138.

    I believe the DSP on both OMAP-L138 and DM814x are the same.  The only thing that I need  to change are the base address for the peripherals and the interrupt controller.  I don't think there are any other differences between the CPUs in regards to the GPP and DSP.

    So,  does that make my port much easier?

    Thanks,

    Victor

  • That cuts scope, which makes it easier, but it's still challenging.

    One key point to consider is that SysLink works with SYS/BIOS (BIOS 6) while DSP Link works with DSP/BIOS (BIOS 5).  Another is that DSP Link supports loading COFF file formats while SysLink supports loading ELF[1].

    SysLink must be used for communication with the Media Controllers on DM814X (which use SYS/BIOS).  If you're ok with BIOS 5/COFF on the DSP, SYS/BIOS on the Media Controllers, and _both_ SysLink and DSP Link on the A8, you can give it a shot.  But I'm not sure anyone has tried that, and it's certainly not in anyone's strategic direction, so you're probably on your own.

    ... unless you buy a mountain of those DM814X devices, at which point I'll come and help you do it.  ;)

    A better approach is to switch to SysLink, which as you mentioned, supports both DM814X and OMAP-L devices.  That updates you to the current generation of products (SYS/BIOS, SysLink, ELF toolchains, etc).

    Chris

    [1] Technically, on OMAP-L, SysLink supports both ELF and COFF, but we're discouraging COFF, and deprecating it in future releases.

  • Yes, I agree with you on all the issues that you raised.

    However,  for my application,  all I need at this point in time is the same functionality that I have on the OMAP-L138 which is strictly GPP-DSP  moved to the DM814x.     I am not planning to use the Media Controllers or whatever new features that SysLink provides.

    If I need something that DSPLInk does not support but SysLink does such as ELF, then I will move to SysLink.

    I most likely will not be buying a mountain of DM814X devices but I was planning to buy a mountain of the follow on chip but that changed due to TI :-o.

    Thanks,

    Victor

  • Hello,

    I was moving along very well until I ran into this problem.

    I was porting the OMAP3530 version over to the DM814x.  However, I ran into this problem with initialization of Timer5. This is done by the DSP and there is no source code but only the dsplink.lib    The OMAP3530 and the DM814x uses different address for Timer5.  I am sure there will be other changes in order for the DSP code to port from the OMAP3530 to DM814X.

    There is no way for me to continue any further since I don't have source code for the OMAP3530 and thus cannot build a dsplink.lib

    Is there any chance that I can get the source code just for the OMAP3530?   I am willing to give you back the finished product.

    Thanks,

    Victor

  • I don't understand - the source code to what?  DSP Link is provided in full source, both for GPP and DSP.

    Chris

  • Hello Victor,

    DSPLink is part of DVSDK of OMAP3530. You can download the dvsdk here: http://www.ti.com/tool/linuxdvsdk-omap3530. Please let us know if you have trouble downloading the dvsdk.

     

  • Hello,

    I was able to port  our code that was working on the OMAP-L138 over to the DM814x.   I cut and pasted code from both the OMAP-L138 and OMAP3530 platforms.

    The only remaining issue is getting the Timer to work.   I believe I can copy CLK_2430 since it looks similar.  However,  I am looking for the source code for this timer which should be under the src/clk2430 directory but it is nowhere to be found.  Also on the issue of source codde, where is the source code for PWRM_getCPULoad()?

    I changed the GLB_CLKTYPE to add this new clock.  I am building this with a new clk8118.h file that I included in dspcfg.s62.  The correct way is to change clk.h62 to include this file but it appears that I will need to build a new bios.a674 library.  Is any way I can build a bios.a674 library?

    Also, by changing the GLK_CLKTYPE, dspcfg.cmd no longer link in bios6748.a674 but uses bios.a674.   Can you tell me how to fix that?

    Thanks,

    Victor

  • Good to hear!

    I think you should post your remaining questions to the BIOS forum (not this Linux one) since the code you're looking for is on the BIOS-side (right?).

    Chris

  • Hi Victor,

    Did you have some specific questions about BIOS?  If so, please tell us (The BIOS Team) by creating a new post on the BIOS forum:

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

    Please also state the version of BIOS you are using in the post as well.  (if you like, you can also paste a link reference to this forum question so that the new post is linked to your original question on the Linux forums).

    Thanks,

    Steve

  • Hello,

    I successfully got the DspLink to work on the DM814x just as well as the OMAP-L138.  So, I no longer have any questions.

    If you are planning to update dspbios_5 in the future for the DM814x, let me know.  Otherwise, I will just use my modified version.

    Thanks,

    Victor