[beagleboard] Debugger Listening on Port 15454?

[sipet929]

I have been trying to run a JavaScript file on the BeagleBone Black 
(Cayenne radar module) and I keep getting the message

Debugger Listening on Port 15454

when I run the js file on the cloud9 ide, it doesn't seem to be doing 
anything.

Anyone have any ideas on how to fix this?

-- 
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/84a8d7e6-875a-45c6-b39e-e2a307be42a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] 4-20 ma measurement with beaglebone black

[balihiboy]

Hello, 

I am wondering if a beaglebone black can be used to measure industrial 4-20 
ma loops?  I see there is an ADC feature, but the voltage range is only to 
1.8V.  Is it possible to set it up to work with the standard 24VDC 
circuitry involved with most 4-20ma loops?

Thank you in advance, 

-JP

-- 
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/d5d74056-d5c1-4e83-a148-b96d8c69093f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4-20 ma measurement with beaglebone black

[evilwulfie]

opamps are your friend


On 8/17/2016 5:26 PM, balihi...@gmail.com wrote:
> Hello, 
>
> I am wondering if a beaglebone black can be used to measure industrial
> 4-20 ma loops?  I see there is an ADC feature, but the voltage range
> is only to 1.8V.  Is it possible to set it up to work with the
> standard 24VDC circuitry involved with most 4-20ma loops?
>
> Thank you in advance, 
>
> -JP
>
> -- 
> 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/d5d74056-d5c1-4e83-a148-b96d8c69093f%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/eb1640fe-f2ea-719a-694f-adb39a34d48a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4-20 ma measurement with beaglebone black

[Przemek Klosowski]

 On 8/17/2016 5:26 PM, balihi...@gmail.com wrote:

> I am wondering if a beaglebone black can be used to measure industrial
> 4-20 ma loops?  I see there is an ADC feature, but the voltage range is
> only to 1.8V.  Is it possible to set it up to work with the standard 24VDC
> circuitry involved with most 4-20ma loops?
>
> A 90 ohm resistor carrying 20mA will develop a voltage of 1.8V. This is
cutting it a little close, so I recommend 68 ohm, which is a more
standard/easier to find value anyway. So, just terminate your 4-20mA line
with this resistor, and connect it to the Beaglebone analog input. Of
course if you're in an industrial environment you need to watch out for
transients, noise and interference, especially since the Beaglebone inputs
are famously fragile, so include some serious input protection (e.g. four
diodes connected as two anti-parallel 2-diode chains, with a filter cap
across it and maybe some series resistance). Then again, you could follow
evilwulfie's advice to use a dedicated buffer op-amp.

-- 
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/CAC%3D1GgEYNO8A-ziJKy0StkuFw6sC5eRRK05_fy3oiPAJ-4_fPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Why did my BeagleBone Black suddenly switched off and not powering up again?

[Sundeep KOKKONDA]

Hello, I encountered the same issue *(I powered my BBB and when I was about 
to SSH to the BBB, suddenly it just switched off. Then I unplugged and 
plugged in the adapter and saw that, the BBB does not power up while the 
power LED just blinks once and goes off).*

If somebody aware please let us know how to fix the issue.

-- 
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/e80bcfb7-afa3-4287-93c5-1b4dd3725f5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: does beagleboard X15 support 4k HDMI output?

[rumkof24]

it supposed work within patch to 4K but it' s simply a dittererd pixel for 
screenpoint; so x 15 is more meta to envoy a light bubble as you appear to 
experience with wear a 3D glass ; this not does to do something in 4K caus 
4K Hdmi based on interact with devices and not glass for 3D - small change 
it X15 works 4k into google glass but I can' t give you guarenty.

Op woensdag 13 juli 2016 23:35:48 UTC+2 schreef Yicheng Bai:
>
> Hi,
>
> does beagleboard X15 support 4k HDMI output?
>
> Thanks.
>

-- 
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/86f17975-300d-4ff5-b14e-1d6f9a6e3488%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4-20 ma measurement with beaglebone black

[Graham]

If you would think to Google "4-20 mA receiver" you could learn a lot.

Peripheral IC's from TI and Maxim that have most everything you need all 
ready designed in.

Modules you could interface to the BBB, etc.

Application notes on how to design receivers, and things to worry about, 
common system problems that people have had with this circuit for the last 
50 years.

Good luck.

==





