Re: [beagleboard] mcasp pinmux settings

[evilwulfie]

Not much help
there is a file i have found  BB-BONE-AUDI-03-00A0.dts
that have other settings

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {

bone_audio_cape_audio_pins: pinmux_bone_audio_cape_audio_pins {
pinctrl-single,pins = <
0x1ac 0x20/* mcasp0_ahclkx, INPUT | MODE0 */
0x19c 0x22/* mcasp0_axr2, INPUT | MODE2 */
0x194 0x20/* mcasp0_fsx, INPUT | MODE0 */
0x198 0x08/* mcasp0_axr0, OUTPUT | MODE0 */
0x190 0x20/* mcasp0_aclkx, INPUT | MODE0 */
>;
};
};
};

seems closer but still backwards in my eye


On 4/28/2016 9:39 PM, William Hermans wrote:
> I really hate when gmail does that crap . . .
>
> pinctrl-single,pins = <
> 0x190 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
> mcasp0_aclkx.mcasp0_aclkx */
> 0x194 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
> mcasp0_fsx.mcasp0_fsx, INPUT */
> 0x198 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
> mcasp0_axr0.mcasp0_axr0 */
> 0x19c (*PIN_INPUT_PULLDOWN* | MUX_MODE2)/*
> mcasp0_ahclkr.mcasp0_axr2 */
> 0x1ac (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
> >;
>
> On Thu, Apr 28, 2016 at 9:38 PM, William Hermans  > wrote:
>
> pinctrl-single,pins = <
> 0x190 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_aclkx.mcasp0_aclkx */
> 0x194 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_fsx.mcasp0_fsx, INPUT */
> 0x198 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_axr0.mcasp0_axr0 */
> 0x19c (*PIN_INPUT*_PULLDOWN | MUX_MODE2)/*
> mcasp0_ahclkr.mcasp0_axr2 */
> 0x1ac (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
> >;
>
> On Thu, Apr 28, 2016 at 9:24 PM, evilwulfie  > wrote:
>
> Ok  I am slightly confused her on the pinmux signal directions.
>
> In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to
> inputs
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bone_audio_cape_audio_pins:
> pinmux_bone_audio_cape_audio_pins {
> pinctrl-single,pins = <
> 0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_aclkx.mcasp0_aclkx */
> 0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_fsx.mcasp0_fsx, INPUT */
> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_axr0.mcasp0_axr0 */
> 0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2)/*
> mcasp0_ahclkr.mcasp0_axr2 */
> 0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
> >;
> };
> };
> };
>
> Am i missing something here ? All pins should be outputs
> except the
> audio input on axr0.mcasp0 which should be an input.
>
> On the UARTS the signal directions are correct.
>
> Is there some black magic that i am missing ?
>
>
> ---
> This email has been checked for viruses by Avast antivirus
> software.
> https://www.avast.com/antivirus
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com.
> 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 beagleboard+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORqcCXzPcuMnNTJN%2By0pV9v%3DRxqAiK-M%2B_k-%3DAeV_6U2KA%40mail.gmail.com
> 

Re: [beagleboard] mcasp pinmux settings

[William Hermans]

I really hate when gmail does that crap . . .

pinctrl-single,pins = <
0x190 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
mcasp0_aclkx.mcasp0_aclkx */
0x194 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
mcasp0_fsx.mcasp0_fsx, INPUT */
0x198 (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
mcasp0_axr0.mcasp0_axr0 */
0x19c (*PIN_INPUT_PULLDOWN* | MUX_MODE2)/*
mcasp0_ahclkr.mcasp0_axr2 */
0x1ac (*PIN_INPUT_PULLDOWN* | MUX_MODE0)/*
MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
>;

On Thu, Apr 28, 2016 at 9:38 PM, William Hermans  wrote:

> pinctrl-single,pins = <
> 0x190 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_aclkx.mcasp0_aclkx */
> 0x194 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_fsx.mcasp0_fsx, INPUT */
> 0x198 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> mcasp0_axr0.mcasp0_axr0 */
> 0x19c (*PIN_INPUT*_PULLDOWN | MUX_MODE2)/*
> mcasp0_ahclkr.mcasp0_axr2 */
> 0x1ac (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
> >;
>
> On Thu, Apr 28, 2016 at 9:24 PM, evilwulfie  wrote:
>
>> Ok  I am slightly confused her on the pinmux signal directions.
>>
>> In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to inputs
>>
>> fragment@0 {
>> target = <&am33xx_pinmux>;
>> __overlay__ {
>> bone_audio_cape_audio_pins: pinmux_bone_audio_cape_audio_pins
>> {
>> pinctrl-single,pins = <
>> 0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
>> mcasp0_aclkx.mcasp0_aclkx */
>> 0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
>> mcasp0_fsx.mcasp0_fsx, INPUT */
>> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
>> mcasp0_axr0.mcasp0_axr0 */
>> 0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2)/*
>> mcasp0_ahclkr.mcasp0_axr2 */
>> 0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
>> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
>> >;
>> };
>> };
>> };
>>
>> Am i missing something here ? All pins should be outputs except the
>> audio input on axr0.mcasp0 which should be an input.
>>
>> On the UARTS the signal directions are correct.
>>
>> Is there some black magic that i am missing ?
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>> --
>> 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 beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com
>> .
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORqcCXzPcuMnNTJN%2By0pV9v%3DRxqAiK-M%2B_k-%3DAeV_6U2KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] mcasp pinmux settings

[William Hermans]

 pinctrl-single,pins = <
0x190 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
mcasp0_aclkx.mcasp0_aclkx */
0x194 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
mcasp0_fsx.mcasp0_fsx, INPUT */
0x198 (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
mcasp0_axr0.mcasp0_axr0 */
0x19c (*PIN_INPUT*_PULLDOWN | MUX_MODE2)/*
mcasp0_ahclkr.mcasp0_axr2 */
0x1ac (*PIN_INPUT*_PULLDOWN | MUX_MODE0)/*
MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
>;

On Thu, Apr 28, 2016 at 9:24 PM, evilwulfie  wrote:

> Ok  I am slightly confused her on the pinmux signal directions.
>
> In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to inputs
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bone_audio_cape_audio_pins: pinmux_bone_audio_cape_audio_pins {
> pinctrl-single,pins = <
> 0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_aclkx.mcasp0_aclkx */
> 0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_fsx.mcasp0_fsx, INPUT */
> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> mcasp0_axr0.mcasp0_axr0 */
> 0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2)/*
> mcasp0_ahclkr.mcasp0_axr2 */
> 0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
> >;
> };
> };
> };
>
> Am i missing something here ? All pins should be outputs except the
> audio input on axr0.mcasp0 which should be an input.
>
> On the UARTS the signal directions are correct.
>
> Is there some black magic that i am missing ?
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com
> .
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORoRjgXeS50Z%2BBDRb2o2G7Ubd9E5ta_yY0quX%2BQJVpy3hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] mcasp pinmux settings

