As the topic says i want the use my evm6678le as a isp for sniffing the hole traffic in my network. i searched and read a lot in this forum but found nothing that solve my problem.
My biggest problem actually is that other PC can see the traffic of my board (i use a hub and the emacExample) but i can't receive traffic. I don't know what i have to do i hope you can help me.
Not being an expert on 802.3, I do not know what ISP means in this context. But I do know what a sniffer is.
Our NDK was written to support normal Ethernet traffic, so you may not have much success by just using what we supply. It makes sense to me that if the bus traffic is coming to the EMAC pins then the peripheral can probably capture it. But that is not something that I expect TI to support in terms of supplying software drivers.
If you would like to get a more informed opinion, I could put in a request to move this thread to the BIOS Forum under Embedded Software. That is where the NDK experts would be. Just let me know. Otherwise you can wait for someone else on this forum who knows more about it than I do.
Search for answers, Ask a question, click Verify when complete, Help others, Learn more.
Thanks for your answer, i wasn't quite sure which is the right forum to post my question.
What version of the NDK are you using? What version of BIOS also.
I want to make sure I have your question correct...For the evm6678, you want to receive all the traffic (UDP, TCP, ICMP, etc.) on the network (regardless of MAC address) in your application...correct?
nkd_2_21_00_32 and bios_6_33_04_39.
yes this is exactly what i want.
It sounds like what you want is promiscuous mode. I remember a customer a while back (year or so ago) was doing this for the C674x. It's all tracked in a forum thread, please check that out:
Thank you for the link it gave me exactly the info I needed. But on my system i can't find a file called "ethdriver.c" and when i want compile the "nimu_eth_evmc6678l" project it doesn't has a output file (like nimu.out)
in the properties for the "nimu_eth_evmc6678l" project i saw that there is a archive output sorry for that question. Other queston tdoes this solution also work with a 6678 board because the pdf is for TMS320C674x/OMAP-L1x.
Yes, you are correct, that customer was working on the evm6748 (OMAPL138) hardware so that guide may not apply to you.
I googled around for a similar guide for the evm6678le EMAC but didn't have much luck. I'm going to ask that the MCSDK team help you with getting the driver into promiscuous mode (and for any documentation on that).
Here's the response from the MCSDK team:
"Customer can download portfolio from below link for this device:
that portfolio has the user’s guide for Ethernet Switch sub-system which should be able to answer the question of promiscuous mode."
Can you please help me where in this document is something about the way i can put my board in the promiscuous mode. The only things i found was about frame statistic, pleas correct me if i'm wrong.
I think this may be the information that you're looking for:
Just one question is this also for the TMS320C6678?
Yes, as far as I was informed this is the correct document. However, I can double check for you.
Was there a problem that you've hit with it? Or are you just unsure because the title says "6655/57"?
Yes I was unsure because of the title. How can i change the bit value at this hex address?
Sorry if this question is stupid but i haven't done something before.
The C6678 and C6657 have different Ethernet modules. You will need to refer to the documents for the Gigabit Ethernet (GbE) Switch Subsystem and the Network Co-Processor module.
Since the word "promiscuous" shows up in the GbE User's Guide only in reference to status bits, it is not supported the same way as the previous devices. It is not mentioned in the MCSDK documents or source files for the C6678 GbE use, so I doubt that our drivers were written to support that mode.
Perhaps someone from the driver team will join the conversation to say that there is support available, but my recommendation is to study these two documents (GbE and NetCP) to learn in detail how they operate and figure out how to write this feature in a driver yourself. In other words I do not expect you to find support in our drivers since this is not a normal communication operation that is needed for most use of the peripheral.
The device may be capable, and if your studies bring you to have specific questions about logic in the GbE or NetCP modules, please ask those in the device forum.
You may also want to review some of the training material available. In the Training section of TI.com, there is a training video set for the C66x SOC architecture. It may be helpful for you to review all of the modules. There is a training video on the NetCP, but I did not notice one for the GbE. You can find the complete video set here.
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.