diff --git a/_layouts/default.html b/_layouts/default.html index f1a6c18..a631d10 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -88,7 +88,7 @@

tweet
  • - usage + gpio
  • finish @@ -150,7 +150,7 @@

    5. tweet

  • - 6. usage + 6. gpio
  • 7. finished diff --git a/blinky.md b/blinky.md index 0268745..dcd395a 100644 --- a/blinky.md +++ b/blinky.md @@ -56,6 +56,9 @@ to run your code in Tessel's RAM. **Look at your Tessel!** The blue and green LEDs on your Tessel's LED panel should blink back and forth. **Bonus:** mess with the code to make the LEDs blink in sync. + +**Extra bonus:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push index.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli). + diff --git a/finished.md b/finished.md index 150a470..48d4812 100644 --- a/finished.md +++ b/finished.md @@ -28,6 +28,6 @@ You've completed the Tessel Tutorial!
    - Prev: CLI Usage + Prev: GPIO
    diff --git a/usage.html b/gpio.html similarity index 77% rename from usage.html rename to gpio.html index 92b97d9..89a8b33 100644 --- a/usage.html +++ b/gpio.html @@ -3,6 +3,6 @@ --- {% capture include_install %} -{% include_relative usage.md %} +{% include_relative gpio.md %} {% endcapture %} {{ include_install | markdownify }} diff --git a/gpio.md b/gpio.md new file mode 100644 index 0000000..12bb2e6 --- /dev/null +++ b/gpio.md @@ -0,0 +1,74 @@ +{::options parse_block_html="true" /} + +
    +
    + +# Beyond Modules + +
    +
    + +[![](https://raw.githubusercontent.com/rwaldron/tessel-io/master/fritzing/tessel.png)](https://github.com/rwaldron/tessel-io/tree/master/fritzing) + +
    +
    + +Tessel's two module ports are not just for modules– they can also be used as flexible, simply [addressable GPIO](//tessel.io/docs/hardwareAPI) (general purpose input/output) pins. + +What does that mean? It means you're not limited to Tessel's ten-pin modules. In theory, you can connect nearly any electronic device or sensor to Tessel! + +### Community modules +
    +
    + +
    +
    + +For an experience nearly as easy as Tessel's ten-pin module experience, take a look at the [Community Modules](https://tessel.io/modules#third-party). + +These are hardware components for which members of the community have created npm libraries, documentation, and wiring information. + +For example: + +
    +
    + +
    +
    + +
    +
    + +
    +
    + +
    +
    + +
    +To see more community-created modules (or to add one you've made!) go to [tessel.io/modules](https://tessel.io/modules#third-party). + +_Note: we're still building out Tessel 2's firmware, so you might hit some bugs trying to use community modules. If you do, please report them! We're collecting status reports on community modules [here](https://github.com/tessel/hardware-modules/issues/5)._ + +### Making your own Modules + +If no one has made the module you want yet, you can be the first! There are a lot of cool components on [SparkFun](//sparkfun.com) and [Adafruit](//adafruit.com) that are fairly easy to connect to Tessel. + +In case you've never built anything with hardware before, we've put up an introduction at [tessel.io/diy](//tessel.io/diy) that should get you up and running. + +Share what you've made, and if you need help, [just ask](https://forums.tessel.io/c/community-modules). Happy inventing! + +
    +
    + +
    + +
    +
    + Prev: Modules +
    + +
    + Next: Finished +
    +
    diff --git a/tweet.md b/tweet.md index 16064cb..e521f12 100644 --- a/tweet.md +++ b/tweet.md @@ -89,7 +89,7 @@ Now run: Modules
    - Next: Usage + Next: Beyond modules
    diff --git a/usage.md b/usage.md deleted file mode 100644 index 42f2752..0000000 --- a/usage.md +++ /dev/null @@ -1,78 +0,0 @@ -{::options parse_block_html="true" /} - -
    -
    - -# Some useful commands... - -You can look at all the options of Tessel's CLI by running - -`t2 -h` - -Or go to the [Tessel 2 CLI docs](//tessel.io/docs/cli). Here are a few of the most useful ones: - -### `t2 run `` - -This command loads code into RAM on Tessel. When Tessel is reset (or the script ends with CTRL + C), Tessel loses the code. This command is useful for running code while developing, and is used throughout this tutorial. - -This command is shown in the [blinky example.](blinky.html) - -`t2 run blinky.js` - -{% highlight sh %} ->> Bundling directory ... ->> Deploying bundle ... ->> Running script ... ->> "I'm blinking! (Press CTRL + C to stop)" ->> "I'm blinking! (Press CTRL + C to stop)" ->> "I'm blinking! (Press CTRL + C to stop)" ->> ... -{% endhighlight %} - -### `t2 push ` - -This command saves code into flash memory on Tessel. This means that Tessel auto-runs this code when powered. The code will stay on here even if you restart Tessel. - -If you "tessel run" while you have code saved in Flash, the new code will run until the Tessel is reset, and then Tessel will switch back to the code from Flash. - -From your "tessel-code" directory, where you saved blinky.js, - -`t2 push blinky.js` - -{% highlight sh %} ->> Bundling directory ... ->> Deploying bundle ... ->> Running script ... ->> Finished deployment -{% endhighlight %} - -### `t2 erase` - -This command erases any JavaScript code saved to Tessel's flash memory. The firmware is left unchanged. If you push buggy code to Tessel, an erase can remove your code. - -Try unplugging and replugging in your Tessel after you have loaded the blinky code in Flash (tessel push). After a few seconds, you should see the LEDs start to blink. - -Now run: - -`t2 erase` - -{% highlight sh %} ->> Attempting to erase filesystem -{% endhighlight %} - -This will erase the blinky code from Tessel, and the LEDs will stop blinking. - -
    -
    - -
    - -
    -
    - Prev: Tweet -
    - -
    - Next: Finished! -
    -