<zmatt>
the overlay explicitly changes rtc0 to be the external rtc and rtc1 the internal one
<zmatt>
they probably do that because rtc0 is considered to be the main rtc of the system
<zmatt>
so the real question is why can't it read the RTC
<Parduz>
ok. Then why timedatectl doesn't works, and hwclock fails on it?
<Parduz>
heh, exactly
<zmatt>
are you using the right pins? is it hooked up correctly? is this overlay for the specific rtc you're using?
<zmatt>
maybe start with that last one
<Parduz>
question: if the wiring were bad, i2cdetect -y -r 2 could not see the 0x68 address "UU", right?
<Parduz>
(oh, if this matters, the module is still without battery)
<zmatt>
Parduz: manpage says UU means i2cdetect skipped that address (didn't perform a check)
<zmatt>
so it means nothing
<Parduz>
well, on the BBB without the module it returns "--" at that address
<zmatt>
UU means the address is in use by a kernel driver, which in this case will be due to the overlay
<Parduz>
understood. So that's why i2cdump return busy.
Shadyman has quit [Quit: Leaving.]
<Parduz>
i thought it was a proof of "good wiring"
<zmatt>
it says absolutely nothing about whether communication with the device is successful, or even whether there's a device at that address at all
<zmatt>
btw did you check kernel log when you got that error from timedatectl ?
<Parduz>
Yup, checking wiring right now. (as a side question: whats the PB-I2C2-RTC-PCF8523.rts is for?)
<Parduz>
'btw did you check kernel log when you got that error from timedatectl'. Nope.
<zmatt>
PB = pocketbeagle
<Parduz>
Could you remind me where it is?
<zmatt>
journalctl -k
<zmatt>
btw be wary of using i2cdetect, it can actually cause some devices to malfunction
<Parduz>
kernel log just says:
<Parduz>
rtc-pcf8523 2-0068: low voltage detected, time is unreliable
<Parduz>
rtc-pcf8523 2-0068: hctosys: unable to read the hardware clock
<zmatt>
i2c is not actually a discoverble bus, you're expected to just know what devices are on your bus. i2cdetect uses a heuristic to guess for each address what a safe way is to probe for the existence of a device, but that's not always going to be a correct guess
<zmatt>
ok sounds like communication with the rtc is working but it has some power-related issue?
<Parduz>
your question "impying" that timedatectl fails if the module is communicating but without battery?
<zmatt>
actually maybe that message just means the rtc has just lost power and therefore needs to be initialized, i.e. you can't get the time (which timedatectl is attempting to do) unless it's been set once
<zmatt>
so, "low voltage detected" means the rtc battery voltage is low
<zmatt>
hence the kernel assumes the rtc's time can't be trusted and gives an error when you try to read
<zmatt>
but that does sound like this makes it impossible to use the rtc without a battery just running on main power
<Parduz>
oook .... trying to understand how it is supposed to used ,,,
<Parduz>
i mean, when the battery runs off, what happens?
<Parduz>
gonna get that battery, i'll tell you how it is gone when i get it installed
<Parduz>
thanks
<Parduz>
zmatt: you told me about a week ago that i could add "&uart3 { bluetooth { status = "disabled"; }; };" to my custom overlay (we were talking about disabling the bluetooth).
<Parduz>
In what "section" of the dts should i put that lines? (my custom overlay is a modded BB-BONE-LCD4-01-00A1.dtc, for reference)
Posterdati has quit [Remote host closed the connection]
Posterdati has joined #beagle
<zmatt>
Parduz: not sure what you mean by "section", but a block of the form &foo { ... }; is always at the top-level, not nested in anything
<Parduz>
so not inside any fragment or overlay branch?
<zmatt>
oh god you're still using the crufty old syntax?
<Parduz>
shouls i start a new BBB image from scratch, what would be the "best" IoT (+openbox) image to get? (when "best" = bug-free / light / fast-booting) ?
<Parduz>
*shoulD
xet7 has quit [Ping timeout: 268 seconds]
rob_w has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
brook has joined #beagle
indigaz has joined #beagle
brook_ has joined #beagle
<Parduz>
well, zmatt, it was the lack of a battery.
<Parduz>
I've even found a note in a PDF from adafruit saying that a battery is mandatory, even if dead, or the module will be unpredictable.
brook__ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has quit [Ping timeout: 250 seconds]
indigaz has quit [Quit: Good bye!]
Parduz has quit [Quit: Client closed]
brook__ has quit [Remote host closed the connection]
brook has joined #beagle
Stat_headcrabed has joined #beagle
florian has quit [Ping timeout: 265 seconds]
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 252 seconds]
wiagn is now known as Stat_headcrabed
brook_ has joined #beagle
brook has quit [Ping timeout: 248 seconds]
brook_ has quit [Ping timeout: 265 seconds]
vagrantc has joined #beagle
brook has joined #beagle
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook has quit [Ping timeout: 240 seconds]
nslu2-log has quit [Ping timeout: 250 seconds]
Stat_headcrabed has quit [Quit: Stat_headcrabed]
nslu2-log has joined #beagle
Stat_headcrabed has joined #beagle
Stat_headcrabed has quit [Client Quit]
ikarso has joined #beagle
brook_ has quit [Remote host closed the connection]
Spencer has joined #beagle
brook has joined #beagle
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook has quit [Ping timeout: 250 seconds]
ft has joined #beagle
Spencer has quit [Quit: Client closed]
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
otisolsen70 has quit [Quit: Leaving]
brook has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
brook has joined #beagle
brook has quit [Remote host closed the connection]
outrageous has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]