fra

23 ms·

181.
Bootstrapping Libc with Newlib(interrupt.memfault.com)
3 points by fra 7y ago|0 comments
182.
Using Type-Level Programming in Rust to Make Safer Hardware Abstractions(blog.auxon.io)
33 points by fra 7y ago|0 comments
183.
Using Asserts in Embedded Systems(interrupt.memfault.com)
5 points by fra 7y ago|0 comments
184.
ARM Cortex-M RTOS Context Switching(interrupt.memfault.com)
1 points by fra 7y ago|0 comments
185.
Embedded C/C++ Unit Testing Basics(interrupt.memfault.com)
3 points by fra 7y ago|0 comments
186.
by fra 7y ago
For what it's worth: musl is much larger than newlib-nano or picolibc. Most of the embedded projects I've worked on could not afford to use musl.
187.
by fra 7y ago
That's a great presentation! I had not seen it. Thanks for sharing.
188.
by fra 7y ago
Until you try to do an over-the-air firmware update :-).
189.
Hand Tracking on Oculus Quest(oculus.com)
8 points by fra 7y ago|0 comments
190.
A Practical Guide to Bluetooth Low Energy (BLE) Throughput(interrupt.memfault.com)
88 points by fra 7y ago|5 comments
191.
Building Better Firmware with Continuous Integration(interrupt.memfault.com)
3 points by fra 7y ago|0 comments
192.
A Practical Guide to ARM Cortex-M Exception Handling(interrupt.memfault.com)
3 points by fra 7y ago|0 comments
193.
by fra 7y ago
While it is true that the core WiFi code is not open source, the ESP-IDF is significantly more open than anything else on the market today. This is not to say that Espressif is the bee's knees. I personally wouldn't use their hard
194.
by fra 7y ago
First and foremost, this speaks to the ubiquity and hacker friendliness of Espressif's chips. Most of their competitors (I'm looking at you, Broadcom), prefer security through obscurity and make it extremely difficult to get acces
195.
Building a CLI for Projects Using Invoke(interrupt.memfault.com)
2 points by fra 7y ago|0 comments
196.
by fra 7y ago
We plan to support embedded Linux in the future.
197.
by fra 7y ago
We've just about hired everybody we need for the time being, but we're open to meeting folks who would bring a lot to the team. Send me a note! francois - at - memfault
198.
by fra 7y ago
Yes, I was excited to meet some of them! It is certainly possible to use Sentry with firmware, but I'd venture to say that Memfault is an easier integration and a better experience.
199.
by fra 7y ago
Thanks! Hope you've enjoyed reading Interrupt, let me know if there's a topic you'd like us to write about.
200.
by fra 7y ago
The connectivity story is indeed one of the major complications. Here's a high level overview on how we deal with it: let's say you have a device connected via UART to a Linux box with WiFi. 1. When an error occurs, the Memfault l
201.
by fra 7y ago
There are a few concepts that do not map neatly: 1. For firmware, each user is on their own hardware. Rather than a session you need to track a device and the state thereof. Devices exist for a longer period of time than sessions do, and yo
202.
by fra 7y ago
Do you have recommendations for data warehousing? Our data does have a fixed structure at the moment.
203.
by fra 7y ago
It would be interesting to chat with someone working on that set up to figure out what an implementation could look like. I wonder if solutions for windows desktop would work in that case?
204.
by fra 7y ago
We took a page from Heap's book and ultimately store the data in Postgres databases.
205.
by fra 7y ago
Yes, we can accommodate a custom transport. In a way, this is just a general application of what we do for the BLE transport: break up data structures into fixed sized packets, send them over the link, reassemble on the other side.
206.
by fra 7y ago
> Any concerns about privacy? Even if Memfault is one-way (as you mentioned in a different comment), that doesn't mean that important user information is not exposed. Battery SOC and last-seen stats aren't completely harmless.
207.
by fra 7y ago
Do you mean the CSR family? We don't currently support the XAP architecture, but it is technically doable and we would do it with the right partner. Get in touch if you want to chat!
208.
by fra 7y ago
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
209.
by fra 7y ago
We have SDKs for iOS, Androids, and other gateway devices to push logs up to the cloud over bluetooth.
210.
by fra 7y ago
Edit: emailing you now. That would be great! Send me an email: francois at memfault. I'd be thrilled to chat (or grab a coffee if you're in the bay).

More ›