Re: [beagleboard] Sainsmart LCD2004 with Beaglebone Black

2015-10-22 Thread Harvey White 
On Thu, 22 Oct 2015 21:23:51 -0400, you wrote:

>Ah, if you are referring to a logic level converter, I had ordered one but
>wasn't sure if that was what I needed.  I'll read more on how to use it,
>and try that.  Thank you.

You're welcome.  However, be aware that there are several kinds of
logic level converter.

The standard variety 8T245 or 74LVC1T45  (think that the numbers are
close) are the standard LS245 type, a bidirectional driver that only
works one way at a time, where the chip has two VCC inputs.  This is
quite useful for parallel inputs/outputs where you're only
transmitting one direction at a time, and have a control line that
enables that (such as a read/write line).

The PCA9517A chip is designed specifically for I2C, and is
bidirectional without needing a control.  The SCL line is driven by
whatever is the I2C master, but the SDA line is alternately driven by
the master (at all times on writes except for the ACK bit) and the
slave (all the times the slave talks to the master except the ACK bit
from the master).   Check the I2C spec for this information.  On the
chip, leave the ENA input open, it seems to work just fine like that
(or I suppose you could pull it up to the appropriate VCC).  

On this chip, use pins 7 and 6 for the local (processor) pins, and use
pins 2 and 3 for the system (chip to chip) connections.  Use pin 8 for
the system VCC and pin 1 for the local VCC.

Pins 7 and 6 are not designed to be paralleled with other chips, and
pins 2 and 3 are designed to be connected to *other* pins 2 and 3 on
other boards, which means that the connections to pins 7 and 6 are
always local.

I2C pins sink to ground and have a resistive pullup to the supply
voltage.  However, there is no guarantee that any chip can tolerate an
input voltage greater than its power supply voltage.  Thus you need a
voltage level translator between systems with different supply
voltages.

This is how I have the chips connected, and it works properly.  Check
the data sheets (NXP) for the details and the backup information.

Harvey


>
>On Thu, Oct 22, 2015 at 9:12 PM, Harvey White 
>wrote:
>
>> On Thu, 22 Oct 2015 17:48:01 -0700 (PDT), you wrote:
>>
>> >Hello,
>> >
>> >I purchased a SainSmart LCD2004, which I believe is a hd44780 LCD with an
>> >i2c module pre-soldered to the back of the board.  This board is designed
>> >for an Arduino, but I wanted to try using it on my Beaglebone.  Is this
>> >doomed to fail?
>>
>> Not necessarily so.  It depends on what the I2C module is.  You will
>> need to know what the I2C commands to the module happen to be, that is
>> one thing.  The known commands for the 44780 are likely to be easy to
>> get.  The module I don't know anything about.
>>
>> >
>> >Following a few online guides, I have the SDA and SDL pins, as well as the
>> >5v and ground pins attached (with a resistor).  I've tried endless python
>> >scripts and libraries, being careful to configure each to use the
>> addresses
>> >that i2cdetect is showing.  Upon running some of the scripts, the LCD
>> >actually blinks.  I tried to go the LCDd route, but no luck with that
>> >either.  The LCD backlight goes on, but no text.
>>
>> The backlight goes on most likely because there's 5 volts on the
>> display.  The uninitialized display shows a sequence of square blocks
>> on line 1 (and nothing on line 2).
>>
>> The SDA and SCL pins need to go to 5 volts through a resistor (each
>> line independently).  The resistor values are generally between about
>> 4.7K and 10K.
>>
>> What I don't know (and you need to check) is whether or not the BBB's
>> I2C system runs from 3.3 volts or 5.0 volts.  If 5.0 volts AND the LCD
>> display I2C runs from 5 volts, then you can connect them directly.  If
>> the LCD and BBB run on 3.3 volts (for the interface), then they can be
>> connected directly.  IF they are not the same, then you need a chip
>> (I'd recommend the PCA9517) to connect the two.  This chip allows
>> dealing with different supply voltages (such as 3.3 and 5.0).
>>
>> I use this chip in systems I design.  Typically, the processor I/O is
>> at 3.3 volts (even the I2C pins), and the system level is 5.0 volts.
>> Thus, I need a chip on each board to the system interface.  For a 5.0
>> volt system, I still use the chip because it provides isolation
>> (there's a limit on current, cable length (related to capacitive
>> loading) and capacitive loading on each driver; check the specs.)
>>
>> You might want to look at these issues, they're reasonably easy to
>> fix.
>>
>> Harvey
>>
>>
>> >
>> >If I'm in the wrong Forum, or missing something simple, let me know.   I
>> >can expand on anything that I've tried.
>> >
>> >A little background - I'm a competent Linux user, so running tools and
>> >banging together scripts is the easy part for me.  The connecting the
>> >electronic components has been the learning part of this journey.
>> >
>> >Many thanks.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You rec

Re: [beagleboard] Re: BBK - pwmchip inconsistencies

2015-10-22 Thread Pierre-Louis Constant 
Hi William , TJF, 

Digging into the directories, I found a solution.

WARNING : It's only for kernel 4.1.6 with the newest debian 8.2 image from 
the mighty Robert Nelson. The device tree has been a bit modified according 
to https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-pwm

