[beagleboard] Re: Unnecessary network data traffic
Good idea! I'll try this and post again if I can observe something suspicious. 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/6490002d-5d66-4c9a-80be-e793610eeb5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Unnecessary network data traffic
Yes, I changed the default password for debian user and root user, but I didn't disable either. Should I enable logging for everything or something specific? 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/f33729f8-b247-44d4-815d-8ad33a8a4e99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: How to run programms automatically at boot up in beaglebone black
Hello. I used PM2 to do what you described and it worked very well. There's also "Forever" that is recommended by the community, but I think PM2 is more complete. PM2 Example: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04 https://www.digitalocean.com/community/tutorials/how-to-use-pm2-to-setup-a-node-js-production-environment-on-an-ubuntu-vps FOREVER Example: https://causeyourestuck.io/2016/04/30/run-node-js-script-startup/ -- 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/28921e7d-0437-4183-a34d-3eaac69e6b45%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Unnecessary network data traffic
Hello! I've installed a standalone application in a Beaglebone Black and apparently the data traffic on the network has increased a lot. My customer could not prove that it was the BBB yet, but I believe it's not, since everything in it's a simple I/Os control, monitoring by a REST application made in NodeJS/Javascript, with the data being stored in MySQL database, everything installed in the BBB and without access to other external applications. BBB is connected to the network, but in theory, it should not be generating traffic. Is there any reason for BBB to be generating data traffic unnecessarily? 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/36a727d7-3d33-466f-84a1-c4597512c3f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to disable Cloud9 IDE on BBB
Thanks! Are there any other services that I should be aware of before handing the BBB to the customer? My app uses the Socket.io library. I imagine there is no relationship between these things, because the services "cloud9.service" and "cloud9.socket" are independent apps, right? Thanks again! -- 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/f4e561dd-a763-4296-a57b-c4a60e263347%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to disable Cloud9 IDE on BBB
Hi! I created an app in NodeJS for Beaglebone and I don't want anyone to have access to the code via Cloud9 or any other way. My questions are: 1) How to disable the Cloud9 IDE on Beaglebone Black? I've already tried "*systemctl disable cloud9.service*" but it did not work. Even after restarting the BBB, Cloud9 still works; 2) What else is it necessary to disable at BBB? 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/622e18db-f2ea-4738-8407-65b87731d25e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
I couldn't point to the rtc0 device, but after much suffering I was able to create the rtc1 device. root@beaglebone:~# ls -al | grep rtc* -rw-r--r-- 1 root root 0 Jul 27 2017 rtc0 root@beaglebone:~# ls -la /dev/rtc* lrwxrwxrwx 1 root root 4 May 21 2016 /dev/rtc -> rtc0 crw--- 1 root root 254, 0 May 21 2016 /dev/rtc0 crw--- 1 root root 254, 1 May 21 2016 /dev/rtc1 -- 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/0cc24d0f-0bb7-455b-b64b-9b148d16ff67%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Greg, it's okay. I was able to make the RTC be recognized as rtc1 in the system. Just turned off the BBB, disconnected everything that was connected to the hardware and starts again. I'm sure the RTC module was properly connected to the BBB, so I believe that there could only be some configuration conflict going on. Thank you! -- 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/bfb502e5-4ed0-4153-8685-c8bdf06ccaca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Greg, I'd just like to prevent the RTC from being updated with the system date and time so that I can even use a script to do this task when I need to. How do I prevent the RTC from being updated automatically? Command response "timedatectl" root@beaglebone:~# timedatectl Local time: Fri 2017-07-28 09:59:52 -03 Universal time: Fri 2017-07-28 12:59:52 UTC RTC time: Sat 2016-05-21 22:38:04 Time zone: America/Sao_Paulo (-03, -0300) Network time on: yes NTP synchronized: no RTC in local TZ: no -- 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/aa019f88-d142-4f87-bfd3-8bb4f96f7261%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Actually what is happening is this: when I remove the power from the BBB, the date and time return to the default setting. Because the RTC is automatically associated with system time auto-tuning, then its time is also being changed incorrectly (I had not noticed this in reboot because it is necessary to remove the power). How do I prevent the system from automatically correcting the RTC? How do I remove this connection from the RTC with the system? I intend to create a script to set date and time. -- 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/20544dc3-3ce0-4ff7-82d8-9afcdb1c8e0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Finally I got ... the last hint from William Hermans indicated me something about the device name, which could be "rtcX", which made me execute: "ls -la /dev/rtc*": root@beaglebone:~# ls -la /dev/rtc* lrwxrwxrwx 1 root root 4 May 21 2016 /dev/rtc -> rtc0 crw--- 1 root root 254, 0 May 21 2016 /dev/rtc0 1) Replace "rtc1" with "rtc0" in the commands and everything works! (the system date and time were already correct): hwclock -w -f /dev/rtc0 2) To test if it worked and if the date and time were actually adjusted, I changed the system time, restarted the BBB and disconnected it from the internet to ensure the date and time would not be auto-tuned. After restarting it, I checked if the system time was still wrong and then read the RTC time (which must be correct!). hwclock -r -f /dev/rtc0 It works!!! RTC date and time were correct. I don't even know how to thank everyone for their help. It should be simple to solve this problem, but it takes a lot of time, especially for those who don't have experience like me. Thank you very much! -- 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/9c2b0a36-e70d-4fec-a904-6a0f6b5e0a49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Just adding: root@beaglebone:/# i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -- 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/889cf8a7-46be-4df9-ba0e-a46ba44c6eca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Is there any other difference in this latest version of Debian? I'm following a tutorial below, but the command "hwclock -r -f /dev/rtc1" is indicating failure to communicate with the new device: *TUTORIAL*: https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time *ERROR*: root@beaglebone:~# hwclock -r -f /dev/rtc1 hwclock: Cannot access the Hardware Clock via any known method. *DEVICES*: root@beaglebone:/# ls -la /sys/bus/i2c/devices total 0 drwxr-xr-x 2 root root 0 Jul 27 20:19 . drwxr-xr-x 4 root root 0 Jul 27 20:19 .. lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0024 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024 lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0034 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0034 lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0050 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050 lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0070 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0070 lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0054 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0054 lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0055 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0055 lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0056 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0056 lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0057 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0057 lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-0 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0 lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-1 -> ../../../devices/platform/ocp/4802a000.i2c/i2c-1 lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-2 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2 -- 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/02f0803f-23ce-4f6a-985c-daadcd9f7d2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Ok! Thanks for the tip! -- 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/93881bed-2f46-45e0-8987-f23a9dad1063%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
*Grahan:* You're 100% correct. Running "i2cdetect -y -r 2" instead of "1" at the end, it detected the RTC at address 0x68, as we can see in the available tutorials. Answering your question, I'm using the latest available Debian release (bone-debian-8.8-iot-armhf-2017-07-01-4gb.img) available here: https://rcn-ee.net/rootfs/bb.org/testing/2017-07-01/iot/ *William Hermans: * When I run the command "i2cdetect -l", I get this information: root@beaglebone:~# i2cdetect -l i2c-0 i2c OMAP I2C adapterI2C adapter i2c-1 i2c OMAP I2C adapterI2C adapter i2c-2 i2c OMAP I2C adapterI2C adapter Now I can continue with the process normally and as soon as it works I report here. Thank you again!!! -- 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/3ac8db97-2938-433e-992b-2422278bb1c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
Hi! I bought the I2C logic converter 3.3V => 5v and I've connected the RTC to the BBB, but running "i2cdetect -y -r 1" doesn't find the RTC device. I've checked the wiring of the connections and I repeated the process a few times, but it doesn't detect the RTC. Any suggestion? -- 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/8020d029-3445-4a93-acf7-de2bfc84e67d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
I'm convinced that the PCA9306 and the RTC PHILIPS PCF85063TP are excellent solutions. However, removing the resistors I think is not good. I'm going to use the bidirectional I2C-bus translator because it's easier to find where I live. Thank you everyone for the attention. PS: William Hermans, the link is working fine for me. I don't understand why it didn't work for you... No problem! http://www.ebay.com/itm/5-PCS-I2C-RTC-DS1307-AT24C32-Real-Time-Clock-Module-For-AVR-ARM-PIC-/172308340060?epid=846722400&hash=item281e609d5c:g:VxcAAOSwawpXsn0J -- 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/6ac00173-6952-4d45-990a-9f92a003917a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: RTC's SDA and SCL Resistors
John, I get it. But I do not know how it would be possible to do this in my DS1307 module which is of this type: http://www.ebay.com/itm/5-PCS-I2C-RTC-DS1307-AT24C32-Real-Time-Clock-Module-For-AVR-ARM-PIC-/172308340060?epid=846722400&hash=item281e609d5c:g:VxcAAOSwawpXsn0J How would It connect to 3.3V hardware instead of 5V? Thank you again! -- 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/2b99797f-afbb-4408-a47d-3efcbf10b0d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] RTC's SDA and SCL Resistors
Hi! I'm installing a real-time clock (RTC) on Beaglbone Black and I'm seeing divergent information abount hardware of the DS1307 integrated circuit, that operates at 5V voltage, while the I2C IO buses of the BeagleBone operate at 3.3V. In the Adafruit RTC, they indicate removing the SCL and SDA resistors from the DS1305 kit as shown here: https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/wiring-the -rtc In linux.org, nothing is reported about the resistors and there are other places that also do not say anything about the resistors: http://elinux.org/Adafruit:_RTC_DS1307 *Question*: Should I keep the SCL and SDA resistors? Or should I remove the resistors? -- 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/3e5c2f95-d7d4-47e6-9fd9-6c027792386f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Self-executing interrupt problem
I'm still testing, but I think the problem was even the lack of resistors. Thank you again! -- 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/908717fc-64b4-406d-9afa-d023030569eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Self-executing interrupt problem
I think you're right John. I don't have a pulldown resistor. I forgot it... I'll try again now and let you know the answer when I'm done. 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/2ef5a80a-750b-4dc6-921c-e09b01080c9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Self-executing interrupt problem
Hello again John. I was able to observe the error occurring and the interruption being executed without reason. But the response from "console.log (JSON.stringify (x));" was still the same when the interrupt was executed correctly, ie when I pressed the button. So, if you have any suggestions, I appreciate any help. -- 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/0113bec9-4291-42c7-8d13-68c138957164%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Self-executing interrupt problem
John, in the correct execution of the interrupt, that is, when I press a
button so that the interrupt is actually executed, the answer is this
below. I'm still waiting to know if self-interrupt will run again and then
see what new response from "console.log (JSON.stringify (x))".
Response to the *correct interrupt*:
{
"pin": {
"name":"UART4_RXD",
"gpio":30,
"mux":"gpmc_wait0",
"eeprom":18,
"key":"P9_11",
"muxRegOffset":"0x070",
"options":[
"gpmc_wait0",
"mii2_crs",
"NA",
"rmii2_crs_dv",
"mmc1_sdcd",
"NA",
"NA",
"gpio0_30"
]
},
"value":0,
"output": {"handler":true}
}
What should I observe in this response when the error occurs again?
Em sexta-feira, 21 de julho de 2017 18:10:55 UTC-3, john3909 escreveu:
>
> In toggleState, use console.log(JSON.stringify(x)); to see why the
> interrupt triggered.
>
> Regards,
> John
>
>
>
>
> On Jul 21, 2017, at 1:52 PM, William B >
> wrote:
>
> Hello! I'm using an interrupt with Beaglebone Black as indicated below,
> however I'm having problem.
> PROBLEM: The interrupt that goes through the callback function
> "toggleState" is triggering itself, without any external reason or action.
>
> Has anyone seen this happen and knows how to solve it?
>
>
> EXAMPLE:
>
> myInput = 'P9_11';
>
> b.pinMode(myInput, b.INPUT);
> b.attachInterrupt(myInput, true, b.CHANGE, toggleState);
>
> function toggleState(x) { << Running for no reason
> console.log('Interruption triggered');
> }
>
> --
> 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...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/51f710e8-8055-4f1f-aa80-c6eb22289d13%40googlegroups.com
>
> <https://groups.google.com/d/msgid/beagleboard/51f710e8-8055-4f1f-aa80-c6eb22289d13%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/a208cb00-45ef-4c01-a5ae-f2989fcfc61b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Self-executing interrupt problem
Hello! I'm using an interrupt with Beaglebone Black as indicated below,
however I'm having problem.
PROBLEM: The interrupt that goes through the callback function
"toggleState" is triggering itself, without any external reason or action.
Has anyone seen this happen and knows how to solve it?
EXAMPLE:
myInput = 'P9_11';
b.pinMode(myInput, b.INPUT);
b.attachInterrupt(myInput, true, b.CHANGE, toggleState);
function toggleState(x) { << Running for no reason
console.log('Interruption triggered');
}
--
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/51f710e8-8055-4f1f-aa80-c6eb22289d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Static IP with connman solved
Hi! I just wanted to report an error that occurred to me and how I solved it. I installed a new version of Debian on Beaglebone Black, which was made available at https://rcn-ee.net/rootfs/bb.org/testing/2017-07-01/iot/ by Robert Nelson. I use static IP on Ethernet and configure it via connman as follows: 1) Discover the identification of the ethernet interface: ls -la /var/lib/connman drwx-- 2 root root 4096 Jul 19 15:37 ethernet_b0d5ccfbbc59_cable <=== this is my MAC Address 2) Configure static IP: connmanctl config ethernet_b0d5ccfbbc59_cable --ipv4 manual 192.168.137.2 255.255.255.0 192.168.137.1 3) Configure DNS (this can be done together with the previous command): connmanctl config ethernet_b0d5ccfbbc59_cable --nameservers 192.168.1.1 8.8.8.8 *ERROR*: When executing item 1, the following error was displayed: Method "SetProperty" with signature "sv" on interface "net.connman.Service" doesn't exist Running "connmanctl services" no interface was displayed: root@beaglebone:~# connmanctl connmanctl> services <== Here should appear "ethernet_b0d5ccfbbc59_cable" or "ethernet", I do not know ... connmanctl> *SOLUTION*: The connman is already configured for dynamic ip, so I did the following: 1- connect the Beaglebone to the router; 2- check which IP the Beaglebone registered; 3) access the Beaglebone for this dynamic IP; 4) run the command: connmanctl config ethernet_b0d5ccfbbc59_cable --ipv4 manual 192.168.137.2 255.255.255.0 192.168.137.1 5) You will lose the connection after executing item 4, then just access the BBB again using the new IP, which in my case is 192.168.137.2. -- 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/e622ba1b-eb58-442f-a5bf-713adb52f6a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
