Destide@feddit.uk to Programmer Humor@lemmy.mlEnglish · 1 day agoInfallible Codelemmy.mlimagemessage-square148fedilinkarrow-up1433
arrow-up1433imageInfallible Codelemmy.mlDestide@feddit.uk to Programmer Humor@lemmy.mlEnglish · 1 day agomessage-square148fedilink
minus-squarexthexder@l.sw0.comlinkfedilinkarrow-up6·edit-215 hours agoGPIOs are usually controlled by a single bit of a register anyway. Most likely you need to do something like: // Set high PORTB |= 1 << PINB5; // Set low PORTB &= ~(1 << PINB5);
minus-squareCroquette@sh.itjust.workslinkfedilinkarrow-up2·13 hours agoI am a lazy dev (not really, clients always want fast code), so I use the provided HAL libraries 99.9% of the time. But I have seen code where someone would write something like gpio_write(PIN_X, true) and it always stood out to me.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up1·6 hours agoDefine on as true or something? Or maybe that’s more confusing. I’m not a C dev so I’m not gonna pretend to understand idiomatic microcontroller code lol.
minus-squareCroquette@sh.itjust.workslinkfedilinkarrow-up1·10 minutes agoSometimes, people do that. But using 0/1 is explicit enough since you can refer to a line as ‘1’ or ‘0’ for high/low on the hardware as well
GPIOs are usually controlled by a single bit of a register anyway. Most likely you need to do something like:
// Set high PORTB |= 1 << PINB5; // Set low PORTB &= ~(1 << PINB5);I am a lazy dev (not really, clients always want fast code), so I use the provided HAL libraries 99.9% of the time.
But I have seen code where someone would write something like
gpio_write(PIN_X, true)and it always stood out to me.
Define on as true or something? Or maybe that’s more confusing. I’m not a C dev so I’m not gonna pretend to understand idiomatic microcontroller code lol.
Sometimes, people do that. But using 0/1 is explicit enough since you can refer to a line as ‘1’ or ‘0’ for high/low on the hardware as well