cfriedt

```shell
twister -p native_sim -p qemu_riscv64 -p qemu_x86 -p qemu_x86_64 -p qemu_cortex_a53 -p mps2/an385 -T tests/posix
...
INFO    - Total complete:  270/ 270  100%  skipped:   84, failed:    0, error:    0
INFO    - 45 test scenarios (270 test instances) selected, 84 configurations skipped (58 by static filter, 26 at runtime).
INFO    - 186 of 270 test configurations passed (100.00%), 0 failed, 0 errored, 84 skipped with 0 warnings in 403.48 seconds
INFO    - In total 7029 test cases were executed, 3759 skipped on 6 out of total 21 platforms (28.57%)
INFO    - 181 test configurations executed on platforms, 5 test configurations were only built.
```

cfriedt

From 398403cec5a0167c0d027196913b17759cc1a2a1 Mon Sep 17 00:00:00 2001
From: Chris Friedt <cfriedt@tenstorrent.com>
Date: Tue, 2 Jul 2024 20:13:49 -0400
Subject: [PATCH] fdtable: avoid pulling in posix header & types

Although fdtable sat a layer below posix, as part of
the base os, it was reaching up a layer for posix types,
creating another dependency cycle.

Additionally, <sys/select.h> no longer has

cfriedt

# The contents of this file should go into ~/.zephyrrc
# It is sourced with
# source zephyr-env.sh

# Download the Zephyr SDK from
# https://github.com/zephyrproject-rtos/sdk-ng/releases

ZEPHYR_SDK_VERSION=0.16.5-1
PREFIX=/opt/zephyr
VENV=$PREFIX/.venv

cfriedt

#!/bin/bash
set -e

# usage:
# ./zephyr-release-stats.sh | tee zephyr-release-stats.csv

cd $HOME/zephyrproject/zephyr

RELEASES=( v2.0.0 v2.1.0 v2.2.0 v2.3.0 v2.4.0 v2.5.0 v2.6.0 v2.7.0 v3.0.0 v3.1.0 v3.2.0 v3.3.0 v3.4.0 v3.5.0 )
N=${#RELEASES[@]}

cfriedt

Using Linux, Zephyr & Greybus for IoT - Post Plumbers Publication

• Plumbers Recap
• Greybus for IoT
• What Are The Key Values in Greybus for IoT?
  • Discoverability
  • Keep the Intelligence in the Host
  • Standard Communication Protocols and APIs
• What Next with Greybus for IoT?

• Gbridge

cfriedt

Using Linux, Zephyr & Greybus for IoT with the CC1352R SensorTag

• Introduction
  • Why??
  • History
• Hardware Requirements
• Prerequisites
• Console (Minicom)
  • Set Up Minicom

• Run Minicom

cfriedt

Blink an LED using Linux, Zephyr & Greybus via IEEE 802.15.4

• Introduction
  • Why??
  • History
• Hardware Requirements
• Prerequisites
• Console (Minicom)
  • Set Up Minicom

• Run Minicom

cfriedt

Blink an LED using Linux, Zephyr & Greybus via Bluetooth

• Introduction
  • Why??
  • History
• Hardware Requirements
• Prerequisites
• Console (Minicom)
  • Set Up Minicom

• Run Minicom

cfriedt

Linux to Zephyr TCP Communication over IEEE 802.15.4 and 6LowPAN

This document describes, in some detail, the steps required to establish a reliable TCP commmunication channel between a Linux workstation and Zephyr device over IEEE 802.15.4 and IPv6 (via 6LowPAN).

Hardware Requirements

• a Linux workstation running Ubuntu Bionic
  • Only x86_64 is supported at this time
• a board that is supported by Zephyr with support for IEEE 802.15.4
• In this example, we use the cc1352r1_launchxl

cfriedt

What Would Travis Do (on Windows)

A Travis-CI Compatible Environment for Windows on Google Cloud

This gist should help users set a Google Cloud Virtual Machine (VM) environment similar environment to that provided by the Travis CI for Windows.

Initially, the regular traditional Windows Command Prompt is used for executing commands, and then git-bash is used for subsequent commands, much like the Travis environment.

Create a new VM Instance