On Thursday, August 18, 2016 at 10:03:12 AM UTC-5, Przemek Klosowski wrote:
>
>  On 8/17/2016 5:26 PM, bali...@gmail.com  wrote: 
>
>> I am wondering if a beaglebone black can be used to measure industrial 
>> 4-20 ma loops?  I see there is an ADC feature, but the voltage range is 
>> only to 1.8V.  Is it possible to set it up to work with the standard 24VDC 
>> circuitry involved with most 4-20ma loops?
>>
>> A 90 ohm resistor carrying 20mA will develop a voltage of 1.8V. This is 
> cutting it a little close, so I recommend 68 ohm, which is a more 
> standard/easier to find value anyway. So, just terminate your 4-20mA line 
> with this resistor, and connect it to the Beaglebone analog input. Of 
> course if you're in an industrial environment you need to watch out for 
> transients, noise and interference, especially since the Beaglebone inputs 
> are famously fragile, so include some serious input protection (e.g. four 
> diodes connected as two anti-parallel 2-diode chains, with a filter cap 
> across it and maybe some series resistance). Then again, you could follow 
> evilwulfie's advice to use a dedicated buffer op-amp.
>
>

-- 
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/00917cb1-80b6-4a82-9d78-e8a042f1d321%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why did my BeagleBone Black suddenly switched off and not powering up again?

[evilwulfie]

try a different power supply. the PMIC is picky cant be too fast or too
slow of a ramp up.


On 8/18/2016 8:10 AM, Sundeep KOKKONDA wrote:
>
> Hello, I encountered the same issue /*(I powered my BBB and when I was
> about to SSH to the BBB, suddenly it just switched off. Then I
> unplugged and plugged in the adapter and saw that, the BBB does not
> power up while the power LED just blinks once and goes off).*/
>
> If somebody aware please let us know how to fix the issue.
> -- 
> 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/e80bcfb7-afa3-4287-93c5-1b4dd3725f5f%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/9a716327-c683-9181-d4b4-1b4b5065a5d6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4-20 ma measurement with beaglebone black

[drhunter95]

There is a TI reference design for 4-20mA loop 
interfaces http://www.ti.com/tool/tida-00550. It is designed as a cape.
Iain

On Thursday, August 18, 2016 at 4:24:45 PM UTC+1, Graham wrote:
>
> If you would think to Google "4-20 mA receiver" you could learn a lot.
>
> Peripheral IC's from TI and Maxim that have most everything you need all 
> ready designed in.
>
> Modules you could interface to the BBB, etc.
>
> Application notes on how to design receivers, and things to worry about, 
> common system problems that people have had with this circuit for the last 
> 50 years.
>
> Good luck.
>
> ==
>
>
>
>
>
> On Thursday, August 18, 2016 at 10:03:12 AM UTC-5, Przemek Klosowski wrote:
>>
>>  On 8/17/2016 5:26 PM, bali...@gmail.com wrote: 
>>
>>> I am wondering if a beaglebone black can be used to measure industrial 
>>> 4-20 ma loops?  I see there is an ADC feature, but the voltage range is 
>>> only to 1.8V.  Is it possible to set it up to work with the standard 24VDC 
>>> circuitry involved with most 4-20ma loops?
>>>
>>> A 90 ohm resistor carrying 20mA will develop a voltage of 1.8V. This is 
>> cutting it a little close, so I recommend 68 ohm, which is a more 
>> standard/easier to find value anyway. So, just terminate your 4-20mA line 
>> with this resistor, and connect it to the Beaglebone analog input. Of 
>> course if you're in an industrial environment you need to watch out for 
>> transients, noise and interference, especially since the Beaglebone inputs 
>> are famously fragile, so include some serious input protection (e.g. four 
>> diodes connected as two anti-parallel 2-diode chains, with a filter cap 
>> across it and maybe some series resistance). Then again, you could follow 
>> evilwulfie's advice to use a dedicated buffer op-amp.
>>
>>

-- 
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/33e62589-6e59-4eac-8971-a59e6d0d832c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Decrease ramdisk (tmpfs) to increase available RAM memory

[Colin Bester]

I am looking to increase the amount of RAM by about 100K and was wondering 
if I could 'steal' some from ramdisk.

I see several tmpfs when running mount command but don't see setting up of 
tmps in /etc/fstab so am guessing this is done elsewhere.

Firstly is this possible and/or wise to do and secondly any suggestions on 
where to find creation of ram disks on startup.

Thanks
Colin

-- 
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/9aaaeff8-ea52-4b53-a094-fc189a61e350%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[Matt]

Hi,

Working in kernel 4.4.16-bone-rt-r11 and am not seeing the corresponding 
entries in /dev/ for the enabled UARTS.

My custom DTS (BB-APA-01) enables a number of UARTS but I am not seeing the 
corresponding /dev/ttyO2, ttyO4, ttyO5, etc.  

Tried also loading the BB-UART2-00A0.dtbo from /lib/firmare/ as you can see 
below when I cat slots.  

root:~# cat /sys/devices/platform/bone_capemgr/slots 
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01
 5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-ADC
 6: P-O-L-   2 Override Board Name,00A0,Override Manuf,BB-UART2