[evilwulfie]

Ok  I am slightly confused her on the pinmux signal directions.

In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to inputs

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
bone_audio_cape_audio_pins: pinmux_bone_audio_cape_audio_pins {
pinctrl-single,pins = <
0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
mcasp0_aclkx.mcasp0_aclkx */
0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
mcasp0_fsx.mcasp0_fsx, INPUT */
0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
mcasp0_axr0.mcasp0_axr0 */
0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2)/*
mcasp0_ahclkr.mcasp0_axr2 */
0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0)/*
MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */
>;
};
};
};

Am i missing something here ? All pins should be outputs except the
audio input on axr0.mcasp0 which should be an input.

On the UARTS the signal directions are correct.

Is there some black magic that i am missing ?


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 1-Wire

[TJF]

Am Donnerstag, 28. April 2016 19:40:19 UTC+2 schrieb hoerting...@gmx.at:
>
> Hello!
>
> *1. Max sensors*
> When I try:
> echo 20 > w1_master_max_slave_count
>
> I get:
> bash: w1_master_max_slave_count: Permission denied
> (of course I´m root
>
 
sudo su
echo 20 > w1_master_max_slave_count
exit
 

> *2. Polling time*
> Well, 19sec in total is OK! It are just room temperatur and this must not 
> update so fast. But can I add more as 10 sensors because of Point 3?
>
> *3. max cable length*
> I mean the total cable length of the 1-Wire bus ... when I connect in 
> Daisy-Chain I have around 50m to the last 1-Wire sensor.
>

Of course, it depends on the electro-magnetic pollution in your area. Ie. 
frequency converters with heavy loads are crititcal.

I read about networks with a weight of 200 m using additional w1 drivrer 
chips with 5V power supply. But I didn't test it.

It's recommended to avoid Daisy-Chain configuration. Instead think about a 
tree structure: one root connected to the master and several terminals with 
short wiring to the slaves or further terminals. More than 20 sensors 
shouldn't be an issue when the radius is small (< 20 m, when I tried a 
radius of 25 m in my system, I had to reduce the pullup from 4k7 to 3k3.)

BR

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/00d85114-addc-4423-abcf-68d1b3b8426e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Adafruit BBIO Python library

[Peter Lawler]

Hi folks,
Just a quick note to let you know I've spent some time tracking down the 
differences between 3.8 and later versions for the Adafruit BBIO Python 
library.


I first noted this post 
https://forums.adafruit.com/viewtopic.php?f=49&t=91903&p=468811#p469266 
which discusses that the 3.8 Adafruit library won't work on 4.1, and 
that there were some fixes out in the wild so to speak but that Adafruit 
weren't in a rush to get them happening.


So I took a look at one of the solutions, by grizmio, and it Just Worked 
for me.


I've now shoved a bunch of ifdef's around the changes in the C code that 
grizmio made, so I am *hoping* it's simultaneously 3.8 and 4.1 friendly.


I don't have a spare 3.8 machine at hand right now, but if there's 
anyone out there who could try it out and see what happens, it'd be 
appreciated. All I know is bad C and that it compiles. Please don't 
shoot me for doing things wrong ;)



https://github.com/PeteLawler/adafruit-beaglebone-io-python

Regards,

Pete.

--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5722C8A7.8070001%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is bonescript compatible with node version >0.10.x ?

[Wally Bkg]

On Wednesday, April 13, 2016 at 10:08:09 AM UTC-5, RobertCNelson wrote:

>
> On Tue, Apr 12, 2016 at 8:53 PM, Wally Bkg  > wrote:
>
>> Any suggestions on getting node-red-node-beaglebone to work with 
>> bonescript-0.5-beta3?  I'm thrilled that all the bonescript examples in 
>> cloud9 IDE now work (analogwrite, analogRead, digitalRead, digitalWrite, & 
>> attachInterrupt) without errors or spurious error messages, but the 
>> node-red-node-beaglebone npm install fails. 
>>
>
> sudo su
> cd /root/.node-red/
> npm install --unsafe-perm --progress=false node-red-node-beaglebone
>
> #issues:
> i2c is broken...
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

I just did this npm install after apt-get update and apt-get upgrade to be 
sure I had the latest everything.

It appears to have installed, with the same i2c errors (can live without 
i2c) you showed, but the "beaglebone" nodes still don't show up after a 
reboot.
What am I missing?

The "your second flow" UK powergrid example works fine, I just don't have 
the node-red-node-beaglebone nodes showing up in the left side pane.

 

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/95a106c9-9693-4f65-a9b4-4b17bb747284%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is bonescript compatible with node version >0.10.x ?

[William Hermans]

>
> *Playing with some code snippets I've found on-line, I'm starting to
> develop an appreciation for nodejs. . .*
>

Nodejs is actually a really good development platform. It's really fast,
and it being an event driven, object oriented platform. Thanks to
Javascript. It is well suited for many tasks on any hardware platform.

The only real downsides is that Nodejs can have high latency at times,
depending. Nodejs being based on javascript brings all the bad that is
javascript, into Nodejs( there is still a lot of good too ). Then so many
other things that it is hard to mention it all. Such as NPM, poor coding
standards among those who demonstrate the language( Function chaining
should be a hang-able offense - for starters ), and many others.

On Thu, Apr 28, 2016 at 11:10 AM, Wally Bkg  wrote:

> Thanks for such a great answer and concise history of the issues!
> At least we're newer than Raspberry Pi2 Jessie that I installed yesterday
> which is still at 0.10.29  :)
>
> Playing with some code snippets I've found on-line, I'm starting to
> develop an appreciation for nodejs and think it'd be a way better choice
> for my newbie friend than python.  Nodejs is very amenable to
> "cut-and-paste" programming  where one finds an example that does something
> sorta like you want and then learn enough to modify it for your needs --
> very newbie friendly.  Node-red graphical "flow" programming is even more
> newbie friendly when starting with an idea and a blank page.
>
>
> On Thursday, April 28, 2016 at 12:30:08 PM UTC-5, RobertCNelson wrote:
>
>>
>>
>> On Thu, Apr 28, 2016 at 12:22 PM, Wally Bkg  wrote:
>>
>>> Are the nodejs and npm for ARM versions numbered differently?  or are
>>> they really this far behind the x86 versions?
>>>
>>> on Ubuntu 32-bit 16.04:
>>> nodejs -v
>>> v4.2.6
>>>
>>> From what I gather, I'm new at the nodejs stuff, 4.4.3 is the "current"
>>> stable LTS version.  I've no appreciation of the consequences of these
>>> version differences beyond some feature used in sample code not being
>>> available in the version I'm trying it on :(
>>>
>>> npm -v
>>> 3.5.2
>>>
>>
>> For awhile 'nodejs' was stagnant (0.8.x/0.10.x era) then it got forked
>> around (0.12.x) and io.js came out, then io.js merged with nodejs... yada
>> yada things are moving fast now...
>>
>> https://github.com/nodejs/LTS#lts_schedule
>>
>> ReleaseLTS StartMaintenance StartLTS End
>> v0.10 (current) 2015-10-01 2016-10-01
>> v0.12 (current) 2016-04-01 2017-04-01
>> v4.2.0 2015-10-01 2017-04-01 2018-04-01
>> v.Next 2016-10-01 2018-04-01
>> For beagleboard.org we've moved from 0.10.x (which we shipped in wheezy)
>> to 0.12.x in jessie just in the last month or to.  We were unable to do the
>> full jump to v4.x at the time..
>>
>> By mid summer (2016) i'd like us to be getting things read to move to
>> 'v4.x'  as 'stretch' will ship with that  (unless they jump to the new v6.x
>> lts released this week)..
>>
>> While "npm" is a separate project bundled with nodejs..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/3a11f217-2bf8-4236-baac-c87914fbf4d9%40googlegroups.com
> 
> .
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORotCP6Fp4WCiC1LMcdMnmD0x1_SujnV06tDbJapQ6sYNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is bonescript compatible with node version >0.10.x ?

[Wally Bkg]

Thanks for such a great answer and concise history of the issues!
At least we're newer than Raspberry Pi2 Jessie that I installed yesterday 
which is still at 0.10.29  :)

Playing with some code snippets I've found on-line, I'm starting to develop 
an appreciation for nodejs and think it'd be a way better choice for my 
newbie friend than python.  Nodejs is very amenable to "cut-and-paste" 
programming  where one finds an example that does something sorta like you 
want and then learn enough to modify it for your needs -- very newbie 
friendly.  Node-red graphical "flow" programming is even more newbie 
friendly when starting with an idea and a blank page.


On Thursday, April 28, 2016 at 12:30:08 PM UTC-5, RobertCNelson wrote:
>
>
>
> On Thu, Apr 28, 2016 at 12:22 PM, Wally Bkg  > wrote:
>
>> Are the nodejs and npm for ARM versions numbered differently?  or are 
>> they really this far behind the x86 versions?
>>
>> on Ubuntu 32-bit 16.04:
>> nodejs -v
>> v4.2.6
>>
>> From what I gather, I'm new at the nodejs stuff, 4.4.3 is the "current" 
>> stable LTS version.  I've no appreciation of the consequences of these 
>> version differences beyond some feature used in sample code not being 
>> available in the version I'm trying it on :(
>>
>> npm -v
>> 3.5.2
>>
>
> For awhile 'nodejs' was stagnant (0.8.x/0.10.x era) then it got forked 
> around (0.12.x) and io.js came out, then io.js merged with nodejs... yada 
> yada things are moving fast now...
>
> https://github.com/nodejs/LTS#lts_schedule
>
> ReleaseLTS StartMaintenance StartLTS End
> v0.10 (current) 2015-10-01 2016-10-01
> v0.12 (current) 2016-04-01 2017-04-01
> v4.2.0 2015-10-01 2017-04-01 2018-04-01
> v.Next 2016-10-01 2018-04-01
> For beagleboard.org we've moved from 0.10.x (which we shipped in wheezy) 
> to 0.12.x in jessie just in the last month or to.  We were unable to do the 
> full jump to v4.x at the time..
>
> By mid summer (2016) i'd like us to be getting things read to move to 
> 'v4.x'  as 'stretch' will ship with that  (unless they jump to the new v6.x 
> lts released this week)..
>
> While "npm" is a separate project bundled with nodejs..
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3a11f217-2bf8-4236-baac-c87914fbf4d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: 1-Wire

[evilwulfie]

50m is rather pushing the max way past recomended

https://www.maximintegrated.com/en/app-notes/index.mvp/id/148

and thats using twisted pair ethernet


On 4/28/2016 8:36 AM, hoerting.busin...@gmx.at wrote:
> Hello!
>
> *1. Max sensors*
> When I try:
> |
> echo 20>w1_master_max_slave_count
> |
>
> I get:
> |
> bash:w1_master_max_slave_count:Permissiondenied
> |
> (of course I´m root)
>
> *2. Polling time*
> Well, 19sec in total is OK! It are just room temperatur and this must
> not update so fast. But can I add more as 10 sensors because of Point 3?
>
> *3. max cable length*
> I mean the total cable length of the 1-Wire bus ... when I connect in
> Daisy-Chain I have around 50m to the last 1-Wire sensor.
>
> -- 
> 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 beagleboard+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/78193f8e-87c7-4350-aab7-917a30f08df3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/49579175-4642-b7a5-4180-d35ce56fabcc%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 1-Wire

[hoerting . business]

Hello!

*1. Max sensors*
When I try:
echo 20 > w1_master_max_slave_count

I get:
bash: w1_master_max_slave_count: Permission denied
(of course I´m root)

*2. Polling time*
Well, 19sec in total is OK! It are just room temperatur and this must not 
update so fast. But can I add more as 10 sensors because of Point 3?

*3. max cable length*
I mean the total cable length of the 1-Wire bus ... when I connect in 
Daisy-Chain I have around 50m to the last 1-Wire sensor.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/78193f8e-87c7-4350-aab7-917a30f08df3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Connecting USB device into GPIO ?

[Wally Bkg]

Any reason not to use a powered USB hub?  It could probably power the BBG 
as well.

On Thursday, April 21, 2016 at 3:36:43 PM UTC-5, Ded Sec wrote:
>
> As topic leads, can a USB device be hooked into GPIO's?
> I need Wifi and BLE devices in BBG but dues one USB  its one or other. So 
> since BLE uses less power i wonder if im able to connect BLE dongle into 
> GPIO's instead ?
> I would guess this is question for both hardware and software topics.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ee313fe4-2ac1-432b-b887-aaa245bb7efe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] rtl8192cu always rfkilled on Debian Jessie (systemd?)

[Robert Nelson]

On Thu, Apr 28, 2016 at 12:30 PM, Andrew Kirch  wrote:

