This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

programing 8051 to read spi protocol

hi i am a student tryin to read the data between two spi devices by tapping the lines in the middle please help me if anyone hav a code to read the ss,mosi,miso,sclk signals using GPIO they vl jst act lyk input port n read

Parents
  • Remember that the SPI protocol has various modes of operation. Like data bits captured on falling or rising edges, etc. So ensure that the device you are communicating with are compatible with your processor's code.

    en.wikipedia.org/.../Serial_Peripheral_Interface_Bus

    And since this is a 'class' the idea is that YOU figure it out, and not request 'free' source code. Such free source code might not work, and you won't know how to fix it, and the whole point in 'learning' is lost.

    --Cpt. Vince Foster
    2nd Cannon Place
    Fort Marcy Park, VA

Reply
  • Remember that the SPI protocol has various modes of operation. Like data bits captured on falling or rising edges, etc. So ensure that the device you are communicating with are compatible with your processor's code.

    en.wikipedia.org/.../Serial_Peripheral_Interface_Bus

    And since this is a 'class' the idea is that YOU figure it out, and not request 'free' source code. Such free source code might not work, and you won't know how to fix it, and the whole point in 'learning' is lost.

    --Cpt. Vince Foster
    2nd Cannon Place
    Fort Marcy Park, VA

Children
  • When it comes to tapping SPI communication, you should configure your processor as a SPI slave with the corresponding settings as used on the SPI bus.

    You will need two SPI interfaces if you are going to capture the data on both the MISO and the MOSI lines.

    For exra points, use child language such as "vl jst act lyk input port n read" when turning in the project.

  • By the way - if you intend to read the signals using GPIO pins instead of SPI interfaces, that SPI communication better be slow.

    It is no fun to implement a SPI slave in software. SPI is capable of many MHz while already low kHz speeds will start to be problematic in software.