**** BEGIN LOGGING AT Mon Mar 08 02:59:57 2021 Mar 08 04:49:18 Hello, Mar 08 04:49:52 I am using Beaglebone Black Wireless Board with latest Image File with graphical user interface Mar 08 04:50:47 But I want GUI based image of above mentioned board, please suggest the suitable board image file. Mar 08 04:52:00 https://beagleboard.org/latest-images Mar 08 04:52:55 *without GUI Mar 08 04:53:24 there are no official images with lxqt gui for the beaglebone anymore but they are still available on the testing images page: https://elinux.org/Beagleboard:Latest-images-testing#Debian_10_.28Buster.29_LXQt Mar 08 04:55:28 they were dropped from the official images since a desktop environment don't really run well on a beaglebone and is rarely useful, and the lxqt images also don't comfortably fit in eMMC (running from SD card would be recommended, but makes things even slower) Mar 08 04:57:19 note that if you just want a custom GUI (single fullscreen application) then you don't need an lxqt image for that Mar 08 04:58:17 So, we can not use GUI in Beaglebone Black Wireless , if I am flashing image file through SD card..... Mar 08 04:58:31 define "GUI" Mar 08 04:59:09 what do you mean when you say that? what do you actually need? Mar 08 04:59:23 Like Raspberry Pi having a desktop GUI same like in BBB Wireless also Mar 08 05:00:28 I don't have a raspberry pi, but I'll assume you mean a desktop environment Mar 08 05:00:35 yes Mar 08 05:01:42 Using command line I m accessing BBB board but I want to design a software and run on this board Mar 08 05:02:07 but without GUI, How can I access ?? Mar 08 05:02:15 via ssh Mar 08 05:02:39 (via usb networking or via its wireless access point) Mar 08 05:02:51 yeah, through putty software I am getting terminal of board Mar 08 05:03:50 okay, so what do you mean by "access" if that's not it? Mar 08 05:04:55 means, only command line window I have, not desktop environment Mar 08 05:05:31 but why would you need a desktop environment _on the beaglebone_ ? what would you do with it? Mar 08 05:07:42 anyway, it is of course possible to run a desktop environment, but because a desktop environment requires a lot of space, the lxqt image (which is the IoT image + desktop environment) doesn't fit on eMMC. you could try to strip it from stuff you don't need to try to fit it if you have a really good reason for it, but that seems questionable Mar 08 05:09:04 I have to control the two slave boards as both slave boards connected through BBB Wireless board, I have to design a application/software for user friendly for giving command to the slave boards Mar 08 05:11:06 that's what I said earlier: if you just want a custom gui (single fullscreen application) you don't need an entire desktop environment for that, in fact if you use Qt5 as framework you don't even need X11 at all, Qt5 applications can run directly on the framebuffer Mar 08 05:11:42 ok Mar 08 05:11:48 but I've also seen instructions for a minimal X11 install that doesn't require much space... lemme think where I've seen those Mar 08 05:13:51 ok I have to look as you have suggested, I will follow the same Mar 08 05:14:01 Thank you for your help Mar 08 05:14:08 https://gist.github.com/jadonk/39d0fcfc323347d88e995cdfee02bdad Mar 08 05:15:22 follow the instructions in the README ... the script invoked in the last line is part of the same gist: https://gist.githubusercontent.com/jadonk/39d0fcfc323347d88e995cdfee02bdad/raw/85899557cb36ba8fd800af24dd0d30eedc5810e8/setup_desktop.sh Mar 08 05:15:31 Is there any step by step process to follow al the steps ?? Mar 08 05:16:53 ... the README *is* the step-by-step process Mar 08 05:17:34 you can probably just copy-paste its instructions into a shell Mar 08 05:18:22 log in with putty, open a root shell using "sudo -i", then paste the commands from the README Mar 08 05:20:56 note that it requires internet access, so your beaglebone must be connected to your wifi network Mar 08 05:21:36 hmm this also doesn't look like a minimal X11 install, it seems to be a small desktop environment Mar 08 05:23:36 and the instructions also don't work anymore :D .. oh well Mar 08 05:24:08 this also wasn't the instructions I was looking for, just some other google result Mar 08 05:25:14 installing X11 on a beaglebone is uncommon and I personally have never had a use for it, hence I don't really have known-good instructions handy Mar 08 05:25:33 we just used qt5 for our GUI Mar 08 06:52:34 Ok, i will try to install and let you know!! Mar 08 09:11:28 i need some help figuring out why my pinmuxing doesn't work I have a application that uses dcan and can request data from a device and it works with the following in my device tree: https://termbin.com/pk37 Mar 08 09:12:16 but when i change it to this: https://termbin.com/4np2 it stops working and I do not know why Mar 08 09:13:26 my dcan node looks like this: https://termbin.com/g76v Mar 08 09:18:37 Duality: what kernel? Mar 08 09:19:26 also, is it intentional that you swapped pullup/pulldown? Mar 08 09:19:57 that's the only difference I see Mar 08 09:20:25 zmatt: yea i just noticed that too and that is not intentinal Mar 08 09:20:45 kernel: 4.19.94+ Mar 08 09:20:54 I'll change that the right way around and test Mar 08 09:37:28 zmatt: that resolved it :) Mar 08 09:37:42 it's crazy but friday i have been staring at that a while Mar 08 09:37:48 for a while Mar 08 09:38:35 pulldown seems like a strange thing anyway, shouldn't it be pullup ("recessive") for both? Mar 08 09:40:25 I am not sure Mar 08 09:40:54 other device trees even show it without pullup/down Mar 08 09:41:31 like for example am335x-boneblue.dts at dcan1_pins doens't have pullup/down configure for those Mar 08 09:42:55 what do you meen by recessive? Mar 08 09:44:26 no pullup might be needed on either: the phy will normally always drive the can_rx line so pullup/pulldown in the am335x probably has no effect, and the phy may have internal pullup on its can_tx input Mar 08 09:45:22 so I think the only thing you can do wrong is pulldown on can_tx, all other pull-options on either pin probably work :D Mar 08 09:46:15 i see Mar 08 09:46:27 first google hit for can recessive: http://www.copperhilltechnologies.com/can-bus-guide-dominant-and-recessive-bus-level/ Mar 08 09:46:39 recessive is the idle state Mar 08 09:47:38 which is a high level on the lines between am335x and can-phy, hence pullup Mar 08 09:49:01 I don't know why but i tried google and i only got biology and gene related things Mar 08 09:49:19 lol Mar 08 17:33:24 Anyone have beaglebone black rev c. flashing experience? Mar 08 17:35:36 jerrywalo[m]: most beaglebone users do Mar 08 17:36:49 I have flashed and need to verify. ssh'd into to the board. ran lsb_release -al....got release 10 and codename buster back. is the release 10 same as 10.3 which I downloaded from site? Mar 08 17:37:10 check image date with: cat /etc/dogtag Mar 08 17:38:09 debian version can be seen with: cat /etc/debian_version Mar 08 17:40:00 im getting no such file or directory on the etc/dogtag....am getting bullseye/sid on the 2nd cmd Mar 08 17:40:27 what image did you flash? every beagleboard.org image has an /etc/dogtag Mar 08 17:40:33 that's a lot of different animals Mar 08 17:40:55 cats, dogs, bulls Mar 08 17:41:04 I have rev c. used 64bit iot flasher Mar 08 17:41:22 there is no "64bit iot flasher", I have no idea what that would even mean Mar 08 17:41:40 and I didn't ask for hardware revision but what image you flashed (precisely) Mar 08 17:41:49 but on a different cmd im getting version 10 codename buster Mar 08 17:44:12 this is the image i used....https://debian.beagleboard.org/images/bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz Mar 08 17:45:14 that should have 10.3 in its /etc/debian_version and "BeagleBoard.org Debian Buster IoT Image 2020-04-06" in its /etc/dogtag Mar 08 17:45:43 unless that somehow gets messed up during flashing, I don't have a quick way to test that (though it seems rather unlikely) Mar 08 17:46:46 when reflashing, do you just insert the card and boot up? Mar 08 17:47:17 yes, if you boot it from an eMMC flasher image it will automatically proceed to reflash eMMC (and then power itself off) Mar 08 17:48:35 (the exception is if eMMC has a really ancient or weird system with an incompatible bootloader, in which case it may be needed to power on the beaglebone with the S2 button held (can let go once power led turns on) to get it to boot from sd card, but usually that's not needed) Mar 08 17:48:57 seems like ive been doing everything right. is there a way to verify what both on the card and whats been flashed? Mar 08 17:49:36 you sure /etc/dogtag doesn't exist? didn't make a typo? Mar 08 17:49:49 did you do anything after reflashing? Mar 08 17:51:16 I'm not sure if I have a beaglebone around that I can reflash to test Mar 08 17:52:24 Actually this is waht I got on dogtag....BeagleBoard.org Debian Buster IoT Image 2020-04-06, but no version # Mar 08 17:52:42 that's the expected content Mar 08 17:53:27 so maybe /etc/debian_version somehow gets weird content during flashing... I know that file is auto-generated but I'm not quite sure how or by what Mar 08 17:53:52 anyway, it clearly did flash properly Mar 08 17:53:58 sorry about the mix up, was accidentally ssh'd out. ran 2nd command you gave me and yeah its 10.3 Mar 08 17:54:11 :P Mar 08 17:55:11 the hostname is in the shell prompt, it shouldn't be hard to see whether your shell is on the beaglebone or not Mar 08 17:55:23 so it looks like im good, except when I ls -a into the board I'm looking for the uEnv.txt file and nothing Mar 08 17:55:35 you mean /boot/uEnv.txt ? Mar 08 17:56:07 that seems to be the file to enable spidev Mar 08 17:56:18 nah you don't need to mess with that to use spi Mar 08 17:56:51 you can just configure the pins using config-pin and you're good to go Mar 08 17:58:15 spi tutorial: https://pastebin.com/nS6FELGH Mar 08 17:59:52 Im trying to flash a bios chip and used a file flashrom/armv7l/flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 and really too sure why its not detecting Mar 08 18:00:10 did you configure the pins using config-pin ? Mar 08 18:00:44 see my paste for the commands Mar 08 18:01:04 no not yet, but thankyou for the link Mar 08 18:03:24 thanks for your help for now **** ENDING LOGGING AT Tue Mar 09 02:59:57 2021