How to use simultaneously TCPIP stack and SD card?

stoyanoff · Joined: 20 Jul 2011 Posts: 375

Hi, everyone! I have CCS Complier v4.134, TCP IP stack v30_November_06 and the mdd package. So I want to create a program which is using both - TCPIP and SD card. So I tried with one of the examples in the tcpip stack - ex7a.c
So I just added the ex_mdd_common.h:

temtronic · Posted: Mon Oct 01, 2012 6:36 am

The error may not be in that header file...but it is in some code before where the error message appears, so you have to look at ALL the code before the error( it can be several lines before...)

on another point, have you got tcpip working by itself ? Then , do you have the SD program working by itself? When both work without the other, then 'merge' the code into one program.

This way you KNOW they work and any errors are due to the 'merging' code.

divide and conqueor !

hth
jay

stoyanoff · Joined: 20 Jul 2011 Posts: 375

The TCPIP stack and the mdd stack works fine separately. So I tried to put them into 1 program but I have to remove the second device declaration and because in my code the mdd header is second I removed there the device options. This is the only one change I made. Now the p18Cxxx.h include returns an error I suppose!
Do you have an example for mix adjustments???

stoyanoff · Joined: 20 Jul 2011 Posts: 375

Does anyone know how to adjust the both stacks??

Ttelmah · Joined: 11 Mar 2010 Posts: 19536

Step back a bit.

Anything beginning with 'ex', is likely to be an _example_, or part of an example, which itself then calls the driver. It is only the driver that you should load if using this with your own code.
So (for instance), ex_fat.c, loads the two drivers, mmcsd.c (low level driver for an mmc card), and then fat.c (which gives the higher level fat access).
Draw a little diagram. Start with the example file. Then show below this what drivers it loads, and the order these are loaded. Then look at the example, and see what order calls are made in (and read the notes in the drivers), so you have the fact that fat_init needs to be called before you start accessing the card.
Then make your main file, and include just the drivers in the order needed, and initialise the devices as needed.
You seem to be trying to 'hybridise' two examples, rather than using them as examples of how to use the drivers.

Best Wishes

stoyanoff · Joined: 20 Jul 2011 Posts: 375

Look! I took one of the tcpip example files - ex7a.c. It has only this include file:

Douglas Kennedy · Joined: 07 Sep 2003 Posts: 755 Location: Florida

The device is specified by ex. #device PIC18F2685.
Maybe a search of all of your code for #device will help you find a second, third or more #device declaration that if present are the source of your issue. If there is only one #device then remember this is a very fast compiler so it needs to know very very earlier on ( preferably on the first line the compiler encounters) the specific PIC device so that it can eliminate initiation code for other devices. Make sure the include usually xxxxx.h where xxxx is ex PIC18F2685.h is the first include the compiler sees and that only comment lines should proceed this include in your main code file.

stoyanoff · Joined: 20 Jul 2011 Posts: 375

I did it! The problem was the both tcpip and the mdd stacks are uncompatible, so I had to change a lot in them. I think CCS team have to work some more in this area.
Best regards!

RF_Developer · Joined: 07 Feb 2011 Posts: 839

The CCS TCP/IP stack is a port of an rather old version of the Microchip stack. Its by far the most complex "driver" that CCS make available. They do not appear to have a common driver format or design strategy, and such drivers are intended as starting points for us developers to develop our own code. CCS have never declared any intention to make drivers "compatible" with each other, nor do they appear to have any means to do so.

Yes, CCS *could* do some more work on this, but this sort of thing, i.e. developing our apps from their *sample* and *example* code, is what WE should be doing. I feel its unfair to berate CCS for this, its not their "fault". Its embedded development. Yes, it would be lovely if all the drivers worked together, and heck, why not make them fully plug and play, and hardware absracted too. Great! But that totally misses the point of small scale embedded development.

RF Developer.

stoyanoff · Joined: 20 Jul 2011 Posts: 375

May be the problem has a simple solution: just write a good self documenting code. The main problem of your examples is that the variables they use have same names. So if you use something like: