TCP/IP Stack Micrchip EEPROM Includen

[sven (Gast)]

Hallo zusammen, Hallo Stampede :),

ich habe für mein eigenes Board den TCP IP STack von Microchip 
inkludiert und das funktioniert soweit auch. Bis dato habe ich das 
Image.s immer im internen Speicher abgelegt.

Jetzt würde ich gerne mein EEPROM nutzen.

d.h. in der TCPIP MRF.h

#define MPFS_USE_EEPROM

In der HWP EX16.h die SPI Leitungen auf meine gegebene Hardware matchen 
(SCK1, SDI1, Chip select usw.)

Beim compilieren kommt nun folgender Fehler:
"You_cannot_call_the_XEEInit_function_without_defining_EEPROM_CS_TRIS_in 
_HardwareProfile_h_first(void);"

mit dem folgenden Hinweis:
"// If you get any of these linker errors, it means that you either have 
an error in your HardwareProfile.h or TCPIPConfig.h definitions.  The 
code is attempting to call a function that can't possibly work because 
you
have not specified what pins and SPI module the physical SPI EEPROM chip
is connected to.  Alternatively, if you don't have an SPI EERPOM chip, 
it
means you have enabled a stack feature that requires SPI EEPROM 
hardware.
In this case, you need to edit TCPIPConfig.h and disable this stack
feature.  The linker error tells you which object file this error was
generated from.  It should be a clue as to what feature you need to
disable."

Ich vermute also dass ich noch etwas in der TCP.h aus- bzw. 
einkommentieren muss.

Vielleicht hat jemand eine Idee:

Meine TCP.h

 * V5.36   ---- STACK_USE_MPFS support has been removed 
 ********************************************************************/
#ifndef __TCPIPCONFIG_H
#define __TCPIPCONFIG_H

#include "GenericTypeDefs.h"
#include "Compiler.h"
#define GENERATED_BY_TCPIPCONFIG "Version 1.0.3383.23374"

// =======================================================================
//   Application Options
// =======================================================================

// Note: For the PIC24FJ128GA010, due to code memory limitations, the following items
//       must be commented out: STACK_USE_ZEROCONF_LINK_LOCAL, STACK_USE_DNS_SERVER,
//       STACK_USE_NBNS, STACK_USE_ANNOUNCE, STACK_USE_ICMP_CLIENT, STACK_USE_REBOOT_SERVER

/* Application Level Module Selection
 *   Uncomment or comment the following lines to enable or
 *   disabled the following high-level application modules.
 *
 * If certain compilations are enabled (eg STACK_USE_GENERIC_TCP_CLIENT_EXAMPLE), 
 * check whether the files (eg GenericTCPClient.c) are located in folder (eg \TCPIP\WiFi EZConfig).
 * You may need to copy such files from the Demo App or WiFi Console folder.
 *
 */
#define STACK_USE_UART          // Application demo using UART for IP address display and stack configuration
//#define STACK_USE_UART2TCP_BRIDGE    // UART to TCP Bridge application example
//#define STACK_USE_IP_GLEANING
#define STACK_USE_ICMP_SERVER      // Ping query and response capability
//#define STACK_USE_ICMP_CLIENT      // Ping transmission capability
#define STACK_USE_HTTP2_SERVER      // New HTTP server with POST, Cookies, Authentication, etc.
//#define STACK_USE_SSL_SERVER      // SSL server socket support (Requires SW300052)
//#define STACK_USE_SSL_CLIENT      // SSL client socket support (Requires SW300052)
//#define STACK_USE_AUTO_IP               // Dynamic link-layer IP address automatic configuration protocol
#define STACK_USE_DHCP_CLIENT      // Dynamic Host Configuration Protocol client for obtaining IP address and other parameters
#define STACK_USE_DHCP_SERVER      // Single host DHCP server
//#define STACK_USE_FTP_SERVER      // File Transfer Protocol (old)
//#define STACK_USE_SMTP_CLIENT      // Simple Mail Transfer Protocol for sending email
//#define STACK_USE_SNMP_SERVER      // Simple Network Management Protocol v2C Community Agent
//#define STACK_USE_SNMPV3_SERVER      // Simple Network Management Protocol v3 Agent
//#define STACK_USE_TFTP_CLIENT      // Trivial File Transfer Protocol client
//#define STACK_USE_GENERIC_TCP_CLIENT_EXAMPLE  // HTTP Client example in GenericTCPClient.c. If using EZConfig, need to copy this file from Demo App or WiFi Console.
//#define STACK_USE_GENERIC_TCP_SERVER_EXAMPLE  // ToUpper server example in GenericTCPServer.c. If using EZConfig, need to copy this file from Demo App or WiFi Console.
//#define STACK_USE_TELNET_SERVER      // Telnet server
//#define STACK_USE_ANNOUNCE        // Microchip Embedded Ethernet Device Discoverer server/client
#define STACK_USE_DNS          // Domain Name Service Client for resolving hostname strings to IP addresses
//#define STACK_USE_DNS_SERVER      // Domain Name Service Server for redirection to the local device
//#define STACK_USE_NBNS          // NetBIOS Name Service Server for repsonding to NBNS hostname broadcast queries
//#define STACK_USE_REBOOT_SERVER      // Module for resetting this PIC remotely.  Primarily useful for a Bootloader.
//#define STACK_USE_SNTP_CLIENT      // Simple Network Time Protocol for obtaining current date/time from Internet
//#define STACK_USE_UDP_PERFORMANCE_TEST  // Module for testing UDP TX performance characteristics.  NOTE: Enabling this will cause a huge amount of UDP broadcast packets to flood your network on the discard port.  Use care when enabling this on production networks, especially with VPNs (could tunnel broadcast traffic across a limited bandwidth connection).
//#define STACK_USE_TCP_PERFORMANCE_TEST  // Module for testing TCP TX performance characteristics
//#define STACK_USE_DYNAMICDNS_CLIENT    // Dynamic DNS client updater module
//#define STACK_USE_BERKELEY_API      // Berekely Sockets APIs are available

