Low Level Sensor Programing and Security Enforcement with MRAA
summary
MRAA and companion UPM provide a platform‑independent C/C++/JavaScript/Python API with over 300 sensors supported and about 400 UPM drivers layered on top; a peripheral manager back-end is implemented to proxy all I/O through Android Things’ peripheral manager back-end so user‑space code never touches the kernel; an AGL AFB bus binding routes MRAA calls through the binder with Smack enforcement so per‑application permissions control which I2C/GPIO devices are reachable.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:22Agenda
- 6:12UI Demo
- 7:28C API
- 8:06Python API
- 8:22asynchronous calls
- 9:15why unified API
- 10:14sensors
- 11:49boards
- 12:54platforms
- 15:29weird stuff
- 22:16How it works
- 23:38Complex picture
- 28:03Future plans
- 30:05Further reading
related talks
32mGood Motive but Bad Design: Pitfalls in MPU Usage in Embedded Systems in the Wild
15mRemote MCPs: What we learned from shipping
27mAWare: Preventing Abuse of Privacy-Sensitive Sensors via Operation Bindings
43mDARPA and Privacy Research
13mARM mbed
27mUSMA: Share Kernel Code With Me
57mTrusted Firmware M : Core and Partition Manager
37mImplement Safety with a RTOS Running as a Linux Companion Within...