Hi' Ive got 10 BBBW all pretty close together connected over WiFi, and set
to use a fixed IP, or direct front access with USB-Ethernet .
However they re all still advertising on WiFi and visible next to Corp
network.
I can change the SSID BeagleBone- - thanks to a previous message from
/etc/d
I wonder if anybody has some good success with fixing a static IP on a
BBBW/4.14.49-ti-r54 IotVersion. I'm getting very mixed results. After
running 4 BBBW for a week, two have retained their IP and two have lost
their IP as shown by ifconfig.
I've a requirement to operate 10 of them all in the sam
Mark A. Yoder
Fri, Aug 17, 7:58 AM
to BeagleBoard
The PRU cookbook is nearing completion (more accurately, I'm running out of
summer).
Here's a link https://markayoder.github.io/PRUCookbook/
I'm happy for any feedback you can give me.
--Mark
Great format, I really like it online.
To test it I
f the SHAREDRAM
>>>> approach as it makes for a very simple one way api. I'm partly publishing
>>>> this as a tutorial for anybody else - but its my first try at the PRU.
>>>>
>>>> Here is the logic anlayzer output from the Saleae 8 Channels
ons/392826/auto-run-the-programs-when-the-system-turns-ondebian
Since it sounds like you have been thinking about it - and how it relates
to the PRU - are the init.d running as root.?
thanks
On Mon, Jul 30, 2018 at 6:18 PM Robert Nelson
wrote:
> On Mon, Jul 30, 2018 at 8:13 PM, Neil Han
different
> addresses
>
> On 4/6/2018 11:31 AM, Neil Hancock wrote:
>
> yassyass, This seems to be 6yr old question ~ I got the Bone script JS
> working using cloud9 IDE for an MCP23017 last year -
> I got it working on 4.4.54-ti-r93 and I think I had problems with the
> lat
yassyass, This seems to be 6yr old question ~ I got the Bone script JS
working using cloud9 IDE for an MCP23017 last year -
I got it working on 4.4.54-ti-r93 and I think I had problems with the
later build 4.4.68-ti-r108
I was beginner to BBB, but I had used I2C a lot in uP C env. I choose BBB
; /sys/class/rtc/rtc0/wakealarm
> root@beaglebone:/home/debian# echo `date '+%s' -d '+ 1 minutes'` >
> /sys/class/rtc/rtc0/wakealarm
> root@beaglebone:/home/debian# echo standby > /sys/power/state
>
> Is there a way to trace whats going on? What would I look
Hello Evan
I've done it and designing a cape that manages the power by turning it off
and on under external RTC control.
I've found this works
$ sudo su
$ echo 0 > /sys/class/rtc/rtc0/wakealarm
$ echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm
$echo standby > /sys/power/state
