Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Apr 27, 2017 9:17 PM, "William Hermans" wrote: On Thu, Apr 27, 2017 at 7:07 PM, Robert Nelson wrote: > > it's a pretty small patch: > > https://patchwork.kernel.org/patch/9177249/raw/ > > Documentation/pwm.txt |6 -- >

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 7:07 PM, Robert Nelson wrote: > > it's a pretty small patch: > > https://patchwork.kernel.org/patch/9177249/raw/ > > Documentation/pwm.txt |6 -- > drivers/pwm/sysfs.c | 15 --- > 2 files changed, 16 insertions(+), 5

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 7:16 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 5:06 PM, Robert Nelson > wrote: >> >> It's a little more then that, the first 0 comes from parent: >> >> /sys/class/pwm/pwmchip0/pwm-0:0 >> >>

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 5:06 PM, Robert Nelson wrote: > It's a little more then that, the first 0 comes from parent: > > /sys/class/pwm/pwmchip0/pwm-0:0 > > /sys/class/pwm/pwmchipA/pwm-A:B > > Right, with my implementation as it sits. pwm(x, y) where pwmchipx, -> pwmy. x

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 5:29 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 3:22 PM, William Hermans wrote: >> >> It'll break bonejs too, but I can live with that. Just an additional two >> characters in a string somewhere in my code. A few times .

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 3:22 PM, William Hermans wrote: > It'll break bonejs too, but I can live with that. Just an additional two > characters in a string somewhere in my code. A few times . . .hehe > Actually, it won't break my implementation at all. Just need to change how

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

It'll break bonejs too, but I can live with that. Just an additional two characters in a string somewhere in my code. A few times . . .hehe On Thu, Apr 27, 2017 at 3:18 PM, Robert Nelson wrote: > On Thu, Apr 27, 2017 at 5:15 PM, William Hermans >

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 5:15 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 3:12 PM, Robert Nelson > wrote: >> >> >> https://lkml.org/lkml/2016/6/14/967 >> > > Ouch, so sounds like a boot script hack is the only way right now ? Yay! That

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 3:15 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 3:12 PM, Robert Nelson > wrote: > >> >> https://lkml.org/lkml/2016/6/14/967 >> >> > Ouch, so sounds like a boot script hack is the only way right now ? > Sorry, did

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 5:08 PM, Robert Nelson wrote: > On Thu, Apr 27, 2017 at 5:04 PM, William Hermans wrote: >> >> >> On Thu, Apr 27, 2017 at 2:59 PM, William Hermans wrote: >>> >>> >>> >>> On Thu, Apr 27, 2017 at 2:56 PM, Robert

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 5:04 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 2:59 PM, William Hermans wrote: >> >> >> >> On Thu, Apr 27, 2017 at 2:56 PM, Robert Nelson >> wrote: >>> >>> On Thu, Apr 27, 2017 at 4:55 PM,

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 2:59 PM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 2:56 PM, Robert Nelson > wrote: > >> On Thu, Apr 27, 2017 at 4:55 PM, William Hermans >> wrote: >> > @Robert, >> >> it works for gpio... so i

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:55 PM, William Hermans wrote: > @Robert, > > I'm thinking at this point in time, that we may have to fall off the last > creation of files in that path, and do single file permission changes, would > would be tedious, and painful. So whatever the last

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

@Robert, I'm thinking at this point in time, that we may have to fall off the last creation of files in that path, and do single file permission changes, would would be tedious, and painful. So whatever the last path to be created, you run the udev rule off that, and just traverse down into the

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:50 PM, William Hermans wrote: > > On Thu, Apr 27, 2017 at 2:46 PM, Robert Nelson > wrote: >> >> On Thu, Apr 27, 2017 at 4:43 PM, William Hermans >> wrote: >> > Still having issues with PWM ? >> >> Yeah i

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:46 PM, William Hermans wrote: > By the way, I think the small amount I talked about udev, and permissions on > my git for bonejs. I pretty much got most of that information from rPI > content all over the web. I did have to make several modifications

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 2:46 PM, Robert Nelson wrote: > On Thu, Apr 27, 2017 at 4:43 PM, William Hermans > wrote: > > Still having issues with PWM ? > > Yeah i took a break from that, PWM was too painful.. > > Fixed an LCD and the

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:43 PM, William Hermans wrote: > Still having issues with PWM ? Yeah i took a break from that, PWM was too painful.. Fixed an LCD and the v4.4.x-bone/v4.4.x-rt-bone u-boot overlay problem some users where having.. So let's try the pwm with v4.9.x ;)

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

