Is it a bad idea to replace pull-up resistors with hard pull-ups?Given five 10-Ohm resistors, design a network with an equivalent resistance of 10-OhmIs it a bad idea to switch from using a quartz oscillator for my timing circuit to using a MEMS oscillator?DC-to-DC conversion for solar, off the shelf or custom?Creating a Circuit with Resistors Given the Total ResistanceWhy can't this mixer be built with two resistors?Microwave oven with no heat, Bad design or wrong component choice?How to pulse an LED for a second with just a single switch, resistors and capacitors?Floating Value even with pull-down resistorHow to replace relay with N-Channel Mosfet
Does French have the English "short i" vowel?
便利な工具 what does な means
Dad jokes are fun
Can a person survive on blood in place of water?
Is the Unsullied name meant to be ironic? How did it come to be?
Why did Jon Snow do this immoral act if he is so honorable?
Is it truly impossible to tell what a CPU is doing?
Why did Drogon spare this character?
Grade-school elementary algebra presented in an abstract-algebra style?
Security vulnerabilities of POST over SSL
Why are Stein manifolds/spaces the analog of affine varieties/schemes in algebraic geometry?
Did this character show any indication of wanting to rule before S8E6?
What is the meaning of "<&3" and "done < file11 3< file22"
What weight should be given to writers groups critiques?
How to patch glass cuts in a bicycle tire?
Find this cartoon
Beginner looking to learn/master musical theory and instrumental ability. Where should I begin?
Of strange atmospheres - the survivable but unbreathable
How to deal with a colleague who is being aggressive?
Are there any German nonsense poems (Jabberwocky)?
Is there a simple example that empirical evidence is misleading?
Should there be an "a" before "ten years imprisonment"?
Mercedes C180 (W204) dash symbol
Function argument returning void or non-void type
Is it a bad idea to replace pull-up resistors with hard pull-ups?
Given five 10-Ohm resistors, design a network with an equivalent resistance of 10-OhmIs it a bad idea to switch from using a quartz oscillator for my timing circuit to using a MEMS oscillator?DC-to-DC conversion for solar, off the shelf or custom?Creating a Circuit with Resistors Given the Total ResistanceWhy can't this mixer be built with two resistors?Microwave oven with no heat, Bad design or wrong component choice?How to pulse an LED for a second with just a single switch, resistors and capacitors?Floating Value even with pull-down resistorHow to replace relay with N-Channel Mosfet
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
$begingroup$
On many of my designs, there are ICs which have mode selection or similar inputs that are permanently pulled up or down using resistors.
If I replaced all these with simple hard pullups or pulldowns I would probably save 10 placements per board on average, which is not nothing. Is this a bad idea? And if so why?
circuit-design
$endgroup$
add a comment |
$begingroup$
On many of my designs, there are ICs which have mode selection or similar inputs that are permanently pulled up or down using resistors.
If I replaced all these with simple hard pullups or pulldowns I would probably save 10 placements per board on average, which is not nothing. Is this a bad idea? And if so why?
circuit-design
$endgroup$
4
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
6
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
1
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
1
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33
add a comment |
$begingroup$
On many of my designs, there are ICs which have mode selection or similar inputs that are permanently pulled up or down using resistors.
If I replaced all these with simple hard pullups or pulldowns I would probably save 10 placements per board on average, which is not nothing. Is this a bad idea? And if so why?
circuit-design
$endgroup$
On many of my designs, there are ICs which have mode selection or similar inputs that are permanently pulled up or down using resistors.
If I replaced all these with simple hard pullups or pulldowns I would probably save 10 placements per board on average, which is not nothing. Is this a bad idea? And if so why?
circuit-design
circuit-design
edited May 11 at 3:34
Jasen
12.6k11733
12.6k11733
asked May 10 at 20:36
DrewDrew
2,1481517
2,1481517
4
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
6
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
1
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
1
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33
add a comment |
4
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
6
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
1
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
1
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33
4
4
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
6
6
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
1
1
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
1
1
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33
add a comment |
7 Answers
7
active
oldest
votes
$begingroup$
I asked a similar question on the EEVBlog forum some time ago. I had this idea in my head that any signal I needed permanently low I would tie hard to ground, and any signal that I needed permanently high I would tie up via a resistor.
I didn't really know from where or why I used this scheme, so I asked about it. I think it may have been something that I picked up somewhere that was more applicable in the TTL days.
EEVBlog - Pull-up resistors - technically necessary vs preference?
The general consensus seemed to be, and as Huisman suggests, unless you need to be able to pull the signal in the opposite direction, you can simply pull it hard up/down.
It is worth noting that my question was in relation to CMOS-based devices - it may still be applicable/necessary if you are playing with TTL families.
More technical reasons revolved around noise immunity, especially if your pull-up resistor values were of a high value.
As I am writing this, other reasons I can think of for wanting to
use pull-up/pull-down resistors might include troubleshooting abilities, "hidden features", or debug/service mode selection for example.
Since that thread I am no longer using pull-up resistors unless I need them functionally.
$endgroup$
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
add a comment |
$begingroup$
The idea of pull-up / pull-down a signal is that the signal is being pulled high or pulled down low most of the time, but can sometimes be pulled down or pulled high respectively.
In the case you want to pull down a signal incidentally that is pulled up most of the time, you want to use a pull-up resistor to prevent huge current drawn from the supply.
So, if your circuit really uses pull-up or pull-down resistors as described above, don't remove them. (For example, when a pin is open collector.)
If in your circuit a signal needs to high or low forever (when the supply is present) and no other component can change the state of this signal, then you can hard-wire it. Those signal are not called pulled-up, but high, and, respectively not called pulled-down, but low.
$endgroup$
add a comment |
$begingroup$
The answer will be in the datasheet. If the logic input operating voltage specification includes VCC or V+ then connecting directly to positive supply is OK.
$endgroup$
add a comment |
$begingroup$
Let’s consider a pull-up resistor. The job of a pull-up resistor is to pull a particular pin to the HIGH state. However, the pin won't always be in the HIGH state because some circuitry can pull it down to ground. Consider I²C lines. They are pulled up via pull-up resistors and the microcontroller pulls them down as and when needed. Had these lines been permanently pulled up AKA "hard pulled up", I²C communication wouldn't have happened. The SDA line will see a permanent HIGH state.
Your scenario
In your case, if there's a resistor between the pin and GND/Vcc, don't remove it. If the datasheet says to put a resistor, do it. However if you want to delve deeper and understand the functionality of the pull-up /pull-down, look for the IC block diagram in the datasheet. Sometimes you may even find a circuit diagram of the internal blocks. Try to understand the function of the particular resistor (if you find it difficult to understand the circuit, you can post the schematic here). Like Huisman said, if a pin is permanently pulled up or pulled down, the pin's state isn't called pulled up or pulled down. Instead it is HIGH or LOW.
Some info about pull-up /pull down
Pull-up (and pull-down) resistors are generally high, about 10 kΩ generally and they keep the pin in a defined state - HIGH (or LOW) . When an external circuit pulls down a pulled up pin, it provides a path of lower resistance to the ground for that pin. Hence, the pull-up resistor value depends on the resistance offered by the external circuitry to the pin, to GND. The pull-up value must be significantly greater than the resistance of pull-down path. Some circuit designs with ASICs may use even a higher value of pull-up or pull-down.
So to summarise the answer, a pull-up or pull-down resistor is used when the state of the pin has to be changed via some circuitry. If the pin state won't be changed anytime in future, you can hardwire it to either VCC or GND.
$endgroup$
add a comment |
$begingroup$
I am surprised to see that nobody mentioned DFT here. In some case, using pull up/down resistor leaves room for a test fixture to inject a signal and put the input in a different state for the time of the test. Let's use the simple example of a Chip Enable signal that you want to be always at "enable".
While performing an ICT test, you may want to disable the Chip Enable pin to put the output of the IC in High impedance mode. Doing so, allows the test fixture to inject arbitrary signal at the output of the disabled IC, which would otherwise be impossible if the CE pin would be "hard driven".
This is an additional use-case. Other answers in this threads are valids.
$endgroup$
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
add a comment |
$begingroup$
It really depends on why you are pulling it up. Sometimes unused functions may be toggled by the built-in boot logic of a chip during startup. If a processor can boot from multiple sources, it may have to auto-discover which source is attached during power on. That can lead to some lines being toggled prior to code execution (prior to your code executing). So if the datasheet says "pull up if not used," then you would want to double-check with the manufacturer before tying it high. Or, if possible, maybe you can monitor the behavior of the line during start-up to make sure it is not driven low ever.
$endgroup$
add a comment |
$begingroup$
Hmmm. Have not seen it mentioned yet, but a reason, especially for pins tied high, is to use a resistor for reduced power consumption. Consult the datasheet for the device in question.
$endgroup$
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("schematics", function ()
StackExchange.schematics.init();
);
, "cicuitlab");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "135"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f437946%2fis-it-a-bad-idea-to-replace-pull-up-resistors-with-hard-pull-ups%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
I asked a similar question on the EEVBlog forum some time ago. I had this idea in my head that any signal I needed permanently low I would tie hard to ground, and any signal that I needed permanently high I would tie up via a resistor.
I didn't really know from where or why I used this scheme, so I asked about it. I think it may have been something that I picked up somewhere that was more applicable in the TTL days.
EEVBlog - Pull-up resistors - technically necessary vs preference?
The general consensus seemed to be, and as Huisman suggests, unless you need to be able to pull the signal in the opposite direction, you can simply pull it hard up/down.
It is worth noting that my question was in relation to CMOS-based devices - it may still be applicable/necessary if you are playing with TTL families.
More technical reasons revolved around noise immunity, especially if your pull-up resistor values were of a high value.
As I am writing this, other reasons I can think of for wanting to
use pull-up/pull-down resistors might include troubleshooting abilities, "hidden features", or debug/service mode selection for example.
Since that thread I am no longer using pull-up resistors unless I need them functionally.
$endgroup$
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
add a comment |
$begingroup$
I asked a similar question on the EEVBlog forum some time ago. I had this idea in my head that any signal I needed permanently low I would tie hard to ground, and any signal that I needed permanently high I would tie up via a resistor.
I didn't really know from where or why I used this scheme, so I asked about it. I think it may have been something that I picked up somewhere that was more applicable in the TTL days.
EEVBlog - Pull-up resistors - technically necessary vs preference?
The general consensus seemed to be, and as Huisman suggests, unless you need to be able to pull the signal in the opposite direction, you can simply pull it hard up/down.
It is worth noting that my question was in relation to CMOS-based devices - it may still be applicable/necessary if you are playing with TTL families.
More technical reasons revolved around noise immunity, especially if your pull-up resistor values were of a high value.
As I am writing this, other reasons I can think of for wanting to
use pull-up/pull-down resistors might include troubleshooting abilities, "hidden features", or debug/service mode selection for example.
Since that thread I am no longer using pull-up resistors unless I need them functionally.
$endgroup$
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
add a comment |
$begingroup$
I asked a similar question on the EEVBlog forum some time ago. I had this idea in my head that any signal I needed permanently low I would tie hard to ground, and any signal that I needed permanently high I would tie up via a resistor.
I didn't really know from where or why I used this scheme, so I asked about it. I think it may have been something that I picked up somewhere that was more applicable in the TTL days.
EEVBlog - Pull-up resistors - technically necessary vs preference?
The general consensus seemed to be, and as Huisman suggests, unless you need to be able to pull the signal in the opposite direction, you can simply pull it hard up/down.
It is worth noting that my question was in relation to CMOS-based devices - it may still be applicable/necessary if you are playing with TTL families.
More technical reasons revolved around noise immunity, especially if your pull-up resistor values were of a high value.
As I am writing this, other reasons I can think of for wanting to
use pull-up/pull-down resistors might include troubleshooting abilities, "hidden features", or debug/service mode selection for example.
Since that thread I am no longer using pull-up resistors unless I need them functionally.
$endgroup$
I asked a similar question on the EEVBlog forum some time ago. I had this idea in my head that any signal I needed permanently low I would tie hard to ground, and any signal that I needed permanently high I would tie up via a resistor.
I didn't really know from where or why I used this scheme, so I asked about it. I think it may have been something that I picked up somewhere that was more applicable in the TTL days.
EEVBlog - Pull-up resistors - technically necessary vs preference?
The general consensus seemed to be, and as Huisman suggests, unless you need to be able to pull the signal in the opposite direction, you can simply pull it hard up/down.
It is worth noting that my question was in relation to CMOS-based devices - it may still be applicable/necessary if you are playing with TTL families.
More technical reasons revolved around noise immunity, especially if your pull-up resistor values were of a high value.
As I am writing this, other reasons I can think of for wanting to
use pull-up/pull-down resistors might include troubleshooting abilities, "hidden features", or debug/service mode selection for example.
Since that thread I am no longer using pull-up resistors unless I need them functionally.
edited May 11 at 14:27
Peter Mortensen
1,60031422
1,60031422
answered May 10 at 21:12
Tom STom S
1655
1655
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
add a comment |
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
3
3
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
$begingroup$
Yes, it was a requirement for TTL Hi to prevent secondary breakdown current on overvoltage transients to supply. But not for CMOS. Although my TE's would add them for testability since it serves no function, I said fault detect is adequate with inputs used.
$endgroup$
– Sunnyskyguy EE75
May 10 at 21:16
add a comment |
$begingroup$
The idea of pull-up / pull-down a signal is that the signal is being pulled high or pulled down low most of the time, but can sometimes be pulled down or pulled high respectively.
In the case you want to pull down a signal incidentally that is pulled up most of the time, you want to use a pull-up resistor to prevent huge current drawn from the supply.
So, if your circuit really uses pull-up or pull-down resistors as described above, don't remove them. (For example, when a pin is open collector.)
If in your circuit a signal needs to high or low forever (when the supply is present) and no other component can change the state of this signal, then you can hard-wire it. Those signal are not called pulled-up, but high, and, respectively not called pulled-down, but low.
$endgroup$
add a comment |
$begingroup$
The idea of pull-up / pull-down a signal is that the signal is being pulled high or pulled down low most of the time, but can sometimes be pulled down or pulled high respectively.
In the case you want to pull down a signal incidentally that is pulled up most of the time, you want to use a pull-up resistor to prevent huge current drawn from the supply.
So, if your circuit really uses pull-up or pull-down resistors as described above, don't remove them. (For example, when a pin is open collector.)
If in your circuit a signal needs to high or low forever (when the supply is present) and no other component can change the state of this signal, then you can hard-wire it. Those signal are not called pulled-up, but high, and, respectively not called pulled-down, but low.
$endgroup$
add a comment |
$begingroup$
The idea of pull-up / pull-down a signal is that the signal is being pulled high or pulled down low most of the time, but can sometimes be pulled down or pulled high respectively.
In the case you want to pull down a signal incidentally that is pulled up most of the time, you want to use a pull-up resistor to prevent huge current drawn from the supply.
So, if your circuit really uses pull-up or pull-down resistors as described above, don't remove them. (For example, when a pin is open collector.)
If in your circuit a signal needs to high or low forever (when the supply is present) and no other component can change the state of this signal, then you can hard-wire it. Those signal are not called pulled-up, but high, and, respectively not called pulled-down, but low.
$endgroup$
The idea of pull-up / pull-down a signal is that the signal is being pulled high or pulled down low most of the time, but can sometimes be pulled down or pulled high respectively.
In the case you want to pull down a signal incidentally that is pulled up most of the time, you want to use a pull-up resistor to prevent huge current drawn from the supply.
So, if your circuit really uses pull-up or pull-down resistors as described above, don't remove them. (For example, when a pin is open collector.)
If in your circuit a signal needs to high or low forever (when the supply is present) and no other component can change the state of this signal, then you can hard-wire it. Those signal are not called pulled-up, but high, and, respectively not called pulled-down, but low.
edited May 10 at 21:05
answered May 10 at 20:59
HuismanHuisman
2,6361320
2,6361320
add a comment |
add a comment |
$begingroup$
The answer will be in the datasheet. If the logic input operating voltage specification includes VCC or V+ then connecting directly to positive supply is OK.
$endgroup$
add a comment |
$begingroup$
The answer will be in the datasheet. If the logic input operating voltage specification includes VCC or V+ then connecting directly to positive supply is OK.
$endgroup$
add a comment |
$begingroup$
The answer will be in the datasheet. If the logic input operating voltage specification includes VCC or V+ then connecting directly to positive supply is OK.
$endgroup$
The answer will be in the datasheet. If the logic input operating voltage specification includes VCC or V+ then connecting directly to positive supply is OK.
answered May 10 at 21:03
TransistorTransistor
91.6k788196
91.6k788196
add a comment |
add a comment |
$begingroup$
Let’s consider a pull-up resistor. The job of a pull-up resistor is to pull a particular pin to the HIGH state. However, the pin won't always be in the HIGH state because some circuitry can pull it down to ground. Consider I²C lines. They are pulled up via pull-up resistors and the microcontroller pulls them down as and when needed. Had these lines been permanently pulled up AKA "hard pulled up", I²C communication wouldn't have happened. The SDA line will see a permanent HIGH state.
Your scenario
In your case, if there's a resistor between the pin and GND/Vcc, don't remove it. If the datasheet says to put a resistor, do it. However if you want to delve deeper and understand the functionality of the pull-up /pull-down, look for the IC block diagram in the datasheet. Sometimes you may even find a circuit diagram of the internal blocks. Try to understand the function of the particular resistor (if you find it difficult to understand the circuit, you can post the schematic here). Like Huisman said, if a pin is permanently pulled up or pulled down, the pin's state isn't called pulled up or pulled down. Instead it is HIGH or LOW.
Some info about pull-up /pull down
Pull-up (and pull-down) resistors are generally high, about 10 kΩ generally and they keep the pin in a defined state - HIGH (or LOW) . When an external circuit pulls down a pulled up pin, it provides a path of lower resistance to the ground for that pin. Hence, the pull-up resistor value depends on the resistance offered by the external circuitry to the pin, to GND. The pull-up value must be significantly greater than the resistance of pull-down path. Some circuit designs with ASICs may use even a higher value of pull-up or pull-down.
So to summarise the answer, a pull-up or pull-down resistor is used when the state of the pin has to be changed via some circuitry. If the pin state won't be changed anytime in future, you can hardwire it to either VCC or GND.
$endgroup$
add a comment |
$begingroup$
Let’s consider a pull-up resistor. The job of a pull-up resistor is to pull a particular pin to the HIGH state. However, the pin won't always be in the HIGH state because some circuitry can pull it down to ground. Consider I²C lines. They are pulled up via pull-up resistors and the microcontroller pulls them down as and when needed. Had these lines been permanently pulled up AKA "hard pulled up", I²C communication wouldn't have happened. The SDA line will see a permanent HIGH state.
Your scenario
In your case, if there's a resistor between the pin and GND/Vcc, don't remove it. If the datasheet says to put a resistor, do it. However if you want to delve deeper and understand the functionality of the pull-up /pull-down, look for the IC block diagram in the datasheet. Sometimes you may even find a circuit diagram of the internal blocks. Try to understand the function of the particular resistor (if you find it difficult to understand the circuit, you can post the schematic here). Like Huisman said, if a pin is permanently pulled up or pulled down, the pin's state isn't called pulled up or pulled down. Instead it is HIGH or LOW.
Some info about pull-up /pull down
Pull-up (and pull-down) resistors are generally high, about 10 kΩ generally and they keep the pin in a defined state - HIGH (or LOW) . When an external circuit pulls down a pulled up pin, it provides a path of lower resistance to the ground for that pin. Hence, the pull-up resistor value depends on the resistance offered by the external circuitry to the pin, to GND. The pull-up value must be significantly greater than the resistance of pull-down path. Some circuit designs with ASICs may use even a higher value of pull-up or pull-down.
So to summarise the answer, a pull-up or pull-down resistor is used when the state of the pin has to be changed via some circuitry. If the pin state won't be changed anytime in future, you can hardwire it to either VCC or GND.
$endgroup$
add a comment |
$begingroup$
Let’s consider a pull-up resistor. The job of a pull-up resistor is to pull a particular pin to the HIGH state. However, the pin won't always be in the HIGH state because some circuitry can pull it down to ground. Consider I²C lines. They are pulled up via pull-up resistors and the microcontroller pulls them down as and when needed. Had these lines been permanently pulled up AKA "hard pulled up", I²C communication wouldn't have happened. The SDA line will see a permanent HIGH state.
Your scenario
In your case, if there's a resistor between the pin and GND/Vcc, don't remove it. If the datasheet says to put a resistor, do it. However if you want to delve deeper and understand the functionality of the pull-up /pull-down, look for the IC block diagram in the datasheet. Sometimes you may even find a circuit diagram of the internal blocks. Try to understand the function of the particular resistor (if you find it difficult to understand the circuit, you can post the schematic here). Like Huisman said, if a pin is permanently pulled up or pulled down, the pin's state isn't called pulled up or pulled down. Instead it is HIGH or LOW.
Some info about pull-up /pull down
Pull-up (and pull-down) resistors are generally high, about 10 kΩ generally and they keep the pin in a defined state - HIGH (or LOW) . When an external circuit pulls down a pulled up pin, it provides a path of lower resistance to the ground for that pin. Hence, the pull-up resistor value depends on the resistance offered by the external circuitry to the pin, to GND. The pull-up value must be significantly greater than the resistance of pull-down path. Some circuit designs with ASICs may use even a higher value of pull-up or pull-down.
So to summarise the answer, a pull-up or pull-down resistor is used when the state of the pin has to be changed via some circuitry. If the pin state won't be changed anytime in future, you can hardwire it to either VCC or GND.
$endgroup$
Let’s consider a pull-up resistor. The job of a pull-up resistor is to pull a particular pin to the HIGH state. However, the pin won't always be in the HIGH state because some circuitry can pull it down to ground. Consider I²C lines. They are pulled up via pull-up resistors and the microcontroller pulls them down as and when needed. Had these lines been permanently pulled up AKA "hard pulled up", I²C communication wouldn't have happened. The SDA line will see a permanent HIGH state.
Your scenario
In your case, if there's a resistor between the pin and GND/Vcc, don't remove it. If the datasheet says to put a resistor, do it. However if you want to delve deeper and understand the functionality of the pull-up /pull-down, look for the IC block diagram in the datasheet. Sometimes you may even find a circuit diagram of the internal blocks. Try to understand the function of the particular resistor (if you find it difficult to understand the circuit, you can post the schematic here). Like Huisman said, if a pin is permanently pulled up or pulled down, the pin's state isn't called pulled up or pulled down. Instead it is HIGH or LOW.
Some info about pull-up /pull down
Pull-up (and pull-down) resistors are generally high, about 10 kΩ generally and they keep the pin in a defined state - HIGH (or LOW) . When an external circuit pulls down a pulled up pin, it provides a path of lower resistance to the ground for that pin. Hence, the pull-up resistor value depends on the resistance offered by the external circuitry to the pin, to GND. The pull-up value must be significantly greater than the resistance of pull-down path. Some circuit designs with ASICs may use even a higher value of pull-up or pull-down.
So to summarise the answer, a pull-up or pull-down resistor is used when the state of the pin has to be changed via some circuitry. If the pin state won't be changed anytime in future, you can hardwire it to either VCC or GND.
edited May 11 at 14:27
Peter Mortensen
1,60031422
1,60031422
answered May 11 at 6:24
Pranit Pawar Pranit Pawar
3816
3816
add a comment |
add a comment |
$begingroup$
I am surprised to see that nobody mentioned DFT here. In some case, using pull up/down resistor leaves room for a test fixture to inject a signal and put the input in a different state for the time of the test. Let's use the simple example of a Chip Enable signal that you want to be always at "enable".
While performing an ICT test, you may want to disable the Chip Enable pin to put the output of the IC in High impedance mode. Doing so, allows the test fixture to inject arbitrary signal at the output of the disabled IC, which would otherwise be impossible if the CE pin would be "hard driven".
This is an additional use-case. Other answers in this threads are valids.
$endgroup$
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
add a comment |
$begingroup$
I am surprised to see that nobody mentioned DFT here. In some case, using pull up/down resistor leaves room for a test fixture to inject a signal and put the input in a different state for the time of the test. Let's use the simple example of a Chip Enable signal that you want to be always at "enable".
While performing an ICT test, you may want to disable the Chip Enable pin to put the output of the IC in High impedance mode. Doing so, allows the test fixture to inject arbitrary signal at the output of the disabled IC, which would otherwise be impossible if the CE pin would be "hard driven".
This is an additional use-case. Other answers in this threads are valids.
$endgroup$
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
add a comment |
$begingroup$
I am surprised to see that nobody mentioned DFT here. In some case, using pull up/down resistor leaves room for a test fixture to inject a signal and put the input in a different state for the time of the test. Let's use the simple example of a Chip Enable signal that you want to be always at "enable".
While performing an ICT test, you may want to disable the Chip Enable pin to put the output of the IC in High impedance mode. Doing so, allows the test fixture to inject arbitrary signal at the output of the disabled IC, which would otherwise be impossible if the CE pin would be "hard driven".
This is an additional use-case. Other answers in this threads are valids.
$endgroup$
I am surprised to see that nobody mentioned DFT here. In some case, using pull up/down resistor leaves room for a test fixture to inject a signal and put the input in a different state for the time of the test. Let's use the simple example of a Chip Enable signal that you want to be always at "enable".
While performing an ICT test, you may want to disable the Chip Enable pin to put the output of the IC in High impedance mode. Doing so, allows the test fixture to inject arbitrary signal at the output of the disabled IC, which would otherwise be impossible if the CE pin would be "hard driven".
This is an additional use-case. Other answers in this threads are valids.
answered May 17 at 1:19
Pier-Yves LessardPier-Yves Lessard
36429
36429
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
add a comment |
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
$begingroup$
I did hint at this kind of thing in my reply.
$endgroup$
– Tom S
2 days ago
add a comment |
$begingroup$
It really depends on why you are pulling it up. Sometimes unused functions may be toggled by the built-in boot logic of a chip during startup. If a processor can boot from multiple sources, it may have to auto-discover which source is attached during power on. That can lead to some lines being toggled prior to code execution (prior to your code executing). So if the datasheet says "pull up if not used," then you would want to double-check with the manufacturer before tying it high. Or, if possible, maybe you can monitor the behavior of the line during start-up to make sure it is not driven low ever.
$endgroup$
add a comment |
$begingroup$
It really depends on why you are pulling it up. Sometimes unused functions may be toggled by the built-in boot logic of a chip during startup. If a processor can boot from multiple sources, it may have to auto-discover which source is attached during power on. That can lead to some lines being toggled prior to code execution (prior to your code executing). So if the datasheet says "pull up if not used," then you would want to double-check with the manufacturer before tying it high. Or, if possible, maybe you can monitor the behavior of the line during start-up to make sure it is not driven low ever.
$endgroup$
add a comment |
$begingroup$
It really depends on why you are pulling it up. Sometimes unused functions may be toggled by the built-in boot logic of a chip during startup. If a processor can boot from multiple sources, it may have to auto-discover which source is attached during power on. That can lead to some lines being toggled prior to code execution (prior to your code executing). So if the datasheet says "pull up if not used," then you would want to double-check with the manufacturer before tying it high. Or, if possible, maybe you can monitor the behavior of the line during start-up to make sure it is not driven low ever.
$endgroup$
It really depends on why you are pulling it up. Sometimes unused functions may be toggled by the built-in boot logic of a chip during startup. If a processor can boot from multiple sources, it may have to auto-discover which source is attached during power on. That can lead to some lines being toggled prior to code execution (prior to your code executing). So if the datasheet says "pull up if not used," then you would want to double-check with the manufacturer before tying it high. Or, if possible, maybe you can monitor the behavior of the line during start-up to make sure it is not driven low ever.
answered May 17 at 1:50
mkeithmkeith
11.7k11133
11.7k11133
add a comment |
add a comment |
$begingroup$
Hmmm. Have not seen it mentioned yet, but a reason, especially for pins tied high, is to use a resistor for reduced power consumption. Consult the datasheet for the device in question.
$endgroup$
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
add a comment |
$begingroup$
Hmmm. Have not seen it mentioned yet, but a reason, especially for pins tied high, is to use a resistor for reduced power consumption. Consult the datasheet for the device in question.
$endgroup$
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
add a comment |
$begingroup$
Hmmm. Have not seen it mentioned yet, but a reason, especially for pins tied high, is to use a resistor for reduced power consumption. Consult the datasheet for the device in question.
$endgroup$
Hmmm. Have not seen it mentioned yet, but a reason, especially for pins tied high, is to use a resistor for reduced power consumption. Consult the datasheet for the device in question.
answered May 16 at 20:52
c-squaredc-squared
262
262
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
add a comment |
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
1
1
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Can you please elaborate on how or in what cases power would be saved in some specific scenario?
$endgroup$
– mkeith
May 17 at 1:52
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
$begingroup$
Going strictly on memory, @mkeith, an example was a T1/E1 transceiver, where configuration was determined by a combination of pins being tied low or pulled up. IIRC the datasheet made it clear to use discrete resistors for the pull-ups to reduce power consumption. Perhaps these inputs were BJT transistors as compared to FET inputs; i.e. current is actually drawn. I have seen this practice consistently from our senior engineers' designs so I have been assuming the reasoning was still valid.
$endgroup$
– c-squared
2 days ago
add a comment |
Thanks for contributing an answer to Electrical Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f437946%2fis-it-a-bad-idea-to-replace-pull-up-resistors-with-hard-pull-ups%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
$begingroup$
Include a schematic of what you mean, what's a "hard pullup" do you mean a direct connection (no series resistor) to the supply? Include a link to an example of an IC for which you want to do this. Someone put the resistors in the schematic, ask that person why they did that.
$endgroup$
– Bimpelrekkie
May 10 at 20:49
6
$begingroup$
On rev 0 of any board I tend to strap any configuration or spare input pins high or low using resistors (sometimes zero-ohm), because it may provide a quick fix in an "oh @#$%" moment. With zero-ohms you can remove the resistor, or remove the resistor and use the pad for a wire, etc. Once I'm sure of the design, if production volumes are high enough that it matters I'll make a pass through and just strap things high or low with copper.
$endgroup$
– TimWescott
May 10 at 21:28
1
$begingroup$
If you know that the pin can never be programmed as an output by accident or code error then you can always connect it to a power rail as that is a design aspect of a input pin. This is why microcontrollers in general (special cases exist) will wake up with all pins in input mode and the code must set those others to output that are not shorted to a power rail.
$endgroup$
– KalleMP
May 11 at 9:17
1
$begingroup$
Read the datasheet. If it is ambiguous, contact the MFG. They normally answer questions like this.
$endgroup$
– mkeith
May 17 at 1:33