Hi
We're trying to use some of the GPIO pins as output with a optocoupler attached.
Once started and code has initialized the GPIO ports as DigitalOut everyting works ok.
BUT what we're seeing is
1) when flashing,
2) sending a break over the serial port or
3) pressing/holding the reset button down,
the GPIO pins are inputs with a very small pullup resistor pulling towards 3V in such way that is already capable of driving the opto couplers even when being an input.
For instruments (like we're building) this kind of behavior is very dangerous (inputs should be very high impedance and should never be able to drive anything).
It makes it also virtually impossible to use these GPIO pins as outputs as their behavior as input during reset is very unwanted.
I'm unable to locate the value of the pullup resistor and the input circuitry in the manuals. Any pointers?
So main is question is: is there a way around to this and have the input just have an high impedance/tri-state during reset? I'm not sure where this behavior originates from (mbed boot load or the arm cpu used),
wvd_vegt
Hi
We're trying to use some of the GPIO pins as output with a optocoupler attached.
Once started and code has initialized the GPIO ports as DigitalOut everyting works ok.
BUT what we're seeing is
1) when flashing, 2) sending a break over the serial port or 3) pressing/holding the reset button down,
the GPIO pins are inputs with a very small pullup resistor pulling towards 3V in such way that is already capable of driving the opto couplers even when being an input.
For instruments (like we're building) this kind of behavior is very dangerous (inputs should be very high impedance and should never be able to drive anything).
It makes it also virtually impossible to use these GPIO pins as outputs as their behavior as input during reset is very unwanted.
I'm unable to locate the value of the pullup resistor and the input circuitry in the manuals. Any pointers?
So main is question is: is there a way around to this and have the input just have an high impedance/tri-state during reset? I'm not sure where this behavior originates from (mbed boot load or the arm cpu used),
wvd_vegt