• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Embedded Software » BIOS » BIOS forum » NDK configuration items
Share
BIOS
  • Forum
  • Announcements
Options
  • Subscribe via RSS

Forums

NDK configuration items

This question is answered
BrandyJ
Posted by BrandyJ
on May 29 2012 16:42 PM
Genius4370 points

Hello,

I was wondering how the NDK uses the configuration items exactly.  When I set the SOCKUDPRXLIMIT for example, I don't see where that value is used in the ndk.  I mean, if I search for that #define, I only see where it is being set in the CfgAddEntry and not where its being to say, limit the UDP receive packet.


// UDP Receive limit

rc =8192;

CfgAddEntry( hCfg, CFGTAG_IP, CFGITEM_IP_SOCKUDPRXLIMIT, CFG_ADDMODE_UNIQUE, sizeof(uint), (UINT8 *)&rc, 0 );

Can someone please explain this to me?  Maybe my search is not looking in the correct directories.

Thanks,
Brandy

ndk UDP configuration
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Steven Connell
    Posted by Steven Connell
    on May 29 2012 21:08 PM
    Verified Answer
    Verified by BrandyJ
    Mastermind20540 points

    Hi Brandy,

    The NDK defines a struct of type IPCONFIG with default values (in  ti/ndk/stack/res/exec.c):


    // Configuration Structure
    IPCONFIG _ipcfg = { DEF_ICMP_DO_REDIRECT,
                        DEF_ICMP_TTL,
                        DEF_ICMP_TTL_ECHO,
                        DEF_IP_INDEX,
                        DEF_IP_FORWARDING,
                        DEF_IP_NATENABLE,
                        DEF_IP_FILTERENABLE,
                        DEF_IP_REASM_MAXTIME,
                        DEF_IP_REASM_MAXSIZE,
                        DEF_IP_DIRECTED_BCAST,
                        DEF_TCP_REASM_MAXPKT,
                        DEF_RTC_ENABLE_DEBUG,
                        DEF_RTC_RTADV_TIME,
                        DEF_RTC_RTADV_LIFE,
                        DEF_RTC_RTADV_PREF,
                        DEF_LLI_ARP_DOWN_TIME,
                        DEF_LLI_KEEPALIVE_TIMEOUT,
                        DEF_LLI_INACTIVITY_TIMEOUT,
                        DEF_ROUTE_CLONE_TIMEOUT,
                        DEF_ROUTE_DEFAULT_MTU,
                        DEF_SOCK_TTL_DEFAULT,
                        DEF_SOCK_TOS_DEFAULT,
                        DEF_SOCK_MAXCONNECT,
                        DEF_SOCK_TIMECONNECT,
                        DEF_SOCK_TIMEIO,
                        DEF_SOCK_TCPTXBUF,
                        DEF_SOCK_TCPRXBUF,
                        DEF_SOCK_TCPRXLIMIT,
                        DEF_SOCK_UDPRXLIMIT,    // <-- UDP RX LIMIT
                        DEF_SOCK_BUFMINTX,
                        DEF_SOCK_BUFMINRX,
                        DEF_PIPE_TIMEIO,
                        DEF_PIPE_BUFSIZE,
                        DEF_PIPE_BUFMINTX,
                        DEF_PIPE_BUFMINRX,
                        DEF_TCP_KEEP_IDLE,
                        DEF_TCP_KEEP_INTVL,
                        DEF_TCP_KEEP_MAXIDLE,
                        DEF_ICMP_DONT_REPLY_BCAST,
                        DEF_ICMP_DONT_REPLY_MCAST,
                        DEF_RT_RTGARP,
                        DEF_ICMP_DONT_REPLY_ECHO,
                        DEF_UDP_SEND_ICMP_PORTUNREACH,
                        DEF_TCP_SEND_RST,
                        DEF_SOCK_RAWETHRXLIMIT,
                      };



    Then in ti/ndk/inc/stack/inc/resif.h is where the magic is found.  Here there are macros that reference the values in the above struct:

        extern IPCONFIG _ipcfg;             // Configuration

        #define SOCK_UDPRXLIMIT         (_ipcfg.SockUdpRxLimit)


    When the application changes the configuration values using the CfgAddEntry() API (or ti.ndk.config package), these struct values are modified to be the new values.

    Steve

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • BrandyJ
    Posted by BrandyJ
    on May 30 2012 09:23 AM
    Genius4370 points

    So then

    #define CFGITEM_IP_SOCKUDPRXLIMIT  29  // UDP Receive limit

    is set to the 29th item in the structure which aligns with SOCKUDPRXLIMIT.  Ok.

    Then we build a configuration, and it gets copied on top of the defaults in the CfgExecute() function called by the NS_BootTask?

    I guess, you can figure out this question is related to my post about the ICMP/Destination Port Unreachable. 

    Thanks for your help!

    Brandy

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

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.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use