[Solved] NodeMCU with PCF8574 crashes when starting with button pressed

Hello.
I have a problem that I have been struggling with for a long time.
I have 4 PCF8574 i2c modules hooked up under the NodeMCU.
2 of them I use as output, another 2 as input.
Everything works as expected when I connect the chip to USB with the buttons not pressed. The problem occurs when during power-up - connecting to USB - one of the buttons connected to the PCF input pins is pressed, i.e. shorted to GND, then the program does not respond at all.
Input pins pulled up with 10k resistors to VCC. Status readout using an interrupt.

I tried setting the ports as outputs first, but nothing helps.


.

canion wrote:

I have 4 i2c modules plugged into the NodeMCU PCF8534 .

.
The PCF8574_ESP library used supports the PCF8574/PCF8574A/PCF8575. Typo, as the PCF8534 chip is also .

How are the constructors PCF_switches and PCF_switches2 declared? How do you have the Wire set up? Check out this example:
https://github.com/WereCatf/PCF8574_ESP/blob/.../examples/pcf8574_esp8266/pcf8574_esp8266.ino
Add pcf8574.resetInterruptPin () in setup(), according to the example above.

khoam wrote:

canion wrote:

I have 4 i2c modules plugged into the NodeMCU PCF8534 .

.
The PCF8574_ESP library used supports PCF8574/PCF8574A/PCF8575. Typo?

How are the constructors PCF_switches and PCF_switches2 declared? How do you have the Wire set up? Check out this example:
https://github.com/WereCatf/PCF8574_ESP/blob/.../examples/pcf8574_esp8266/pcf8574_esp8266.ino
Add pcf8574.resetInterruptPin () in setup(), according to the example above.

.

Yes, this is a typo, already corrected:) .
.

Added after 8 [minutes]: .

Code after changes, problem still occurs.

PCF.setClock(100000L) should be after PCF.begin(D2, D1).
Both resetInterruptPin() functions immediately after PCF_switches2.begin().

I have noticed one thing.
The most important thing is to connect the chip when the input ports are not shorted to GND - buttons off.
Once the chip is powered up, I can short the pin to GND and reset the program in that state (with the RST button on the NodeMCU) and then the program works.
Maybe this is a hardware problem? I've tried adding a capacitor to the power supply - didn't help, a delay (1000) at the very beginning of setup() so that the voltage can stabilise after connection - doesn't work either

Added after 3 [minutes]:

khoam wrote:

PCF.setClock(100000L) should be after PCF.begin(D2, D1).
Both resetInterruptPin() functions immediately after PCF_switches2.begin().

After the changes - the problem still occurs

D3 is connected via a resistor to the power supply?
I think that in attacheInterrupt() it is enough to use the FALLING parameter instead of CHANGE.

khoam wrote:

D3 is connected via a resistor to the power supply?
I think that in attacheInterrupt() it is enough to use the FALLING parameter instead of CHANGE.

D3 obviously pulled up to VCC.
changing the response to the falling edge also had no effect

Try a test like this: comment out attacheInterrupt() in setup() and see if the problem occurs i.e. if the program "hangs".

Added after 3 [minutes]: .

EDIT:
The cause is probably very simple. D3 if it is in a low state while the ESP is booting, the chip will not boot
https://randomnerdtutorials.com/esp8266-pinout-reference-gpios/
You need to select a different pin.

khoam wrote:

Try a test like this: comment out attacheInterrupt() in setup() and see if the problem occurs i.e. if the program "hangs".

Added after 3 [minutes]: .

EDIT:
The cause is probably very simple. D3 if it is in a low state while the ESP is booting, the chip will not boot
https://randomnerdtutorials.com/esp8266-pinout-reference-gpios/
You need to select a different pin.

And I feel silly:) Thanks. Problem solved

khoam wrote:

Try a test like this: comment out attacheInterrupt() in setup() and see if the problem occurs i.e. if the program "hangs".

Added after 3 [minutes]: .

EDIT:
The cause is probably very simple. D3 if it is in a low state while the ESP is booting, the chip will not boot
https://randomnerdtutorials.com/esp8266-pinout-reference-gpios/
You need to select a different pin.

And I feel silly:) Thanks. Problem solved

Added after 1 [minute]:

Changing the INT pin from D3 to D5 solved the problem.