//#define STACK_USE_ZEROCONF_LINK_LOCAL  // Zeroconf IPv4 Link-Local Addressing
#define STACK_USE_ZEROCONF_MDNS_SD    // Zeroconf mDNS and mDNS service discovery
#if defined(CFG_INCLUDE_EX16_MRF24WG) && defined(__C32__)
//#define STACK_USE_TCP_MOBILE_APP_SERVER  // This is valid only with Explorer16 eval board and MRF24WG Wi-Fi module
#ifdef STACK_USE_TCP_MOBILE_APP_SERVER
#ifndef STACK_USE_ZEROCONF_LINK_LOCAL && !defined(__PIC24FJ128GA010__)
//#define STACK_USE_ZEROCONF_LINK_LOCAL  // Zeroconf IPv4 Link-Local Addressing
#endif
#ifndef STACK_USE_ZEROCONF_MDNS_SD
#define STACK_USE_ZEROCONF_MDNS_SD    // Zeroconf mDNS and mDNS service discovery
#endif
#endif /* STACK_USE_TCP_MOBILE_APP_SERVER */
#endif  /* CFG_INCLUDE_EX16_MRF24WG  */

// =======================================================================
//   Data Storage Options
// =======================================================================

/* MPFS Configuration
 *   MPFS is automatically included when required for other
 *   applications.  If your custom application requires it
 *   otherwise, uncomment the appropriate selection.
 */
 #define STACK_USE_MPFS2

/* MPFS Storage Location
 *   If html pages are stored in internal program memory,
 *   comment both MPFS_USE_EEPROM and MPFS_USE_SPI_FLASH, then
 *   include an MPFS image (.c or .s file) in the project.
 *   If html pages are stored in external memory, uncomment the
 *   appropriate definition.
 *
 *   Supported serial flash parts include the SST25VFxxxB series.
 */
#define MPFS_USE_EEPROM
//#define MPFS_USE_SPI_FLASH

/* EEPROM Addressing Selection
 *   If using the 1Mbit EEPROM, uncomment this line
 */
//#define USE_EEPROM_25LC1024

/* EEPROM Reserved Area
 *   Number of EEPROM bytes to be reserved before MPFS storage starts.
 *   These bytes host application configurations such as IP Address,
 *   MAC Address, and any other required variables.
 *
 *   For MPFS Classic, this setting must match the Reserved setting
 *   on the Advanced Settings page of the MPFS2 Utility.
 */
#define MPFS_RESERVE_BLOCK        (205ul)

/* MPFS File Handles
 *   Maximum number of simultaneously open MPFS2 files.
 *   For MPFS Classic, this has no effect.
 */
#define MAX_MPFS_HANDLES        (7ul)


// =======================================================================
//   Network Addressing Options
// =======================================================================

/* Default Network Configuration
 *   These settings are only used if data is not found in EEPROM.
 *   To clear EEPROM, hold BUTTON0, reset the board, and continue
 *   holding until the LEDs flash.  Release, and reset again.
 */
#define MY_DEFAULT_HOST_NAME      "MCHPBOARD"

#define MY_DEFAULT_MAC_BYTE1            (0x00)  // Use the default of 00-04-A3-00-00-00
#define MY_DEFAULT_MAC_BYTE2            (0x04)  // if using an ENCX24J600, MRF24W, or
#define MY_DEFAULT_MAC_BYTE3            (0xA3)  // PIC32MX6XX/7XX internal Ethernet 
#define MY_DEFAULT_MAC_BYTE4            (0x00)  // controller and wish to use the 
#define MY_DEFAULT_MAC_BYTE5            (0x00)  // internal factory programmed MAC
#define MY_DEFAULT_MAC_BYTE6            (0x00)  // address instead.

