This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PULL up / pull down when using PxSEL



HI friends,

I am using MSP430G2xxx controller with launchpad MSP430G2.

Could I use PULL UP / PULL DOWN function of I/O pins while not using them as Input / output (other peripheral module function is selected using PxSEL)?  I read at some where that we can use this function only with some MSP's.

Regards,
Dharmendra Sharma
INDIA

  • TI provides Data sheets of all their products which can be downloaded from the corresponding product page. The Data sheets contain clear Port Schematics as well tables describing the configuration for the different Pin functions. Including resistor pull-up/down.

  • I guess Leo and I are both old and have the old habit of reading data-sheet before asking someone else. As for me, I do not even trust the data-sheet. I read it with a grain of salt.

  • Leo,

    Thanks for your advice, this is the first thing I used to do, before going deep into new modules/ peripherals. 

    I forgot to mention in the previous one that I need to use PULL UP's for I2C (with USCI_Bx).

    Few things,

    1.) I am seeking to interface external EEPROM,S with MSP430 using inbuilt PULL resisters 'if" it is possible (to save my space and extra circuitry duee to external one's) 'else' the external pull resisters are last option.

    2.) I searched a lot and find that "some" MSP'S (of series G2XXX ) support this function and also tried the same but didn't succeed. 

    3.) As I believe on 'FACTS' so it good to ask from the people who already did the same, (same I did ) otherwise I will waste my effort on useless tries those aren't possible.  

    4.) I advice you 'please' reply only when you know answer OR able to give direction (hint) towards the solution. Please do reply for a better conversation that goes towards the solution of problem (not exactly the solution). So we (those have doubts) can reach till the solution by step by step in do and ask manner at each step. Please don't reply on post only to do a 'reply' to get 10 points.

    Regards,

    Dharmendra Sharma

    INDIA

  • Dharmendra Sharma said:
    Thanks for your advice, this is the first thing I used to do, before going deep into new modules/ peripherals. 

    As you didn’t know they existence of a Users Guide I could also expect that you don’t know about a Data Sheet.

    Dharmendra Sharma said:

    I forgot to mention in the previous one that I need to use PULL UP's for I2C (with USCI_Bx).

    Few things,

    1.) I am seeking to interface external EEPROM,S with MSP430 using inbuilt PULL resisters 'if" it is possible (to save my space and extra circuitry duee to external one's) 'else' the external pull resisters are last option.

    You shouldn’t gamble with pull-up resistors. Google for the I2C implementation doc’s and read the guidelines for these and also the general guidelines for Bus structures.

    Dharmendra Sharma said:

    2.) I searched a lot and find that "some" MSP'S (of series G2XXX ) support this function and also tried the same but didn't succeed.

    There are some exceptions but they are already discussed here on the forum, no need to re-discuss.

    Dharmendra Sharma said:
    3.) As I believe on 'FACTS' so it good to ask from the people who already did the same, (same I did ) otherwise I will waste my effort on useless tries those aren't possible.

    This, searching and reading, is named a Learning-cycle. Nobody here is paid to educate you.

    Dharmendra Sharma said:

    4.) I advice you 'please' reply only when you know answer OR able to give direction (hint) towards the solution. Please do reply for a better conversation that goes towards the solution of problem (not exactly the solution). So we (those have doubts) can reach till the solution by step by step in do and ask manner at each step. Please don't reply on post only to do a 'reply' to get 10 points.

    Thanks for clarifying, I wasn’t aware about this pointing system.

  • Hey Leo,

    Leo Bosch said:
    You shouldn’t gamble with pull-up resistors. Google for the I2C implementation doc’s and read the guidelines for these and also the general guidelines for Bus structures.

    Leo Bosch said:
    This, searching and reading, is named a Learning-cycle. Nobody here is paid to educate you.

    I don't think that I need to be educated about I2C or any other general communication protocol. Yeah I am newbie in Texas's controller (now love them) but I did a lot work with Philips, Atmel and microchip.  

    Leo Bosch said:
    There are some exceptions but they are already discussed here on the forum, no need to re-discuss.

    I didn't find any single one thats why I am asking (searched a lot before posting the question and after your response). If you could find and if you have time to give meaningful response then please provide the link of suitable thread. 

    and also my apologies for the 4.) 

    and yeah I not need to be paid (you should also) to provide help how is really seeking a proper help and really deserve to be helped. The mean of word 'GURU' is "who provide education/ help for free and without any self interest" (search guru/ gurukula, if you). Be a good one.

    Thanks & Regards

    Dharmendra Sharma

    INDIA

     

  • On some MSPs , the pull-ups are active independently of the port direction, on others (the whole 5x family), the pull-ups are disabled when the pin is in output direction.
    However, the internal ~40k pull-ups, while sufficient for digital inputs, are way too weak for reliable I2C operation. I guess you won’t get further than a few kHz I2C clock (if at all).

     About the guru title, well, it wasn’t chosen but rather given by the forum. But it fits. Nobody here (at least the non-TI-employees) gets paid for answering questions.
    However, doing the homework for your child will prevent it from ever learning anything. So the level of help provided must be limited.
    This includes citing from the datasheet/users guide or posting links of threads someone could find by himself.
    The hint ‘it is there’ should be enough to encourage the scholar to do research on his own, learning to read datasheets or use the forum search better than before.
    Those who always get said what to do won’t ever learn (or even want) to think on their own.

**Attention** This is a public forum