04:45 <Guest63> Hello! n00b beaglebone user here... I have a beaglebone black and wanted to learn development of i2c driver using this device (Using Yocto framework)... is there any beginner's guide available?

08:49 <spout> I'm having a weird bug on a beagle, where connmanctl status return empty

08:55 <set_> Hello spout. Are you using a new image?

08:55 <set_> I ask b/c there is a new way to handle WiFi.

08:56 <spout> i'm using a new image, but it's for ethernet

08:57 <set_> Oh.

08:57 <spout> inux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) (gcc version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020

08:57 <spout> for BBB

08:57 <set_> Sorry. I thought you were using a new image and trying w/ connmanctl w/ WiFi.

08:57 <set_> Here: https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280

08:57 <set_> In that link, there are some ideas about networkd.

08:57 <set_> Oh.

08:58 <set_> You are using the am57xx instead of BBB?

08:58 <spout> it's the image bbb are sold with

08:59 <set_> oh. Try the link I posted and use etcher to flash the image.

08:59 <set_> I think you are getting stuck on older images but you have a am5729 image when you need a am335x image.

08:59 <set_> Are you using the x15 or BBB?

08:59 <spout> it's a weird bug cause i'ts a product we are selling, and one is coming back with that bug

09:00 <spout> but I can't change that easily the version :-/

09:00 <set_> Oh.

09:00 <spout> i'm using a bbb

09:00 <set_> In your image, you show am57xx instead of am335x from what you posted.

09:00 <set_> spout: I am sure if you wait around, someone might be able to help a bit more than me.

09:02 <spout> I'm also checking for physical default

09:03 <spout> but i'm also having this error message

09:03 <spout> The name net.connman.vpn was not provided by any .service files

09:05 <set_> If you have updated/upgraded the machine, then I think Buster and Bullseye report to networkd now instead of connmanctl. I am not 100% sure, though.

09:05 <set_> I would need to test.

09:05 <set_> I may have time later but not now. I am sorry.

09:15 <zmatt> spout: iirc that specific message can be ignored

09:15 <zmatt> but I don't use connman myself so maybe I'm wrong

09:16 <spout> this is weird, I feel like I can't communicate with the eth chip :-/

09:16 <zmatt> set_: the "(voodoo@x3-am57xx-beagle-x15-2gb)" in that output was the system on which the kernel was compiled

09:17 <zmatt> spout: what does "ip link" show ?

09:18 <zmatt> also, "connmanctl status" is a non-existent command, did you mean "connmanctl state" ?

09:20 <set_> Oh.

09:21 <zmatt> spout: https://pastebin.com/raw/rqTB1sFH example output I get for some relevant commands

09:24 <zmatt> oh he left

09:24 <zmatt> "one is coming back with that bug" ... maybe customer just blew up ethernet :P

09:46 <spout> and ip link shows this

09:46 <spout> 4: eth0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000

09:46 <spout>     link/ether 98:f0:7b:1e:48:73 brd ff:ff:ff:ff:ff:ff

09:47 <zmatt> spout: so ethernet is found, but it hasn't detected link up (i.e. it thinks nothing is plugged in)

09:48 <spout> but something is plugged in, i've tested my rj on another thing

09:49 <zmatt> you said this affects a single device that was returned? is it possible the customer just blew up ethernet?

09:49 <zmatt> we've definitely had cases of that

09:52 <spout> that's not totally impossible :-)

09:52 <zmatt> e.g. we've had a case where someone managed to hook it up to a phone line

09:52 <spout> they are working with Canbus with 24V on it also, they could have send a 24V to ethernet

09:53 <zmatt> and they're using ethernet (8P modular) connectors for that? I think you may have just solved your mystery :D

09:53 <spout> I think I'll settle on this

09:54 <zmatt> a long time ago we had a customer who thought it was a great idea to use 3-pin XLR for both DMX (low-voltage serial data) and 230V

09:54 <spout> (no, not eth connector, but they working with loaded naked cables sometime

09:55 <spout> yeah, send the 230 in your smoke machine, and it works !

09:55 <zmatt> naked wires are great, I once accidently dropped a +7V onto a beaglebone's PCB ... may it rest in peace.

09:56 <zmatt> yeah I don't know if it was that particular case, but I remember we got an RMA where the varistor protecting the DMX output was just... gone. nothing left but a scorch mark on the PCB

09:56 <spout> (I've been stage manager for 10 years before switching to industry due to covid)

09:58 <zmatt> makes sense

10:03 <zmatt> spout: another thing I'd worry about is passive PoE injectors... the beaglebone's ethernet connector provides 75Ω common mode termination for each pair to a single point, so there's 150Ω between each pair. if you dump e.g. 24V or worse 48V into that, I'm not sure how well dumping 4W or 15W into tiny termination resistors embedded inside the connector will work out ;)

17:22 <jfsimon1981> Good evening

20:40 <Guest454> hello

20:43 <Guest454> first time in this chat, my Pocket Beagle with Grove cape had trouble with some examples. I upgraded the software and now the second example doesn't load hcsr properly.

20:44 <jkridner> which link are you working from?

20:44 <Guest454> link ambiguous

20:45 <jkridner> https://github.com/beagleboard/cloud9-examples/blob/master/PocketBeagle/Grove/Kit.md#lesson---2-musical-note ?

20:46 <Guest454> the pocket beagle supplied a request to upgrade and I followed those instructions, since it was scripted, I don't know the connection link

20:46 <jkridner> https://github.com/beagleboard/cloud9-examples/blob/master/PocketBeagle/Grove/ToneGenerator.py

20:46 <jkridner> well, the examples were written specifically for the image linked and might not work if upgraded.

20:47 <jkridner> use one of these images? https://debian.beagle.cc/images/grove/

20:48 <Guest454> the upgrade appeared to update most of the software, including examples. How would I figure out what is now incorrect?

20:49 <jkridner> for using the Grove Kit, try to follow the steps on https://github.com/beagleboard/cloud9-examples/blob/master/PocketBeagle/Grove/Kit.md

20:49 <jkridner> hard to say....

20:49 <jkridner> there are some elements of setup that need to be preserved vs. "stock" images for the kit demo instructions to work.

20:50 <jkridner> the steps at https://github.com/beagleboard/cloud9-examples/blob/master/PocketBeagle/Grove/Kit-setup.md have already been applied to the uSD card images recommended.

20:50 <Guest454> it asks to reinstall the driver of hcsr

20:50 <jkridner> the contents of /boot/uEnv.txt should include `uboot_overlay_addr2=/lib/firmware/BB-GPIO-HCSR04.dtbo`

20:51 <jkridner> some aspects that were manually installed for the uSD card image generation might have been incorporated into the "stock Debian" image, such as overlays.

20:53 <jkridner> some packages installed, like https://github.com/Seeed-Studio/seeed-linux-dtoverlays, might have a different version if installed now vs. when the images were made, because no version was specified. :-(

20:53 <Guest454> it refers to version 4.14 and does include boot line

20:53 <jkridner> doesn't seem like anything there changed: https://github.com/Seeed-Studio/seeed-linux-dtoverlays/tree/master/overlays/bb

20:54 <jkridner> Easiest way is to start with a fresh uSD card so you know you've got the configuration right.

20:55 <jkridner> if you want to try out newer software images, someone would likely need to help in updating the contents of the kit tutorials to work with newer PocketBeagle software images.

20:55 <Guest454> what is the correct file to use to write a new SD card?

20:55 <jkridner> https://debian.beagle.cc/images/grove/bone-debian-10.3-iot-grove-kit-armhf-2020-04-06-4gb.img.xz

20:57 <Guest454> I'll give this a try, half of the experiments didn't work with the original SD image.

20:58 <Guest454> I'm trying to separate the code for each sensor to form a library for my own experiments. I can trace the code until I reach compiled python or c code.

20:58 <Guest454> is there further documentation for the seeed software?

21:00 <Guest454> I expect there is further flexibility with port assignments but it is a chore to trace everything to try placing sensors on different ports

21:08 <Guest454> I'm using a MacBook pro laptop. what is the source for the newer unzip code?

21:14 <zmatt> unzip code?

21:14 <zmatt> you don't need to unzip the .xz, Etcher can write .img.xz files directly to sd card

21:16 <zmatt> (it performs on-the-fly decompression)

21:18 <Guest454> I can trace code back to compiled code but without a roadmap I can't predict what other files should be modified to change port assignments

21:18 <Guest454> thnaks

21:20 <Guest454> more questions

21:21 <Guest454> Is there a conversion of grove cape controls and software to the PB without the cape

21:22 <zmatt> I don't know anything whatsoever about this grove stuff

21:23 <Guest454> thanks, I'll try to down rev my software and get try again later

21:24 <zmatt> but I'd be inclined to say "presumably sure", given that grove just seems to be a power + 2 data lines connector

21:25 <zmatt> I never really understood the point

23:35 <inubcakez> Hello

23:38 <inubcakez> I bought a used beaglebone black on eBay and can't seem to connect to it. Tried reflashing with a new debian version but it won't start flashing off the microSD card. Can anyone help me?