|SAN19 Demo Title||SAN19 Demo Description|
|Analog Devices 3D Time of Flight Development Platform||Demonstration of Analog Devices AD-96TOF1-EBZ development kit demonstrating 3D depth mapping.3D depth mapping is useful for many applications ranging from Gesture Control, Surveillance, Simultaneous Location and Mapping (SLAM), People Counting, Collision Avoidance, Computer Depth Perception, and Safety/Proximity Sensing. The two (2) board mezzanine system with laser drive and camera connect to a DragaonBoard 410c processor baseboard to generate point cloud depth images.|
|Bypassing Secure Boot using fault injection||Secure Boot is a mechanism used to ensure no untrusted code is executed on a device. Many modern devices implement some form of secure/encrypted boot to protect the confidentiality of the firmware and data stored on the device, as well as a mechanism to ensure it is not possible to persistently compromise a device. |
As manufacturers are improving the code quality of their solutions and the existence of software vulnerabilities is no longer guaranteed, attackers are also evolving and utilizing other attack methods like hardware attacks. Recent attacks, for example against popular game consoles, used such hardware attacks as first step in building a full exploit.
In this demo we demonstrate fault injection attacks, a category of hardware attacks, to bypass secure boot on a modern Android device. This attack allows an attacker to run unauthenticated and untrusted code at the highest privilege level of the device.
We demonstrate this attack using equipment we developed to help manufacturers test their devices and make them more robust against this type of attacks.
|Mainline* kernel on form-factor Android devices||We demonstrate a couple of SDM845 based mobile phones that run a 'close-to-mainline' kernel with Android from AOSP/master.|
|RDK v3 and Playready on i.mx8mq||RDK 3.0 media stack with 64bit compatibility includes Spark framework, AAMP player, WPE based RDK browser and WPE framework|
|GKI w/ AOSP devboards||Demo running GKI kernel on AOSP devboards|
|Dragonboard 845c updates||The Qualcomm Landing Team will demonstrate the latest and greatest upstream code for the Dragonboard 845c.|
|LAVA in a box||A stand alone system demonstrating working LAVA.|
|DB4V3，SoM96-3399||DB4V3： 96 board bases on Qualcomm SD410 SoC|
SoM96-3399:96 SoM bases on Rochchip RK3399
|96Boards Misc - Demos||The 96Boards team is planning on bringing a collection of small demos that we want to group together and show as a collection.|
These demo's are a collection "make" style projects.
|OpenAmp - Avenger96||A simple demo to show the functionality of OpenAMP on the STM32MP1 based Avenger96 board.|
The demo will showcase the communication between Cortex-M cores running Zephyr and Cortex-A Cores running Linux present in the STM32MP1 SoC.
|Robotic Arm - RB3||A Pick-and-place style Robotic arm based on the Qualcomm RB3 dev board.|
|Security for Bigdata - Apache Ranger and Kerberos on ARM64||Enterprises are embracing big data like never before, using powerful analytics to drive decision-making, identify opportunities, and boost performance. But with the massive increase in data usage and consumption comes a whole set of big data security concerns. We at LDCG Big Data team were successful to port and build security components for big data. This will be a demo of Security at fine grain level integrated into various big data components.|
|TF-M remote secure services with Zephyr on Musca B1e/AN521||Trusted Firmware M (TF-M) is an open source implementation of Platform Security Architecture (PSA) for Arm Cortex M processors. TF-M provides secure services to other cores or non-secure execution environments using PSA APIs on the M profile core.|
This demo is going to extend TF-M to support multiple core system. The hardware will be AN521 and Musca B1, they are all arm SoC with two cores. TF-M running on a secure core to manage secure devices, data and features. All secure partitions and secure features are handled by TF-M itself. Secure core only exposes standard PSA APIs providing secure services. Applications running on another core with Zephyr, they request services to TF-M to access secured features or data. Designers can focus on applications development, and have an easy way to leverage TF-M to get multiple core PSA certified.
This concept can apply to any board which can run TF-M in an isolated core. And for the secure features can be keep up to date with TF-M’s evolution.
|Arrow Electronics demos||Different demos running on Arrow related 96boards platforms|
|Autoware vision detection node running accelerated on a Arm platform||Autoware is a self-driving open source project. We show that its vision detection node which is the most compute-intensive nodes can run at real-time frame rates on a low power arm based platform.|
|MMWG DEMO: libcamera + mainline kernel on Rock Pi 4 B||libcamera with mainline kernel on Rock Pi 4 B|
|Running K3s on arm64 devices||Leo and Kevin will demo running K3s on Arm64. K3s is the lightweight Kubernetes distribution which is famous on edge cloud device. We will show how to an applications running on K3s on Arm64 edge device, and interaction with the Arm64 data center.|
|UCSD Hackathon winners||Winners of UCSD hackathon from Weds of Connect show their work|
|Applied PSA Attestation|
TrustedFirmware-M (developed at Linaro) is the reference implementation for the Platform Security Architecture (PSA), and the Attestation API is one of the innovations for constrained devices.
The goal of the demo is to show how the PSA Attestation API exposes the cyber-physical security functions of PSA Root of Trust services. Through different use-cases, the demo will show how valuable high-level security functions can be built: verifying authenticity of hardware and integrity of software configuration, providing initial/bootstrap authentication service for on-boarding / recovery, attestation of data.
I know Arm is a Linaro member and a Linaro Connect sponsor, but this demo request should not be interpreted as an official Arm request.
Internet connection is required for the demo: ethernet preferred but Wi-Fi is possible.