Skip to content
Snippets Groups Projects
Select Git revision
  • schneider/ir
  • master default protected
  • rahix/user-space-ctx
  • schneider/iaq-python
  • schneider/ble-mini-demo
  • schneider/ble-ecg-stream-visu
  • schneider/mp-exception-print
  • schneider/sleep-display
  • schneider/deepsleep4
  • schneider/deepsleep2
  • schneider/deepsleep
  • schneider/ble-central
  • rahix/bluetooth-app-favorite
  • schneider/v1.17-changelog
  • schneider/ancs
  • schneider/png
  • schneider/freertos-list-debug
  • schneider/212-reset-hardware-when-entering-repl
  • schneider/bonding-fail-if-full
  • schneider/ble-fixes-2020-3
  • v1.18
  • v1.17
  • v1.16
  • v1.15
  • v1.14
  • v1.13
  • v1.12
  • v1.11
  • v1.10
  • v1.9
  • v1.8
  • v1.7
  • v1.6
  • v1.5
  • v1.4
  • v1.3
  • v1.2
  • v1.1
  • v1.0
  • release-1
40 results
Compare
Rahix's avatar
fix(lifecycle): Fix epic_sleep() calls delaying load of new app
rahix authored 
When core 1 repeatedly calls `epic_sleep()`, this could delay an
epic_load() from core 0 because the reset interrupt can only be
delivered after such a call completed.

To work around this, add calls into `do_load()` to notify the dispatcher
task that it should return early from calls like `epic_sleep()`.  This
gets a bit tricky because the dispatcher task also uses
`ulTaskNotifyTake()` to wake up when new API calls arrive.  To make sure
we still break out of `epic_sleep()`, we need to call
`xTaskNotifyGive()` twice in the wait loop.
cf60dfb7
History
Rahix's avatar cf60dfb7
History
Name Last commit Last update
Documentation
bootloader
docker
epicardium
hw-tests
l0dables
lib
openocd
preload
pycardium
spo2
tools
.clang
.clang-format
.clang-tidy
.gitignore
.gitlab-ci.yml
.gitmodules
CHANGELOG.md
COPYING
README.md
bootstrap.sh
card10-cross.ini
default.nix
flash-all.gdb
flash-bootloader.gdb
flash-both.gdb
flash-epicardium.gdb
flash-pycardium.gdb
init.gdb
meson.build
meson_options.txt
requirements.txt
shell.nix
README.md

card10 Firmware Readme

Firmware for the card10 badge for the Chaos Communication Camp 2019.

We keep documentation in the Documentation/ subdirectory. You can find a rendered version over at https://firmware.card10.badge.events.ccc.de/.

How To Help

If you want to help us ensure the card10 will have been exactly as we reconstructed from the audio-logs we recovered, please head over to our wiki, or directly to the issue tracker.

How To Build

A full guide for building is available in the docs as How To Build.

Last Artifacts from Gitlab-CI: pipeline status

How To Flash

Flasing with or without a debugger is described in detail in How To Flash.

Debugger

If you have a debugger, head over to our Debugger page to learn how to use it.

License

Unless otherwise noted in a file, the contents of this repository are licensed under the MIT license. See COPYING for more details.

Old README Contents:

TODO: Move over into new docs

Serial Console

Learn more about card10's Serial Console.

Bootloader

The bootloader is used to flash card10 without an external debugger. It exposes the file system via USB and accepts a card10.bin file as firmware image.

To flash the bootloader, go to the bootloader directory and follow the steps above.

To execute the bootloader, turn off card10, press the lower right button and turn on. Connect card10 via a USB cable to a computer and mount the file system. You can now copy your card10.bin file to the file system. Eject the drive (IMPORTANT!) via your operating system (umount and sync is not enough). Turn card10 off and back on again. It will try to boot the image.

IMPORTANT: The prototypes have the USB data lines reversed. Use the provided USB adapter to connect card10.

Building card10.bin

Run ./build_image. TODO: Add to meson

The tool uses Python to generate a CRC. Make sure to have python-crc16 installed.