**** BEGIN LOGGING AT Sat Feb 20 02:59:57 2021 Feb 20 03:28:49 GenTooMan: One, single motor w/ a C++ SDK is on the way in a working manner w/ the BBB! Feb 20 03:29:10 I finally got everything compiled and transferred. Feb 20 03:30:08 So, now once my tests are complete, I attach that bad pup to the Linux SBC and a slide! Feb 20 03:30:22 BBB and machines! Feb 20 03:30:54 I have been brushing up on C++ to make sure I can read some of what they have produced... Feb 20 08:14:18 I for myself appreciate if I don't have to break out a serial adapter, look up the pin assignments each time, find a usb extension cable long enough, ... Feb 20 08:15:43 having to connect only a single usb cable to have network and serial connection is quite nice. Feb 20 08:28:52 even simply having one cable to power the bbb and establish a network connection to it is already convenient for a lot of users I think Feb 20 09:56:16 though network business can be funny, it's hardly something to rely on. for example, that hint to ssh debian@beaglebone.local is making a lot of assumptions on setup of the computer the beagle is connected to Feb 20 09:57:53 a simple serial link that gives you a login prompt if not a console has much less dependencies. I'd always prefer that Feb 20 09:58:10 well no, I already knew he was using a mac Feb 20 09:58:16 so mdns will definitely work Feb 20 09:59:23 and he wanted to ssh... a serial console can be useful to have, but it's not a substitute for ssh Feb 20 22:18:42 Hello...what would be a good starting point for making something on the BBB work for the AI? Feb 20 22:20:39 For instance, I have a LCD Cape and FLIR Lepton v2 I am trying to make it work w/ the BBAI. Feb 20 22:21:21 I see there is a SPI device on the AI. This is a start for me. Feb 20 23:17:21 I mean...in the .dts and .dtsi files, I see many entries for different peripherals. I also see on github, on the docs, a bunch of entries for the AI peripherls. Feb 20 23:18:28 When I look in the .dtsi and .dts files, none in particular just yet, I see a lot of dra57. and dra75xx files. Feb 20 23:18:45 Sorry. dra57xx. Feb 20 23:19:49 Am I supposed to believe that these dra57. and dra57xx files are the entries to work out for making overlays work? Feb 20 23:22:42 So, technically, for instance: https://github.com/silver2row/BeagleBoard-DeviceTrees/blob/v4.19.x-ti-overlays/src/arm/am572x-bone-common-univ.dtsi Feb 20 23:24:29 This file, and yes it is copied on github from your repo, would be my SoC level files for am5729 and I need to work off that info. for the uboot_overlay that I can add into the /boot/uEnv.txt file for use? Feb 20 23:26:20 It sounds easy but it is not b/c there are so many different options in so many different files. I will keep researching what has happened and what i can do about what has changed in the am5729 compared to the am335x (BBB). Feb 20 23:28:07 Anyway...let me know if you get bored and want to discuss this concern. Thank you. Feb 21 00:57:55 I updated/upgraded and it installed a new GLIBC version, i.e. .29 from .28! Off to recompile everything. Blah. Feb 21 02:57:08 Man! Are you guys testing in SID for a new image? **** ENDING LOGGING AT Sun Feb 21 02:59:58 2021