Hello,
Is there an ethernet stack available in sysbios for the TMS320C674x devices? If not, when?
Thanks!
Paul
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.
Hello,
Is there an ethernet stack available in sysbios for the TMS320C674x devices? If not, when?
Thanks!
Paul
PaulSchoenke said:Is there an ethernet stack available in sysbios for the TMS320C674x devices? If not, when?
There actually is an OS-less software package that has a TCP/IP stack.
http://www.ti.com/tool/starterware-c6dsp
Hi Brandon,
First of all I'm a bit lost :} We have developed a number of products using C6701/C6711/C6713/C6722 over the years using CCS3 and our own code to do interrupts/EDMA/Serial/Simple threading etc. We now want to move to C6748 with Ethernet by initially using the C6748 SOM developed by LogicPD. We have a TMDSEVML138-B for evaluation. I had some early success with using CCS4, downloading the TCPIP Stack that runs under DSP/BIOS5. The Client Demo Works and I was able to serve a web page and echo Socket data and test throughput. All looked good. But since then I've been spinning my wheels for two months. I develop under MS Windows btw. I've tried various combinations of CC4 and CC5, DSP/BIOS5 and SYS/BIOS6, with the TCPIP Stack, and I can't find any tutorial or quickstart that matches my screens or versions that I can follow and get even the simplest example to work or allow me to modify it to do something like add in a timer task or interrupt.
Now there is this starterware-c6dsp approach. It looks attractive to me as SYS/BIOS looks overly complicated and I worry I won't have enough low level control to meet my real-time microsecond deadlines. I downloaded and imported the examples and they Build without errors. But I can't run/debug them. Maybe I don't have the right Target configuration. Seems like XDS100V1 or 2 and TMS320C6748 should be correct and it "Tests" ok. But the the code won't load. The .cmd sets the code to load at 0xC0000000 which fails. If I change the linker to put stuff in L2 internal memory instead of DDR2 memory the code loads, I can step through it, but it doesn't seem to work (DHCP fails and such).
I apologize for the long-winded request. But I would like some recommendation from TI to point me in a recommended direction. We are fairly open as we are making a significant architecture change and want to go with the best set of tools that are currently available.
Any help greatly appreciated and I can supply any other needed info on request and/or if I should post this somewhere else.
Thanks
Tom K