#define MY_DEFAULT_IP_ADDR_BYTE1        (169ul)
#define MY_DEFAULT_IP_ADDR_BYTE2        (254ul)
#define MY_DEFAULT_IP_ADDR_BYTE3        (1ul)
#define MY_DEFAULT_IP_ADDR_BYTE4        (1ul)

#define MY_DEFAULT_MASK_BYTE1           (255ul)
#define MY_DEFAULT_MASK_BYTE2           (255ul)
#define MY_DEFAULT_MASK_BYTE3           (0ul)
#define MY_DEFAULT_MASK_BYTE4           (0ul)

#define MY_DEFAULT_GATE_BYTE1           (169ul)
#define MY_DEFAULT_GATE_BYTE2           (254ul)
#define MY_DEFAULT_GATE_BYTE3           (1ul)
#define MY_DEFAULT_GATE_BYTE4           (1ul)

#define MY_DEFAULT_PRIMARY_DNS_BYTE1  (169ul)
#define MY_DEFAULT_PRIMARY_DNS_BYTE2  (254ul)
#define MY_DEFAULT_PRIMARY_DNS_BYTE3  (1ul)
#define MY_DEFAULT_PRIMARY_DNS_BYTE4  (1ul)

#define MY_DEFAULT_SECONDARY_DNS_BYTE1  (0ul)
#define MY_DEFAULT_SECONDARY_DNS_BYTE2  (0ul)
#define MY_DEFAULT_SECONDARY_DNS_BYTE3  (0ul)
#define MY_DEFAULT_SECONDARY_DNS_BYTE4  (0ul)

// =======================================================================
//   PIC32MX7XX/6XX MAC Layer Options
//   If not using a PIC32MX7XX/6XX device, ignore this section.
// =======================================================================
#define  ETH_CFG_LINK      0    // set to 1 if you need to config the link to specific following parameters
                    // otherwise the default connection will be attempted
                    // depending on the selected PHY
  #define  ETH_CFG_AUTO    1    // use auto negotiation
  #define  ETH_CFG_10      1    // use/advertise 10 Mbps capability
  #define  ETH_CFG_100      1    // use/advertise 100 Mbps capability
  #define  ETH_CFG_HDUPLEX    1    // use/advertise half duplex capability
  #define  ETH_CFG_FDUPLEX    1    // use/advertise full duplex capability
  #define  ETH_CFG_AUTO_MDIX  1    // use/advertise auto MDIX capability
  #define  ETH_CFG_SWAP_MDIX  1    // use swapped MDIX. else normal MDIX

#define EMAC_TX_DESCRIPTORS    2    // number of the TX descriptors to be created
#define EMAC_RX_DESCRIPTORS    8    // number of the RX descriptors and RX buffers to be created

#define  EMAC_RX_BUFF_SIZE    1536  // size of a RX buffer. should be multiple of 16
                    // this is the size of all receive buffers processed by the ETHC
                    // The size should be enough to accomodate any network received packet
                    // If the packets are larger, they will have to take multiple RX buffers
                    // The current implementation does not handle this situation right now and the packet is discarded.


// =======================================================================
//   Transport Layer Options
// =======================================================================

/* Transport Layer Configuration
 *   The following low level modules are automatically enabled
 *   based on module selections above.  If your custom module
 *   requires them otherwise, enable them here.
 */
#define STACK_USE_TCP
#define STACK_USE_UDP

/* Client Mode Configuration
 *   Uncomment following line if this stack will be used in CLIENT
 *   mode.  In CLIENT mode, some functions specific to client operation
 *   are enabled.
 */
#if defined(STACK_USE_DHCP_CLIENT) || defined(STACK_USE_ICMP_CLIENT)
#define STACK_CLIENT_MODE
#endif