root:~# ls /dev/tty*
/dev/tty/dev/tty19/dev/tty3   /dev/tty40/dev/tty51  /dev/tty62
/dev/tty0   /dev/tty2/dev/tty30  /dev/tty41/dev/tty52  /dev/tty63
/dev/tty1   /dev/tty20/dev/tty31  /dev/tty42/dev/tty53  /dev/tty7
/dev/tty10  /dev/tty21/dev/tty32  /dev/tty43/dev/tty54  /dev/tty8
/dev/tty11  /dev/tty22/dev/tty33  /dev/tty44/dev/tty55  /dev/tty9
/dev/tty12  /dev/tty23/dev/tty34  /dev/tty45/dev/tty56  /dev/ttyACM0
/dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57  /dev/ttyS0
/dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58  /dev/ttyS1
/dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59  /dev/ttyS2
/dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6   /dev/ttyS3
/dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60  /dev/ttyS4
/dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61  /dev/ttyS5


What am I missing here?  When a UART is loaded into slots should it then be 
labeld ttyOX in /dev just as in 3.18?

-- 
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/11dca538-30f1-4d2b-a41d-a1d3f0482104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[Mike]

On 08/18/2016 05:57 PM, Matt wrote:

Hi,

Working in kernel 4.4.16-bone-rt-r11 and am not seeing the 
corresponding entries in /dev/ for the enabled UARTS.


/dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57 /dev/ttyS0
/dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58 /dev/ttyS1
/dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59 /dev/ttyS2
/dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6 /dev/ttyS3
/dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60 /dev/ttyS4
/dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61 /dev/ttyS5


What am I missing here?  When a UART is loaded into slots should it 
then be labeld ttyOX in /dev just as in 3.18?

--


/dev/ttyS?

Mike

--
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/f8259417-946a-3a27-c0c1-4f3124e637e1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[Matt99eo]

Don't think the ttyS's are it.  I know for sure in 3.18 you use the /ttyO2 
or whatever number uart you enable. 


On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:
>
> On 08/18/2016 05:57 PM, Matt wrote: 
> > Hi, 
> > 
> > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the 
> > corresponding entries in /dev/ for the enabled UARTS. 
> > 
> > /dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57 
> /dev/ttyS0 
> > /dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58 
> /dev/ttyS1 
> > /dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59 
> /dev/ttyS2 
> > /dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6 /dev/ttyS3 
> > /dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60 /dev/ttyS4 
> > /dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61 
> /dev/ttyS5 
> > 
> > 
> > What am I missing here?  When a UART is loaded into slots should it 
> > then be labeld ttyOX in /dev just as in 3.18? 
> > -- 
>
> /dev/ttyS? 
>
> Mike 
>

-- 
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/e2e3640a-cb58-4d8a-b648-75424dab7c5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[Matt]

Don't think the ttyS's are it.  I know for sure in 3.18 you use the /ttyO2 
or whatever number uart you enable. 

Can anyone confirm that in 4.4 the UARTS show as /ttyS*  ?

Going to check my .dts.

On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:
>
> On 08/18/2016 05:57 PM, Matt wrote: 
> > Hi, 
> > 
> > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the 
> > corresponding entries in /dev/ for the enabled UARTS. 
> > 
> > /dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57 
> /dev/ttyS0 
> > /dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58 
> /dev/ttyS1 
> > /dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59 
> /dev/ttyS2 
> > /dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6 /dev/ttyS3 
> > /dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60 /dev/ttyS4 
> > /dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61 
> /dev/ttyS5 
> > 
> > 
> > What am I missing here?  When a UART is loaded into slots should it 
> > then be labeld ttyOX in /dev just as in 3.18? 
> > -- 
>
> /dev/ttyS? 
>
> Mike 
>

-- 
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/47a3dbf5-9d09-4825-80a4-54213c54c336%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] can't setup more than 2 UART's at the same time

[Matt]

Once you were successful here did you get the corresponding /dev/ttyO2 , 
/dev/ttyO4 , etc?

On Monday, August 8, 2016 at 11:45:00 AM UTC-7, RobertCNelson wrote:
>
> On Mon, Aug 8, 2016 at 1:41 PM, Dror Lugasi  > wrote: 
> > thank you very much Robert! unfortunately i will have it only on 
> Wednesday 
> > so i'll try it then.. 
> > 
> > so i just need to add 
> > 
> > 
> cape_enable=bone_capemgr.enable_partno=BB-UART0,BB-UART2,BB-UART4,BB-UART5 
> > dtb=am335x-boneblack-overlay.dtb 
> > 
> > the -dtb- one line below the -cape_enable- ? 
>
> Doesn't matter, u-boot process the whole /boot/uEnv.txt file.. 
>
> 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/bbd36f31-7dd5-4107-a9cd-fdfa70639edf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[William Hermans]