By the way, I think the small amount I talked about udev, and permissions on my git for bonejs. I pretty much got most of that information from rPI content all over the web. I did have to make several modifications though . .. On Thu, Apr 27, 2017 at 2:43 PM, William Hermans

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

Still having issues with PWM ? On Thu, Apr 27, 2017 at 2:41 PM, Robert Nelson wrote: > and inside one: > > debian@beaglebone:/sys/class/gpio/gpio2$ ls -lha > total 0 > drwxrwxr-x 3 root gpio0 Apr 27 21:38 . > drwxrwxr-x 16 root gpio0 Apr 27 21:38 .. >

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

and inside one: debian@beaglebone:/sys/class/gpio/gpio2$ ls -lha total 0 drwxrwxr-x 3 root gpio0 Apr 27 21:38 . drwxrwxr-x 16 root gpio0 Apr 27 21:38 .. -rw-rw-r-- 1 root gpio 4.0K Apr 27 21:38 active_low lrwxrwxrwx 1 root gpio0 Apr 27 21:38 device -> ../../../gpiochip0 -rw-rw-r--

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:39 PM, William Hermans wrote: > Wow, the Pine64 community is actually active ? hehe. . . Yeah i stole that from them.. with cape-universal/u0boot overlays/4.9.25-ti-r31.2 all came up root:gpio debian@beaglebone:/sys/class/gpio$ ls -lha total 0

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