/* TCP Socket Memory Allocation
 *   TCP needs memory to buffer incoming and outgoing data.  The
 *   amount and medium of storage can be allocated on a per-socket
 *   basis using the example below as a guide.
 */
  // Allocate how much total RAM (in bytes) you want to allocate
  // for use by your TCP TCBs, RX FIFOs, and TX FIFOs.
  #define TCP_ETH_RAM_SIZE          (8192ul)
  #define TCP_PIC_RAM_SIZE          (0ul)
  #define TCP_SPI_RAM_SIZE          (0ul)
  #define TCP_SPI_RAM_BASE_ADDRESS      (0x00)

  // Define names of socket types
  #define TCP_SOCKET_TYPES
    #define TCP_PURPOSE_GENERIC_TCP_CLIENT 0
    #define TCP_PURPOSE_GENERIC_TCP_SERVER 1
    #define TCP_PURPOSE_TELNET 2
    #define TCP_PURPOSE_FTP_COMMAND 3
    #define TCP_PURPOSE_FTP_DATA 4
    #define TCP_PURPOSE_TCP_PERFORMANCE_TX 5
    #define TCP_PURPOSE_TCP_PERFORMANCE_RX 6
    #define TCP_PURPOSE_UART_2_TCP_BRIDGE 7
    #define TCP_PURPOSE_HTTP_SERVER 8
    #define TCP_PURPOSE_DEFAULT 9
    #define TCP_PURPOSE_BERKELEY_SERVER 10
    #define TCP_PURPOSE_BERKELEY_CLIENT 11
    #define TCP_PURPOSE_MOBILE_APP_SERVER 12
  #define END_OF_TCP_SOCKET_TYPES

  #if defined(__TCP_C)
    // Define what types of sockets are needed, how many of
    // each to include, where their TCB, TX FIFO, and RX FIFO
    // should be stored, and how big the RX and TX FIFOs should
    // be.  Making this initializer bigger or smaller defines
    // how many total TCP sockets are available.
    //
    // Each socket requires up to 56 bytes of PIC RAM and
    // 48+(TX FIFO size)+(RX FIFO size) bytes of TCP_*_RAM each.
    //
    // Note: The RX FIFO must be at least 1 byte in order to
    // receive SYN and FIN messages required by TCP.  The TX
    // FIFO can be zero if desired.
    #define TCP_CONFIGURATION
    ROM struct
    {
      BYTE vSocketPurpose;
      BYTE vMemoryMedium;
      WORD wTXBufferSize;
      WORD wRXBufferSize;
    } TCPSocketInitializer[] =
    {
      {TCP_PURPOSE_GENERIC_TCP_CLIENT, TCP_ETH_RAM, 1024, 20},
      {TCP_PURPOSE_GENERIC_TCP_SERVER, TCP_ETH_RAM, 20, 1024},
      //{TCP_PURPOSE_TELNET, TCP_ETH_RAM, 200, 150},
      //{TCP_PURPOSE_TELNET, TCP_ETH_RAM, 200, 150},
      //{TCP_PURPOSE_TELNET, TCP_ETH_RAM, 200, 150},
      //{TCP_PURPOSE_FTP_COMMAND, TCP_ETH_RAM, 100, 40},
      //{TCP_PURPOSE_FTP_DATA, TCP_ETH_RAM, 0, 128},
      //{TCP_PURPOSE_TCP_PERFORMANCE_TX, TCP_ETH_RAM, 200, 1},
      //{TCP_PURPOSE_TCP_PERFORMANCE_RX, TCP_ETH_RAM, 40, 1500},
      //{TCP_PURPOSE_UART_2_TCP_BRIDGE, TCP_ETH_RAM, 256, 256},
      {TCP_PURPOSE_HTTP_SERVER, TCP_ETH_RAM, 1000, 1000},
      {TCP_PURPOSE_HTTP_SERVER, TCP_ETH_RAM, 1000, 1000},
#if defined(STACK_USE_TCP_MOBILE_APP_SERVER)
      {TCP_PURPOSE_MOBILE_APP_SERVER, TCP_ETH_RAM, 1000, 1000},
#endif
      //{TCP_PURPOSE_DEFAULT, TCP_ETH_RAM, 1000, 1000},
      //{TCP_PURPOSE_BERKELEY_SERVER, TCP_ETH_RAM, 25, 20},
      //{TCP_PURPOSE_BERKELEY_SERVER, TCP_ETH_RAM, 25, 20},
      //{TCP_PURPOSE_BERKELEY_SERVER, TCP_ETH_RAM, 25, 20},
      //{TCP_PURPOSE_BERKELEY_CLIENT, TCP_ETH_RAM, 125, 100},
    };
    #define END_OF_TCP_CONFIGURATION
  #endif

/* UDP Socket Configuration
 *   Define the maximum number of available UDP Sockets, and whether
 *   or not to include a checksum on packets being transmitted.
 */
#define MAX_UDP_SOCKETS     (8u)
//#define UDP_USE_TX_CHECKSUM    // This slows UDP TX performance by nearly 50%, except when using the ENCX24J600 or PIC32MX6XX/7XX, which have a super fast DMA and incurs virtually no speed pentalty.


/* Berkeley API Sockets Configuration
 *   Note that each Berkeley socket internally uses one TCP or UDP socket
 *   defined by MAX_UDP_SOCKETS and the TCPSocketInitializer[] array.
 *   Therefore, this number MUST be less than or equal to MAX_UDP_SOCKETS + the
 *   number of TCP sockets defined by the TCPSocketInitializer[] array
 *   (i.e. sizeof(TCPSocketInitializer)/sizeof(TCPSocketInitializer[0])).
 *   This define has no effect if STACK_USE_BERKELEY_API is not defined and
 *   Berkeley Sockets are disabled.  Set this value as low as your application
 *   requires to avoid waisting RAM.
 */
#define BSD_SOCKET_COUNT (5u)


// =======================================================================
//   Application-Specific Options
// =======================================================================

