In this post, we meet the BeaglePlay! The latest SBC from Beagleboard.org. With everything that you would expect from an SBC and some innovative additions, you will definitely want to own one right away!
This is part 4 in a series about OP-TEE, the trusted part of a secure linux implementation. In this part, we see how to write and build our first trusted application based on a simple example.
This is the part 3 in the series of posts about OP-TEE. In this post, we talk about how to set up and test OP-TEE on two very popularly used platforms - QEMU and Raspberry Pi 3.
This is the part 2 in the series of posts about OP-TEE. In this post, we talk about the various components of the OP-TEE project, what their roles are and finally touch up on Global Platform.
In order to enhance the cybersecurity of linux-based systems as well as to meet compliance requirements, more and more systems are making use of TEE or Trusted Execution Environment to implement security-critical functionality. Where does a beginner start? Read on..
An increasing number of modern-day geolocation systems are based on linux. A framework called gpsd enables a simple mechanism to get geo-location data from location sensors. Check out this post that talks about using gpsd.
Yocto is the most preferred build system used by embedded linux developers across the world owing to its layered and modular nature. In this post, we see how to add Yocto support for this board and then build a minimal image to test this support.
The Jupiter Nano ships with a debian image. However, not everyone wants to use debian. Also, something like Yocto allows you to heavily customize your linux image as well as reduce your boot time considerably. Check out this post that lays the foundation for creating a Yocto image.
The Jupiter Nano is an open-source hardware based on an awesome MPU product from Microchip called the SAMA5D27C-LD1G. The boards exposes a lot of IO in spite of a tiny form-factor, boots a full-fledged linux distro as well as can support microcontroller-like development flow.
TLDR: In their run-time engine code, Amazon provides the ability to use PKCS#11 tokens to perform mutual TLS authentication with the cloud. Here, we use Microchip ATECC608 as a PKCS#11 token. By using Microchip's ATECC608, the act of generating and storing keys and certificates is rendered unnecessary and the device-to-cloud on-boarding is a breeze! Welcome … Continue reading Raspberry Pi + ATECC608: Part 3 – Using PKCS#11 Token For MQTT Pub-Sub with AWS IoT Core
