<set_>
is anyone using the linuxcnc builds w/ Bullseye yet?
<set_>
I am asking b/c I had a real difficult time, panicking mostly, erasing some MachineKit .deb files off a Win 'puter last time I doused myself in their builds.
thinkfat has joined #beagle
<set_>
and...I made some posts, mostly garbage now, that have to do w/ building for the BBB and LinuxCNC.
thinkfat_ has quit [Ping timeout: 260 seconds]
<vvn>
I have a beaglebone based product, where the "daughter board" is providing power to the bbb (so the bbb kinda is the daughter board in fact)
<set_>
They have armhf builds which means, they have .deb files I can use. Anyway, if anyone is using such a tool online w/ their BBB(s), please let me know.
<vvn>
I have a custom DTS and bootloader, and the only kernel change I carry is this: http://ix.io/3UTL
<vvn>
I would like to get rid of this so I can use the stock beaglebone kernel. Is there a way to configure the sys/hw RTC via the device tree maybe?
<vvn>
Cc: zmatt
vagrantc has quit [Quit: leaving]
starblue has quit [Ping timeout: 240 seconds]
<vvn>
I might just disable the SoC RTC as a quick solution, not sure I would need it...
starblue has joined #beagle
akaWolf has quit [Ping timeout: 250 seconds]
akaWolf has joined #beagle
Jam98 has joined #beagle
<Jam98>
Hey, do any of you know how can I connect a linear actuator to the beaglebone Blue?
<set_>
6v?
Jam98 has quit [Client Quit]
<set_>
I know the motor(s) connection on the BBBlue...
<set_>
Blah.
<set_>
... are 6v!
<set_>
Jam98: If you ever read the logs, use a 6v linear actuator on the DC Motor connections on the BBBlue.
<set_>
That way, you do not under/over power the motor(s) on those connectors.
<set_>
For instance, if you were to test the motor(s) at a specific interval that is under 6v, you may acquire an odd reading. It would be something not expected.
ikarso has quit [Quit: Connection closed for inactivity]
buckket has quit [Quit: buckket]
buckket has joined #beagle
beanie0815 has joined #beagle
<beanie0815>
Hi folks, maybe stupid question, but i spent hours figuring that out. Which part of the software within the default Debian image initiated the flashing of user LED 0 after bootup? I try to find the program performing this but could not find anything
set_ has joined #beagle
set_ has quit [Ping timeout: 256 seconds]
xet7 has quit [Remote host closed the connection]
konsgn has joined #beagle
beanie0815 has quit [Quit: Client closed]
lucascastro has quit [Ping timeout: 256 seconds]
ikarso has joined #beagle
<jfsimon1981_c>
Hi, Try se seek in uEnv boot sequence, the board uses u-boot i'm i'm right.
<jfsimon1981_c>
You can check in that direction.
vigneshr has quit [Quit: Connection closed for inactivity]
vagrantc has quit [Quit: leaving]
<zmatt>
u-boot has nothing to do with it, the leds are all controlled by the kernel, and the default led trigger is configured via DT (but can be changed after boot)
konsgn has quit [Quit: Leaving]
lucascastro has joined #beagle
thinkfat_ has joined #beagle
thinkfat has quit [Read error: Connection reset by peer]
Jam31 has joined #beagle
<Jam31>
How can I connect a 12V actuator to the beaglebone?