It's a bit ugly but it works. With reference to that page 
http://klaus.ede.hih.au.dk/index.php/BBB_Enabling_PWM : 

Looking for address 4830 in the memory map, you'll find this is in the 
> L4_PER block, and this is listed as the “PWM subsystem 0″, and 48300200 is 
> the EHR0 PWM channel and 48300100 the eCAP0 PWM. Also, address 4830200 is 
> the “PWM subsystem 1″, and address 4830400 is the “PWM subsystem 2″. 


If I list /sys/devices/platform/ocp/subsystem/devices, I get a list of 
symbolic links :

debian@arm:~$ ls /sys/devices/platform/ocp/subsystem/devices/
4030.ocmcram 4820.interrupt-controller  ocp:P8_10_pinmux
44d0.wkup_m3 4830.epwmssocp:P8_11_pinmux
44e0.prcm48300100.ecap  ocp:P8_12_pinmux
44e07000.gpio48300180.eqep  ocp:P8_13_pinmux
44e09000.serial  48300200.ehrpwmocp:P8_14_pinmux
44e0b000.i2c 48302000.epwmssocp:P8_15_pinmux
44e1.scm 48302180.eqep  ocp:P8_16_pinmux
44e1.scm_conf48302200.ehrpwmocp:P8_17_pinmux
44e10620.control 48304000.epwmssocp:P8_18_pinmux
44e10650.cpsw-phy-sel48304100.ecap  ocp:P8_19_pinmux
44e10800.pinmux  48304180.eqep  ocp:P8_26_pinmux
44e11324.wkup_m3_ipc 48304200.ehrpwmocp:P9_11_pinmux
44e35000.wdt 4830e000.lcdc  ocp:P9_12_pinmux
44e3e000.rtc 4831.rng   ocp:P9_13_pinmux
4740.dma-controller  4900.edma  ocp:P9_14_pinmux
4740.usb 4a10.ethernet  ocp:P9_15_pinmux
47401300.usb-phy 4a101000.mdio  ocp:P9_16_pinmux
47401400.usb 4a30.pruss ocp:P9_17_pinmux
47401b00.usb-phy 4a334000.pru0  ocp:P9_18_pinmux
47401c00.usb 4a338000.pru1  ocp:P9_21_pinmux
48022000.serial  4c00.emif  ocp:P9_22_pinmux
48024000.serial  5310.sham  ocp:P9_23_pinmux
4802a000.i2c 5350.aes   ocp:P9_24_pinmux
4803.spi 5600.sgx   ocp:P9_26_pinmux
48038000.mcasp   alarmtimer ocp:P9_27_pinmux
48042000.timer   bone_capemgr   ocp:P9_30_pinmux
48044000.timer   clk_mcasp0 ocp:P9_42_pinmux
48046000.timer   clk_mcasp0_fixed   ocp:P9_91_pinmux
48048000.timer   cpufreq-voltdm.0   omap-pcm-audio
4804a000.timer   edma-dma-engine.0  oprofile-perf.0
4804c000.gpiofixedregulator@0   pm33xx.0
4806.mmc hdmi   pmu
480c8000.mailbox hdmi_audio@0   reg-dummy
480ca000.spinlockleds   serial8250
4819c000.i2c musb-hdrc.0.auto   snd-soc-dummy
481a.spi musb-hdrc.1.auto   soc
481a8000.serial  ocpsoc:mpu
481ac000.gpioocp:cape-universal sound
481ae000.gpioocp:l4_wkup@44c0   tps65217-bl
481cc000.can ocp:P8_07_pinmux   tps65217-pmic
481d.can ocp:P8_08_pinmux
481d8000.mmc ocp:P8_09_pinmux


I can from there list the directory according to the memory address from 
the Sitara SRM.  For instance 48300200.ehrpwm.

debian@arm:/sys/devices/platform/ocp/subsystem/devices/48300200.ehrpwm/pwm$ 
ls
pwmchip0


>From there on , I can determine the pwmchip number attributed at boot time. 

As TJF mentioned, there are two channels per EHRPWM, and it's a matter of 
echo 0 or 1 to .../pwmchip0/export as before (o for channel A , 1 for 
channel B).

Programmatically,  I ended up modifying the library from 
https://github.com/SaadAhmad/beaglebone-black-cpp-PWM 
. 

There are a few things that were needed, but the core of the solution looks 
like that : 