william@beaglebone:~$ dmesg |grep tty
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
[0.002187] console [tty0] enabled
[0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
base_baud = 300) is a 8250
[2.884801] console [ttyS0] enabled
william@beaglebone:~$ clear
william@beaglebone:~$ ls /sys/devices/
armv7_cortex_a8  breakpoint  platform  soc0  software  system  tracepoint
virtual
william@beaglebone:~$ ls /sys/devices/platform/
alarmtimercpufreq-dtleds  omap-pcm-audio  pm33xx.0  power
serial8250  ti-cpufreq.0
bone_capemgr  fixedregulator@0  ocp   opp_table0  pmu   reg-dummy
soc uevent
william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
william@beaglebone:~$ ls /lib/firmware/ |grep UART
BB-UART1-00A0.dtbo
BB-UART2-00A0.dtbo
BB-UART2-RTSCTS-00A0.dtbo
BB-UART3-00A0.dtbo
BB-UART4-00A0.dtbo
BB-UART4-RS485-00A0.dtbo
BB-UART5-00A0.dtbo
william@beaglebone:~$ sudo sh -c"echo 'BB-UART2' >
/sys/devices/platform/bone_capemgr/slots"
[sudo] password for william:
sh: 0: Illegal option -h
william@beaglebone:~$ sudo sh -c "echo 'BB-UART2' >
/sys/devices/platform/bone_capemgr/slots"
william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
william@beaglebone:~$ dmesg |grep tty
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
[0.002187] console [tty0] enabled
[0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
base_baud = 300) is a 8250
[2.884801] console [ttyS0] enabled
[778201.669492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 198,
base_baud = 300) is a 8250


On Thu, Aug 18, 2016 at 4:17 PM, Matt  wrote:

> Don't think the ttyS's are it.  I know for sure in 3.18 you use the /ttyO2
> or whatever number uart you enable.
>
> Can anyone confirm that in 4.4 the UARTS show as /ttyS*  ?
>
> Going to check my .dts.
>
> On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:
>>
>> On 08/18/2016 05:57 PM, Matt wrote:
>> > Hi,
>> >
>> > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the
>> > corresponding entries in /dev/ for the enabled UARTS.
>> >
>> > /dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57
>> /dev/ttyS0
>> > /dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58
>> /dev/ttyS1
>> > /dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59
>> /dev/ttyS2
>> > /dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6
>> /dev/ttyS3
>> > /dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60
>> /dev/ttyS4
>> > /dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61
>> /dev/ttyS5
>> >
>> >
>> > What am I missing here?  When a UART is loaded into slots should it
>> > then be labeld ttyOX in /dev just as in 3.18?
>> > --
>>
>> /dev/ttyS?
>>
>> Mike
>>
> --
> 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/47a3dbf5-9d09-4825-80a4-54213c54c336%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/CALHSORrF9s1MQpobfxJa%2B%3DY_G7_cMOq%2BYcnNYcOoyyZ5zO4MOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[William Hermans]

william@beaglebone:~$ ls /sys/devices/platform/ocp/
4030.ocmcram  4803.spi4806.mmc
4831.rng   5350.aes
40302000.ocmcram_nocache  48038000.mcasp  480c8000.mailbox
4900.edma  5600.sgx
44e07000.gpio 4803c000.mcasp  480ca000.spinlock
4980.tptc  driver_override
44e09000.serial   48042000.timer  4819c000.i2c
4990.tptc  modalias
44e0b000.i2c  48044000.timer  481a.spi
49a0.tptc  ocp:l4_wkup@44c0
44e35000.wdt  48046000.timer  481ac000.gpio
4a10.ethernet  of_node
44e3e000.rtc  48048000.timer  481ae000.gpio
4a30.pruss power
4740.usb  4804a000.timer  481d8000.mmc
4c00.emif  subsystem
48024000.serial   4804c000.gpio   4820.interrupt-controller
5310.sham  uevent
william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial
driver  driver_override  modalias  of_node  power  subsystem  tty  uevent
william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial/tty
ttyS2


On Thu, Aug 18, 2016 at 4:32 PM, William Hermans  wrote:

> william@beaglebone:~$ dmesg |grep tty
> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
> [0.002187] console [tty0] enabled
> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
> base_baud = 300) is a 8250
> [2.884801] console [ttyS0] enabled
> william@beaglebone:~$ clear
> william@beaglebone:~$ ls /sys/devices/
> armv7_cortex_a8  breakpoint  platform  soc0  software  system  tracepoint
> virtual
> william@beaglebone:~$ ls /sys/devices/platform/
> alarmtimercpufreq-dtleds  omap-pcm-audio  pm33xx.0  power
> serial8250  ti-cpufreq.0
> bone_capemgr  fixedregulator@0  ocp   opp_table0  pmu
> reg-dummy  soc uevent
> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
> william@beaglebone:~$ ls /lib/firmware/ |grep UART
> BB-UART1-00A0.dtbo
> BB-UART2-00A0.dtbo
> BB-UART2-RTSCTS-00A0.dtbo
> BB-UART3-00A0.dtbo
> BB-UART4-00A0.dtbo
> BB-UART4-RS485-00A0.dtbo
> BB-UART5-00A0.dtbo
> william@beaglebone:~$ sudo sh -c"echo 'BB-UART2' >
> /sys/devices/platform/bone_capemgr/slots"
> [sudo] password for william:
> sh: 0: Illegal option -h
> william@beaglebone:~$ sudo sh -c "echo 'BB-UART2' >
> /sys/devices/platform/bone_capemgr/slots"
> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
> william@beaglebone:~$ dmesg |grep tty
> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
> [0.002187] console [tty0] enabled
> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
> base_baud = 300) is a 8250
> [2.884801] console [ttyS0] enabled
> [778201.669492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 198,
> base_baud = 300) is a 8250
>
>
> On Thu, Aug 18, 2016 at 4:17 PM, Matt  wrote:
>
>> Don't think the ttyS's are it.  I know for sure in 3.18 you use the
>> /ttyO2 or whatever number uart you enable.
>>
>> Can anyone confirm that in 4.4 the UARTS show as /ttyS*  ?
>>
>> Going to check my .dts.
>>
>> On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:
>>>
>>> On 08/18/2016 05:57 PM, Matt wrote:
>>> > Hi,
>>> >
>>> > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the
>>> > corresponding entries in /dev/ for the enabled UARTS.
>>> >
>>> > /dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57
>>> /dev/ttyS0
>>> > /dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58
>>> /dev/ttyS1
>>> > /dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/dev/tty59
>>> /dev/ttyS2
>>> > /dev/tty16  /dev/tty27/dev/tty38  /dev/tty49/dev/tty6
>>> /dev/ttyS3
>>> > /dev/tty17  /dev/tty28/dev/tty39  /dev/tty5/dev/tty60
>>> /dev/ttyS4
>>> > /dev/tty18  /dev/tty29/dev/tty4   /dev/tty50/dev/tty61
>>> /dev/ttyS5
>>> >
>>> >
>>> > What am I missing here?  When a UART is loaded into slots should it
>>> > then be labeld ttyOX in /dev just as in 3.18?
>>> > --
>>>
>>> /dev/ttyS?
>>>
>>> Mike
>>>
>> --
>> 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/ms
>> gid/beagleboard/47a3dbf5-9d09-4825-80a4-54213c54c336%40googlegroups.com
>> 

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[William Hermans]

william@beaglebone:~$ apt-cache search setserial
setserial - controls configuration of serial ports
william@beaglebone:~$ sudo apt-get install setserial
. . .
The following NEW packages will be installed:
  setserial
0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
Need to get 49.9 kB of archives.
After this operation, 139 kB of additional disk space will be used.

william@beaglebone:~$ setserial -g /dev/ttyS[0-5]
/dev/ttyS0, UART: 8250, Port: 0x, IRQ: 158
/dev/ttyS1, UART: unknown, Port: 0x, IRQ: 0
/dev/ttyS2, UART: 8250, Port: 0x, IRQ: 198
/dev/ttyS3, UART: unknown, Port: 0x, IRQ: 0
/dev/ttyS4, UART: unknown, Port: 0x, IRQ: 0
/dev/ttyS5, UART: unknown, Port: 0x, IRQ: 0


On Thu, Aug 18, 2016 at 4:34 PM, William Hermans  wrote:

