3 ms·
On the subject of small code: embedded folk have to do this sort of thing all the time. Put a wifi AP and client on a tiny processor with 1Mb of flash/256K of R
by JoeAltmaier 8y ago
On the subject of small code: embedded folk have to do this sort of thing all the time. Put a wifi AP and client on a tiny processor with 1Mb of flash/256K of RAM. Host a web site so the user can configure the device. Contact a cloud server for continuous IoT provisioning. And perform whatever function the device does.
- vanderZwan 8y agoOTOH, the embedded context is kind of special in that you can hyper-optimize for each device, right? For example: a program that runs on a desktop may have to take into account many edge-cases, but if an embedded device has quirks then they always apply for that device, so you can remove the "non-edge case" code from the binary.
- JoeAltmaier 8y agoFurther: there are 'board support packages' or BSPs that are tailored to the processor, support chips and package that you're coding too. They work exactly for that configuration and no other. It'd be impossible to fit much in there otherwise!