Re:Why systemd is a problem for embedded Linux
by vv_ on Monday November 04, 2024 @05:55AM
(#42040410)
Typically in IoT you'll count RAM in kB not MB and definitely not GB. See STM32 H5/H7/L4/L4+/U0 as an example.
[ Parent
| on HN ]
Re:Why systemd is a problem for embedded Linux
by bmicraft on Monday November 04, 2024 @10:38AM
(#42042516)
Typically in IoT you'll use an soc that actually supported some kind of network connection
Re:Why systemd is a problem for embedded Linux
by vv_ on Tuesday November 05, 2024 @06:18AM
(#42050586)
Depends.
In Automotive (i.e. telematics devices) you'll want a separate MCU for CAN-bus. For example, if you are doing Request-Response model you'll want to make use of the built-in filters. Besides, it is unlikely that a modem would support the CAN interface.
In Cellular IoT you'll prefer a separate MCU as it is much easier to port to different hardware. For example, you can hook-up the module via UART and use CMUX (AT/GNSS/PPP) and you'll cover 80%+ of the modules available in the market with very minimal specific implementation layers to enter into these modes.