**** BEGIN LOGGING AT Thu Sep 08 02:59:56 2022 Sep 08 03:38:23 So, w/ the can1 bus on the BBB, would RX be connected to RX on the transceiver and likewise w/ TX? Or is that backwards? Sep 08 03:39:07 RX -> RX && TX -> TX OR RX -> TX && TX -> RX? Sep 08 03:40:19 The reason I was asking are these ideas: 1. beyondlogic.org has a small article on it. 2. I always thought TX goes to RX and vice versa. Sep 08 03:48:47 Hmm...I looked up articles. It seems that the TX does go to TX and the same for RX. Blah. Sep 08 03:50:22 a transceiver is a transmitter and a receiver, so it has a transmit ("tx") _input_ for data to be transmitted and a receive ("rx") output for received data Sep 08 03:51:07 so the can tx output of the beaglebone indeed goes to the tx input of the transceiver, and the rx output of the transceiver goes to the can rx input of the beaglebone Sep 08 03:52:07 the "tx goes to rx" principle applies to cases where you're connecting e.g. two uart interfaces directly, the transmit output of one going to the receive input of the other Sep 08 07:29:35 oh Sep 08 18:51:07 Does anyone know if the BBAIx64 has been shown to work with any MIPI-DSI displays? Sep 08 21:46:48 RobotRocket: https://www.amazon.com/Compute-Display-Adapter-Official-Waveshare/dp/B094WC68WH/ + Sep 08 21:46:49 https://www.seeedstudio.com/5-Inch-800-480-DSI-Interface-LCD-Capacitive-TouchScreen-p-4559.html is what we used.. Sep 08 21:50:05 NishanthMenon: Excellent. This is validated with BBAIx64 (TDA4VM)? Sep 08 21:51:20 RobotRocket: what's that x doing in front of the 64? :D it's AI-64, not AIx64 Sep 08 21:51:59 My bad. :-) Sep 08 21:52:47 RobotRocket: https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v5.10.x-ti-arm64/src/arm64/overlays/k3-j721e-beagleboneai64-RPi-7inch-panel.dts Sep 08 21:55:12 NishanthMenon: Thanks. That answers the question. Sep 08 21:55:26 i wish i could quickly check it out, but meh, panel and cable are at my desk, but ai64 is at home :( Sep 08 21:58:56 I figure that someone got this working with BBAI-64 or they wouldn't have pushed that DTS to the overlays. Sep 08 23:47:38 Hi Sep 08 23:51:20 This is a hopefully an easy question:  I have a Beaglebone Black and I loaded the image: BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz onto an SD card and tried to boot from it.  To my amazement, it flashed my eMMC (which was not my first choice).  Is this a flasher image and how should I have known? Sep 08 23:54:23 BBB-blank- images are old flasher images yeah, though nowadays they have "emmc-flasher" in the image name, and even newer ones (bullseye testing images) don't have separate flasher images but you use a command Sep 08 23:54:42 debian 9.5 is ancient btw Sep 08 23:55:57 latest official images are always here: https://beagleboard.org/latest-images (the "SD" images are simple bootable images, flashers have "eMMC" and "Flasher" in the link) Sep 08 23:58:19 Guest43: I would generally recommend flashing to eMMC though, or if for whatever reason you do want to run from SD card it's recommended to wipe eMMC or at least wipe the bootloader from eMMC... that way you ensure you avoid the situation where the bootloader (loaded from eMMC by default) might mismatch the system being booted (from SD), which can result in boot failure or more subtle problems where ... Sep 08 23:58:25 ...it'll seem to boot fine but have issues Sep 08 23:59:50 Ok thanks for the quick answer.  The 4GB limit on the disk space is sort of an issue I am running into on the eMMC, that is the reason I was running from the SD card. Sep 09 00:01:25 the 10.3 2020-04-06 IoT image uses about 2.5G of space Sep 09 00:02:45 Ohhh... interesting. did not realize that.  Maybe I can try that...   That image is on the link you provided earlier? Sep 09 00:03:09 the iot images in general still contain a lot of crap not everyone will need, people who are comfortable with just installing whatever packages they need may prefer to start with a minimal image (formerly known as console image) which uses only a few hundred MB of space Sep 09 00:03:24 yeah, "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" Sep 09 00:03:41 (the 4GB is referring to the image size, not the used space after install) Sep 09 00:03:47 Cool!  Thx ZMatt!! Sep 09 00:04:17 df -h is showing 3.5 GB used after flashing Sep 09 00:04:45 maybe that ancient IoT image installed even more unnecessary crap Sep 09 00:05:20 3.5G is kinda ridiculous Sep 09 00:05:21 Or more likely,  I screwed up somewhere... hahaha! Sep 09 00:06:01 Actrually, what I said is incorrect: Sep 09 00:06:13 it is only 2.0 G Sep 09 00:06:33 sorry, I am speaking about an earlier mishap:  Sorry for the confusuinb' Sep 09 00:06:36 confusion Sep 09 00:06:57 so the newer image actually uses a bit more space, though it still leaves plenty of free space Sep 09 00:08:02 Ok cool.   I will try 10.x image  .  And will use flasher since the blank image really has nothing I need to save.  Thanks again ZMatt, you have been quite helpful!!! **** ENDING LOGGING AT Fri Sep 09 02:59:56 2022