RE: [beagleboard] Re: Mesh on BBBW

2017-10-27 Thread Iain Hunter
Hi Jose, I’ve never used the build script with compat/backports on a 4.4 kernel. Only suggestion I can make is to work out what the actual build error is. Ie why is there a problem here /home/sensorfield/wl8-build/build-utilites/src/compat_wireless/compat/backport-4.4.c: In function ‘backport_

Re: [beagleboard] Duplex stream for reading and writing commands to /dev/rpmsg_pru31

2017-10-27 Thread Hugh Frater
I know the stream is transmitting OK, my PRU code reacts as expected to the messages I'm sending over. I'm going to look at the data in more detail over this weekend, I've been off this project for 10 days or so. I'm beginning to wonder if I fudge around this by using shared memory between the

Re: [beagleboard] Overlays and 4.14 Linux kernel for CAN

2017-10-27 Thread Robert Nelson
On Fri, Oct 27, 2017 at 10:59 AM, Tracy Smith wrote: > Need to enable DCAN1 and DCAN2 support for the BeagleBone Black. > > > 1) Are overlays supported by the 4.14 Linux kernel? You can use "U-Boot" overlays: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > 2) Where can I

Re: [beagleboard] Error in am335x-pocketbeagle.dts

2017-10-27 Thread Robert Nelson
On Fri, Oct 27, 2017 at 12:20 PM, Robert Nelson wrote: > Hi Philip, > > On Fri, Oct 27, 2017 at 12:14 PM, Philip Munts wrote: >> While testing a 7 Segment Click, I found an error in >> am335x-pocketbeagle.dts: The mode for P2_25 (SPI1 MOSI) should be 4 >> (spi1_d1), not 5 (spi1_cs0). >> >> @@ -6

Re: [beagleboard] Duplex stream for reading and writing commands to /dev/rpmsg_pru31

2017-10-27 Thread Nahuel Greco
Smells like the problem is at the nodejs side, maybe you can try not running the node program and cat'ing the device to see if the characters are shown. What's the value of the 'data' received in the callback? Saludos, Nahuel Greco. On Fri, Oct 27, 2017 at 11:05 AM, Hugh Frater wrote: > Hi Nah

Re: [beagleboard] Error in am335x-pocketbeagle.dts

2017-10-27 Thread Robert Nelson
Hi Philip, On Fri, Oct 27, 2017 at 12:14 PM, Philip Munts wrote: > While testing a 7 Segment Click, I found an error in > am335x-pocketbeagle.dts: The mode for P2_25 (SPI1 MOSI) should be 4 > (spi1_d1), not 5 (spi1_cs0). > > @@ -660,7 +660,7 @@ > > /* P2_25 (ZCZ ball E17) */ > P2_25_default_

[beagleboard] Error in am335x-pocketbeagle.dts

2017-10-27 Thread Philip Munts
While testing a 7 Segment Click, I found an error in am335x-pocketbeagle.dts: The mode for P2_25 (SPI1 MOSI) should be 4 (spi1_d1), not 5 (spi1_cs0). @@ -660,7 +660,7 @@ /* P2_25 (ZCZ ball E17) */ P2_25_default_pin: pinmux_P2_25_default_pin { pinctrl-single,pins = < - AM33XX_IOPAD(0x096c,

[beagleboard] Replace default iptables with ufw rules?

2017-10-27 Thread maxmike
I wanted to test removing all default iptable rules and replacing them with my own, using ufw. I have a very simple LAN that just needs 1/2 dozen ports, and iptable defaults are causing major conflicts when I try blocking IP's. So I created the ufw rule: *ufw allow 22/tcp* then I issued:

[beagleboard] Overlays and 4.14 Linux kernel for CAN

2017-10-27 Thread Tracy Smith
Need to enable DCAN1 and DCAN2 support for the BeagleBone Black. 1) Are overlays supported by the 4.14 Linux kernel? 2) Where can I find documentation on enabling CAN1 and CAN2 for the BeagleBone Black for the 4.x kernel? 3) If overlays are no longer supported, any documentation on enab

Re: [beagleboard] Duplex stream for reading and writing commands to /dev/rpmsg_pru31

2017-10-27 Thread Hugh Frater
Hi Nahuel, You can't cat the device file because linux doesn't allow concurrent access to the device file descriptor from more than one userspace program, and we need to open that device file from within our node.js program to write to the PRU. I do have a hardware UART looped back from the PRU

Re: [beagleboard] Re: Beagle Bone Black stopping at Starting Kernel....

2017-10-27 Thread Ashish Maurya
Hi all, Thanks for your replies and time. Problem got solved after properly understanding boot process and so many failed attempts. Problem was that /dev/mmcblk0p2 entry was not present in /etc/fstab of the rootfs for beaglebone-black Adding the entry mounted fs properly. *root@beaglebone:~# ca