How about using a tri-state buffer between the GPIO and your watchdog? On boot, you have low-value resistor pulls on the #OE and IN pins of the tri-state buffer so the output floats, then as soon as the software comes up you assert #OE and start toggling IN. e.g. https://www.fairchildsemi.com/datas...

Archive.zip It's probably also worth deleting/renaming any dt-blob.dts you have, disconnecting GPIO17 and rebooting. Although it isn't possible to read back the pull state, you can use "[sudo] raspi-gpio get 17" to show the current input level, which should be 0. You can then verify that the pulls ...

If you don't get a response from someone who has successfully done this then create a github issue here: https://github.com/raspberrypi/firmware/issues where more of the devs will see it. Include your mods to dt-blob. I think what you want is theoretically possible, but may need a bit of digging to...

Hello, I am evaluating the use a Raspberry Pi Model B+ v1.2 board in an industrial control system. I am perfectly able to control all the pin pullups and pulldowns from userspace (I have verified all with an oscilloscope) however this does not help me. In particular, I need to disable the pullup on ...