Skip to content

Latest commit

 

History

History
77 lines (49 loc) · 3.19 KB

API-1.0.md

File metadata and controls

77 lines (49 loc) · 3.19 KB
Raw

Toboot API v1.0

Toboot allows for some interaction between your application and the Tomu itself.

Version

This document describes v1.0 of the API, which is the default API used if your program doesn't declare compatibility with another API version.

Watchdog Timer

Toboot sets the watchdog timer. You must disable it, or start feeding it right away. A quick hack to disable the Watchdog timer is to write:

*(uint32_t *)0x40088000UL = 0;

Application Entrypoint

Your application's stack pointer is expected to live at offset 0x4000, and the entrypoint is expected to be at offset 0x4004. This is the same as the stock Silabs bootloader, and follows standard ARM Cortex M0 behavior.

Toboot is guaranteed to exist within the first 0x2000 bytes, and in fact future versions may even be under 0x1000 bytes. This means that you can have code and data within the 0x2000-0x4000 region. You can even use it as storage if you like.

By adopting this convention, we ensure compatibility with legacy Toboot code and bootloaders.

Boot Token

The first 8 bytes of memory (offset 0x20000000 - 0x20000008) are reserved for a Toboot token. The boot token has the following structure:

struct boot_token {
    // Set this to 0x74624346 and reboot to enter bootloader
    uint32_t magic;

    // Set this to 0 when your program starts.
    uint8_t  boot_count;

    // The bootloader should set this to 0x23 for Tomu.
    uint8_t  board_model;

    // Unused.
    uint16_t reserved;
};

The value board_model is defined to be 0x23. The boot_count value describes the number of times the board has rebooted. If the board fails to reboot three times in a row, it will enter Toboot automatically.

The magic value allows you to enter Toboot programmatically. Set this value to 0x74624346 and reboot.

Toboot Configuration Values

The configuration values for Toboot V1.0 are stored at offset 0x94 from the start of the binary image. Normally this is where external interrupt vector 21 lives, however the highest interurpt vector on the EFM32HG is 20. Therefore, Toboot V1.0 uses this word as the Toboot Configuration Flag to configure how Toboot behaves. It is a 32-bit word with the following format:

0xrrrrLLLL

rrrr are reserved values. Set these to 0.

If LLLL is set to 0x70b0, then users cannot enter Toboot by shorting out the pads. Use this to lock out firmware uploads, except programmatically.

Offset 0x98 is the Toboot App Flag. This configures how your app is loaded. It contains the following format:

0xrrSSKKKK

rr values are reserved. Set these to 0.

The KKKK values are the key. They must be set to 0x6fb0, otherwise the App Configuration Flag is ignored.

Set SS to the starting page number to load your program at. Page sizes are 1024 bytes. To maintain compatibility with earlier programs, you may want to set this value to 0x00106fb0, which will explicitly cause programs to be loaded at offset 0x4000. Be very careful with this value, because you can use it to overwrite Toboot. This approach is deprecated in favor of using something like Booster to update Toboot itself.