---
title: "Platforms"
canonical_url: https://developer.repebble.com/pebbleos/docs/sdk/platforms/
last_updated: 2026-11-18
sdk_version: 4.44
---
# Platforms

Source: https://developer.repebble.com/pebbleos/docs/sdk/platforms/

A platform is what apps are built against. It is a name and a description:

| 

Part

 | 

Values

 |
| --- | --- |
| 

Display

 | 

width and height; rectangular or round; colour (8-bit) or black and white (1-bit)

 |
| 

Features

 | 

`microphone`, `smartstrap`, `smartstrap_power`, `health`, `compass`, `touch`, `rgb_backlight`, `speaker`

 |
| 

Limits

 | 

what an app may take: code and memory, worker memory, resources, the largest font glyph

 |
| 

ABI

 | 

what app binaries are compiled for; `armv7m` is Cortex-M3 Thumb code with soft float

 |

The name labels the platform’s directory in the SDK and in a `.pbw`. Everything the builds need to know of a platform follows from its description.

## Where platforms are defined

The platform is the firmware’s: nothing below it (the kernel, the drivers, a board) knows of it, and another application built on PebbleOS has none. `pebble/Kconfig.platform` lists the platforms and declares what a platform is described by. Each platform states its own values in `pebble/platforms/Kconfig.<name>`. The firmware picks one for each board it runs on, in its settings for the board, `pebble/boards/<board>.conf`:

```
CONFIG_PLATFORM_EMERY=y
```

Neither a board nor these settings can describe or alter a platform, so two boards of one platform cannot differ. The frozen platforms (Aplite, Basalt, Chalk and Diorite), which no firmware is built for, are described in `tools/pebble_sdk_platform.py`.

## Adding a platform

Hardware that fits no platform gets one of its own: an entry in the choice of `pebble/Kconfig.platform`,

```
config PLATFORM_SLATEbool "Slate"
```

and a `pebble/platforms/Kconfig.slate` with a default for each property it has. What it leaves out keeps the default of `Kconfig.platform`: black and white, rectangular, no feature, 64K for an app.

```
if PLATFORM_SLATEconfig PLATFORM_NAMEdefault "slate"config PLATFORM_COLORdefault yconfig PLATFORM_DISPLAY_WIDTHdefault 240config PLATFORM_DISPLAY_HEIGHTdefault 240config PLATFORM_MICROPHONEdefault yendif # PLATFORM\_SLATE
```

The board its SDK is packaged from is added to `sdk/boards.yml` ([Building the SDK](https://developer.repebble.com/pebbleos/docs/sdk/building.md)).

The same file states the RAM of its apps, `APP_RAM_4X_SEGMENT_SIZE` and `APP_RAM_4X_RUNTIME_SIZE`. The RAM of the 2.x and 3.x apps it runs follows from its shape and colour depth.

No tool is told about the platform. `tools/pebble_sdk_platform.py` derives from the description what the builds read:

- the defines apps are compiled with: `PBL_PLATFORM_SLATE`, `PBL_COLOR` or `PBL_BW`, `PBL_RECT` or `PBL_ROUND`, `PBL_DISPLAY_WIDTH` and `_HEIGHT`, and one per feature, such as `PBL_MICROPHONE`;

- the tags of resource file names: `slate`, `color`, `rect`, `mic`, `240w`, `240h`;

- the size limits.

What the system draws differently per platform (the status bar, the action bar, default text sizes) is that of the nearest of Emery, Flint and Gabbro: Gabbro if the display is round, Emery if it is rectangular and colour, Flint otherwise.

## In the SDK

`pbl build sdk` writes the description of the build’s platform to `build/sdk/<platform>/platform.json`, beside its headers and library:

```
{"version": 1,"name": "emery","abi": "armv7m","display": { "width": 200, "height": 228, "shape": "rect", "color": true },"features": ["microphone", "smartstrap", "smartstrap\_power", "health","compass", "touch", "rgb\_backlight", "speaker"],"limits": { "app\_binary": 131072, "app\_memory": 131072,"worker\_memory": 10240, "resources": 1048576,"resources\_appstore": 262144, "font\_glyph": 512 },"moddable": true}
```

The app build lists the platforms of an SDK from these files, so a platform is added to an SDK by adding its directory. A project picks among them by name, with `targetPlatforms` ([Building apps](https://developer.repebble.com/pebbleos/docs/sdk/app_build.md)).

## What an app binary says

An app binary says what the platform it was built for is like, in a 16-byte `PebblePlatformInfo` that follows the GNU build ID note. Neither the `PebbleProcessInfo` header nor the note moves, so firmware that predates the record finds both where they were. `PROCESS_INFO_HAS_PLATFORM_INFO` in the header’s flags says the record is there.

| 

Offset

 | 

Size

 | 

Field

 |
| --- | --- | --- |
| 

0xA8

 | 

1

 | 

version (1)

 |
| 

0xA9

 | 

1

 | 

length of the record in bytes (16)

 |
| 

0xAA

 | 

1

 | 

ABI (1 is `armv7m`)

 |
| 

0xAB

 | 

1

 | 

display shape: 0 rectangular, 1 round

 |
| 

0xAC

 | 

2

 | 

display width

 |
| 

0xAE

 | 

2

 | 

display height

 |
| 

0xB0

 | 

4

 | 

features, one bit each in the order of the list above

 |
| 

0xB4

 | 

2

 | 

app memory the binary needs, in KiB

 |
| 

0xB6

 | 

1

 | 

bits of colour of a pixel: 1 for black and white, 6 for 64 colours

 |
| 

0xB7

 | 

1

 | 

reserved, zero

 |

Fields are only added at the end and the length grows with them, so a reader skips what it does not know. It also ignores the feature bits it does not know, and takes a display shape it does not know as one it cannot show.

A platform that `PebbleProcessInfoFlags` has no value for is `PROCESS_INFO_PLATFORM_OTHER` there. Firmware that predates the record takes such an app to be for its own platform. Apps for the frozen platforms carry no record: the firmware knows those platforms, and their SDK does not know the record.

Generated from PebbleOS [7753e801d](https://github.com/coredevices/pebbleos/commit/7753e801d93d20f2d37534ce2fa69d9952015237). This page is maintained in the pebbleos repository: [docs/sdk/platforms.md](https://github.com/coredevices/pebbleos/blob/7753e801d93d20f2d37534ce2fa69d9952015237/docs/sdk/platforms.md).
