02:38 <set_> 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?

02:39 <set_> RX -> RX && TX -> TX OR RX -> TX && TX -> RX?

02:40 <set_> 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.

02:48 <set_> Hmm...I looked up articles. It seems that the TX does go to TX and the same for RX. Blah.

02:50 <zmatt> 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

02:51 <zmatt> 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

02:52 <zmatt> 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

06:29 <set_> oh

17:51 <RobotRocket> Does anyone know if the BBAIx64 has been shown to work with any MIPI-DSI displays?

20:46 <NishanthMenon> RobotRocket: https://www.amazon.com/Compute-Display-Adapter-Official-Waveshare/dp/B094WC68WH/ +

20:46 <NishanthMenon> https://www.seeedstudio.com/5-Inch-800-480-DSI-Interface-LCD-Capacitive-TouchScreen-p-4559.html is what we used..

20:50 <RobotRocket> NishanthMenon: Excellent. This is validated with BBAIx64 (TDA4VM)?

20:51 <zmatt> RobotRocket: what's that x doing in front of the 64? :D it's AI-64, not AIx64

20:51 <RobotRocket> My bad. :-)

20:52 <NishanthMenon> RobotRocket: https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v5.10.x-ti-arm64/src/arm64/overlays/k3-j721e-beagleboneai64-RPi-7inch-panel.dts

20:55 <RobotRocket> NishanthMenon: Thanks. That answers the question.

20:55 <NishanthMenon> i wish i could quickly check it out, but meh, panel and cable are at my desk, but ai64 is at home :(

20:58 <RobotRocket> I figure that someone got this working with BBAI-64 or they wouldn't have pushed that DTS to the overlays.

22:47 <Guest43> Hi

22:51 <Guest43> 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?

22:54 <zmatt> 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

22:54 <zmatt> debian 9.5 is ancient btw

22:55 <zmatt> 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)

22:58 <zmatt> 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 ...

22:58 <zmatt> ...it'll seem to boot fine but have issues

22:59 <Guest43> 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.

23:01 <zmatt> the 10.3 2020-04-06 IoT image uses about 2.5G of space

23:02 <Guest43> Ohhh... interesting. did not realize that.  Maybe I can try that...   That image is on the link you provided earlier?

23:03 <zmatt> 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

23:03 <zmatt> yeah, "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher"

23:03 <zmatt> (the 4GB is referring to the image size, not the used space after install)

23:03 <Guest43> Cool!  Thx ZMatt!!

23:04 <Guest43> df -h is showing 3.5 GB used after flashing

23:04 <zmatt> maybe that ancient IoT image installed even more unnecessary crap

23:05 <zmatt> 3.5G is kinda ridiculous

23:05 <Guest43> Or more likely,  I screwed up somewhere... hahaha!

23:06 <Guest43> Actrually, what I said is incorrect:

23:06 <Guest43> it is only 2.0 G

23:06 <Guest43> sorry, I am speaking about an earlier mishap:  Sorry for the confusuinb'

23:06 <Guest43> confusion

23:06 <zmatt> so the newer image actually uses a bit more space, though it still leaves plenty of free space

23:08 <Guest43> 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!!!