// -- HTTP2 Server options -----------------------------------------------

  // Maximum numbers of simultaneous HTTP connections allowed.
  // Each connection consumes 2 bytes of RAM and a TCP socket
  #define MAX_HTTP_CONNECTIONS  (2u)

  // Optional setting to use PIC RAM instead of Ethernet/Wi-Fi RAM for
  // storing HTTP Connection Context variables (HTTP_CONN structure for each 
  // HTTP connection).  Undefining this macro results in the Ethernet/Wi-Fi 
  // RAM being used (minimum PIC RAM usage, lower performance).  Defining 
  // this macro results in PIC RAM getting used (higher performance, but uses 
  // PIC RAM).  This option should not be enabled on PIC18 devices.  The 
  // performance increase of having this option defined is only apparent when 
  // the HTTP server is servicing multiple connections simultaneously.
  //#define HTTP_SAVE_CONTEXT_IN_PIC_RAM

  // Indicate what file to serve when no specific one is requested
  #define HTTP_DEFAULT_FILE    "index.htm"
  #define HTTPS_DEFAULT_FILE    "index.htm"
  #define HTTP_DEFAULT_LEN    (10u)    // For buffer overrun protection.
                        // Set to longest length of above two strings.

  // Configure MPFS over HTTP updating
  // Comment this line to disable updating via HTTP
  #define HTTP_MPFS_UPLOAD    "mpfsupload"
  //#define HTTP_MPFS_UPLOAD_REQUIRES_AUTH  // Require password for MPFS uploads
    // Certain firewall and router combinations cause the MPFS2 Utility to fail
    // when uploading.  If this happens, comment out this definition.

  // Define which HTTP modules to use
  // If not using a specific module, comment it to save resources
  #define HTTP_USE_POST          // Enable POST support
  //#define HTTP_USE_COOKIES        // Enable cookie support
  //#define HTTP_USE_AUTHENTICATION      // Enable basic authentication support

  //#define HTTP_NO_AUTH_WITHOUT_SSL    // Uncomment to require SSL before requesting a password

    // Define the listening port for the HTTP server
    #define HTTP_PORT               (80u)
  
    // Define the listening port for the HTTPS server (if STACK_USE_SSL_SERVER is enabled)
  #define HTTPS_PORT        (443u)
  
    // Define the maximum data length for reading cookie and GET/POST arguments (bytes)
  #define HTTP_MAX_DATA_LEN    (100u)
  
    // Define the minimum number of bytes free in the TX FIFO before executing callbacks
  #define HTTP_MIN_CALLBACK_FREE  (16u)

  //#define STACK_USE_HTTP_APP_RECONFIG    // Use the AppConfig web page in the Demo App (~2.5kb ROM, ~0b RAM)
  //#define STACK_USE_HTTP_MD5_DEMO      // Use the MD5 Demo web page (~5kb ROM, ~160b RAM)
  //#define STACK_USE_HTTP_EMAIL_DEMO    // Use the e-mail demo web page

// -- SSL Options --------------------------------------------------------

  #define MAX_SSL_CONNECTIONS    (2ul)  // Maximum connections via SSL
  #define MAX_SSL_SESSIONS    (2ul)  // Max # of cached SSL sessions
  #define MAX_SSL_BUFFERS      (4ul)  // Max # of SSL buffers (2 per socket)
  #define MAX_SSL_HASHES      (5ul)  // Max # of SSL hashes  (2 per, plus 1 to avoid deadlock)

  // Bits in SSL RSA key.  This parameter is used for SSL sever
  // connections only.  The only valid value is 512 bits (768 and 1024
  // bits do not work at this time).  Note, however, that SSL client
  // operations do currently work up to 1024 bit RSA key length.
  #define SSL_RSA_KEY_SIZE    (512ul)


// -- Telnet Options -----------------------------------------------------

  // Number of simultaneously allowed Telnet sessions.  Note that you
  // must have an equal number of TCP_PURPOSE_TELNET type TCP sockets
  // declared in the TCPSocketInitializer[] array above for multiple
  // connections to work.  If fewer sockets are available than this
  // definition, then the the lesser of the two quantities will be the
  // actual limit.
  #define MAX_TELNET_CONNECTIONS  (1u)

  // Default local listening port for the Telnet server.  Port 23 is the
  // protocol default.
  #define TELNET_PORT        23

  // Default local listening port for the Telnet server when SSL secured.
  // Port 992 is the telnets protocol default.
  #define TELNETS_PORT      992

  // Force all connecting clients to be SSL secured and connected via
  // TELNETS_PORT.  Connections on port TELNET_PORT will be ignored.  If
  // STACK_USE_SSL_SERVER is undefined, this entire setting is ignored
  // (server will accept unsecured connections on TELNET_PORT and won't even
  // listen on TELNETS_PORT).
  //#define TELNET_REJECT_UNSECURED

  // Default username and password required to login to the Telnet server.
  #define TELNET_USERNAME      "admin"
  #define TELNET_PASSWORD      "microchip"


