https://github.com/microbit-foundation/standalone-error-v1
Error program for micro:bit v1
https://github.com/microbit-foundation/standalone-error-v1
Last synced: over 1 year ago
JSON representation
Error program for micro:bit v1
- Host: GitHub
- URL: https://github.com/microbit-foundation/standalone-error-v1
- Owner: microbit-foundation
- License: mit
- Created: 2020-09-17T08:33:24.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2021-03-29T16:56:26.000Z (over 5 years ago)
- Last Synced: 2025-01-20T21:56:42.610Z (over 1 year ago)
- Language: C
- Size: 19.5 KB
- Stars: 0
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# stand-alone-error-v1
Stand alone error program for micro:bit v1
## Build
This project is built using Yotta. Instructions for building using Yotta can be found [here](https://lancaster-university.github.io/microbit-docs/offline-toolchains/#yotta).
*NOTE:* The `yotta target` is configured in the `.yotta.json` file already, as this project uses a different target to the default specified in the tutorial above. The `yotta target` step from the instructions should be skipped.
The compiled hex file can then be found at `build/bbc-microbit-classic-gcc-nosd/source/stand-alone-error-v1.hex`
## License
All files were created by the Micro:bit Educational Foundation and are MIT licensed.
## Code of Conduct
Trust, partnership, simplicity and passion are our core values we live and breathe in our daily work life and within our projects. Our open-source projects are no exception. We have an active community which spans the globe and we welcome and encourage participation and contributions to our projects by everyone. We work to foster a positive, open, inclusive and supportive environment and trust that our community respects the micro:bit code of conduct. Please see our [code of conduct](https://microbit.org/safeguarding/) which outlines our expectations for all those that participate in our community and details on how to report any concerns and what would happen should breaches occur.