Shop OBEX P1 Docs P2 Docs Learn Events
Pins 30/31 — Parallax Forums

Pins 30/31

PhilldapillPhilldapill Posts: 1,283
edited 2009-10-21 02:48 in Propeller 1
Besides programming the Propeller, is special care needed to be able to use I/O 30 and 31? I'm not totally strapped for pins, but it would be nice to have them out if needed in the future.

Comments

  • mikedivmikediv Posts: 825
    edited 2009-10-21 00:47
    Phil it can be done and I have had to resort to using pin 30 but to be honest with the reset problems on some prop chips especially the prop USB stick I would not do it , So yes you can but with a big camp tor caveat
    Why not multiplex?
  • MicrocontrolledMicrocontrolled Posts: 2,461
    edited 2009-10-21 00:52
    I use them as standard I/O all the time.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Computers are microcontrolled.

    Robots are microcontrolled.
    I am microcontrolled.

    But you·can·call me micro.

    Want to·experiment with the SX or just put together a cool project?
    SX Spinning light display·


  • mikedivmikediv Posts: 825
    edited 2009-10-21 02:09
    Micro the problem I run into is I end up leaving the prop board connected to my PC a lot of the time so I can just re-program or re-load code can you expand on how you use them? do you program your prop chip with 30-31 or some other way I am curious what do you do if you have to program your board? an example would be really helpful
  • Peter JakackiPeter Jakacki Posts: 10,193
    edited 2009-10-21 02:40
    Very simply, don't create headaches for yourself by chopping down the last tree on Easter Island. If resources are scarce then rethink your requirements. You say that all the other I/O are direct but you didn't say why or what they are even. There are many I/O lines that can be multiplexed and usually for things like indicators, switched outputs, switched inputs, etc but don't sacrifice the Prop's link to the outside world which besides programming is very useful for debugging. Sometimes I use the pins as an application specific serial port but it's still a serial port than can be accessed when need be.

    Now, the I2C lines to the EEPROM do double duty all the time both as an I2C port to other devices and also as a common clock and Prop data out for SPI'ish ports.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    *Peter*
  • Cluso99Cluso99 Posts: 18,069
    edited 2009-10-21 02:48
    I use them for other things too. You just cannot have the propplug connected at the same time when you are using them for other purposes unless you take care of the conflict in some way. If you eeprom is already loaded and you do not require P30/31 for programming that's fine. Preferable to have P31 with a 10K pullup. The prop will not drive P30 while powering up until it recognises the download sequence on P31. Otherwise, you may require links/shunts. I think this is covered in the Prop Manual.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Links to other interesting threads:

    · Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
    · Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
    · Prop Tools under Development or Completed (Index)
    · Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)
    · Search the Propeller forums·(uses advanced Google search)
    My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
Sign In or Register to comment.