Enter code here...void InitPinFS()
{
LoadDeviceTreeModule(std::string("cape-universaln")); //Modified 
for kernel 4.1.6 and cape-universaln
//std::string pinModule = std::string("sc_pwm_") + GetPinName();
//LoadDeviceTreeModule(pinModule);

//Find chip name
std::string m_chipAddress;
std::string m_pwmNumber;
//EHRPWM0A
if (m_pinName == "P9_22" || m_pinName == "P9_31") {

Re: [beagleboard] Sainsmart LCD2004 with Beaglebone Black

2015-10-22 Thread Joshua Lebo 
Ah, if you are referring to a logic level converter, I had ordered one but
wasn't sure if that was what I needed.  I'll read more on how to use it,
and try that.  Thank you.

On Thu, Oct 22, 2015 at 9:12 PM, Harvey White 
wrote:

> On Thu, 22 Oct 2015 17:48:01 -0700 (PDT), you wrote:
>
> >Hello,
> >
> >I purchased a SainSmart LCD2004, which I believe is a hd44780 LCD with an
> >i2c module pre-soldered to the back of the board.  This board is designed
> >for an Arduino, but I wanted to try using it on my Beaglebone.  Is this
> >doomed to fail?
>
> Not necessarily so.  It depends on what the I2C module is.  You will
> need to know what the I2C commands to the module happen to be, that is
> one thing.  The known commands for the 44780 are likely to be easy to
> get.  The module I don't know anything about.
>
> >
> >Following a few online guides, I have the SDA and SDL pins, as well as the
> >5v and ground pins attached (with a resistor).  I've tried endless python
> >scripts and libraries, being careful to configure each to use the
> addresses
> >that i2cdetect is showing.  Upon running some of the scripts, the LCD
> >actually blinks.  I tried to go the LCDd route, but no luck with that
> >either.  The LCD backlight goes on, but no text.
>
> The backlight goes on most likely because there's 5 volts on the
> display.  The uninitialized display shows a sequence of square blocks
> on line 1 (and nothing on line 2).
>
> The SDA and SCL pins need to go to 5 volts through a resistor (each
> line independently).  The resistor values are generally between about
> 4.7K and 10K.
>
> What I don't know (and you need to check) is whether or not the BBB's
> I2C system runs from 3.3 volts or 5.0 volts.  If 5.0 volts AND the LCD
> display I2C runs from 5 volts, then you can connect them directly.  If
> the LCD and BBB run on 3.3 volts (for the interface), then they can be
> connected directly.  IF they are not the same, then you need a chip
> (I'd recommend the PCA9517) to connect the two.  This chip allows
> dealing with different supply voltages (such as 3.3 and 5.0).
>
> I use this chip in systems I design.  Typically, the processor I/O is
> at 3.3 volts (even the I2C pins), and the system level is 5.0 volts.
> Thus, I need a chip on each board to the system interface.  For a 5.0
> volt system, I still use the chip because it provides isolation
> (there's a limit on current, cable length (related to capacitive
> loading) and capacitive loading on each driver; check the specs.)
>
> You might want to look at these issues, they're reasonably easy to
> fix.
>
> Harvey
>
>
> >
> >If I'm in the wrong Forum, or missing something simple, let me know.   I
> >can expand on anything that I've tried.
> >
> >A little background - I'm a competent Linux user, so running tools and
> >banging together scripts is the easy part for me.  The connecting the
> >electronic components has been the learning part of this journey.
> >
> >Many thanks.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/4LoTzFAwzxg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Sainsmart LCD2004 with Beaglebone Black

2015-10-22 Thread Harvey White 
On Thu, 22 Oct 2015 17:48:01 -0700 (PDT), you wrote:

>Hello,
>
>I purchased a SainSmart LCD2004, which I believe is a hd44780 LCD with an 
>i2c module pre-soldered to the back of the board.  This board is designed 
>for an Arduino, but I wanted to try using it on my Beaglebone.  Is this 
>doomed to fail?

Not necessarily so.  It depends on what the I2C module is.  You will
need to know what the I2C commands to the module happen to be, that is
one thing.  The known commands for the 44780 are likely to be easy to
get.  The module I don't know anything about.

>
>Following a few online guides, I have the SDA and SDL pins, as well as the 
>5v and ground pins attached (with a resistor).  I've tried endless python 
>scripts and libraries, being careful to configure each to use the addresses 
>that i2cdetect is showing.  Upon running some of the scripts, the LCD 
>actually blinks.  I tried to go the LCDd route, but no luck with that 
>either.  The LCD backlight goes on, but no text.

The backlight goes on most likely because there's 5 volts on the
display.  The uninitialized display shows a sequence of square blocks
on line 1 (and nothing on line 2).

The SDA and SCL pins need to go to 5 volts through a resistor (each
line independently).  The resistor values are generally between about
4.7K and 10K.

What I don't know (and you need to check) is whether or not the BBB's
I2C system runs from 3.3 volts or 5.0 volts.  If 5.0 volts AND the LCD
display I2C runs from 5 volts, then you can connect them directly.  If
the LCD and BBB run on 3.3 volts (for the interface), then they can be
connected directly.  IF they are not the same, then you need a chip
(I'd recommend the PCA9517) to connect the two.  This chip allows
dealing with different supply voltages (such as 3.3 and 5.0).

I use this chip in systems I design.  Typically, the processor I/O is
at 3.3 volts (even the I2C pins), and the system level is 5.0 volts.
Thus, I need a chip on each board to the system interface.  For a 5.0
volt system, I still use the chip because it provides isolation
(there's a limit on current, cable length (related to capacitive
loading) and capacitive loading on each driver; check the specs.)

You might want to look at these issues, they're reasonably easy to
fix.

Harvey


>
>If I'm in the wrong Forum, or missing something simple, let me know.   I 
>can expand on anything that I've tried.
>
>A little background - I'm a competent Linux user, so running tools and 
>banging together scripts is the easy part for me.  The connecting the 
>electronic components has been the learning part of this journey.
>
>Many 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Sainsmart LCD2004 with Beaglebone Black

2015-10-22 Thread Joshua Lebo 
Hello,

I purchased a SainSmart LCD2004, which I believe is a hd44780 LCD with an 
i2c module pre-soldered to the back of the board.  This board is designed 
for an Arduino, but I wanted to try using it on my Beaglebone.  Is this 
doomed to fail?

Following a few online guides, I have the SDA and SDL pins, as well as the 
5v and ground pins attached (with a resistor).  I've tried endless python 
scripts and libraries, being careful to configure each to use the addresses 
that i2cdetect is showing.  Upon running some of the scripts, the LCD 
actually blinks.  I tried to go the LCDd route, but no luck with that 
either.  The LCD backlight goes on, but no text.

If I'm in the wrong Forum, or missing something simple, let me know.   I 
can expand on anything that I've tried.

A little background - I'm a competent Linux user, so running tools and 
banging together scripts is the easy part for me.  The connecting the 
electronic components has been the learning part of this journey.

Many 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet is unable to receive packets, but is able to send packets. Any help on how to fix this?

2015-10-22 Thread Przemek Klosowski 
Your BBB has two interfaces, usb0 and eth0. It looks like you're connected
via USB, presumably to your PC, but the wired ethernet interface eth0 is up
too, and the routing matches on both, so the packets could be leaving
through both interfaces. I assume you don't have the wired network
connected, so the reason you're not getting a reply is either because your
PC is not set up to route the USB out via its own uplink.
Why would that be? we don't know because you didn't say what's your
environment--you have to specify what are you running on your BBB and on
your PC, and how you've set it up.

On Thu, Oct 22, 2015 at 5:34 PM,  wrote:

>
> root@beaglebone:~# ping google.com
> PING google.com (4.35.21.173) 56(84) bytes of data.
> ping 169.254.136.128
> ^C
> --- google.com ping statistics ---
> 175 packets transmitted, 0 received, 100% packet loss, time 174012ms
>
>
>
>
> root@beaglebone:/# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 0.0.0.0 192.168.7.1 0.0.0.0 UG0  00
> usb0
> 0.0.0.0 134.74.185.50   0.0.0.0 UG0  00
> eth0
> 134.74.185.00.0.0.0 255.255.255.0   U 0  00
> eth0
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0
>
>
>
> root@beaglebone:/# ifconfig
> eth0  Link encap:Ethernet  HWaddr d0:5f:b8:f5:93:cd
>   inet addr:134.74.185.104  Bcast:134.74.185.255
>  Mask:255.255.255.0
>   inet6 addr: fe80::d25f:b8ff:fef5:93cd/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:7577 errors:0 dropped:5 overruns:0 frame:0
>   TX packets:657 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:910737 (889.3 KiB)  TX bytes:68224 (66.6 KiB)
>   Interrupt:40
>
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> usb0  Link encap:Ethernet  HWaddr 56:ec:45:ea:75:d9
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   inet6 addr: fe80::54ec:45ff:feea:75d9/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:3642 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2046 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:361627 (353.1 KiB)  TX bytes:324515 (316.9 KiB)
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Ethernet is unable to receive packets, but is able to send packets. Any help on how to fix this?

2015-10-22 Thread pvmerisier 

root@beaglebone:~# ping google.com
PING google.com (4.35.21.173) 56(84) bytes of data.
ping 169.254.136.128
^C
--- google.com ping statistics ---
175 packets transmitted, 0 received, 100% packet loss, time 174012ms




root@beaglebone:/# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse 
Iface
0.0.0.0 192.168.7.1 0.0.0.0 UG0  00 usb0
0.0.0.0 134.74.185.50   0.0.0.0 UG0  00 eth0
134.74.185.00.0.0.0 255.255.255.0   U 0  00 eth0
192.168.7.0 0.0.0.0 255.255.255.252 U 0   



root@beaglebone:/# ifconfig
eth0  Link encap:Ethernet  HWaddr d0:5f:b8:f5:93:cd
  inet addr:134.74.185.104  Bcast:134.74.185.255  Mask:255.255.255.0
  inet6 addr: fe80::d25f:b8ff:fef5:93cd/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:7577 errors:0 dropped:5 overruns:0 frame:0
  TX packets:657 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:910737 (889.3 KiB)  TX bytes:68224 (66.6 KiB)
  Interrupt:40

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb0  Link encap:Ethernet  HWaddr 56:ec:45:ea:75:d9
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::54ec:45ff:feea:75d9/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:3642 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2046 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:361627 (353.1 KiB)  TX bytes:324515 (316.9 KiB)

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBK - pwmchip inconsistencies

2015-10-22 Thread William Hermans 
Heya plc66,

Have you seen this yet ?
https://briancode.wordpress.com/2015/01/06/working-with-pwm-on-a-beaglebone-black/

Unfortunately I have yet to use PWMs on the BBB, so can not offer you any
first hand experience advice.

On Thu, Oct 22, 2015 at 8:42 AM, TJF  wrote:

> Hi!
>
> I don't know much about the sysfs PWM capabilities. But I know a bit about
> the AM335x CPU. It has three PWMSS subsystems, each has a PWM module, each
> has two outputs (A and B). So there're six PWM outputs in total. I guess
> this is what sysfs supports.
>
> Additionaly you can generate PWM pulse trains by the eCAP modules (also
> integrated in each PWMSS). AFAIK this isn't supported by sysfs (but
> libpruio  can handle that).
> Only two eCAP output pins are available on the BBB headers (P9_28 and
> P9_42). So you can have a maximum of eight PWM outputs at a time.
>
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: USB Hub freeze

2015-10-22 Thread Guido Paoluzi Cusani 
Forwarded to TI Sitara processors Linux\USB support, waiting for good news.
Sensitive to USB power levels\input noise?

On 22 October 2015 at 17:00, Davide Birra  wrote:

> Same problem here. BBB keeps on disconnecting my USB devices.
>
>
> Il giorno martedì 20 ottobre 2015 12:56:11 UTC+2, Guido Paoluzi Cusani ha
> scritto:
>>
>> My communication link:
>> BBB USB <-> USB2514B based USB hub <-> FTDI FT232
>> Abruptly fails for no evident reason (possibly EMI or other induced
>> noise... there is a vast evidence ( better say a lot of rumors ) of the BBB
>> USB being very sensitive all over the web).
>> uname -r output:
>> 4.1.10-ti-r21
>> dmesg output:
>> [ 4951.213705] usb 1-1.1: USB disconnect, device number 3
>> [ 4951.215742] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
>> disconnected from ttyUSB0
>> [ 4951.216492] ftdi_sio 1-1.1:1.0: device disconnected
>> [ 4951.458827] usb 1-1.1: new full-speed USB device number 5 using
>> musb-hdrc
>> [ 4951.538810] usb 1-1.1: device descriptor read/64, error -32
>> [ 4951.728815] usb 1-1.1: device descriptor read/64, error -32
>> [ 4951.918801] usb 1-1.1: new full-speed USB device number 6 using
>> musb-hdrc
>> [ 4951.998947] usb 1-1.1: device descriptor read/64, error -32
>> [ 4952.188807] usb 1-1.1: device descriptor read/64, error -32
>> [ 4952.378887] usb 1-1.1: new full-speed USB device number 7 using
>> musb-hdrc
>> [ 4952.798847] usb 1-1.1: device not accepting address 7, error -32
>> [ 4952.898825] usb 1-1.1: new full-speed USB device number 8 using
>> musb-hdrc
>> [ 4953.318766] usb 1-1.1: device not accepting address 8, error -32
>> [ 4953.325078] usb 1-1-port1: unable to enumerate USB device
>> the link doesn't recover unless the hub goes through a hardware reset or
>> a power OFF\ON cycle;
>> The hub appears to go in "Suspended Mode" when the problem arises.
>> I am wondering:
>> there is a Sitara Linux MUSB Issue with the USB_RESUME in AMSDK
>> 08.00.00.00: is the kernel 4.1.10-ti-r21 incorporating the workaround?
>> Any way I can software reset the hub from Linux?
>> Any hint on what is happening?
>> Thanks in advance for any help on this.
>>
>> Guido
>>
>>
>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/FAX9OLvLsdg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: USB Hub freeze

2015-10-22 Thread Davide Birra 
Same problem here. BBB keeps on disconnecting my USB devices.

Il giorno martedì 20 ottobre 2015 12:56:11 UTC+2, Guido Paoluzi Cusani ha 
scritto:
>
> My communication link:
> BBB USB <-> USB2514B based USB hub <-> FTDI FT232
> Abruptly fails for no evident reason (possibly EMI or other induced 
> noise... there is a vast evidence ( better say a lot of rumors ) of the BBB 
> USB being very sensitive all over the web).
> uname -r output:
> 4.1.10-ti-r21 
> dmesg output:  
> [ 4951.213705] usb 1-1.1: USB disconnect, device number 3
> [ 4951.215742] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now 
> disconnected from ttyUSB0
> [ 4951.216492] ftdi_sio 1-1.1:1.0: device disconnected
> [ 4951.458827] usb 1-1.1: new full-speed USB device number 5 using 
> musb-hdrc
> [ 4951.538810] usb 1-1.1: device descriptor read/64, error -32
> [ 4951.728815] usb 1-1.1: device descriptor read/64, error -32
> [ 4951.918801] usb 1-1.1: new full-speed USB device number 6 using 
> musb-hdrc
> [ 4951.998947] usb 1-1.1: device descriptor read/64, error -32
> [ 4952.188807] usb 1-1.1: device descriptor read/64, error -32
> [ 4952.378887] usb 1-1.1: new full-speed USB device number 7 using 
> musb-hdrc
> [ 4952.798847] usb 1-1.1: device not accepting address 7, error -32
> [ 4952.898825] usb 1-1.1: new full-speed USB device number 8 using 
> musb-hdrc
> [ 4953.318766] usb 1-1.1: device not accepting address 8, error -32
> [ 4953.325078] usb 1-1-port1: unable to enumerate USB device 
> the link doesn't recover unless the hub goes through a hardware reset or a 
> power OFF\ON cycle; 
> The hub appears to go in "Suspended Mode" when the problem arises.
> I am wondering:
> there is a Sitara Linux MUSB Issue with the USB_RESUME in AMSDK 
> 08.00.00.00: is the kernel 4.1.10-ti-r21 incorporating the workaround?
> Any way I can software reset the hub from Linux?
> Any hint on what is happening?
> Thanks in advance for any help on this.
>
> Guido
>  
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using two BeaglBoard with USB

2015-10-22 Thread Robert Nelson 
On Thu, Oct 22, 2015 at 5:12 AM, Mourad Elamra.  wrote:
> Hi,
> i´m using two BeagblBoard with my PC. i need to connected with USB. but
> everyone hav a USB Ip Address= 192.168.7.2
>
> how can i change the static Ip Address from one Board ?
>

Hi Mourad,

Depending on how old your root file system is:

cat /etc/dogtab

we recently added a script: /opt/scripts/boot/autoconfigure_usb0.sh

So in /etc/network/interfaces

You just need to change the *7* to *8* or (anything 1-255)


# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1

and on the next reboot,

/opt/scripts/boot/autoconfigure_usb0.sh

makes sure it's setup correctly..

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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBK - pwmchip inconsistencies

2015-10-22 Thread TJF 
Hi!

I don't know much about the sysfs PWM capabilities. But I know a bit about 
the AM335x CPU. It has three PWMSS subsystems, each has a PWM module, each 
has two outputs (A and B). So there're six PWM outputs in total. I guess 
this is what sysfs supports.

Additionaly you can generate PWM pulse trains by the eCAP modules (also 
integrated in each PWMSS). AFAIK this isn't supported by sysfs (but libpruio 
 can handle that). Only two eCAP 
