Jessie wouldn't make much difference. The kernel version has a bit impact.
The location of cape manager and indexes of the device tree entries have
hard dependencies.

On Sun, Jan 10, 2016 at 11:58 AM Wally Bkg <[email protected]> wrote:

> That would be nice.
>
> I'm not familar with npm beyond the cut and paste commands I used
> following the node-red installation instructions.  So how do I use npm to
> update BoneScript?
>
> The 0.2.5 system seems to mostly work although the fade.js example totally
> fails throwing undefined errors updating PWM freq, value, & duty,
>
> The 0.2.4 system pretty much nothing works, even the simple blinkled.js
> totally fails as mentioned below.
>
> What are the odds of BoneScript working better with Jessie?  I'd prefer to
> have everything running Jessie.
>
>
>
> On Saturday, January 9, 2016 at 8:58:13 PM UTC-6, Jason Kridner wrote:
>
>> Seems we could switch it over to the native Debian package system rather
>> than npm.
>>
> On Sat, Jan 9, 2016 at 5:28 PM Wally Bkg <[email protected]> wrote:
>>
> I've a pair of Beaglebone Greens, one running "latest" from
>>> beagleboard.org image 2015-11-12 kernel 3.8.13-bone79, the other
>>> running what came loaded in the eMMC: 2015-03-01 kernel 3.8.13-bone71.1
>>>
>>> Both are "current" with apt-get update ; apt-get upgrade as of a day or
>>> two ago.  I'm having some BoneScript/Node-RED issues and noticed the
>>> 2015-11-12 image has BoneScript 0.2.5, whereas the 2015-03-01 has
>>> BoneScript 0.2.4
>>>
>>> Is BoneScript not part of the "normal" apt-get update/upgrade
>>> maintenance?
>>>
>>> I just did apt-get update/upgrade on the BoneScript 0.2.4 system before
>>> I post this message and I get:
>>> W: Size of file
>>> /var/lib/apt/lists/security.debian.org_dists_wheezy_updates_main_binary-armhf_Packages.gz
>>> is not what the server reported 400377 400405
>>> From the update, and the upgrade shows 5new packages, none of which
>>> appear to have anything to do with BoneScript.
>>>
>>>
>>> The first BBG (with BS 0.2.5) I wanted to setup with an 8GB SD card and
>>> "standardize" with my BBW and BBB running Jessie, but I burned the "latest"
>>> Wheezy image to its eMMC when I tried some BoneScript stuff to help out a
>>> friend and had issues, and got an answer here that BoneScript was not
>>> working for 4.1 kernels yet so I should use 3.8 series if I want BoneScript.
>>>
>>> I'm finding that most of the BoneScript examples have issues -- throwing
>>> apparently harmless error messages, or just plain not working and throwing
>>> apparently fatal error messages.  I'm beginning to doubt that BoneScript is
>>> a very useful starting point for a newbie (my friend).
>>>
>>> For instance the blinkled.js example at:
>>> http://192.168.7.2:3000/ide.html
>>> prints this in the examples/blinkled.js tab when I run it:
>>>
>>> debugger listening on port 15454
>>>
>>> /usr/local/lib/node_modules/bonescript/my.js:57
>>>             if(slot[0]) {
>>>                    ^
>>> TypeError: Cannot read property '0' of null
>>>     at Object.exports.load_dt
>>> (/usr/local/lib/node_modules/bonescript/my.js:57:20)
>>>     at Object.exports.create_dt
>>> (/usr/local/lib/node_modules/bonescript/my.js:123:33)
>>>     at Object.exports.setPinMode
>>> (/usr/local/lib/node_modules/bonescript/hw_capemgr.js:83:12)
>>>     at Object.f.pinMode
>>> (/usr/local/lib/node_modules/bonescript/index.js:160:15)
>>>     at Object.<anonymous> (/var/lib/cloud9/examples/blinkled.js:6:7)
>>>     at Module._compile (module.js:456:26)
>>>     at Object.Module._extensions..js (module.js:474:10)
>>>     at Module.load (module.js:356:32)
>>>     at Function.Module._load (module.js:312:12)
>>>     at Module.runMain [as _onTimeout] (module.js:497:10)
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to