// -- SNMP Options -------------------------------------------------------

  // Comment following line if SNMP TRAP support is needed
  //#define SNMP_TRAP_DISABLED

  //#define SNMP_STACK_USE_V2_TRAP
  #if defined(STACK_USE_SNMPV3_SERVER)
    #define SNMP_V1_V2_TRAP_WITH_SNMPV3
  #endif

  // This is the maximum length for community string.
  // Application must ensure that this length is observed.
  // SNMP module adds one byte extra after SNMP_COMMUNITY_MAX_LEN
  // for adding '\0' NULL character.
  #define SNMP_COMMUNITY_MAX_LEN    (8u)
  #define SNMP_MAX_COMMUNITY_SUPPORT  (3u)
  #define NOTIFY_COMMUNITY_LEN    (SNMP_COMMUNITY_MAX_LEN)

  // Default SNMPv2C community names.  These can be overridden at run time if
  // alternate strings are present in external EEPROM or Flash (actual
  // strings are stored in AppConfig.readCommunity[] and
  // AppConfig.writeCommunity[] arrays).  These strings are case sensitive.
  // An empty string means disabled (not matchable).
  // For application security, these default community names should not be
  // used, but should all be disabled to force the end user to select unique
  // community names.  These defaults are provided only to make it easier to
  // start development.  Specifying more strings than
  // SNMP_MAX_COMMUNITY_SUPPORT will result in the later strings being
  // ignored (but still wasting program memory).  Specifying fewer strings is
  // legal, as long as at least one is present.  A string larger than
  // SNMP_COMMUNITY_MAX_LEN bytes will be ignored.
  #define SNMP_READ_COMMUNITIES    {"public", "read", ""}
  #define END_OF_SNMP_READ_COMMUNITIES
  #define SNMP_WRITE_COMMUNITIES       {"private", "write", "public"}
  #define END_OF_SNMP_WRITE_COMMUNITIES
#endif

[Dummschwaetzer (Gast)]

In this case, you need to edit TCPIPConfig.h and disable this stack
feature.  The linker error tells you which object file this error was
generated from.  It should be a clue as to what feature you need to
disable."

[sven (Gast)]

Dummschwaetzer schrieb:
> In this case, you need to edit TCPIPConfig.h and disable this
> stack
> feature.  The linker error tells you which object file this error was
> generated from.  It should be a clue as to what feature you need to
> disable."


Danke :)
Der Linker Error ist ja

"You_cannot_call_the_XEEInit_function_without_defining_EEPROM_CS_TRIS_in 
_HardwareProfile_h_first"

Leider sagt mir das nichts über das Object file aus oder was auch immer 
ich in der TCPIP.h ändern muss.

Das EEPROM_CS_TRIS et. habe ich ja bereits in der HWP EX16_MRF24W XC16.h 
definiert!

[sven (Gast)]

Die HWP EX16_MRF24W XC16.h wird dann auch in der Hardwareprofile.h über
#include "Configs/HWP EX16_MRF24W XC16.h"
inkludiert. Da stehen ja meine ganzen Hardware Deklarationen bzgl. des 
EEPROM Drin. Deswegen verstehe ich die Fehlermeldung nicht ganz!

[Stampede (Gast)]

Hi,

der Fehler wird von der Datei XEEPROM.h generiert, welche die 
"HardwareProfile.h" einbindet. Die Frage ist nun, welches Hardwareprofil 
wird von "HardwareProfile.h" eingebunden?
"Configs/HWP EX16_MRF24W XC16.h" kann es ja eigentlich nicht sein, da 
sonst das EEPROM_TRIS bekann sein würde. Ebenso macht es eigentlich 
keinen Sinn, das Profil für den Explorer16 auf einem eigenen Board zu 
verwenden.

>>Die HWP EX16_MRF24W XC16.h wird dann auch in der Hardwareprofile.h über
>>#include "Configs/HWP EX16_MRF24W XC16.h"
Sicher?

Gruß
Stampede

[sven (Gast)]

Hallo Stampede.

Auf dich ist einfach Verlass :)

Ich habe mir halt eine eigene Leiterplatte entwickelt und als 
Grundgerüst das Explorer16 also die HWP EX16_MRF24W XC16.h ausgewählt 
und dann an meine Hardware angeglichen. Wie gesagt läuft der TCP/IP 
Stack auch ohne EEPROM schon mal.

Stampede schrieb:
> Hi,
>
> der Fehler wird von der Datei XEEPROM.h generiert, welche die
> "HardwareProfile.h" einbindet. Die Frage ist nun, welches Hardwareprofil
> wird von "HardwareProfile.h" eingebunden?
> "Configs/HWP EX16_MRF24W XC16.h" kann es ja eigentlich nicht sein...

Doch leider wohl Auszug aus der "HardwareProfile.h":

