ds1307 at 0x68*
On Monday, February 24, 2014 9:58:23 AM UTC-3, Fernando Derkoski wrote:
>
> Hello,
>
> Before the upgrade I was testing the RTC and it was normal, but after I
> runned the okpg upgrade this happens:
>
> *root@beaglebone:~# i2cdetect -y -r 1*
> *] 0 1
Yeah noob here, My /etc/localtime was not correct. Now the whole thing work
just fine.
On Monday, February 24, 2014 1:45:18 PM UTC-3, Fernando Derkoski wrote:
>
> I tried *echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device*
>
> and now is working, sort of, because the
n your BBB ?
>
> The Adafruit Tutorial is made for a RTC Battery Backened registered under
> /dev/rtc1, as follows:
>
> echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
> hwclock -s -f /dev/rtc1
> hwclock -w
>
> Any suggestion, comment, idea is welcome
>
So I don't really know how to workaround this, I have tried to execute
> those commands using *crontab *without any success,
>
> If you have any idea, please let me know
>
> Thank you very much for your time
>
> Best Regards
>
> Ivan
>
> On Thursday, July 31, 20
ot@beaglebone:/sys/class/i2c-adapter/i2c-1# ll | grep new
> --w--- 1 root root 4096 Dec 31 1999 new_device
>
> What do think?
>
> Thanks for taking the time
>
> Best regards
>
> Ivan
>
>
> On Friday, August 1, 2014 1:31:24 PM UTC-5, Fernando Derkoski wrote:
:/sys/class/i2c-adapter/i2c-1# ll | grep new
> --w--- 1 root root 4096 Dec 31 1999 new_device
>
> What do think?
>
> Thanks for taking the time
>
> Best regards
>
> Ivan
>
>
> On Friday, August 1, 2014 1:31:24 PM UTC-5, Fernando Derkoski wrote:
>
> Hi I
So I installed the Debian distribution, and now the RTC only updates the
clock on reboot (warm start) not on boot (cold start)
When i do an Boot:
root@beaglebone:~# dmesg | grep 'i2c\|rtc'
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8
quiet root=UUID=e7ab605c-ecc8-4fe9-
Hi there I installed the image that came with the dvd, it works, but I
cannot access the GPIO with node, with octalbonescript this is the
error CapeMgr not found: undefined
/usr/local/lib/node_modules/octalbonescript/index.js:155
var n = pin.gpio;
^
TypeError: Cannot read prop
changes regarding how to access the gpios
> between the kernel 3.2 and 3.8.. so I recommend you make sure you have the
> right nodejs version installed. And also reinstall all the modules by the
> package manager.
>
>
> On Thu, Dec 4, 2014 at 9:54 PM, Fernando Derkoski > w
Hello,
This problem happens to me as well, I have 3 beaglebones black Rev C, with
the latest kernel, 3.8.13-bone70. Anyone knows how to resolve this problem?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
Nelson wrote:
>
> On Tue, May 19, 2015 at 3:24 PM, Fernando Derkoski > wrote:
> > Hello,
> >
> > This problem happens to me as well, I have 3 beaglebones black Rev C,
> with
> > the latest kernel, 3.8.13-bone70. Anyone knows how to resolve this
> problem?
they were using
the 3.3 pin of the beaglebone as well. I hope that this information help
someone.
On Tuesday, May 19, 2015 at 5:56:44 PM UTC-3, RobertCNelson wrote:
>
> On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski > wrote:
> > Hi, first thank you for the response, her
I have 4 beaglebones with Debian and I have an process in node.js that
write and read some files one of those files is an GPIO, it works fine but
after a while I receive this error:
error: Unable to write to /sys/class/gpio/gpio112/value
And my process cannot do anything anymore, like connect by
13 matches
Mail list logo