Wow, the Pine64 community is actually active ? hehe. . . On Thu, Apr 27, 2017 at 2:35 PM, Robert Nelson wrote: > On Thu, Apr 27, 2017 at 4:27 PM, Metelko wrote: > > I used the following udev rule (similar to William Hermans, without the > >

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

On Thu, Apr 27, 2017 at 4:27 PM, Metelko wrote: > I used the following udev rule (similar to William Hermans, without the > pinmux/state changes using a new 'gpio' group). > > udev rule: > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio /sys/class/gpio; > chmod

Re: [beagleboard] Re: Reboot instead of shutdown

So now I'm in pitbull mode, but I wont be able to do any further research at this time. https://www.kernel.org/doc/Documentation/devicetree/bindings/usb/am33xx-usb.txt . . . USB ~~~ - compatible: ti,musb-am33xx - reg: offset and length of "USB Controller Registers", and offset and length of

Re: [beagleboard] Re: Reboot instead of shutdown

It would not be part of "my" FAQ. I have no affiliation with beagleboard.org, at all. I'm just some guy, who has had 4+ years hands on experience with this specific platform, who also just so happens to get paid by a third party who builds systems based on this platform as well. But obviously I do

Re: [beagleboard] Re: Reboot instead of shutdown

On Thu, Apr 27, 2017 at 7:26 PM, William Hermans wrote: > It's meant to impress on the point that the hardware was designed with > cost in mind, and that the software for this hardware is provided free of > charge. > I realize that. This is why I suggested a solution

Re: [beagleboard] Re: Depauperate Beagle Board Green

Andrea, Maybe this will solve your problem: https://www.adafruit.com/product/909 There are also panel mount USB pass through cables too. I'm not sure if adafruit has them, but if not amazon has them for sure. On Thu, Apr 27, 2017 at 9:59 AM, William Hermans wrote: > Seems I

Re: [beagleboard] Re: Reboot instead of shutdown

On Thu, Apr 27, 2017 at 9:53 AM, ithinu wrote: > Perhaps a work-around would be to provide a software possibility of > freezing the unit after the kernel is down. Handy for someone who has a > power-hungry cape requiring a power supply, no Ethernet and would like to >

Re: [beagleboard] Re: Depauperate Beagle Board Green

Seems I was not awake, enough, before I read the post. But was still good for a laugh while I was off in left field somewhere. But changing out ethernet, *AND* USB for DIP connectors is still odd to me. I'll just chalk that up to me not being an EE, and move on with my life. Andrea, OrCAD is a

[beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Thanks for all the replies. Reply to Przemek Klowoski = I agree it is almost certainly a serial buffer overflow somewhere. By filling and emptying the buffers between my code on the BBB and my code on the PC I can detect a 12KB buffer. I believe that this 12KB buffer

Re: [beagleboard] Re: Reboot instead of shutdown

Perhaps a work-around would be to provide a software possibility of freezing the unit after the kernel is down. Handy for someone who has a power-hungry cape requiring a power supply, no Ethernet and would like to safely replace the sd card. If it were possible to detect, that the unit is

Re: [beagleboard] Re: Reboot instead of shutdown

By the way those changes which I mentioned for the USB OTG port are made through device tree configurations. I think in the main board file, but that problem has been corrected so long ago, I do not remember exactly how. Here, we do not connect to our boards in this manner, ever.I have one

Re: [beagleboard] Re: Reboot instead of shutdown

On Thu, Apr 27, 2017 at 1:27 AM, ithinu wrote: > > Short story, you're using a powered hub, and you need to keep that hub > from sending power back into the host. > > No, the hub is not powered. Also, as I said, the problem exists only with > the combination power

Re: [beagleboard] Re: Depauperate Beagle Board Green

What do you mean?  -- 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

RE: [beagleboard] Re: Depauperate Beagle Board Green

It's a good start. If you can make these change you just help me 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,

Re: [beagleboard] Re: Depauperate Beagle Board Green

removing -> changing. On Thu, Apr 27, 2017 at 9:16 AM, William Hermans wrote: > > > On Thu, Apr 27, 2017 at 9:00 AM, Gerald Coley > wrote: > >> I could modify the DSN file, but I am on a diet, trying to cut back on >> all the free work I have been

Re: [beagleboard] Re: Depauperate Beagle Board Green

On Thu, Apr 27, 2017 at 9:00 AM, Gerald Coley wrote: > I could modify the DSN file, but I am on a diet, trying to cut back on all > the free work I have been doing lately. > > > > The DSN file is only the schematic, it will not change the PCB. > lol, you did better than

Re: [beagleboard] NHD-7.0CTP-CAPE-N no picture

Hi Robert I finaly got this image to boot and give me a picture. https://www.dropbox.com/s/n4hgu39ccskbl8c/ubuntu-14.04-3.8.img.gz?dl=0 it is one of the images that NHD links to in the user manual. I can't get it to flash to the eMMC though. but I gues that is a subject for another thread. I

RE: [beagleboard] Re: Depauperate Beagle Board Green

I could modify the DSN file, but I am on a diet, trying to cut back on all the free work I have been doing lately. The DSN file is only the schematic, it will not change the PCB. Gerald From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of Andrea Rondini Sent:

[beagleboard] How to use shared memory between PRU and ARM (in C): an example

Here's an example I'd like to make share: how to use shared memory between PRU and ARM using uio_pruss and prussdrv: http://catch22.eu/beaglebone/beaglebone-pru-ipc/ Feel free to comment here on this forum post. There's also a git repository

[beagleboard] no terminal on J1

HI, Is there a way to switch of the serial terminal on J1 ? Cos I connected a ftdi interface to the port and nothing happens. If I bridge the ftdi if ports 3 and 4 I get a nice echo. So that’s working fine. Immo -- For more options, visit http://beagleboard.org/discuss --- You received this

[beagleboard] Re: Depauperate Beagle Board Green

This all files i'm using: https://drive.google.com/open?id=0B0aOLjkeXaIMZFhjSUdHbmtlTTg Il giorno giovedì 27 aprile 2017 15:46:58 UTC+2, Andrea Rondini ha scritto: > > Hi to everyone. > I need your help, because I have to remove any connectors on the board. > Specifically, I have to create a

[beagleboard] Re: Depauperate Beagle Board Green

I've this version i've attached. Please can you help me to modify layout? https://drive.google.com/drive/folders/0B0aOLjkeXaIMZFhjSUdHbmtlTTg?usp=sharing Il giorno giovedì 27 aprile 2017 15:46:58 UTC+2, Andrea Rondini ha scritto: > > Hi to everyone. > I need your help, because I have to remove

RE: [beagleboard] Depauperate Beagle Board Green

You should have no issues with OrCad if you have the right revision. I need to know what revision of OrCAD you have. Can you tell me that? What PCB program are you using? Beagle was done in Allegro, not OrCAD PCB. Gerald From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]

[beagleboard] Depauperate Beagle Board Green

Hi to everyone. I need your help, because I have to remove any connectors on the board. Specifically, I have to create a board with DIP connectors instead of RJ45 connector, USB Power Connect, USB and external connectors. Can you help me? I have problems with OrCad. Every time I try to change an

RE: [beagleboard] Customize hardware BBG

What version OrAD do you have? Gerald From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of andrearondini1...@gmail.com Sent: Thursday, April 27, 2017 3:37 AM To: BeagleBoard Subject: [beagleboard] Customize hardware BBG Hi to

Re: [beagleboard] Enable UART1 in Jessie BBB.

> > > git clone https://github.com/beagleboard/bb.org-overlays > cd ./bb.org-overlays > > ./dtc-overlay.sh > ./install.sh > > sudo reboot > > After doing ./dtc-overlay.sh i am getting error on target board "dpkg" command not found Thanks, Raghavendra -- For more options, visit

[beagleboard] Exe runs with no errors except when as Startup service

Hello, I have written a whole cplusplus Ehe which I successfully and without errors are able to run as ./Program. But when I add it as startup script, a) getline continuously receiving empty cr lf. I disabled it by checking for empty chars, but why is this? B) after exactly 2.37min the exe

