element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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 Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • 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
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • 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 I2C communication between PIC16F877a and Raspberry pi 3
  • 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 Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 665 subscribers
  • Views 2132 views
  • Users 0 members are here
  • raspberry_pi
Related

I2C communication between PIC16F877a and Raspberry pi 3

alexvarghese
alexvarghese over 7 years ago

hi,

Can any one help me to start a communication with PIC 16f877a controller and raspberry pi  through I2C protocol .i am new to both Raspberry pi and Pic controller .i know only the basics in Pic and raspberry pi . PIC will sense the data from a ultrasonic sensor. the sensed data has to be transfer to the Rpi .

  • Sign in to reply
  • Cancel
Parents
  • rew
    0 rew over 7 years ago

    Hi,

     

    This is a bit of an ambitious first project. i2c communications is not very easy: Although the protocol allows the slave (your PIC in this case) to slow down communications from the master (the PI in this case), the hardware on the PI has a bug that makes this unreliable.

     

    So in practice, the pic will have to be VERY fast, to be sure that it won't slow down communication with the pi to work around the bug.

     

    I would recommend that you use the UART to communicate with the PIC.

    It is reasonably easy to have something like:

    if (character_available () ) {

       character = get_character ();

       if (character == '\n') { 

          process_command (buffer);

          pos = 0;

       }  else {

         print_character (character);

         buffer[pos++] = character;

       }

     

    So now your PIC can accept commands from the pi. You can use a terminal program like minicom to communicate with your PIC. This allows for easy debugging as well.

     

    Just like i2c, this requires you to hook up two data-wires between the pi and the PIC. (besides power and ground).

     

    I worked with PIC microcontrollers early this century, but I've switched to other microcontrollers since then. So I'm not familiar with the PIC specific details. But I do know stuff about PI, I2C and microcontrollers in general.

     

    (The example code above is slightly too simple: For example, you'll quickly appreciate adding something like:

     

    if ((pos > 0) && (character == DELETE)) {     pos--;

         print_string ("\b \b");

      }

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • rew
    0 rew over 7 years ago

    Hi,

     

    This is a bit of an ambitious first project. i2c communications is not very easy: Although the protocol allows the slave (your PIC in this case) to slow down communications from the master (the PI in this case), the hardware on the PI has a bug that makes this unreliable.

     

    So in practice, the pic will have to be VERY fast, to be sure that it won't slow down communication with the pi to work around the bug.

     

    I would recommend that you use the UART to communicate with the PIC.

    It is reasonably easy to have something like:

    if (character_available () ) {

       character = get_character ();

       if (character == '\n') { 

          process_command (buffer);

          pos = 0;

       }  else {

         print_character (character);

         buffer[pos++] = character;

       }

     

    So now your PIC can accept commands from the pi. You can use a terminal program like minicom to communicate with your PIC. This allows for easy debugging as well.

     

    Just like i2c, this requires you to hook up two data-wires between the pi and the PIC. (besides power and ground).

     

    I worked with PIC microcontrollers early this century, but I've switched to other microcontrollers since then. So I'm not familiar with the PIC specific details. But I do know stuff about PI, I2C and microcontrollers in general.

     

    (The example code above is slightly too simple: For example, you'll quickly appreciate adding something like:

     

    if ((pos > 0) && (character == DELETE)) {     pos--;

         print_string ("\b \b");

      }

    • Cancel
    • Vote Up +2 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