> All,
>
> I have been trying for weeks in vain to get rfkill to unblock (soft) (and
> leave unblocked) wlan0, an rtl8192cu.
>
> relevant software versions:
> systemd   215-17+deb8u4rcnee1~bpo80+20160313+1
> rfkill0.5-1
>
> root@beaglebone:/var/lib/systemd/rfkill# uname -a
> Linux beaglebone 4.1.15-ti-rt-r40 #1 SMP PREEMPT RT Thu Jan 7 23:32:08 UTC
> 2016 armv7l GNU/Linux
>
> I've tried systemd's boot time parameter systemd.restore_state=1, and
> modified
> /var/lib/systemd/rfkill/platform-musb-hdrc.1.auto-usb-0:1:1.0:phy0, with
> both a 0, and a 1 in the file.  Regardless of the contents
> of platform-musb-hdrc.1.auto-usb-0:1:1.0:phy0, wlan0 was softblocked after
> systemd was through.
>
> Examining kernel-parameters.txt, I next went for: rfkill.default_state=1
> rfkill.master_switch_mode=0
> wlan0 was still soft-blocked
>
> I next added a pre-up line, "pre-up rfkill unblock wifi", to
> /etc/network/interfaces, which brought the interface up, and then rfkill
> shut it down ~7 seconds later, and soft-blocked it.
>
> I would greatly appreciate any help you guys might have in getting rfkill
> to enable wifi on boot.  There was a thread back in December of 2015
> , which
> recommended network-manager, but I prefer connmand, and as rcn-ee pointed
> out in that thread, there are issues with network manager, and the ethernet
> port.
>

been fighting connman with this on bluetooth... Make sure connman settings
under WiFi has "Enable=true".  i had been looking under rfkill/systemd the
whole time..

/var/lib/connman/settings

[WiFi]
Enable=true

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYj9pK%3DNdZVxQ30422jkE_VMTLrNNje1hykxQENwAX6mFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is bonescript compatible with node version >0.10.x ?

[Robert Nelson]

On Thu, Apr 28, 2016 at 12:22 PM, Wally Bkg  wrote:

> Are the nodejs and npm for ARM versions numbered differently?  or are they
> really this far behind the x86 versions?
>
> on Ubuntu 32-bit 16.04:
> nodejs -v
> v4.2.6
>
> From what I gather, I'm new at the nodejs stuff, 4.4.3 is the "current"
> stable LTS version.  I've no appreciation of the consequences of these
> version differences beyond some feature used in sample code not being
> available in the version I'm trying it on :(
>
> npm -v
> 3.5.2
>

For awhile 'nodejs' was stagnant (0.8.x/0.10.x era) then it got forked
around (0.12.x) and io.js came out, then io.js merged with nodejs... yada
yada things are moving fast now...

https://github.com/nodejs/LTS#lts_schedule

ReleaseLTS StartMaintenance StartLTS End
v0.10 (current) 2015-10-01 2016-10-01
v0.12 (current) 2016-04-01 2017-04-01
v4.2.0 2015-10-01 2017-04-01 2018-04-01
v.Next 2016-10-01 2018-04-01
For beagleboard.org we've moved from 0.10.x (which we shipped in wheezy) to
0.12.x in jessie just in the last month or to.  We were unable to do the
full jump to v4.x at the time..

By mid summer (2016) i'd like us to be getting things read to move to
'v4.x'  as 'stretch' will ship with that  (unless they jump to the new v6.x
lts released this week)..

While "npm" is a separate project bundled with nodejs..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYisXLA94GwDk9QSMKs8o%3DD9NGDJaSvSf6qT0%2B-X5uGzqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] rtl8192cu always rfkilled on Debian Jessie (systemd?)

[Andrew Kirch]

All,

I have been trying for weeks in vain to get rfkill to unblock (soft) (and 
leave unblocked) wlan0, an rtl8192cu.

relevant software versions:
systemd   215-17+deb8u4rcnee1~bpo80+20160313+1
rfkill0.5-1 

root@beaglebone:/var/lib/systemd/rfkill# uname -a
Linux beaglebone 4.1.15-ti-rt-r40 #1 SMP PREEMPT RT Thu Jan 7 23:32:08 UTC 
2016 armv7l GNU/Linux

I've tried systemd's boot time parameter systemd.restore_state=1, and 
modified 
/var/lib/systemd/rfkill/platform-musb-hdrc.1.auto-usb-0:1:1.0:phy0, with 
both a 0, and a 1 in the file.  Regardless of the contents 
of platform-musb-hdrc.1.auto-usb-0:1:1.0:phy0, wlan0 was softblocked after 
systemd was through.

Examining kernel-parameters.txt, I next went for: rfkill.default_state=1 
rfkill.master_switch_mode=0
wlan0 was still soft-blocked

I next added a pre-up line, "pre-up rfkill unblock wifi", to 
/etc/network/interfaces, which brought the interface up, and then rfkill 
shut it down ~7 seconds later, and soft-blocked it. 

I would greatly appreciate any help you guys might have in getting rfkill 
to enable wifi on boot.  There was a thread back in December of 2015 
, which 
recommended network-manager, but I prefer connmand, and as rcn-ee pointed 
out in that thread, there are issues with network manager, and the ethernet 
port.

Andrew



-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9fa83808-9143-47e5-9685-64aa852be4c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is bonescript compatible with node version >0.10.x ?

[Wally Bkg]

Are the nodejs and npm for ARM versions numbered differently?  or are they 
really this far behind the x86 versions?

on Ubuntu 32-bit 16.04:
nodejs -v
v4.2.6

>From what I gather, I'm new at the nodejs stuff, 4.4.3 is the "current" 
stable LTS version.  I've no appreciation of the consequences of these 
version differences beyond some feature used in sample code not being 
available in the version I'm trying it on :(

npm -v
3.5.2

On Wednesday, April 27, 2016 at 5:12:51 PM UTC-5, RobertCNelson wrote:
>
>
>
> On Wed, Apr 27, 2016 at 4:50 PM, > wrote:
>
>> For me bonescript only works with node version 0.10!
>>
>>  root@arm:~# node -v
>>  v0.10.32
>>  root@arm:~# npm -v
>>  1.4.28
>>
>
>
> v0.12.x support is in the 0.5.0 branch of bonescript.
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/10bdd76e-e4d1-40b2-b52d-03101e62bf72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Fast Pin Toggling Using MMAP

[Micka]

use the PRU it's faster ^^

Le jeu. 28 avr. 2016 à 17:55, William Hermans  a écrit :