[beagleboard] Setup a Bluetooth SPP slave connection on BBBW

Hello everybody! I'm using for a few years now your BeagleBone Black board to create an embedded device communicating with an Android phone with Bluetooth SPP profile. To achieve that, I connected a bluetooth module to UART and I used to communicate with it directly addressing the

Re: [beagleboard] Enable UART1 in Jessie BBB.

> > Hi, We are using TI SDK 03.02.00.05 with Kernel 4.4.32 I didnt get /dev/ttyO* when i enabled UARTs in am335x-bone-common.dtsi and am33xx.dtsi files but im getting /dev/ttyS*. So how to get /dev/ttyO* . And how to usse overlays on latest kernel OR withought Overlay how can i test UARTs on

[beagleboard] Customize hardware BBG

Hi to everyone. We're a group of hard-working guys in the hardware world. Anyway, we use some OrCad software. We need to modify a Beagle Board Green. We have to insert DIP connectors instead of the normal RJ45 and USB connectors. Can anyone help us solve this problem? Apparently OrCad is hostile

[beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot.

If you have this problem and only care about solutions, jump to "workarounds" below. ### RECAP For unlucky souls who come fresh upon this problem and down want to read though a better part of a decade's worth of conflicting reports 1. Due to a design issue, the BeagleBone Black and

[beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot.

This one: Hi All, After removing C24 and C30 (next to the large unpopulated 20-pin header P2 on the bottom of the board) we ran 1000 power cycles and had a 100% success rate - i.e. board booted and phy detected every time. We used a programmable power supply and some scripts processing the uart

[beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot.

FYI: The hardware fix described earlier in this thread give 100% success, first time, every time. On 27 April 2017 at 15:42, wrote: > If you have this problem and only care about solutions, jump to > "workarounds" below. > > ### RECAP > > For unlucky souls who come fresh upon

[beagleboard] Re: BBB ssh ro...@192.168.7.2 : connection refused.

Though obscure, I am unsure if this is related to the issue I highlighted here[1]. I would suggest connecting a console cable and see if there is any output during boot. Thanks. --Luther [1]https://groups.google.com/d/msg/beagleboard/ritwRgywoUY/9XCJFJ6aAgAJ On Tuesday, April 25, 2017 at

Re: [beagleboard] Re: Reboot instead of shutdown

> Short story, you're using a powered hub, and you need to keep that hub from sending power back into the host. No, the hub is not powered. Also, as I said, the problem exists only with the combination power supply/usb connection, which I rarely need. But it still can be a problem of someone

[beagleboard] Error: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!

I had a successful boot on my BBB, and then managed to login, but then device started hanging. I plugged in the serial console cable and saw the below error in the console. After some time, maybe about 5 min, the system un-hung. Kernel version: 4.4.54-ti-r93. Appreciate if there are any