Linaro Connect Bangkok

Zephyr 1.14 is a long-expected LTS (Long-Term Support) release for Zephyr RTOS (https://www.zephyrproject.org/), a Linux Foundation project . A lot of effort went both into extending networking support for it and making it stable. This session discusses both things which fit and didn't fit into the LTS release.

Open Asymmetric Multi-Processing (OpenAMP) provides an open source framework that allows operating systems to interact within a broad range of complex homogeneous and heterogeneous architectures and allows asymmetric multiprocessing applications to leverage parallelism offered by the multicore configuration.  This session will introduce the framework and how to use it.

This session will describe the OpenAMP libmetal shared memory API. The talk will include the interface default backend implementation in Linux system

Trusted Firmware M is an open source implementation of Platform Security Architecture (PSA) for Arm M profile processors. It was publicly launched in Linaro Connect HKG18.
This talk discusses some of the challenges being tackled in TF-M to enable wider adoption. Two flavours of core design, concurrent context management, secure interrupt handling, multi-core support are just some of the hot issues on the plate.

Trusted Firmware-M (TF-M) is an implementation of Platform Security Architecture (PSA) for M class processors. TF-M includes a couple of secure services. Many partners want to take advantage of that to extend their PSA features.

Our design is to extend TF-M’s services to Zephyr based dual-core SoC. A Zephyr instance runs in secure core with secure services, another Zephyr instance runs in non-secure core which can call secure services. For this solution, the first step is to modularize secure services in TF-M and remove service platform dependencies. Then start them as Zephyr threads in secure core. And at last, implement IPC interface for the service requests from non-secure core to secure core by leveraging openAMP which is supported in Zephyr. This session will discuss the TF-M secure services modularization, running secure services in Zephyr and the IPC implementation.

IOT CUBE BOX – Shiratech First Indoor/Outdoor out of the Box IOT solution Based on 96Board IOT Extended addition
based on New ST CPU + Quectel BG96 M1/Cat NB1/EGPRS Modem
70% readymade product that can help users achieve fast time to market in the IOT world of products, High quality Design, API for user and cloud interface
Built In features
•    2 x Microphones 
•    Gas Sensor for a variety of sensing applications 
•    2 X DI (Digital Input)
•    2 X DO (Digital Output)
•    2 X AI (Analog Input)
•    External Sensor interface (GPIO, SPI, I2C, UART)
•    1 X SIM CARD
•    1 X SD CARD
•    2Gbit DDR3 Memory (32 bit)
•    8G Nand Memory (8 bit)
•    1 x USB
•    1 x UART
•    Linaro Debian BSP

Target Applications
•    Gass Monitoring applications 
•    Home appliance – IOT devices
•    Baby sense
•    IOT Sensing applications
•    Safe City /Smart City
• Home security

When developing embedded systems, it is common to have mixed-criticality requirements: one application is critical, and often comes with real-time requirements, while the other application is far less critical and it is typically based on Linux. Static partitioning is the best way to meet these requirements.

This talk will introduce Dom0-less: a brand new way of using Xen to build mixed-criticality solutions. Dom0-less is a Xen feature that adds a novel approach to static partitioning based on virtualization. It allows multiple domains to start at boot time directly from the Xen hypervisor, decreasing boot times dramatically. Dom0-less makes booting a critical application in less than a second an achievable goal. Xen userspace tools, such as xl and libvirt, become only optional. Even Dom0, the cardinal point of every Xen deployment since its inception, becomes inessential.

Dom0-less extends the existing device tree based Xen boot protocol to cover information required by additional domains. Binaries, such as kernels and ramdisks, are loaded by the bootloader (u-boot) and advertised to Xen via new device tree bindings.

The audience will learn how to use Dom0-less to partition the system. Uboot and device tree configuration details will be explained to enable the audience to get the most out of this feature. The presentation will also include a live demo of the technology.