Issue running LED test script

[ph0bos]

When running the following installation/test commands;

$ sudo npm install -g cylon-cli
$ cylon generate tessel my-teasel-project
$ cd my-teasel-project
$ npm install
$ tessel run blink.js

I'm consistently presented with the following output;

I, [2014-09-06T09:12:01.377Z] INFO -- : Initializing connections.
I, [2014-09-06T09:12:01.405Z] INFO -- : Initializing connection 'tessel'.
D, [2014-09-06T09:12:01.433Z] EBUG -- : Loading adaptor 'tessel'.
D, [2014-09-06T09:12:14.163Z] EBUG -- : Registering Tessel adaptor for Robot 34012
D, [2014-09-06T09:12:14.188Z] EBUG -- : Registering ambient-attx4 Driver for Robot 34012
D, [2014-09-06T09:12:14.240Z] EBUG -- : Registering accel-mma84 Driver for Robot 34012
D, [2014-09-06T09:12:14.292Z] EBUG -- : Registering audio-vs1053b Driver for Robot 34012
D, [2014-09-06T09:12:14.345Z] EBUG -- : Registering camera-vc0706 Driver for Robot 34012
D, [2014-09-06T09:12:14.397Z] EBUG -- : Registering climate-si7005 Driver for Robot 34012
D, [2014-09-06T09:12:14.449Z] EBUG -- : Registering gps-a2235h Driver for Robot 34012
D, [2014-09-06T09:12:14.501Z] EBUG -- : Registering servo-pca9685 Driver for Robot 34012
D, [2014-09-06T09:12:14.553Z] EBUG -- : Registering relay-mono Driver for Robot 34012
D, [2014-09-06T09:12:14.605Z] EBUG -- : Registering ir-attx4 Driver for Robot 34012
D, [2014-09-06T09:12:14.657Z] EBUG -- : Registering ble-ble113a Driver for Robot 34012
D, [2014-09-06T09:12:14.990Z] EBUG -- : Registering i2c BlinkM driver for Robot 34012
D, [2014-09-06T09:12:15.041Z] EBUG -- : Registering i2c HMC6352 driver for Robot 34012
D, [2014-09-06T09:12:15.092Z] EBUG -- : Registering i2c MPL115A2 driver for Robot 34012
D, [2014-09-06T09:12:15.143Z] EBUG -- : Registering i2c BMP180 driver for Robot 34012
D, [2014-09-06T09:12:15.194Z] EBUG -- : Registering i2c MPU6050 driver for Robot 34012
D, [2014-09-06T09:12:15.245Z] EBUG -- : Registering i2c LCD driver for Robot 34012
I, [2014-09-06T09:12:15.317Z] INFO -- : Initializing devices.
I, [2014-09-06T09:12:15.345Z] INFO -- : Initializing device 'led'.
D, [2014-09-06T09:12:15.378Z] EBUG -- : Loading driver 'led'.
I, [2014-09-06T09:12:15.464Z] INFO -- : Starting connections.
I, [2014-09-06T09:12:15.502Z] INFO -- : Connecting to 'tessel'.
D, [2014-09-06T09:12:15.528Z] EBUG -- : Connecting to Tessel 'tessel'...
I, [2014-09-06T09:12:15.553Z] INFO -- : Connecting to adaptor 'tessel'.
I, [2014-09-06T09:12:15.589Z] INFO -- : Starting devices.
I, [2014-09-06T09:12:15.626Z] INFO -- : Starting device 'led' on pin 1.
I, [2014-09-06T09:12:15.651Z] INFO -- : Driver led started.
I, [2014-09-06T09:12:15.689Z] INFO -- : Working.
/app/blink.js:8: attempt to call method 'toggle' (a nil value)

Tessel Versions

tessel version        
INFO v0.3.13

tessel version --board
TESSEL! Connected to <DEVICE_ID>
INFO Serial #: <SERIAL>
INFO Wifi Version: 1.28
INFO Firmware Commit: d378c4b
INFO Runtime Commit: a9151ad

[zankich]

@ph0bos Thank's for reporting the issue, I've been able to confirm this locally and am investigating it!

[zankich]

this appears to be an issue in the tessel runtime https://github.com/tessel/runtime/issues/487

[deadprogram]

Looks like we are blocked until @tessel team can fix a few runtime issues. :violin:

[zankich]

@ph0bos the tessel team as resolved our issues and cylon will now run on at least firmware v0.1.24

[zankich]

The cylon gpio and i2c drivers as well as the official tessel hardware modules will now work with at least cylon-tessel v0.9.0 and tessel firmware version v0.1.24.