> *1) I could not find START_ADDR, END_ADDR, OE, SETDATAOUT, CLEARDATAOUT
>> from technical manual. Where can I find them for the pins from P9_11 ...
>> upto P9_18*
>>
>
> Setdataout, and cleardataout are in the TRM. Pages 4093-4094.
>
> *2) what is the explanation of the following statement? What does it do?*
>>
>> *define PIN ( 1<<28) *
>>
>
>
>
> *If you do not know what this does, then you need to read, and understand
> how bit manipulation works in C. This specifically is what is known as a
> bit shift.*
>
>> *3) **I am going to use it for SPI communication, so since the timing is
>> critical, and Linux is not RT, there is a possibility that some other
>> interrupts may damage my communaction. Do you think that it would be a
>> problem? If yes, what precautions can I get?*
>>
>
> Bad idea. You have SPI modules on the board already. Why would you not use
> them ? Also, if you know Linux is not real time( enough ) then why would
> you use Linux ?
>
> On Thu, Apr 28, 2016 at 8:02 AM, TJF  wrote:
>
>> Hi Frank!
>>
>> Your example controls one GPIO subsystem. The pins P9_11 to P9_18 are
>> connected to two GPIO subsystems. That's why you cannot control all pins at
>> 2.6 MHz. You'll have to find a set of pins connected to a single GPIO
>> subsystem (either GPIO0 or GPIO1).
>>
>> As John mentioned, this is stuff for the PRUSS.
>>
>> BR
>>
>> --
>> 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 beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/4fa09157-deff-49cf-b899-ed775ed2562b%40googlegroups.com
>> 
>> .
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORojmnsJo31UbR7C7RnaoCrGKFGP3a9R%3DKBd1Cy5s6J_iQ%40mail.gmail.com
> 
> .
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtmZ6HpMJ1Sf%2Bgug6uOddb%2BdbwCemnkJaNHHpoggcTFjVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Fast Pin Toggling Using MMAP

[William Hermans]

> *1) I could not find START_ADDR, END_ADDR, OE, SETDATAOUT, CLEARDATAOUT
> from technical manual. Where can I find them for the pins from P9_11 ...
> upto P9_18*
>

Setdataout, and cleardataout are in the TRM. Pages 4093-4094.

*2) what is the explanation of the following statement? What does it do?*
>
> *define PIN ( 1<<28) *
>



*If you do not know what this does, then you need to read, and understand
how bit manipulation works in C. This specifically is what is known as a
bit shift.*
>
> *3) **I am going to use it for SPI communication, so since the timing is
> critical, and Linux is not RT, there is a possibility that some other
> interrupts may damage my communaction. Do you think that it would be a
> problem? If yes, what precautions can I get?*
>

Bad idea. You have SPI modules on the board already. Why would you not use
them ? Also, if you know Linux is not real time( enough ) then why would
you use Linux ?

On Thu, Apr 28, 2016 at 8:02 AM, TJF  wrote:

> Hi Frank!
>
> Your example controls one GPIO subsystem. The pins P9_11 to P9_18 are
> connected to two GPIO subsystems. That's why you cannot control all pins at
> 2.6 MHz. You'll have to find a set of pins connected to a single GPIO
> subsystem (either GPIO0 or GPIO1).
>
> As John mentioned, this is stuff for the PRUSS.
>
> BR
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/4fa09157-deff-49cf-b899-ed775ed2562b%40googlegroups.com
> 
> .
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORojmnsJo31UbR7C7RnaoCrGKFGP3a9R%3DKBd1Cy5s6J_iQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 1-Wire

[TJF]

Hi!

Am Donnerstag, 28. April 2016 15:52:40 UTC+2 schrieb hoerting...@gmx.at:
>
> Hello,
>
> I want to use 1-wire DS18B20+ sensors with the BBB.
> On my breadcrump is work with 2 sensors.
>
> My question:
> with:
> cat w1_bus_master1/w1_master_max_slave_count
> he show me max 10 sensors ... why?
>

AFAIR this is a default value in the kernel driver. You can echo a larger 
number in order to override it.
 

> I need around 25 sensors with a wire length of 50m.
>
> Is this possible?
>

> I use all 3 wires (GND, VCC (5V) and Data)
>

When you sample 25 sensors by the kernel driver, each conversation takes 
about 750 ms, in total ~19 seconds. So your process must not have high 
temperatur gradients. You can speed up conversations by broadcast 
triggering (~1 second in total). This isn't supported by the kernel driver.

What do you mean by cable length? The weight or the radius?

>
>- The radius of a network is the wire distance from the master end to 
>the most distant slave.
>- The weight of a network is the total amount of connected wire in the 
>network.
>
> In a thermal solar system I use eight sensors with a bus radius of 15 m 
and a weight of 45 m (BBB GPIO, no additional hardware, simple cable and 
RJ12 connectors).

BR

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5808ab70-1a32-4d85-a4af-444c96b23540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Fast Pin Toggling Using MMAP

[TJF]

Hi Frank!

Your example controls one GPIO subsystem. The pins P9_11 to P9_18 are 
connected to two GPIO subsystems. That's why you cannot control all pins at 
2.6 MHz. You'll have to find a set of pins connected to a single GPIO 
subsystem (either GPIO0 or GPIO1).

As John mentioned, this is stuff for the PRUSS.

BR

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4fa09157-deff-49cf-b899-ed775ed2562b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] 1-Wire

[hoerting . business]

Hello,

I want to use 1-wire DS18B20+ sensors with the BBB.
On my breadcrump is work with 2 sensors.

My question:
with:
cat w1_bus_master1/w1_master_max_slave_count

he show me max 10 sensors ... why?

I need around 25 sensors with a wire length of 50m.

Is this possible?

I use all 3 wires (GND, VCC (5V) and Data)

Thank you!

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cf1a76da-fb70-469f-9956-9d73be0f6002%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 problem with DE/!RE

[Robert Nelson]

On Thu, Apr 28, 2016 at 1:56 AM, florian.feldbauer85 via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Hey,
>
> I had a look at the kernel source at github. From the code
> I would say the 8250 driver supports RS485. Only the
> "rs485-rts-active-high" flag from the device tree overlay
> seems not to be supported. But the same setting can be done via the struct
> serial_rs485 from user space.
>
> Also RS485 seems to be working to a limited point.
> Again: The only problem is receiving messages, which seems for what ever
> reason to be limited to 49 bytes.
> If my kernel is not supporting RS485 I would expect that either sending or
> receiving is not working at all.
> But from all the Pictures I linked in my previous mails, you can see, that
> the 8250 driver is switching the
> RTS signal with the correct polarity.
>
> Can someone point to to the kernel source for the kernel I am using
> (4.4.6-ti-r15)?
>


Grab https://github.com/RobertCNelson/yakbuild  follow the readme..

For 4.4.6-ti-r15, select:

toolchain="gcc_linaro_gnueabihf_5"
kernel_tag="4.4.6-ti-r15"

source:
https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.4.6-ti-r15

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYg%3DS%3DRkP3akybDx9zJwC3r%3DQ35_99tnz%3DeaL_dVrsszRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: bare metal on the BBB

[arniejayremez]

You obviously have not tried starterware..dd