defined(CFG_INCLUDE_EX16_MRF24WB) || defined(CFG_INCLUDE_EX16_MRF24WG)
  // DM240001 Explorer 16 board, PIC24FJ128GA010/PIC24FJ256GB110/PIC24FJ256GA110/PIC24FJ256GB210/PIC24HJ256GP610/dsPIC33FJ256GP710/PIC32MX360F512L/PIC32MX460F512L/PIC32MX795F512L/possibly others, AC164136-4 MRF24W Wi-Fi PICtail/PICtail Plus
  #if defined(__C30__)
    #include "Configs/HWP EX16_MRF24W XC16.h"
                
  #else
    #include "Configs/HWP EX16_MRF24W XC32.h"
  #endif
        #if defined(CFG_INCLUDE_EX16_MRF24WG)
            #define MRF24WG
        #endif

Mit <strg> auf die "Configs/HWP EX16_MRF24W XC16.h" komme ich dann 
direkt in die HWP EX16_MRF24W XC16.h, wo ich das EEPROM initialisert 
habe:

#if defined MPFS_USE_EEPROM
#if defined(__PIC24FJ256GB110__)
  // PIC24FJ256GB110 USB PIM has RD12 pin on Explorer 16 schematic 
  // remapped and actually connected to PIC24FJ256GB110 pin 90 (RG0).  
  #define EEPROM_CS_TRIS    (TRISGbits.TRISG0)
  #define EEPROM_CS_IO    (LATGbits.LATG0)
#elif defined(__PIC24FJ256GB210__)
  // PIC24FJ256GB210 USB PIM has RD12 pin on Explorer 16 schematic 
  // remapped and actually connected to PIC24FJ256GB210 pin 90 (RG0) when 
  // JP1 on PIM has pins 1-2 shorted (USB).  When JP1 pins 2-3 are shorted 
  // (PMP), PIC pin 90 does connect to RD12.  To make the PIM work with 
  // either jumper setting, we will drive both RG0 and RD12 simultaneously
  // as chip select to the same states.  For an actual application, you'd 
  // want to specify only the single necessary pin as this double 
  // assignment operation generates inefficient code by the C compiler.
  #define EEPROM_CS_TRIS    TRISGbits.TRISG0 = TRISDbits.TRISD12
  #define EEPROM_CS_IO    LATGbits.LATG0 = LATDbits.LATD12
#else
        // so auf Leiterplatte
  #define EEPROM_CS_TRIS    (TRISDbits.TRISD13) // CHIPSELECT EE1 an RD13
  #define EEPROM_CS_IO    (LATDbits.LATD13)
        // so auf Starterkit
//  #define EEPROM_CS_TRIS    (TRISDbits.TRISD12)
//  #define EEPROM_CS_IO    (LATDbits.LATD12)
#endif
// ao auf Leiterplatte
#define EEPROM_SCK_TRIS    (TRISDbits.TRISD1)  // SCK1 an RD1
#define EEPROM_SDI_TRIS    (TRISDbits.TRISD1)  // SDI1 an RD12
#define EEPROM_SDO_TRIS    (TRISDbits.TRISD2) // SD01 an RD2
#define EEPROM_SPI_IF    (IFS0bits.SPI1IF)
#define EEPROM_SSPBUF    (SPI1BUF)
#define EEPROM_SPICON1    (SPI1CON1)
#define EEPROM_SPICON1bits  (SPI1CON1bits)
#define EEPROM_SPICON2    (SPI1CON2)
#define EEPROM_SPISTAT    (SPI1STAT)
#define EEPROM_SPISTATbits  (SPI1STATbits)

Deswegen ist es ja auch für mich so verwunderlich!!!

[Stampede (Gast)]

Hallo,

aber das kann ja dann nur noch bedeuten dass "CFG_INCLUDE_EX16_MRF24WB" 
oder "CFG_INCLUDE_EX16_MRF24WG" nicht definiert ist.

[sven (Gast)]

