Hacker News Reader

Currently, Memfault is one-way so it is not quite like having JTAG access to your device from the cloud.

But it still needs to be secure, and we typically encrypt all data going from the device to the cloud (some devices, sadly, do not have the ability to do the encryption).

Edit: removed double negative.

View on HN

How can it be one-way if you can push new releases to the device?

Rather than "pushing" releases and data to each device, the devices query for the URL to the latest firmware (if any).

This still isn't one-way, what protocol parsers are you implementing in firmware to do this?

It's up to the firmware or customer architecture to decide that. Many companies in the industry use an S3 bucket to publish firmware binaries to their devices, and these binaries are read by hubs, mobile applications, connected linux boxes, and yes, sometimes firmware devices themselves. Memfault provides a couple of layers on top of S3, allowing the customer to group devices into cohorts and do staged roll-outs.

Reply on news.ycombinator.com