**** BEGIN LOGGING AT Wed Nov 30 02:59:56 2022
Nov 30 05:25:55 <Chamindu> Hello folks. I have a strange issue on BBB, after a while HDMI stopped working. but the board boots up fine and I can access the board when connected to usb.
Nov 30 05:26:28 <Chamindu> it happened on 2 voards
Nov 30 05:30:58 <zmatt> check logs I guess?  "HDMI stopped working" sounds a bit vague, what exactly are you observing?  are you getting no signal whatsoever?  is whatever application is using the hdmi output starting normally?
Nov 30 05:40:11 <Chamindu> no signal whatsoever
Nov 30 05:41:24 <Chamindu> I am booting into the buster iot that is installed into the eMMC
Nov 30 05:42:26 <Chamindu> I have not installed any custom applications
Nov 30 05:42:49 <zmatt> just to be clear, you mean the hdmi on these boards died entirely, or do you mean hdmi works initially after boot but stops working after a while?
Nov 30 05:43:00 <Chamindu> died entirely
Nov 30 05:43:13 <zmatt> hmm, I don't think I've ever heard of anything like that
Nov 30 05:43:39 <zmatt> then again, I'm not sure how many people actually use the hdmi output...
Nov 30 05:44:20 <Chamindu> In the final product i will not be using hdmi as well. I will use a display cape
Nov 30 05:45:17 <Chamindu> is there any configuration setting to enable hdmi?
Nov 30 05:46:21 <zmatt> in /boot/uEnv.txt you can add a suitable video= parameter to force-enable the HDMI, there's a comment near the bottom that has an example of that
Nov 30 05:46:34 <Chamindu> thanks i will try that
Nov 30 05:47:30 <zmatt> I don't expect anything from that, unless the hdmi monitor presence detection is the part that somehow died
Nov 30 05:47:34 <Chamindu> I saw a warning saying not to connect anything to the board while it is now powered, but that only applies to the gpio right not to hdmi?
Nov 30 05:47:56 <zmatt> yeah
Nov 30 05:49:42 <zmatt> for gpio the specific warning is to never expose I/O to a voltage higher than the supply voltage (+ a small margin) for that I/O domain, which is of course 0V when the board is unpowered
Nov 30 05:51:49 <Chamindu> got it
Nov 30 05:52:22 <Chamindu> thanks for the info
**** BEGIN LOGGING AT Wed Nov 30 13:02:59 2022
Nov 30 15:39:29 <Chamindu> Is there a gui desktop available in "BeagleBoard.org Debian Buster IoT Image 2020-04-06"
Nov 30 15:40:21 <Chamindu> This is the default image that came in my BBB rev C
Nov 30 16:40:41 <Chamindu> I found that there is a folder called opt/scripts/tools/wm can i use the shell scripts to install a desktop?
Dec 01 01:28:12 <set_> Hello...would installing arm-linux-eabi break the BBB or is there a way to enable it when building the kernel or is it a module?
Dec 01 01:28:34 <zmatt> set_: ehm, that sentence does not make any sense
Dec 01 01:29:24 <zmatt> "arm-linux-eabi" refers to an architecture/target, not to a piece of software
Dec 01 01:30:20 <zmatt> (though the target that more accurately describes the bbb is arm-linux-gnueabihf)
Dec 01 01:32:29 <set_> Oh. I thought for the bbb, using -eabi- is for baremetal.
Dec 01 01:33:10 <zmatt> baremetal would be arm-none-eabihf (or arm-none-eabi if the hardware floating point abi isn't used)
Dec 01 01:33:23 <set_> Oh.
Dec 01 01:33:24 <set_> Blah.
Dec 01 01:33:31 <set_> No wonder the BBB kept dying on me.
Dec 01 01:33:36 <zmatt> ?
Dec 01 01:33:39 <set_> Phew. I am just glad nothing is busted.
Dec 01 01:33:48 <set_> ?
Dec 01 01:33:50 <set_> Oh.
Dec 01 01:34:05 <set_> I installed arm-linux-eabi and the board refused to boot afterwards.
Dec 01 01:34:15 <zmatt> that sentence doesn't make sense
Dec 01 01:34:24 <zmatt> you can't "install arm-linux-eabi"
Dec 01 01:34:24 <set_> I used apt.
Dec 01 01:34:41 <set_> oh.
Dec 01 01:34:45 <set_> Hmm.
Dec 01 01:34:52 <set_> Maybe gcc-arm-linux-eabi?
Dec 01 01:35:13 <set_> Let me double check.
Dec 01 01:36:00 <zmatt> that might be gcc-arm-linux-gnueabi, which would indeed be the wrong gcc to use on a bbb
Dec 01 01:36:10 <set_> gcc-arm-linux-gnueabi, right.
Dec 01 01:36:16 <set_> Oh. Okay.
Dec 01 01:36:19 <zmatt> (the correct gcc to use is already installed by default obviously)
Dec 01 01:36:59 <zmatt> in general to get the correct gcc to use on a target, just install "gcc" ... gcc packages with an explicit target are cross-compilers
Dec 01 01:37:09 <set_> I know. I understand about the floating point (not really) but I thought to use the bbb as a baremetal device, that gnueabi would be used.
Dec 01 01:37:10 <set_> Oh.
Dec 01 01:37:25 <zmatt> you're not going to use the bbb as a baremetal device
Dec 01 01:37:35 <set_> I was using arm_neon.h and got nowhere. This is what lead me to...fine.
Dec 01 01:37:42 <set_> Blah.
Dec 01 01:38:08 <set_> 1GHz!
Dec 01 01:38:12 <set_> Vroom!
Dec 01 01:39:47 <set_> Okay...fine and dandy as usual. No nothing and super satisfied! Man, pipe dreams are a thing of the past I would presume.
Dec 01 01:40:02 <set_> Anyway, I will move on.
Dec 01 01:40:08 <set_> No baremetal for me.
Dec 01 01:41:25 <set_> @zmatt: I said, "Anyway, I will move on."
Dec 01 01:41:38 <set_> I also said, "No baremetal for me."
Dec 01 01:42:20 <set_> erm...erm...wawa!
Dec 01 01:42:22 <zmatt> you want a cookie from me or something? :P
Dec 01 01:42:26 <set_> No sir.
Dec 01 01:42:50 <set_> I just need a cookie! Chocolate and brownie stuffed!
Dec 01 01:42:53 <set_> Ha.
Dec 01 01:43:43 <set_> I was just showing off my capabilities to let sleeping dogs lay.
Dec 01 01:43:49 <set_> "No waking the beast over here!"
**** ENDING LOGGING AT Thu Dec 01 02:59:57 2022