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.

C6678 - EMAC CSL

Guru 10750 points


Hi,

Will there be an EMAC CSL for the C6678? Is there a C6678 Emac example without using the SYS/BIOS?

Thanks,

HR

  • Hi HR,

    There is no EMAC CSL for C6678. But we have one for switch CPSW, one for SGMII in the CSL. I haven't seen any example in CSL, but it should not be difficult to have the example to get the code, but you have an example in PA lld folder.

     

    Thanks,

    Arun.

  • Hi.

    I have been doing extensive development on the C6472 DSP for the last two years using the 'bare' approach of NOT using any operating system (i.e SYS/DSP/BIOS) and only making use of DSPLIB, IQMATH for core algorithms and the CSL for peripherals.

    We now want to migrate some of our application to the C6678 platform since it still supports fixed point arithmetic and has more cores and higher clock rate. According to the technical marketing claims, the C6472 and the C6678 the are 100% code compatible. However, this is obviously true only for the core code. Thus, only the DSPLIB and IQMATH code are portable, NOT the CSL, since this is a device specific library only.

    My questions are:

    • We have noticed a CSL element that comes with the MCSDK for the C6678, but at the moment we have not explored, and therefore are unsure as to whether this CSL element will meet our needs.
    • Is there a plan to release a CSL similar to that of the C6474 and C6472 for the C667x devices, so that we will NOT be forced to use an operating system? Or, are we now forced to migrate our applications to an RTOS environment in order to gain the advantage of the faster platform??

    Ideally we would like to stick to our bare approach since it allows us to squeeze that extra bit of performance out of our application and allows full control over what happens to/from memory, which is also an aspect proven to affect our performance to a very high degree. We currently use every inch of the memory, and therefore cannot sacrifice memory for the support of an operating system.

    What do we do?

    Estian.

  • I too have discovered this problem. It seems that TI has decided that all users of the C6678 MUST use BIOS.