element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum TCP/IP commnunications while GPIO interrupt
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 20 replies
  • Subscribers 677 subscribers
  • Views 4046 views
  • Users 0 members are here
  • raspberry_pi_b+
  • raspberry_pi
  • raspberry-pi
Related

TCP/IP commnunications while GPIO interrupt

Former Member
Former Member over 10 years ago

Hi,

 

I am developing an audio recording system using Raspberry Pi B+.

 

To guarantee the sampling rate, an external GPIO interrupt with 16 kHz  was implemented.

Then, for each interrupt, A/D conversion having 16-bit resolution was followed to get a sample.

Finally, for every 100ms, the buffered 1600 samples were transmitted to the server PC by applying TCP/IP-based communications.

 

However, I found that several samples were missed whenever the buffered samples were transmitted by TCP/IP.

I doubt that the GPIO interrupt for A/D conversion was missed whenever the TCP/IP socket communications are executed.

 

The core program codes written in C are as follows.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

        struct sockaddr_in server_addr;

 

        //External GPIO interrupt setting      

        wiringPiSetup();

        pinMode(5, INPUT);

        wiringPiISR(5, INT_EDGE_FALLING, &ISR);

 

         //Setting for TCP/IP socket communications

        Socket = socket(AF_INET, SOCK_DGRAM, 0);
        bzero((char *)&server_addr, sizeof(server_addr));

        server_addr.sin_family = AF_INET;
        server_addr.sin_addr.s_addr = inet_addr("192.168.0.3");
        server_addr.sin_port = htons(8101);

        connect(Socket, (struct sockaddr *)&server_addr, sizeof(server_addr);

 

        while(1)

        {

              //Buffered samples transmitting

              if(buffFullFlag == TRUE) write(Socket, buf0, BUF_LEN*sizeof(unsigned short));    

         }

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The attached file shows an example of the waveform of transmitted data.

 

Could you tell me the reason and solution about my problem ??

Attachments:
imageGPIO interrupt error.pdf
  • Sign in to reply
  • Cancel
Parents
  • Problemchild
    0 Problemchild over 10 years ago

    16 K interrupts per second is a very large number for a whole Linux infrastructure to be disrupted. The overhead is quite probably eating right into your available CPU power just there. Rather than a simple ADC I would suggest you use an audio CODEC IC which although a little more complex than a simple ADC has everything already sorted and probably a big buffer meaning that you can sample at higher rates with out excessive interrupt overhead. Take a look at the Wolfson Codec strapped to the Audio board that E14 sell this would sort you out if it does recording ....Yes it does image

     

    Signal conditioning and everything else in one ready for your application.  This will reduce your overheads supporting realtime sampling costs of construction etc even if you change after prototype stage!

     

    John A

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Problemchild
    0 Problemchild over 10 years ago

    16 K interrupts per second is a very large number for a whole Linux infrastructure to be disrupted. The overhead is quite probably eating right into your available CPU power just there. Rather than a simple ADC I would suggest you use an audio CODEC IC which although a little more complex than a simple ADC has everything already sorted and probably a big buffer meaning that you can sample at higher rates with out excessive interrupt overhead. Take a look at the Wolfson Codec strapped to the Audio board that E14 sell this would sort you out if it does recording ....Yes it does image

     

    Signal conditioning and everything else in one ready for your application.  This will reduce your overheads supporting realtime sampling costs of construction etc even if you change after prototype stage!

     

    John A

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube