**** BEGIN LOGGING AT Tue Sep 15 02:59:57 2020 **** BEGIN LOGGING AT Tue Sep 15 03:25:22 2020 **** BEGIN LOGGING AT Tue Sep 15 05:48:42 2020 **** BEGIN LOGGING AT Tue Sep 15 06:39:35 2020 **** BEGIN LOGGING AT Tue Sep 15 06:55:18 2020 **** BEGIN LOGGING AT Tue Sep 15 07:54:01 2020 **** BEGIN LOGGING AT Tue Sep 15 08:43:12 2020 Sep 15 09:13:21 Hi! Sep 15 09:14:15 I can't succeed for weeks to get some information about UL number of the PCB of the beaglebone Black and/or any information relative to flammability class Sep 15 09:15:35 i have to collect this information in the frame of the CE marking (and US deviations analysis) of a product we want to design (and sell) in which the beaglebone will be integrated Sep 15 09:16:11 i have collected all inforamtion about EMC and RoHS Sep 15 09:17:07 but in the electrical safety "chapter" of our certification, the laboratory will ask for sth that ensure the flame resistance of the PCB **** BEGIN LOGGING AT Tue Sep 15 10:02:27 2020 **** BEGIN LOGGING AT Tue Sep 15 10:16:04 2020 **** BEGIN LOGGING AT Tue Sep 15 10:43:03 2020 **** BEGIN LOGGING AT Tue Sep 15 12:27:53 2020 Sep 15 13:25:47 I bought BeagleBone black and I tried to upload the new image to the BBB. After it was done flashing, the leds were off as expected. But, even after removing SD card and powering off the BBB and repowering it, the LEDS remain off!! Now I can't even connect to my PC. Can someone help me with this issue? Sep 15 13:30:30 I bought BeagleBone black and I tried to upload the new image to the BBB. After it was done flashing, the leds were off as expected. But, even after removing SD card and powering off the BBB and repowering it, the LEDS remain off!! Now I can't even connect to my PC. Can someone help me with this issue? Sep 15 13:31:07 I bought BeagleBone black and I tried to upload the new image to the BBB. After it was done flashing, the leds were off as expected. But, even after removing SD card and powering off the BBB and repowering it, the LEDS remain off!! Now I can't even connect to my PC. Can someone help me with this issue? Sep 15 13:31:22 Please someone answer Sep 15 14:00:29 welp, 20 min here probably wont get you the answer you are looking for Sep 15 14:03:43 heyo, anyone know how to get into the invite only channels? #linux/#electronics, I'm looking at you. Sep 15 14:04:06 Thinking more generic questions could go there. Sep 15 14:06:06 but in the meantime, I am apparently hunting a sasquach of a component. anyone seen a Rtc with internal temp compensated osc, runs on 5v, is i2C, and has something that could be used as a tamper input? I can find most of these, but not everything at once. Sep 15 14:07:25 so far I got https://www.mouser.com/datasheet/2/302/PCF2127-1127482.pdf as closest, but i really don't want to add yet another regulation to get down from 5v Sep 15 14:07:48 and with nA draw, diode dropping wont work too well. Sep 15 14:08:24 *close to uA draw to be fair Sep 15 14:11:24 hahha, bah, got in, just needed to register. **** BEGIN LOGGING AT Tue Sep 15 14:48:44 2020 Sep 15 15:23:30 why 5V? Sep 15 15:24:07 most RTCs are designed to run of a 3V lithium battery Sep 15 17:03:18 Can someone please tell me how much flash ROM does the Pocket Beagle board has ? Sep 15 17:03:49 none Sep 15 17:04:10 yeah, the pocketbeagle has no eMMC, it boots from sd card Sep 15 17:04:28 So, I have to connect an external flash or maybe use SD-Card to put the OS ? Sep 15 17:04:40 OS on it ? Sep 15 17:04:42 microSD card specifically Sep 15 17:05:06 OK, thank you. Sep 15 17:14:35 Hey zmatt, so I'm trying to use py-uio on the BeagleBone AI and I am only seeing a broken symbolic link 'pruss' in /dev/uio. Sep 15 17:14:51 I followed the installation instructions, what would be the most likely cause of this? Sep 15 17:15:10 I'm thinking maybe my device tree isn't correct. Sep 15 17:15:22 yep that would be the reason Sep 15 17:15:56 It's always the DTs. Sep 15 17:16:26 the devil is in the DeTailS Sep 15 17:17:09 Wait, I see one of the likely many dumb things I did. I had dtb-am5729-beagleboneai-uio.dtb in my uENV.txt instead of dtb=am5729-beagleboneai-uio.dtb Sep 15 17:17:10 are there any /dev/uio* devices? Sep 15 17:17:25 ah that won't help Sep 15 17:20:36 I think that was the problem. Now the basic-test.py example is working. Sep 15 17:20:44 \o/ Sep 15 17:22:11 so the symlink from /dev/uio/pruss to pruss1 is just for convenience so the existing examples work unmodified. when creating an application for the bbai specifically you'd probably want to explicitly use either the pruss1 or pruss2 instance Sep 15 17:22:55 what fortran programmer assigned those numbers? Sep 15 17:23:04 yeah it's awful Sep 15 17:23:24 the omap-derived SoCs have this obnoxious mix of 1-based and 0-based numbering Sep 15 17:23:51 and for some things for which the TRM uses 1-based numbering, u-boot and the kernel use 0-based numbering Sep 15 17:24:27 I don't know where this 1-based numbering of peripheral comes from but somebody needs to be slapped with a trout Sep 15 17:25:08 (pruss is a great example since the two instances are pruss1 and pruss2 yet the two pru cores of each are pru0 and pru1) Sep 15 17:25:27 wonderful Sep 15 18:07:44 zmatt: pm? Sep 15 18:08:01 hm? Sep 15 18:08:09 fm Sep 15 18:17:05 am Sep 15 18:18:21 also, going to use an ldo to drop from the 5v: tps7A02 Sep 15 18:18:52 5v as the sys voltage that runs off big batt, the coin cell is only for times when it gets removed Sep 15 18:36:16 zmatt, how did you figure out how to make the dra7-uio-pruss.dtsi device tree fragment? I guess you could name the pruss1 and 2 nodes whatever you want right, you just need to have the "compatible" line tell the Kernel which drivers use the pru devices? Sep 15 18:36:40 &pruss1 and &pruss2 reference existing nodes in the dra7.dtsi Sep 15 18:37:23 Gotcha Sep 15 18:37:56 so these are mostly already declared right, I just change the compatible-string to swap out the driver, add the ti,pintc-offset (which ought to be something the driver derives from the compatible-string but this isn't the case) and add the "pruss-instance" property which is used solely by the udev rule for creating the symlinks in /dev/uio/ Sep 15 18:41:29 So for a given node how do you know what options you have for drivers? I mean, I guess there are only two options for the pruss which is something you would probably know already. Sep 15 18:42:09 the compatible-string determines which driver is loaded. typically there's only one that makes sense for a device Sep 15 18:42:29 it is rather unusual to have two "competing" drivers for a device Sep 15 18:43:13 Ok, thanks! Sep 15 18:59:33 zmatt: still too common