Es scheint aber definiert zu sein (auch wenn ich nicht sehe wo, sonst 
wäre der folgende Code nach nicht farbig, sondern grau unterlegt und ich 
könnte mit <strg> nicht Configs/HWP EX16_MRF24W XC16.h anklicken:

#elif defined(CFG_INCLUDE_EX16_MRF24WB) || defined(CFG_INCLUDE_EX16_MRF24WG)
  // DM240001 Explorer 16 board, PIC24FJ128GA010/PIC24FJ256GB110/PIC24FJ256GA110/PIC24FJ256GB210/PIC24HJ256GP610/dsPIC33FJ256GP710/PIC32MX360F512L/PIC32MX460F512L/PIC32MX795F512L/possibly others, AC164136-4 MRF24W Wi-Fi PICtail/PICtail Plus
  #if defined(__C30__)
    #include "Configs/HWP EX16_MRF24W XC16.h"
                
  #else
    #include "Configs/HWP EX16_MRF24W XC32.h"
  #endif
        #if defined(CFG_INCLUDE_EX16_MRF24WG)
            #define MRF24WG
        #endif

Ich hätte viel mehr erwartet, dass die If Anweisung

#elif defined(HWP EX16_MRF24W XC16.h)

heissen. Keine Ahnung wo die CFG_INCLUDE_EX16_MRF24WB im Stack herkommt, 
aber es scheint wie gesagt definiert zu sein, da es farbig unterlegt ist 
und ich per anlicken direkt in der HWP EX16_MRF24W XC16.h lande.


EDIT:
[/c]#include "Configs/HWP EX16_MRF24W XC16.h"[/c] ist fabig unterlegt, 
da definiert.
[/c]#include "Configs/HWP EX16_MRF24W XC32.h"[/c] natürlich nicht.

Bin ein wenig ratlos!

[sven (Gast)]

HMM. Komischerweise wird in der MAINdemo.c der folgende Befehl in Zeile 
1021

#if defined(EEPROM_CS_TRIS)
    EEPROM_CS_IO = 1;
    EEPROM_CS_TRIS = 0;

auch nicht erkannt. Es scheint also ein Problem zwischen der DEfintion 
in der HWP EX16_MRF24W XC16.h und dem Nutzen dieser in den anderen 
Dateien zu geben. Merkwürdig, da ich in der HWP EX16_MRF24W XC16.h auch 
SPI und alle PINs des MRF definiert habe und es da keine Probleme gab!

[sven (Gast)]

Eine letzte Bemerkung:

ich habe die EEPROM Definitionen in der HWP EX16_MRF24W XC16.h jetzt 
nicht wie VORHER:

#elif defined(__PIC24FJ256GB210__)
  
  //#define EEPROM_CS_TRIS    TRISGbits.TRISG0 = TRISDbits.TRISD12
  //#define EEPROM_CS_IO    LATGbits.LATG0 = LATDbits.LATD12
#else
        // so auf Leiterplatte
  #define EEPROM_CS_TRIS    (TRISDbits.TRISD13) // CHIPSELECT EE1 an RD13
  #define EEPROM_CS_IO    (LATDbits.LATD13)

//#endif
// so auf Leiterplatte
#define EEPROM_SCK_TRIS    (TRISDbits.TRISD1)  // SCK1 an RD1
#define EEPROM_SDI_TRIS    (TRISDbits.TRISD1)  // SDI1 an RD12
#define EEPROM_SDO_TRIS    (TRISDbits.TRISD2) // SD01 an RD2
#define EEPROM_SPI_IF    (IFS0bits.SPI1IF)
#define EEPROM_SSPBUF    (SPI1BUF)
#define EEPROM_SPICON1    (SPI1CON1)
#define EEPROM_SPICON1bits  (SPI1CON1bits)
#define EEPROM_SPICON2    (SPI1CON2)
#define EEPROM_SPISTAT    (SPI1STAT)
#define EEPROM_SPISTATbits  (SPI1STATbits)

#endif

sondern unter die SPI2 Definition geschrieben:

#elif defined(MRF24W_IN_SPI2) && !defined(__32MX460F512L__) && !defined(__32MX795F512L__)
  // SPI3 für mein eigenes Board
        #define WF_CS_TRIS      (TRISBbits.TRISB11)
  #define WF_CS_IO      (LATBbits.LATB11)
  #define WF_SDI_TRIS      (TRISBbits.TRISB13) // SDI3 RPI45
  #define WF_SCK_TRIS      (TRISFbits.TRISF12)  // SCK3 RP108
  #define WF_SDO_TRIS      (TRISFbits.TRISF13) // SDO3 RP109
  #define WF_RESET_TRIS                   (TRISBbits.TRISB9)
  #define WF_RESET_IO      (LATBbits.LATB9)

        // so auf Leiterplatte
  #define EEPROM_CS_TRIS    (TRISDbits.TRISD13) // CHIPSELECT EE1 an RD13
  #define EEPROM_CS_IO    (LATDbits.LATD13)
// so auf Leiterplatte
#define EEPROM_SCK_TRIS    (TRISDbits.TRISD1)  // SCK1 an RD1
#define EEPROM_SDI_TRIS    (TRISDbits.TRISD1)  // SDI1 an RD12
#define EEPROM_SDO_TRIS    (TRISDbits.TRISD2) // SD01 an RD2
#define EEPROM_SPI_IF    (IFS0bits.SPI1IF)
#define EEPROM_SSPBUF    (SPI1BUF)
#define EEPROM_SPICON1    (SPI1CON1)
#define EEPROM_SPICON1bits  (SPI1CON1bits)
#define EEPROM_SPICON2    (SPI1CON2)
#define EEPROM_SPISTAT    (SPI1STAT)
#define EEPROM_SPISTATbits  (SPI1STATbits)

Kann mir dies bitte Jemand erklären?????????

[Stampede (Gast)]

Diese defines "defined(CFG_INCLUDE_EX16_MRF24WB) || 
defined(CFG_INCLUDE_EX16_MRF24WG)" kommen irgendwo aus deinen 
Präprozessoreinstellungen bzw. in den Projekteinstellungen.
"MRF24W_IN_SPI2" hingegen steht ja exakt so in dem File selbst drin.
Das ist der Unterschied und daher reusltiert auch bestimmt der Fehler.

[sven (Gast)]

hmm, OK, danke Dir