Hi:
I want using 8875 to work. But mcsdk only 8870 and 8878, not exsit 8875.
Please tell me how to do for 8875.
Other, how do I use mcsdk to create a boot, kernel, and rootfs for target dsp?
Can you tell how do it?
Thank you very much.
Camille
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.
Hi:
I want using 8875 to work. But mcsdk only 8870 and 8878, not exsit 8875.
Please tell me how to do for 8875.
Other, how do I use mcsdk to create a boot, kernel, and rootfs for target dsp?
Can you tell how do it?
Thank you very much.
Camille
Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.
Hi Camille,
What is you application requirement? You may need consider using keystone II devices(K2H, K2E), where ARM cores runs linux and DSP cores runs TI-RTOS or standalone DSP applications.
Please check TI product folder.
Thank you.
Today C665x platforms are not supported on linux-c6x. You can port BSP if you need it.
In practice C665x are pretty close to C667x from a Linux standpoint, the BSP is just slightly different. The main difference is that C665x use GEMAC network interface instead of NetCP for C667x. In Linux, the GEMAC + MDIO drivers exist (we used them on C647x/C645x and on DaVinci/Sitara platforms as well) but today it is not used by KeyStone C6x BSP.
Also C6657 have a UPP device. It is not supported in Linux 2.6.0.34 and don't know if you need it.
Basically there is not a huge work to port linux-c6x on C6657, one with a minimum Linux knowledge could do it:
- Introduce the C665x platform in /arch/c6x/platforms (mainly Kconfig, defines, #ifdef…)
- Set the appropriate PSC and PLL configurations for this platform (I suppose they may vary from the C667x ones)
- Change the network driver initialization to use GEMAC instead of NetCP (all the current C667x PHY/SGMII init must be disabled as well)
- Maybe the GEMAC device driver will need some adaptations
If you are going in this direction, it would be good if you can contribute by providing you C665x port to linux-c6x.org.
Thank you.