Add crate info to coding retreat post

This commit is contained in:
Wesley Moore 2019-03-23 13:17:47 +11:00
parent 46798fbf65
commit 7cc2622fbe
No known key found for this signature in database
GPG key ID: BF67766C0BC2D0EE
2 changed files with 10 additions and 7 deletions

View file

@ -34,7 +34,7 @@ and a walk or two around the surrounds.
After [linux.conf.au] I got inspired to set up some self-hosted home sensors After [linux.conf.au] I got inspired to set up some self-hosted home sensors
and automation. I did some research and picked up two [Texas Instruments and automation. I did some research and picked up two [Texas Instruments
SensorTags][SensorTag] and a debugger add-on. It uses a [CC2650] SensorTags][SensorTag] and a debugger add-on. It uses a [CC2650]
microcontroller with an ARM Cortex-M3 core and has support a number for low microcontroller with an ARM Cortex-M3 core and has support for a number of low
power wireless standards, such as Bluetooth, ZigBee, and 6LoWPAN. The CC2650 power wireless standards, such as Bluetooth, ZigBee, and 6LoWPAN. The CC2650
also has a low power 16-bit sensor controller that can be used to help achieve also has a low power 16-bit sensor controller that can be used to help achieve
years long battery life from a single CR2032 button cell. In addition to the years long battery life from a single CR2032 button cell. In addition to the
@ -59,9 +59,9 @@ View Description XML files (SVD) into a Rust crate. Unfortunately TI don't
publish SVD files for their devices. As luck would have it though, [M-Labs] publish SVD files for their devices. As luck would have it though, [M-Labs]
have found that TI do publish XML descriptions in format of their own called have found that TI do publish XML descriptions in format of their own called
DSLite. They have written a tool, [dslite2svd], that converts this to SVD, so DSLite. They have written a tool, [dslite2svd], that converts this to SVD, so
you can then use `svd2rust`. It took a while to get `dslite2svd` working and I you can then use `svd2rust`. It took a while to get `dslite2svd` working. I had
had to tweak to the tool to handle differences in the files I was processing, to tweak it to handle differences in the files I was processing, but eventually
but eventually I was able to generate a crate that compiled. I was able to generate a crate that compiled.
Now that I had an API for the chip I turned to working out how to program and Now that I had an API for the chip I turned to working out how to program and
debug the SensorTag with a very basic Rust program. I used the excellent debug the SensorTag with a very basic Rust program. I used the excellent
@ -214,7 +214,10 @@ The rest of the code is up on [Sourcehut]. It's all in a pretty rough state at
the moment. I plan to tidy it up over the coming weeks and eventually publish the moment. I plan to tidy it up over the coming weeks and eventually publish
the crates. If you're curious to see it now though, the repos are: the crates. If you're curious to see it now though, the repos are:
* [cc2650f128](https://git.sr.ht/~wezm/cc2650f128) -- chip support crate * [cc2650f128](https://git.sr.ht/~wezm/cc2650f128)
[![crates.io](https://img.shields.io/crates/v/cc2650.svg)](https://crates.io/crates/cc2650)
[![Documentation](https://docs.rs/cc2650/badge.svg)](https://docs.rs/cc2650)
-- chip support crate
generated by `dslite2svd` and `svd2rust`. generated by `dslite2svd` and `svd2rust`.
* [cc26x0-hal](https://git.sr.ht/~wezm/cc26x0-hal) (see `wip` branch, currently * [cc26x0-hal](https://git.sr.ht/~wezm/cc26x0-hal) (see `wip` branch, currently
very rough). very rough).

View file

@ -4,7 +4,7 @@ extra: I attended a small coding retreat with some friends and worked on running
kind: article kind: article
section: technical section: technical
created_at: 2019-03-12 19:45:00.000000000 +11:00 created_at: 2019-03-12 19:45:00.000000000 +11:00
#updated_at: 2019-03-02T14:09:11+11:00 updated_at: 2019-03-23T13:16:07+11:00
keywords: keywords:
- rust - rust
- embedded - embedded