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.
Linux/66AK2E05: K2E EVM error: netcp: Could not open DMA queue for channel "tx-pipe-2620110": 0 ; eth0 is down...
Part Number: 66AK2E05
We performed set of experiment to understand pktdma of netcp behavior and its configuration. 1. We found the in case of K2H , no boot mode, hello words example is running fine which send the "hello word " to some other pc and receive back by running the window application which send back what it received. We found here that netcp packet dma RX and TX channel are able to enabled by cppi module. 2. Same is the case of when running linux in arm , BUT here on loading hello world application in dsp, ethernet link is accessible only from dsp. Now in case of K2E. 1a, Same hello world application loaded in dsp when EVM is configured in no boot mode, here We found here that netcp packet dma RX and TX channel are always found in disable state . This behavior is not understandable . Please let us know how NETCP'S pkt dma rx and tx channel always get disable , even on forcefully trying to enable it in no boot mode?? Something missing??
In reply to lding:
Currently we are using pdk package and drivers of Qmms and Cppi from--- C:\ti\pdk_keystone2_3_01_04_07\packages\ti\drv and running the example from C:\ti\mcsdk_bios_3_01_04_07\examples\ndk\helloWorld.
Can you please conduct the test for above mentioned package and drivers with the example code.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
We conducted a test with the binary provided by you NIMU_emacExample_EVMK2EC66BiosExampleProject.out on our K2E setup and following is the result. Please give a look at NETCP_PKTDMA_TX and NETCP_PKTDMA_RX memory region and mapping.
In reply to anshul rathi:
The memory region of NETCP_PKTDMA_TX and NETCP_PKTDMA_RX is fine but the values off all the parameters in both TX and RX are 0 ( tx_enable is disable and same in case of rx) and also want to know about Why is " the code stuck at CSL_SerdesLaneEnable_Lane_Init_RX function ? "
Can you give us the download path for pdk_k2hk_4_0_3.
While running the " NIMU_emacExample_EVMK2EC66BiosExampleProject " with the latest 4.3 release for K2E, the code gets struct on " CSL_SerdesWaitForSigDet ". Can you explain why is it so?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.