On Friday, January 29, 2016 at 3:56:25 PM UTC+2, Karl Karpfen wrote:
>
> OK...but why inventing the wheel again? 
> 
>
> Am Sonntag, 24. Januar 2016 13:01:06 UTC+1 schrieb dd:
>>
>> Hi all.  I am bringing up a bare metal system on the beaglebone black and 
>> giving it away!  So if you want to have some fun, while learning alot about 
>> this ARM core, get involved.  The drivers are in Assembly (easy once you 
>> get the hang of it) with the main program in C.  All the build files are 
>> there, so you won't waste months trying to compile/load/run the dang 
>> thing.  I do not use an IDE, just use Notepad++ and GNUwin32 'make' from a 
>> DOS command line.  
>> Feel free to take whatever drivers you need for your project/hackjob: 
>>  UART, I2C, MMC, IRQ, GPIO, PWM, RTC.  
>> So now you can build a FAST and ROBUST standalone control system. 
>> Stack/interrupt setup and the loadscript is handy.  Getting an image up 
>> was a BITCH!.  
>> I am now working on ethernet.  Then the beast will be live on the 
>> internet!  
>>
>> Check it out at 
>> www.baremetal.tech   and   ww.github.com/ddlawrence
>>
>> I could sure use some help.  It is fun, really!  No more bugs! (except 
>> your own of course)
>>
>> hack on..dd
>>
>>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8f79e8fe-913e-455c-8fe4-38fccba1b1b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 problem with DE/!RE

[florian.feldbauer85 via BeagleBoard]

Hey,

I had a look at the kernel source at github. From the code
I would say the 8250 driver supports RS485. Only the 
"rs485-rts-active-high" flag from the device tree overlay
seems not to be supported. But the same setting can be done via the struct 
serial_rs485 from user space.

Also RS485 seems to be working to a limited point.
Again: The only problem is receiving messages, which seems for what ever 
reason to be limited to 49 bytes.
If my kernel is not supporting RS485 I would expect that either sending or 
receiving is not working at all.
But from all the Pictures I linked in my previous mails, you can see, that 
the 8250 driver is switching the
RTS signal with the correct polarity.

Can someone point to to the kernel source for the kernel I am using 
(4.4.6-ti-r15)?
At least looking at the releases/tags in the repo at github this version is 
not listed...
I'd like to have a look at the exact same source which is currently running 
on my setup,
to see if there is some bug or missing support in the kernel...

Cheers
Florian


Am Mittwoch, 27. April 2016 03:05:27 UTC+2 schrieb Peter Hurley:
>
> On 04/26/2016 12:07 AM, florian.feldbauer85 via BeagleBoard wrote: 
> > @Alex: I recommend, you read my mail ;-) 
>
> I suggest you re-read his email again where he tells you that 
> RS485 is unsupported by your kernel configuration. 
>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/14dcf94b-bfda-4fb5-a09d-b1b6078f7762%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone black emmc reg

[er . pankaj6878]

HI can anybody tell me , How we can read and write on a particular address 
of eMMC card in BBB?

On Wednesday, February 24, 2016 at 7:45:51 PM UTC+5:30, 
sanal.sa...@gmail.com wrote:
>
>
> Hi all,
>
>  
>
> I am working on beaglebone black board.
>
> I am new to this firm. build yocto image for beagle bon black board by 
> referring the below document 
>
> http://www.embarcados.com.br/beaglebone-black-yocto/ 
> 
>
>  
>
> What is my problem I need to flash this image to EMMC  how can I do that ?
>
> How can flash the image to EMMC?
>
> If beagle bone black board EMMC have any specialty , please help me to 
> solve this issue.
>
>
> Regards 
> Sachu
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/248e2a17-386b-4261-bd3c-142a770f9d4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 problem with DE/!RE

['Florian Feldbauer' via BeagleBoard]

On 04/28/2016 02:21 PM, Florian Feldbauer wrote:



On 04/28/2016 01:36 PM, Taceant Omnes wrote:

On 26 April 2016 at 08:07, florian.feldbauer85 via BeagleBoard
 wrote:


I did some further tests.
Actually none of the screens from my scope looks like I would 
expect it...


Picture 1 shows the result, if I try to read something on the bus 
with a 14s

timeout (nothing was sended on the bus...)
Pic1
Picture 2 shows the same, but this time there were messages send 
over the
bus. After 49 bytes, the beagle bone toggles the DE/!RE gpio to 
high for
unknown reasons (the test program is still reading from the UART 
interface)

Pic2
Picture 3 shows the test, where the BeagleBone is sending
Pic3

Your scope picture #3 does appear to show data being sent, however you
seem to say that your picture #2 portrays a test in which you received
49 bytes, however I don't see any sign of data being received in that
picture. Maybe I am missing something.

in all 4 picture from my 2nd post, channel 4 (green) shows one of
the two data lines of the bus.
Looking at #2 one can see, that this signal is starting toggling 
shortly before
the DE/RE signal goes high. That's the 49 bytes I receive. After that 
the data line
is still toggling araound but no longer between 0 and 1 but something 
in between,
because now, there are two devices sending on the bus. One is still 
the PC which
sends random data, the other one is the BeagleBone sending a constant 
0...

(TX and DE/RE are constant high)



I am not an expert in these things, but my current understanding is
that what the 485 driver provides extra to what the UART driver does
is the automatic switch of the driver enable pin. One test I would
suggest, a test I have done myself, is to send and receive data with
485 using the UART driver. In this case the DE/RE needs to be set
manually. I do it using echo to  /sys/class/gpio. Once that is working
well you could start test usinging the 485 driver. You should be able
to use your existing rs485_test.c program for that.


@Alex: I recommend, you read my mail ;-)
I did not look into the kernel source nor am I sure which driver is 
used in my Setup,

but the problem is not the "rs485-rts-active-high" flag

As Micka and Alex said the 4.1 and 4.4 driver do not have 485 support
enabled. Per an email by Robert you need to enable the OMAP serial
kernel configuration option and rebuild the kernel.

I'm still a bit puzzled how "rs485 is not supported" looks like...
For me, being able to send and receiving data is quiet the
contrary of "not supported".
Where can I find the sources of the kernel used in the 
debian-jessie-console 8.4 image
from April 07 in order to rebuild it? (I prefer changing as less as 
possible, thus I'd like

to use the exact same kernel source tree as it is now)

Just found the link to Roberts script-repo at github..
I will rebuild the kernel with the OMAP driver and test the RS485 
interface again...


  Florian


Best regards,
Florian






--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/57220673.3020700%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Fast Pin Toggling Using MMAP

[John Syne]