> william@beaglebone:~$ ls /sys/devices/platform/ocp/
> 4030.ocmcram  4803.spi4806.mmc
> 4831.rng   5350.aes
> 40302000.ocmcram_nocache  48038000.mcasp  480c8000.mailbox
> 4900.edma  5600.sgx
> 44e07000.gpio 4803c000.mcasp  480ca000.spinlock
> 4980.tptc  driver_override
> 44e09000.serial   48042000.timer  4819c000.i2c
> 4990.tptc  modalias
> 44e0b000.i2c  48044000.timer  481a.spi
> 49a0.tptc  ocp:l4_wkup@44c0
> 44e35000.wdt  48046000.timer  481ac000.gpio
> 4a10.ethernet  of_node
> 44e3e000.rtc  48048000.timer  481ae000.gpio
> 4a30.pruss power
> 4740.usb  4804a000.timer  481d8000.mmc
> 4c00.emif  subsystem
> 48024000.serial   4804c000.gpio   4820.interrupt-controller
> 5310.sham  uevent
> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial
> driver  driver_override  modalias  of_node  power  subsystem  tty  uevent
> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial/tty
> ttyS2
>
>
> On Thu, Aug 18, 2016 at 4:32 PM, William Hermans 
> wrote:
>
>> william@beaglebone:~$ dmesg |grep tty
>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
>> [0.002187] console [tty0] enabled
>> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>> base_baud = 300) is a 8250
>> [2.884801] console [ttyS0] enabled
>> william@beaglebone:~$ clear
>> william@beaglebone:~$ ls /sys/devices/
>> armv7_cortex_a8  breakpoint  platform  soc0  software  system
>> tracepoint  virtual
>> william@beaglebone:~$ ls /sys/devices/platform/
>> alarmtimercpufreq-dtleds  omap-pcm-audio  pm33xx.0
>> power  serial8250  ti-cpufreq.0
>> bone_capemgr  fixedregulator@0  ocp   opp_table0  pmu
>> reg-dummy  soc uevent
>> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>  0: PF  -1
>>  1: PF  -1
>>  2: PF  -1
>>  3: PF  -1
>> william@beaglebone:~$ ls /lib/firmware/ |grep UART
>> BB-UART1-00A0.dtbo
>> BB-UART2-00A0.dtbo
>> BB-UART2-RTSCTS-00A0.dtbo
>> BB-UART3-00A0.dtbo
>> BB-UART4-00A0.dtbo
>> BB-UART4-RS485-00A0.dtbo
>> BB-UART5-00A0.dtbo
>> william@beaglebone:~$ sudo sh -c"echo 'BB-UART2' >
>> /sys/devices/platform/bone_capemgr/slots"
>> [sudo] password for william:
>> sh: 0: Illegal option -h
>> william@beaglebone:~$ sudo sh -c "echo 'BB-UART2' >
>> /sys/devices/platform/bone_capemgr/slots"
>> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>  0: PF  -1
>>  1: PF  -1
>>  2: PF  -1
>>  3: PF  -1
>>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
>> william@beaglebone:~$ dmesg |grep tty
>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
>> [0.002187] console [tty0] enabled
>> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>> base_baud = 300) is a 8250
>> [2.884801] console [ttyS0] enabled
>> [778201.669492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 198,
>> base_baud = 300) is a 8250
>>
>>
>> On Thu, Aug 18, 2016 at 4:17 PM, Matt 
>> wrote:
>>
>>> Don't think the ttyS's are it.  I know for sure in 3.18 you use the
>>> /ttyO2 or whatever number uart you enable.
>>>
>>> Can anyone confirm that in 4.4 the UARTS show as /ttyS*  ?
>>>
>>> Going to check my .dts.
>>>
>>> On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:

 On 08/18/2016 05:57 PM, Matt wrote:
 > Hi,
 >
 > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the
 > corresponding entries in /dev/ for the enabled UARTS.
 >
 > /dev/tty13  /dev/tty24/dev/tty35  /dev/tty46/dev/tty57
 /dev/ttyS0
 > /dev/tty14  /dev/tty25/dev/tty36  /dev/tty47/dev/tty58
 /dev/ttyS1
 > /dev/tty15  /dev/tty26/dev/tty37  /dev/tty48/d

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

[William Hermans]

http://bfy.tw/7Hr5

Anyhow, consider this horse beaten to death.

On Thu, Aug 18, 2016 at 4:42 PM, William Hermans  wrote:

> william@beaglebone:~$ apt-cache search setserial
> setserial - controls configuration of serial ports
> william@beaglebone:~$ sudo apt-get install setserial
> . . .
> The following NEW packages will be installed:
>   setserial
> 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
> Need to get 49.9 kB of archives.
> After this operation, 139 kB of additional disk space will be used.
>
> william@beaglebone:~$ setserial -g /dev/ttyS[0-5]
> /dev/ttyS0, UART: 8250, Port: 0x, IRQ: 158
> /dev/ttyS1, UART: unknown, Port: 0x, IRQ: 0
> /dev/ttyS2, UART: 8250, Port: 0x, IRQ: 198
> /dev/ttyS3, UART: unknown, Port: 0x, IRQ: 0
> /dev/ttyS4, UART: unknown, Port: 0x, IRQ: 0
> /dev/ttyS5, UART: unknown, Port: 0x, IRQ: 0
>
>
> On Thu, Aug 18, 2016 at 4:34 PM, William Hermans 
> wrote:
>
>> william@beaglebone:~$ ls /sys/devices/platform/ocp/
>> 4030.ocmcram  4803.spi4806.mmc
>> 4831.rng   5350.aes
>> 40302000.ocmcram_nocache  48038000.mcasp  480c8000.mailbox
>> 4900.edma  5600.sgx
>> 44e07000.gpio 4803c000.mcasp  480ca000.spinlock
>> 4980.tptc  driver_override
>> 44e09000.serial   48042000.timer  4819c000.i2c
>> 4990.tptc  modalias
>> 44e0b000.i2c  48044000.timer  481a.spi
>> 49a0.tptc  ocp:l4_wkup@44c0
>> 44e35000.wdt  48046000.timer  481ac000.gpio
>> 4a10.ethernet  of_node
>> 44e3e000.rtc  48048000.timer  481ae000.gpio
>> 4a30.pruss power
>> 4740.usb  4804a000.timer  481d8000.mmc
>> 4c00.emif  subsystem
>> 48024000.serial   4804c000.gpio   4820.interrupt-controller
>> 5310.sham  uevent
>> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial
>> driver  driver_override  modalias  of_node  power  subsystem  tty  uevent
>> william@beaglebone:~$ ls /sys/devices/platform/ocp/48024000.serial/tty
>> ttyS2
>>
>>
>> On Thu, Aug 18, 2016 at 4:32 PM, William Hermans 
>> wrote:
>>
>>> william@beaglebone:~$ dmesg |grep tty
>>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
>>> [0.002187] console [tty0] enabled
>>> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>>> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>>> base_baud = 300) is a 8250
>>> [2.884801] console [ttyS0] enabled
>>> william@beaglebone:~$ clear
>>> william@beaglebone:~$ ls /sys/devices/
>>> armv7_cortex_a8  breakpoint  platform  soc0  software  system
>>> tracepoint  virtual
>>> william@beaglebone:~$ ls /sys/devices/platform/
>>> alarmtimercpufreq-dtleds  omap-pcm-audio  pm33xx.0
>>> power  serial8250  ti-cpufreq.0
>>> bone_capemgr  fixedregulator@0  ocp   opp_table0  pmu
>>> reg-dummy  soc uevent
>>> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>>  0: PF  -1
>>>  1: PF  -1
>>>  2: PF  -1
>>>  3: PF  -1
>>> william@beaglebone:~$ ls /lib/firmware/ |grep UART
>>> BB-UART1-00A0.dtbo
>>> BB-UART2-00A0.dtbo
>>> BB-UART2-RTSCTS-00A0.dtbo
>>> BB-UART3-00A0.dtbo
>>> BB-UART4-00A0.dtbo
>>> BB-UART4-RS485-00A0.dtbo
>>> BB-UART5-00A0.dtbo
>>> william@beaglebone:~$ sudo sh -c"echo 'BB-UART2' >
>>> /sys/devices/platform/bone_capemgr/slots"
>>> [sudo] password for william:
>>> sh: 0: Illegal option -h
>>> william@beaglebone:~$ sudo sh -c "echo 'BB-UART2' >
>>> /sys/devices/platform/bone_capemgr/slots"
>>> william@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>>  0: PF  -1
>>>  1: PF  -1
>>>  2: PF  -1
>>>  3: PF  -1
>>>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
>>> william@beaglebone:~$ dmesg |grep tty
>>> [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1
>>> [0.002187] console [tty0] enabled
>>> [0.002223] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>>> [1.998154] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>>> base_baud = 300) is a 8250
>>> [2.884801] console [ttyS0] enabled
>>> [778201.669492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 198,
>>> base_baud = 300) is a 8250
>>>
>>>
>>> On Thu, Aug 18, 2016 at 4:17 PM, Matt 
>>> wrote:
>>>
 Don't think the ttyS's are it.  I know for sure in 3.18 you use the
 /ttyO2 or whatever number uart you enable.

 Can anyone confirm that in 4.4 the UARTS show as /ttyS*  ?

 Going to check my .dts.

 On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote:
>
> On 08/18/2016 05:57 PM, Matt wrote:
> > Hi,
> >
> > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the
> > corresponding entries in /dev/ 

[beagleboard] Re: Debugger Listening on Port 15454?

[Chintan Pathak]

This is not enough information to answer your question. 

What is the source of the js file ? If possible share its contents. 

JS can run on server as well as client. If you plan to run it on BBB with 
an output of Debugger listen... its most probably a serverside (NodeJS) 
file. How are you running it through Cloud9 ? Describe your steps, maybe 
attach screenshot. What output are you expecting ?

On Thursday, August 18, 2016 at 6:53:41 AM UTC-7, sipe...@gmail.com wrote:
>
> I have been trying to run a JavaScript file on the BeagleBone Black 
> (Cayenne radar module) and I keep getting the message
>
> Debugger Listening on Port 15454
>
> when I run the js file on the cloud9 ide, it doesn't seem to be doing 
> anything.
>
> Anyone have any ideas on how to fix this?
>

