Group Actions
Engagement
  • Author Author: packetgeek
  • Date Created: Date Created
  • Views 1158 views
  • Likes 0 likes
  • Comments 7 comments
Related
Recommended

Si4707 effort on hold

packetgeek

I'm putting the I2C coding effort for the Si4707 chip on hold.  The basic initialization code (same as for the Si4703 breakout board) does not work with the Sparkfun board.  Cause seems to be double-use of pull-up resistors (one set on the Pi, another on the Sparkfun board) that were added by Sparkfun.  Because of this, I don't believe that the I2C interface will work with the Pi without modifying the board.

 

Supporting this are the following:

 

Will revisit the chip when I'm learning how to work with the SPI interface, or work with a computer that doesn't add its own set of pull-up resisistors.  Maybe a Cubieboard or the XMOS controller.  Will need to dig.  In the mean time, this allows me to move on to the AS3935 lightning sensor and the Si4735 eval kit.

Parents

  • In software you can change whether it is a pull up or up down:

     

    GPIO.setup(23, GPIO.IN, pull_up_down=GPIO.PUD_DOWN)
    GPIO.setup(24, GPIO.IN, pull_up_down=GPIO.PUD_UP)

    Do not know if this helps...

    Clem

  • in reply to clem57

    I may have found another possible cause...  I'd moved to playing with the MOD-1016 lightning sensor and it refused to work.  It kept complaining about not being able to set up call-backs for pin 17 (which is used by the sensor as an interrupt, to signal the RPi that an update is available).  I messed with it for a couple hours and finally moved the interrupt to pin 23 and tweaked the code.  After that, it worked fine.

     

    So...  I'm wonder if the Si4707 will initialize if I move the reset signalling to a different pin.  Project for the weekend (next weekend?), I guess.  I'm hoping that the problem is just that something else in the RPi has laid claim to pin 17 and not that I've damaged the input.

     

    - Tim

Comment
  • in reply to clem57

    I may have found another possible cause...  I'd moved to playing with the MOD-1016 lightning sensor and it refused to work.  It kept complaining about not being able to set up call-backs for pin 17 (which is used by the sensor as an interrupt, to signal the RPi that an update is available).  I messed with it for a couple hours and finally moved the interrupt to pin 23 and tweaked the code.  After that, it worked fine.

     

    So...  I'm wonder if the Si4707 will initialize if I move the reset signalling to a different pin.  Project for the weekend (next weekend?), I guess.  I'm hoping that the problem is just that something else in the RPi has laid claim to pin 17 and not that I've damaged the input.

     

    - Tim

Children
No Data