> On Apr 28, 2016, at 4:46 AM, frank brewer  wrote:
> 
> 
> I just noticed the faster way of toggling pins by using mmap, and after 
> trying chiragnagpal's example, I could achieve 2.6MHz. 
> 
> 
> 
> Example was for 1 pin only, now I want to use 8 pins, so I edited .dtc file 
> as following:
> 
> /*
> * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Purpose License Version 2 as
> * published by the Free Software Foundation
> *
> * Original from: 
> github.com/jadonk/validation-scripts/blob/master/test-capemgr/
> *
> * Modified by Derek Molloy for the example on www.derekmolloy.ie
> * that maps GPIO pins for the example
> */
> 
> 
> /dts-v1/;
> /plugin/;
> 
> 
> /{
>compatible = "ti,beaglebone", "ti,beaglebone-black";
>part-number = "DM-GPIO-Test";
>version = "00A0";
> 
> 
>fragment@0 {
>  target = <&am33xx_pinmux>;
> 
> 
>  __overlay__ {
>   pinctrl_test: DM_GPIO_Test_Pins {
> pinctrl-single,pins = <
> 
> 
> 0x070 0x07  /* P9_11 60 OUTPUT MODE7 - The 
> LED Output */
> 0x078 0x07  /* P9_12 60 OUTPUT MODE7 - The 
> LED Output */
> 0x074 0x07  /* P9_13 60 OUTPUT MODE7 - The 
> LED Output */
> 0x048 0x07  /* P9_14 60 OUTPUT MODE7 - The 
> LED Output */
> 0x040 0x07  /* P9_15 60 OUTPUT MODE7 - The 
> LED Output */
> 0x04c 0x07  /* P9_16 60 OUTPUT MODE7 - The 
> LED Output */
> 0x15c 0x07  /* P9_17 60 OUTPUT MODE7 - The 
> LED Output */
> 0x158 0x07  /* P9_18 60 OUTPUT MODE7 - The 
> LED Output */
> 
> 
> 
> 
>/* OUTPUT  GPIO(mode7) 0x07 pulldown, 0x17 
> pullup, 0x?f no pullup/down */
>/* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 
> pullup, 0x?f no pullup/down */
> 
> 
> >;
>   };
>  };
>};
> 
> 
>fragment@1 {
> target = <&ocp>;
> __overlay__ {
> test_helper: helper {
> compatible = "bone-pinmux-helper";
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_test>;
> status = "okay";
> };
> };
> };
> };
> 
> 
> However I could not figure out how to edit the header file used in the 
> example. Here is the header file of the example:
> 
> #ifndef _BEAGLEBONE_GPIO_H_
> #define _BEAGLEBONE_GPIO_H_
> 
> 
> #define GPIO1_START_ADDR 0x4804C000
> #define GPIO1_END_ADDR 0x4804DFFF
> #define GPIO1_SIZE (GPIO1_END_ADDR - GPIO1_START_ADDR)
> #define GPIO_OE 0x134
> #define GPIO_SETDATAOUT 0x194
> #define GPIO_CLEARDATAOUT 0x190
> 
> 
> 
> 
> #define PIN (1<<28)
> 
> 
> 
> 
> #endif
> 
> 
> Questions:
> 
> 1) I could not find START_ADDR, END_ADDR, OE, SETDATAOUT, CLEARDATAOUT from 
> technical manual. Where can I find them for the pins from P9_11 ... upto P9_18
See AM3358 TRM Table 2-3 GPIO1
> 
> 2) what is the explanation of the following statement? What does it do?
> define PIN ( 1<<28)
Take a 1 and left shift by 28. This means bit 28 is set.

>From Section 25.4
134h GPIO_OE
190h GPIO_CLEARDATAOUT
194h GPIO_SETDATAOUT

Learn to read the TRM. Section 2.1, Memory Map. Last section of each chapter is 
the register layout, for example, 25.4 is the GPIO register layout. 

> 
> 3) I am going to use it for SPI communication, so since the timing is 
> critical, and Linux is not RT, there is a possibility that some other 
> interrupts may damage my communaction. Do you think that it would be a 
> problem? If yes, what precautions can I get?
It is possible because the data is synchronized to the clock. However, I would 
recommend doing this with PRU.

Regards,
John
> 
> Regards,
> Frank
> 
> -- 
> 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 beagleboard+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/fe2ed36d-96bb-43d3-aeee-9e85fcbfd04b%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
For more options, visit h

Re: [beagleboard] Re: RS485 problem with DE/!RE

['Florian Feldbauer' via BeagleBoard]

On 04/28/2016 01:36 PM, Taceant Omnes wrote:

On 26 April 2016 at 08:07, florian.feldbauer85 via BeagleBoard
 wrote:


I did some further tests.
Actually none of the screens from my scope looks like I would expect it...

Picture 1 shows the result, if I try to read something on the bus with a 14s
timeout (nothing was sended on the bus...)
Pic1
Picture 2 shows the same, but this time there were messages send over the
bus. After 49 bytes, the beagle bone toggles the DE/!RE gpio to high for
unknown reasons (the test program is still reading from the UART interface)
Pic2
Picture 3 shows the test, where the BeagleBone is sending
Pic3

Your scope picture #3 does appear to show data being sent, however you
seem to say that your picture #2 portrays a test in which you received
49 bytes, however I don't see any sign of data being received in that
picture. Maybe I am missing something.

in all 4 picture from my 2nd post, channel 4 (green) shows one of
the two data lines of the bus.
Looking at #2 one can see, that this signal is starting toggling shortly 
before
the DE/RE signal goes high. That's the 49 bytes I receive. After that 
the data line
is still toggling araound but no longer between 0 and 1 but something in 
between,
because now, there are two devices sending on the bus. One is still the 
PC which

sends random data, the other one is the BeagleBone sending a constant 0...
(TX and DE/RE are constant high)



I am not an expert in these things, but my current understanding is
that what the 485 driver provides extra to what the UART driver does
is the automatic switch of the driver enable pin. One test I would
suggest, a test I have done myself, is to send and receive data with
485 using the UART driver. In this case the DE/RE needs to be set
manually. I do it using echo to  /sys/class/gpio. Once that is working
well you could start test usinging the 485 driver. You should be able
to use your existing rs485_test.c program for that.


@Alex: I recommend, you read my mail ;-)
I did not look into the kernel source nor am I sure which driver is used in my 
Setup,
but the problem is not the "rs485-rts-active-high" flag

As Micka and Alex said the 4.1 and 4.4 driver do not have 485 support
enabled. Per an email by Robert you need to enable the OMAP serial
kernel configuration option and rebuild the kernel.

I'm still a bit puzzled how "rs485 is not supported" looks like...
For me, being able to send and receiving data is quiet the
contrary of "not supported".
Where can I find the sources of the kernel used in the 
debian-jessie-console 8.4 image
from April 07 in order to rebuild it? (I prefer changing as less as 
possible, thus I'd like

to use the exact same kernel source tree as it is now)

