- Mon Apr 18, 2016 1:25 pm
#45736
I was trying to integrate a serial music player with the udp control framework I'm doing, and hit a snag...
My udp framework uses the onboard blue gpio01 (TX) led to do things like flash out the ip address etc, but that then seems to later prevent serialprintln from transmitting, which also uses gpio01 as TXD.
I suspect this might be due to gpio01 already being assigned as output and left in a high or low state rather floating - but changing the pin to input with pi isn't going to help.
I see the pi and po commands that configure pins as inputs or outputs, but don't see anything like a pf(float) command that could 'un-configure' a pin to leave it floating... is that something that is possible?
If not, I think I can 'cludge' things by using serial2 for TX and serial(1) for RX, but it would be useful if there was a more elegent solution.
My udp framework uses the onboard blue gpio01 (TX) led to do things like flash out the ip address etc, but that then seems to later prevent serialprintln from transmitting, which also uses gpio01 as TXD.
I suspect this might be due to gpio01 already being assigned as output and left in a high or low state rather floating - but changing the pin to input with pi isn't going to help.
I see the pi and po commands that configure pins as inputs or outputs, but don't see anything like a pf(float) command that could 'un-configure' a pin to leave it floating... is that something that is possible?
If not, I think I can 'cludge' things by using serial2 for TX and serial(1) for RX, but it would be useful if there was a more elegent solution.