output pins are available on the BBB headers (P9_28 and P9_42). So you can 
have a maximum of eight PWM outputs at a time.

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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] USB gadget g_multi and Windows host

2015-10-22 Thread Stephan Klatt 
Hi,

I was trying get the BBB (jessie, kernel 4.1.10-ti-r21, rcn-ee.net console 
Debian Image 2015-10-09) working as USB mass storage and network gadget 
using g_multi:
modprobe g_multi file=/var/local/usb_mass_storage.img

This works fine for Linux hosts, but Windows fails to install a driver. The 
problem is apparently that both modules usb_f_rndis and usb_f_ecm are 
configured in the kernel:

from https://www.kernel.org/doc/Documentation/usb/gadget_multi.txt:

> The only thing to worry is that the gadget has to have a single
> configuration so a dual RNDIS and CDC ECM gadget won't work unless you
> create a proper INF -- and of course, if you do submit it!
>
>
Is there a reason why both modules are enabled? Could usb_f_ecm be disabled 
by default so g_multi SHOULD work for Windows?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone black ADC via Bonescript slow? - how to improve or alternatives?

2015-10-22 Thread TJF 
Hi istvan!

libpruio  is designed to sample 
ADC at full speed (200 kHz). Accurate timing is available in measurement 
mode (MM, predefined number of samples) or ring buffer mode (RB, continous 
sampling).