Best regards,
Florian




--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/57220051.6020003%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Fast Pin Toggling Using MMAP

[frank brewer]

I just noticed the faster way of toggling pins by using mmap, and after 
trying chiragnagpal's example, I could achieve 2.6MHz. 



Example was for 1 pin only, now I want to use 8 pins, so I edited .dtc file 
as following:

/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Purpose License Version 2 as
* published by the Free Software Foundation
*
* Original from: 
github.com/jadonk/validation-scripts/blob/master/test-capemgr/
*
* Modified by Derek Molloy for the example on www.derekmolloy.ie
* that maps GPIO pins for the example
*/


/dts-v1/;
/plugin/;


/{
   compatible = "ti,beaglebone", "ti,beaglebone-black";
   part-number = "DM-GPIO-Test";
   version = "00A0";


   fragment@0 {
 target = <&am33xx_pinmux>;


 __overlay__ {
  pinctrl_test: DM_GPIO_Test_Pins {
pinctrl-single,pins = <


0x070 0x07  /* P9_11 60 OUTPUT MODE7 - The 
LED Output */
0x078 0x07  /* P9_12 60 OUTPUT MODE7 - The 
LED Output */
0x074 0x07  /* P9_13 60 OUTPUT MODE7 - The 
LED Output */
0x048 0x07  /* P9_14 60 OUTPUT MODE7 - The 
LED Output */
0x040 0x07  /* P9_15 60 OUTPUT MODE7 - The 
LED Output */
0x04c 0x07  /* P9_16 60 OUTPUT MODE7 - The 
LED Output */
0x15c 0x07  /* P9_17 60 OUTPUT MODE7 - The 
LED Output */
0x158 0x07  /* P9_18 60 OUTPUT MODE7 - The 
LED Output */




   /* OUTPUT  GPIO(mode7) 0x07 pulldown, 0x17 
pullup, 0x?f no pullup/down */
   /* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 
pullup, 0x?f no pullup/down */


>;
  };
 };
   };


   fragment@1 {
target = <&ocp>;
__overlay__ {
test_helper: helper {
compatible = "bone-pinmux-helper";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_test>;
status = "okay";
};
};
};
};


However I could not figure out how to edit the header file used in the 
example. Here is the header file of the example:

#ifndef _BEAGLEBONE_GPIO_H_
#define _BEAGLEBONE_GPIO_H_


#define GPIO1_START_ADDR 0x4804C000
#define GPIO1_END_ADDR 0x4804DFFF
#define GPIO1_SIZE (GPIO1_END_ADDR - GPIO1_START_ADDR)
#define GPIO_OE 0x134
#define GPIO_SETDATAOUT 0x194
#define GPIO_CLEARDATAOUT 0x190




#define PIN (1<<28)




#endif


*Questions:*

*1)* I could not find START_ADDR, END_ADDR, OE, SETDATAOUT, CLEARDATAOUT 
from technical manual. Where can I find them for the pins from P9_11 ... 
upto P9_18

*2)* what is the explanation of the following statement? What does it do?
define PIN ( 1<<28) 

*3) *I am going to use it for SPI communication, so since the timing is 
critical, and Linux is not RT, there is a possibility that some other 
interrupts may damage my communaction. Do you think that it would be a 
problem? If yes, what precautions can I get?

Regards,
Frank

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fe2ed36d-96bb-43d3-aeee-9e85fcbfd04b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 problem with DE/!RE

[Taceant Omnes]

On 28 April 2016 at 12:36, Taceant Omnes  wrote:

> As Micka and Alex said the 4.1 and 4.4 driver do not have 485 support
> enabled. Per an email by Robert you need to enable the OMAP serial
> kernel configuration option and rebuild the kernel.

Per email by Robert with respect to kernel options:
"
disable: CONFIG_SERIAL_8250_OMAP

enable: CONFIG_SERIAL_OMAP
"

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAKkGsY%2B4mCavFRPhg%3Dj0%3D9WZC9s1u0zuSs1CQJpXfL5hNF6J5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RS485 problem with DE/!RE

[Taceant Omnes]

On 26 April 2016 at 08:07, florian.feldbauer85 via BeagleBoard
 wrote:

>> > I did some further tests.
>> > Actually none of the screens from my scope looks like I would expect it...
>> >
>> > Picture 1 shows the result, if I try to read something on the bus with a 
>> > 14s
>> > timeout (nothing was sended on the bus...)
>> > Pic1
>> > Picture 2 shows the same, but this time there were messages send over the
>> > bus. After 49 bytes, the beagle bone toggles the DE/!RE gpio to high for
>> > unknown reasons (the test program is still reading from the UART interface)
>> > Pic2
>> > Picture 3 shows the test, where the BeagleBone is sending
>> > Pic3

Your scope picture #3 does appear to show data being sent, however you
seem to say that your picture #2 portrays a test in which you received
49 bytes, however I don't see any sign of data being received in that
picture. Maybe I am missing something.

I am not an expert in these things, but my current understanding is
that what the 485 driver provides extra to what the UART driver does
is the automatic switch of the driver enable pin. One test I would
suggest, a test I have done myself, is to send and receive data with
485 using the UART driver. In this case the DE/RE needs to be set
manually. I do it using echo to  /sys/class/gpio. Once that is working
well you could start test usinging the 485 driver. You should be able
to use your existing rs485_test.c program for that.

>> @Alex: I recommend, you read my mail ;-)
>> I did not look into the kernel source nor am I sure which driver is used in 
>> my Setup,
>> but the problem is not the "rs485-rts-active-high" flag

As Micka and Alex said the 4.1 and 4.4 driver do not have 485 support
enabled. Per an email by Robert you need to enable the OMAP serial
kernel configuration option and rebuild the kernel.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAKkGsYKhcGxN78Rsx327GTM5CNOfbkHMN07mwTFg0OqxoCKTZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Calibration issues with a touchscreen

[Sujit Singh]

I downloaded qt4-embedded on my Beaglebone black to run a qt gui on my BBB 
and display it on a touchscreen but I'm having calibration issues such as:
root@beaglebone:~# ts_calibrate
xres = 1024, yres = 768
tslib: Selected device is not a touchscreen (must support ABS and KEY event 
types)


some other references:
root@beaglebone:~# opkg install tslib-calibrate
Package tslib-calibrate 
(1.0+gitrAUTOINC+e17263ef401ee885a27d649b90b577cfb44500e0-r9.2) installed 
in root is up to date.
root@beaglebone:~# uname -a
Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux

I have an angstrom OS installed on my BBB.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3ebfdbcf-888b-48fb-8eb3-23a8a8e5ca89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.