-- 
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/65727319-9cda-4c25-92d1-707e7eca1091%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Right way to get the gpio values from the device tree in the device driver for BeagleboneBlack

[Jane]

Hello,

This topic is not solely related to beagleboneBlack , still posting on this 
group .

With reference to the example below what is the correct way to get the gpio 
values from the device tree :

I modified the existing leds-ns2 device tree as below(slow1 ,cmd1) :


  blue-sata {

   label = "ns2:blue:sata";

   slow-gpio = <&gpio0 29 0>;

   cmd-gpio = <&gpio0 30 0>;

+ slow1-gpio=<&gpio 31 0>;

+ cmd1-gpio=<&gpio 32 0>;

   modes-map = ;

   };

 

 

And modified the driver by adding slow1 and cmd1 in all the structure (just 
like slow and cmd) in the attached leds-ns2.c driver

But when I am trying to get the gpio number for slow1 and cmd1 I am getting 
the below error(number gpio #31 and 32 are random numbers of gpio for 
testing, does it matters?) :

error : leds-ns2:probe of ns2-leds failed with error -2.What does error 
code -2 represents ?Is this a device tree parsing error?

ret = of_get_named_gpio(child, "slow1-gpio", 0);

 if (ret < 0)

 return ret;

same error if I try to get the cmd1-gpio . 
 

Thanks in advance !

Regards,

Rp

-- 
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/4f1ce45b-5a75-4152-a93d-ea33f2df87bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
/*
 * leds-ns2.c - Driver for the Network Space v2 (and parents) dual-GPIO LED
 *
 * Copyright (C) 2010 LaCie
 *
 * Author: Simon Guinot 
 *
 * Based on leds-gpio.c by Raphael Assenat 
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation; either version 2 of the License, or
 * (at your option) any later version.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include "leds.h"

/*
 * The Network Space v2 dual-GPIO LED is wired to a CPLD. Three different LED
 * modes are available: off, on and SATA activity blinking. The LED modes are
 * controlled through two GPIOs (command and slow): each combination of values
 * for the command/slow GPIOs corresponds to a LED mode.
 */

struct ns2_led_data {
	struct led_classdev	cdev;
	unsigned		cmd;
	unsigned		slow;
	bool			can_sleep;
	unsigned char		sata; /* True when SATA mode active. */
	rwlock_t		rw_lock; /* Lock GPIOs. */
	int			num_modes;
	struct ns2_led_modval	*modval;
};

static int ns2_led_get_mode(struct ns2_led_data *led_dat,
			enum ns2_led_modes *mode)
{
	int i;
	int ret = -EINVAL;
	int cmd_level;
	int slow_level;

	cmd_level = gpio_get_value_cansleep(led_dat->cmd);
	slow_level = gpio_get_value_cansleep(led_dat->slow);

	for (i = 0; i < led_dat->num_modes; i++) {
		if (cmd_level == led_dat->modval[i].cmd_level &&
		slow_level == led_dat->modval[i].slow_level) {
			*mode = led_dat->modval[i].mode;
			ret = 0;
			break;
		}
	}

	return ret;
}

static void ns2_led_set_mode(struct ns2_led_data *led_dat,
			 enum ns2_led_modes mode)
{
	int i;
	bool found = false;
	unsigned long flags;

	for (i = 0; i < led_dat->num_modes; i++)
		if (mode == led_dat->modval[i].mode) {
			found = true;
			break;
		}

	if (!found)
		return;

	write_lock_irqsave(&led_dat->rw_lock, flags);

	if (!led_dat->can_sleep) {
		gpio_set_value(led_dat->cmd,
			   led_dat->modval[i].cmd_level);
		gpio_set_value(led_dat->slow,
			   led_dat->modval[i].slow_level);
		goto exit_unlock;
	}

	gpio_set_value_cansleep(led_dat->cmd, led_dat->modval[i].cmd_level);
	gpio_set_value_cansleep(led_dat->slow, led_dat->modval[i].slow_level);

exit_unlock:
	write_unlock_irqrestore(&led_dat->rw_lock, flags);
}

static void ns2_led_set(struct led_classdev *led_cdev,
			enum led_brightness value)
{
	struct ns2_led_data *led_dat =
		container_of(led_cdev, struct ns2_led_data, cdev);
	enum ns2_led_modes mode;

	if (value == LED_OFF)
		mode = NS_V2_LED_OFF;
	else if (led_dat->sata)
		mode = NS_V2_LED_SATA;
	else
		mode = NS_V2_LED_ON;

	ns2_led_set_mode(led_dat, mode);
}

static int ns2_led_set_blocking(struct led_classdev *led_cdev,
			enum led_brightness value)
{
	ns2_led_set(led_cdev, value);
	ret