**** BEGIN LOGGING AT Tue Mar 07 03:00:03 2017 Mar 07 06:52:53 Hello, I use Beaglebone Black, with SD card image: bone-debian-7.11-lxde-4gb-armhf-2016-06-15-4gb and installed touch screen cape 4d LCD. All works properly. But when edit "nano /boot/uEnv.txt" -> only uncomment the row: #dtb=am335x-boneblack-emmc-overlay.dtb (which is: ##BeagleBone Black: HDMI (Audio/Video) disabled:), and then reboot -> the board do not boot -> all 4 LEDs lights continuously and nothing... Why at all the LCD cape w Mar 07 06:53:00 Why if this row only disables HDMI, the whole boars stops to booting?! Can any help me, why the uEnv.txt cant be edited? Thank you, in advance! Mar 07 06:58:09 if you disable the DTB, then there is no information on what hardware it is, so the kernel probably either stalls or panics Mar 07 06:58:55 and for such things access to the debug UART is strictly mandatory Mar 07 06:59:12 we can NOT help play guessing games Mar 07 07:25:04 I apologize, but I just start with such type systems and have very little experience with linux and system programming. Now I research the content of uEnv.txt and note that the first part of file is about config. for linux kernels 4.1...., but my system kernel is 3.8... The last configs are at the end of the uEnv.txt. There I uncomment row about the HDMI disabling and the board boots normally! Excuse me again, I continue fight with th Mar 07 07:46:10 milen: if you don't have access to the debug UART, STOP. RIGHT. NOW. and get a proper cable Mar 07 09:18:09 Hi Guys Mar 07 09:35:56 I have recently aquired a beagleboard black board. i need some direction, as I would like to write my code in C and still use the board. any advice? Mar 07 09:36:38 so far all the examples i have found are in bonescript Mar 07 09:38:26 the project is to make the MPU-9250 of invensense work with thw the beaglebone black. Mar 07 10:19:24 Aryan: compiling your own c code is done the same way as compiling any other c code Mar 07 10:19:41 Aryan: look at how the build system you use works, then do the same Mar 07 10:21:31 does that thing have a linux driver? Mar 07 10:22:05 Zmatt: you mean the board? Mar 07 10:22:27 yes it is supposed to work with linux Mar 07 10:22:29 MPU-9250 Mar 07 10:23:31 but I have downloadd the usb widow driver Mar 07 10:23:45 that is the one i started with Mar 07 10:24:39 you're now talking about the beaglebone I'm assuming? Mar 07 10:25:10 Zmatt: the MPU-9250 is the sensor that i have to hok up to the beaglebone Mar 07 10:25:31 Zmatt: yes the beaglebone is linux compatible Mar 07 10:25:38 ... *sigh* Mar 07 10:25:53 you keep answering completely different things than I ask Mar 07 10:26:37 Zmatt: My appologies. acn we start from the begining. i think i got a bit lost Mar 07 10:27:52 I was initially just wondering out loud whether the mpu-9250 has a linux driver, since in that case you probably don't need to write much code at all Mar 07 10:30:27 then you said something about an usb driver, which can't apply to the MPU9250 since it connects via SPI or I2C, so I was trying to figure out what you were talking about Mar 07 10:37:25 Zmatt: ok, What I meant is that I'm running the beaglebone black from my computer using windows via USB. as it is also possible to run the board directly to a screen using HDMI (but it seem easier for me to do it with using windows on my computer)) Mar 07 10:39:58 zmatt: the protocol code for gyros/acceleration sensors is usally pretty small, if you have a working spi/i2c interface already Mar 07 10:40:09 zmatt: depending on how complex the device is, between 100 and 300loc Mar 07 10:41:08 KotH: fair enough Mar 07 10:41:13 Zmatt:I figured out how the hardware part works (I mean how to connect my MPU-9250 sensor to the beagle board). Now the problem is using C to get the ste up going. Mar 07 10:41:47 Aryan: ssh to the beaglebone, compile C code like you would on any other linux system Mar 07 10:42:06 Zmatt: so far all the examples i found are in bonesript or python Mar 07 10:42:08 Upstream kernel supports the 9150, and Invensense provides drivers that also support the 9250. Mar 07 10:42:27 bunk: yeah I spotted that also Mar 07 10:44:05 Zmatt,bunk: thanks guys: i will look it up and try to figure out how to make the SSH work before asking further questions Mar 07 11:18:44 hi Mar 07 11:19:12 i want to enable can bus in BBB how to do it Mar 07 11:19:49 i am using BBB(debian image) Mar 07 11:50:20 hi! Mar 07 12:22:17 vamsi: you can use https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAN1-00A0.dts Mar 07 12:56:25 zmatt: there? Mar 07 17:57:56 is there any actual guide to using PRUs on the current kernel (4.4)? every single guide seems to be for older kernels and completely fails on 4.4. Mar 07 18:39:37 hi... is there a libre version of the gpu driver for the black yet? Mar 07 18:40:40 Im working with beaglebone a6 board with 3.14.49 ti kernel. Patched the davinci mdio patch for network. Still the board ethernet loss response after some hours of run. The full system build with yocto with qt eglfs. Is there any hints to solve the ethernet instability issue ? Mar 07 18:50:09 I'd like to make my own tablet using the beaglebone. Mar 07 18:50:15 Wondering, would there be any issues with using a gechic hdmi touch screen, and strapping the beaglebone on its back side? Or would it be better to buy a bare touch screen and using some other connection type? Mar 07 18:50:20 @zmatt i found a question regarding the network phy reset in stackoverflow , is there any solution for that ? Mar 07 19:20:12 prem: that sounds like an entirely different issue Mar 07 19:20:20 the mdio problem always occurred at boot Mar 07 19:20:29 and please do not send private messages Mar 07 19:21:17 ask your questions here in the channel and have patience Mar 07 19:21:21 K Mar 07 19:22:22 Sry. Mar 07 19:23:02 although I'm not sure how many people will be enthausiastic about supporting a problem on a yocto system running some ancient kernel, I'm not Mar 07 19:24:27 Guest19712/CrazEd: actually if you load the uio_pruss_enable overlay then it would work basically like it used to Mar 07 19:24:31 *should Mar 07 19:25:36 in which way do the guides fail? Mar 07 19:26:35 if you want to setup pins, you can either use cape-universal (enabled by default) and its "pin-config" utility, or you can disable cape-universal and setup pinmux with overlays like before Mar 07 19:28:20 zmatt: btw cape universal is just modified device tree or something more? Mar 07 19:30:10 cape-universal is an ugly hack in my opinion Mar 07 19:30:15 So zmatt: you are suggesting to use newer kernel. Have you found any instability in network in older kernels. Is there any way to add qt with eglfs support in debian lxqt console image. Mar 07 19:31:07 prem: we're using qt (5.7) with eglfs on debian (stretch) Mar 07 19:31:33 you probably don't want an lxqt image for that, just start with console and install what you need Mar 07 19:33:39 https://www.mail-archive.com/beagleboard@googlegroups.com/msg43945.html I posted this about how I got the new sgx driver stack working Mar 07 19:36:12 as long as Qt can find the sgx userspace libs and the libgbm I link to in that post, you can simply set the environment vars QT_QPA_PLATFORM=eglfs QT_QPA_EGLFS_INTEGRATION=eglfs_kms Mar 07 19:38:33 maciejjo: basically what cape-universal does: it enables nearly all peripherals without pinmux, defines pinmux definition blocks for pretty much every function -> pin mapping, and then uses a custom kernel driver to allow runtime selection between the various configurations defined for a pin Mar 07 19:39:05 ok, it sounds like a hack indeed Mar 07 19:39:23 the peripherals don't even know that they're not connected to pins, they and their drivers still will be active Mar 07 19:39:50 zmatt: the console image of bbb using the ti kernel or nelsons kernel , steps specified in eewiki Mar 07 19:40:53 prem: I patched a 4.9-bone kernel Mar 07 19:46:09 zmatt: how u configured qt 5.7 for 4.9. i only tried it through yocto only. The manual build steps not worked as expected. Mar 07 19:46:39 prem: apt-get install qt5-default Mar 07 19:47:24 + whatever libs were needed Mar 07 19:49:36 the standard qt from Qt and the new sgx libs seem to get along, there was only one small bump in the road, namely that the sgx libs expect libgbm.so.2 while libqeglfs-kms-integration.so depends on libgbm.so.1 Mar 07 19:51:10 The rootfs is debian ? Mar 07 19:51:22 I fixed this by creating a libgbm.so.1 which merely depends on libgbm.so.2: gcc -shared -o libgbm.so.1 libgbm.so.2 -x c /dev/null Mar 07 19:51:50 yes Mar 07 19:52:11 I already said I was using debian stretch Mar 07 19:52:44 Will try tomarrow zmatt: thanks alot Mar 07 19:52:58 try kmscube first to confirm you got sgx working Mar 07 19:53:15 (link to repo is in the post I linked to earlier) Mar 07 19:53:48 if that works, getting qt to work is just a small fight over shared library names Mar 07 20:07:02 Yup. Will do it update Mar 07 20:07:15 & Mar 07 20:27:55 Hi, I have a question on making a flasher image... Normally, I start with an RCN flasher image as my base. Then I modify (adding / removing packages etc) until I have a "golden" BBG. Then I use /opt/scripts/tools/beaglebone-black-eMMC-flasher.sh to create a new Flasher that will clone my golden unit. Here's the rub. An RCN flasher also will set the BoardID EEPROM if it is not already set. But my new flasher will not. How Mar 07 20:27:56 can I add the BoardID EEPROM setting to my new flasher image? Mar 07 20:42:25 try and have a look at his and the beagleboard github Mar 07 20:43:39 https://github.com/RobertCNelson/boot-scripts/tree/master/tools Mar 07 20:43:51 WARNING: Do not use: Mar 07 20:43:51 beaglebone-black-eMMC-flasher.sh Mar 07 20:43:51 init-eMMC-flasher.sh Mar 07 20:43:52 They are only in this directory for support of the Ancient 2014 release. Mar 07 20:45:38 https://github.com/RobertCNelson/boot-scripts/tree/master/tools/eMMC Mar 07 20:47:07 ancient, heh. Mar 07 20:54:29 @tbr thanks will have a look Mar 07 22:56:43 has the beaglebone black gpu driver been liberated? Mar 08 00:15:46 Hi all - I'm trying to build my own Beaglebone image with a custom device tree (based on the bbgw) - Does anyone have pointers or a link to a help doc that outlines the process? Mar 08 00:15:48 Thanks! :) Mar 08 00:29:12 pokezel: making a custom device tree and building an image are two fairly unrelated tasks Mar 08 00:29:50 analucia: we're sending the troops in right now with air support Mar 08 00:30:47 zmatt: i thought it would be a pacific operation! Mar 08 00:32:04 analucia: on a more serious note: only a tiny bit of effort has ever been done in reverse engineering, and according to someone I know at ImgTec what little they produced was wrong Mar 08 00:32:58 I once sent an email asking if I could get edit rights on the wiki but never got a response Mar 08 00:33:07 zmatt: thank you for the information Mar 08 00:33:14 I don't think enough people care Mar 08 00:33:23 to summon the effort needed Mar 08 00:33:54 zmatt: perhaps ryf certification on fsf would be a good incentive for marketing Mar 08 00:36:43 even if it were (doubtful?), generally the people who care about marketing are not the same people as those with the highly technical skill set required to work on something like this Mar 08 00:37:58 maybe it would help if people would get used to having the gpu working in the first place... I've gotten them to work but it wasn't exactly easy Mar 08 00:38:45 (them = the official userspace libs for sgx) **** ENDING LOGGING AT Wed Mar 08 03:00:01 2017