The library is coded in FreeBASIC. Somebody worked on a JavaScript binding, 
but I don't know the current state.

C / C++ bindings and examples are included in the package.

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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot get audio over HDMI working

2015-10-22 Thread Gerald Coley 
http://www.elinux.org/Beagleboard:BeagleBoneBlack_HDMI#Supported_Resolutions

Gerald

On Thu, Oct 22, 2015 at 8:37 AM, Jonathan Smith 
wrote:

> Strange, as I get audio over HDMI just fine.  If I recall though it has
> something to do with not being able to do 1920x1080 at full 60HZ, and still
> do audio, seems like it was 40 or something.  I'd have to dig through the
> archives a bit for that.
>
> On Thu, Oct 22, 2015 at 7:35 AM, Bill Pretty 
> wrote:
>
>> I believe that is because there is no onboard audio codec on the BBB as
>> there is on RaspberryPi.
>>
>>
>>
>> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
>> *On Behalf Of *h1449057trbvm...@gmail.com
>> *Sent:* Wednesday, October 21, 2015 9:44 PM
>> *To:* BeagleBoard
>> *Subject:* [beagleboard] Cannot get audio over HDMI working
>>
>>
>>
>> I'm trying to get audio to come out over my HDMI connection to my
>> television.
>> The video over HDMI works fine.
>> I've read through http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI and
>> tried both of the listed resolutions that support audio.  I tried each
>> (separately) by adding
>> "optargs=video=HDMI-A-1:1280x720@60" to /boot/uEnv.txt and I can see a
>> change in the displayed resolution when I reboot, but no audio.
>> I started with the 2015-03-01 Debian image from
>> beagleboard.org/latest-images and have been adding packages to it using
>> apt-get.  "uname -r" reports "3.8.13-bone70"
>> For testing I'm using mplayer and a FLV video file I know has sound when
>> I play it on my other computers.
>>
>> Not sure what else to try as I am far from a Linux guru and Google
>> searches either produce people saying it cannot be done or people who say
>> it is super easy (but don't explain how they got it to work).
>>
>> I do know that when I run the fbset command I get
>> debian@beaglebone:~$ fbset
>>
>> mode "1920x1080"
>> geometry 1920 1080 1920 1080 16
>> timings 0 0 0 0 0 0 0
>> accel true
>> rgba 5/11,6/5,5/0,0/0
>> endmode
>>
>> which does not appear to list any EDID information, but I don't know what
>> (if anything) I can do about that.
>>
>> Ideas?
>>
>> -Will
>>
>> --
>> 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.
>> 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.
>> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot get audio over HDMI working

2015-10-22 Thread Jonathan Smith 
Strange, as I get audio over HDMI just fine.  If I recall though it has
something to do with not being able to do 1920x1080 at full 60HZ, and still
do audio, seems like it was 40 or something.  I'd have to dig through the
archives a bit for that.

On Thu, Oct 22, 2015 at 7:35 AM, Bill Pretty 
wrote:

> I believe that is because there is no onboard audio codec on the BBB as
> there is on RaspberryPi.
>
>
>
> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
> *On Behalf Of *h1449057trbvm...@gmail.com
> *Sent:* Wednesday, October 21, 2015 9:44 PM
> *To:* BeagleBoard
> *Subject:* [beagleboard] Cannot get audio over HDMI working
>
>
>
> I'm trying to get audio to come out over my HDMI connection to my
> television.
> The video over HDMI works fine.
> I've read through http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI and
> tried both of the listed resolutions that support audio.  I tried each
> (separately) by adding
> "optargs=video=HDMI-A-1:1280x720@60" to /boot/uEnv.txt and I can see a
> change in the displayed resolution when I reboot, but no audio.
> I started with the 2015-03-01 Debian image from
> beagleboard.org/latest-images and have been adding packages to it using
> apt-get.  "uname -r" reports "3.8.13-bone70"
> For testing I'm using mplayer and a FLV video file I know has sound when I
> play it on my other computers.
>
> Not sure what else to try as I am far from a Linux guru and Google
> searches either produce people saying it cannot be done or people who say
> it is super easy (but don't explain how they got it to work).
>
> I do know that when I run the fbset command I get
> debian@beaglebone:~$ fbset
>
> mode "1920x1080"
> geometry 1920 1080 1920 1080 16
> timings 0 0 0 0 0 0 0
> accel true
> rgba 5/11,6/5,5/0,0/0
> endmode
>
> which does not appear to list any EDID information, but I don't know what
> (if anything) I can do about that.
>
> Ideas?
>
> -Will
>
> --
> 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.
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Cannot get audio over HDMI working

2015-10-22 Thread Bill Pretty 
I believe that is because there is no onboard audio codec on the BBB as there 
is on RaspberryPi.

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of h1449057trbvm...@gmail.com
Sent: Wednesday, October 21, 2015 9:44 PM
To: BeagleBoard
Subject: [beagleboard] Cannot get audio over HDMI working

 

I'm trying to get audio to come out over my HDMI connection to my television.
The video over HDMI works fine.
I've read through http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI and tried 
both of the listed resolutions that support audio.  I tried each (separately) 
by adding
"optargs=video=HDMI-A-1:1280x720@60" to /boot/uEnv.txt and I can see a change 
in the displayed resolution when I reboot, but no audio.
I started with the 2015-03-01 Debian image from beagleboard.org/latest-images 
and have been adding packages to it using apt-get.  "uname -r" reports 
"3.8.13-bone70"
For testing I'm using mplayer and a FLV video file I know has sound when I play 
it on my other computers.

Not sure what else to try as I am far from a Linux guru and Google searches 
either produce people saying it cannot be done or people who say it is super 
easy (but don't explain how they got it to work).

I do know that when I run the fbset command I get
debian@beaglebone:~$ fbset

mode "1920x1080"
geometry 1920 1080 1920 1080 16
timings 0 0 0 0 0 0 0
accel true
rgba 5/11,6/5,5/0,0/0
endmode

which does not appear to list any EDID information, but I don't know what (if 
anything) I can do about that.

Ideas?

-Will

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone black ADC via Bonescript slow? - how to improve or alternatives?

2015-10-22 Thread istvan 
 Dear Community, 


I am trying to read the analog inputs of a BegaleBoneBlack. So, I have 
taken the obvious route: to use BoneScript (as it gives me a read function 
straight away). My code is:

var b = require('bonescript');
var myReadTask;
var myStoreBuffer = [];

function readVoltage(){
b.analogRead("P9_36", saveValue)
}


function saveValue(reading){
var vv = reading.value*1.8;
myStoreBuffer[myStoreBuffer.length] = vv;
}


function startMyTasks(){
myReadTask = setInterval(readVoltage,1);
}

function stopMyTasks(){
clearInterval(myReadTask);
}

function finalStage(){
console.log("Number of elements logged = " + myStoreBuffer.length);
}


setTimeout(startMyTasks, 1000);
setTimeout(stopMyTasks, 1100);
setTimeout(finalStage, 1200);



--

Now this does work, but it obviously reads very slowly, because instead of 
the expected 100 values ( reading should be called every 1 ms, for 100ms 
total running time), I only get 6 or 7. Thus the reading speed is hell of a 
lot slower than the expected 125ns per read. 

  My question is: is there a way to improve this via BoneScript --- or is 
there some easy alternative? 

  I have seen quite a few posts on the topic on the forum, but most are 
quite advanced -- and I am lacking some detailed descriptions/explanations. 
 Is there some easier way for someone who does know 
C++/C#/Java/JavaScript/LabView/Matlab ... but is quite new into hardware 
close issues like this? 

  My final goal is to have something like a producer-consumer system: the 
BBB should read analog data as fast as possible (but at defined rate) --- 
while my PC would run some code to get the data back from the bone (over 
USB/Ethernet/whatever is best..)

  Any ideas? 

 Thanks a lot!


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBK - pwmchip inconsistencies

2015-10-22 Thread plc66 . aus 
Hello everyone, 

I have come across a problem on the BBK (Debian 8.2 , 2015-09-11 release) 
and would be very grateful for a bit of an explanation. 

I need to work with the PWMs and therefore I have developed a little ugly 
script in order to work with config-pin.sh 
(https://github.com/cdsteinkuehler/beaglebone-universal-io) and then export 
the pwmchip. Down the line I'd like to to have the script running at 
start-up, prior to launching a executable.

The cape-universaln overlay is applied. The script goes as follow : 

#!/bin/bash


echo "Configuring pins"

sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P9.22 pwm'
sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P9.21 pwm'
sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P9.14 pwm'
sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P9.16 pwm'
sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P8.19 pwm'
sudo sh -c '/home/debian/beaglebone-universal-io/config-pin P8.13 pwm'

echo "Export pins"
if sudo sh -c 'echo "0" > /sys/class/pwm/pwmchip0/export' ; then
echo "pwmchip0:pwm0 exported"
else echo "pwmchip0:pwm0 export failed"
fi

if sudo sh -c 'echo "1" > /sys/class/pwm/pwmchip0/export' ; then
echo "pwmchip0:pwm1 exported"
else echo "pwmchip0:pwm1 export failed"
fi

if sudo sh -c 'echo "0" > /sys/class/pwm/pwmchip1/export'; then
echo "pwmchip1:pwm0 exported"
else echo "pwmchip1:pwm0 export failed"
fi

if sudo sh -c 'echo "1" > /sys/class/pwm/pwmchip1/export' ; then
echo "pwmchip1:pwm1 exported"
else echo "pwmchip1:pwm1 export failed"
fi
 
if sudo sh -c 'echo "0" > /sys/class/pwm/pwmchip2/export'; then
echo "pwmchip2:pwm0 exported"
else echo "pwmchip2:pwm0 export failed"
fi

if sudo sh -c 'echo "1" > /sys/class/pwm/pwmchip2/export'; then
echo "pwmchip2:pwm1 exported"
else echo "pwmchip2:pwm1 export failed"
fi

if sudo sh -c 'echo "0" > /sys/class/pwm/pwmchip4/export'; then
echo "pwmchip4:pwm0 exported"
else echo "pwmchip4:pwm0 export failed"
fi

if sudo sh -c 'echo "1" > /sys/class/pwm/pwmchip4/export'; then
echo "pwmchip4:pwm1 exported"
else echo "pwmchip4:pwm1 export failed"
fi

if sudo sh -c 'echo "0" > /sys/class/pwm/pwmchip6/export'; then
echo "pwmchip6:pwm0 exported"
else echo "pwmchip6:pwm0 export failed"
fi

if sudo sh -c 'echo "1" > /sys/class/pwm/pwmchip6/export'; then
echo "pwmchip6:pwm1 exported"
else echo "pwmchip6:pwm1 export failed"
fi



I was happily drinking my 10th coffee when i noticed the following:

First boot: 

debian@arm:~$ cd /sys/class/pwm/
debian@arm:/sys/class/pwm$ ls
pwmchip0  pwmchip2  pwmchip4  pwmchip5  pwmchip6

Second boot:

debian@arm:~$ cd /sys/class/pwm/
debian@arm:/sys/class/pwm$ ls
pwmchip0  pwmchip1  pwmchip2  pwmchip4  pwmchip6

Firstly the result of my little script gives me a total of 7 successfully 
exported pwms. Shouldn't there be 8 ???

Secondly the numbering of the pwmchips is not consistent, and it is going 
to cause some issues when I develop the following C++ part. 

Any idea ?


Thanks in advance.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cannot get audio over HDMI working

2015-10-22 Thread h1449057trbvmcom 
I'm trying to get audio to come out over my HDMI connection to my 
television.
The video over HDMI works fine.
I've read through http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI and 
tried both of the listed resolutions that support audio.  I tried each 
(separately) by adding
"optargs=video=HDMI-A-1:1280x720@60" to /boot/uEnv.txt and I can see a 
change in the displayed resolution when I reboot, but no audio.
I started with the 2015-03-01 Debian image from 
beagleboard.org/latest-images and have been adding packages to it using 
apt-get.  "uname -r" reports "3.8.13-bone70"
For testing I'm using mplayer and a FLV video file I know has sound when I 
play it on my other computers.

Not sure what else to try as I am far from a Linux guru and Google searches 
either produce people saying it cannot be done or people who say it is 
super easy (but don't explain how they got it to work).

I do know that when I run the fbset command I get
debian@beaglebone:~$ fbset

mode "1920x1080"
geometry 1920 1080 1920 1080 16
timings 0 0 0 0 0 0 0
accel true
rgba 5/11,6/5,5/0,0/0
endmode

which does not appear to list any EDID information, but I don't know what 
(if anything) I can do about that.

Ideas?

-Will

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using two BeaglBoard with USB

2015-10-22 Thread Mourad Elamra. 
Hi,
i´m using two BeagblBoard with my PC. i need to connected with USB. but 
everyone hav a USB Ip Address= 192.168.7.2

how can i change the static Ip Address from one Board ?

Thanks very mush 

-- 
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.
For more options, visit https://groups.google.com/d/optout.