**** BEGIN LOGGING AT Tue Jan 08 02:59:57 2019 Jan 08 04:41:49 What is the address to the UART4_RX pin, i.e. P9_11? Jan 08 04:59:57 "address" ? Jan 08 05:03:24 Yes. I thought there were addresses for each pin? Jan 08 05:03:47 what do you mean "address" ? what sort of address? for what? Jan 08 05:04:45 I have this library that calls for addresses. Jan 08 05:04:53 Please hold. I will get the correct terms for it. Jan 08 05:05:40 if you mean the device path for uart4, it's /dev/ttyS4 Jan 08 05:06:24 port, baudrate, address, timeout -----> the address section needs a special address Jan 08 05:06:38 I thought it was ttyO4? Jan 08 05:07:09 275? Jan 08 05:07:54 it's ttyO4 if the omap-serial driver were used rather than the 8250-omap driver, but it hasn't been in a looooong time. ttyO4 still works though since backward-compatibility symlinks are created Jan 08 05:08:20 Oh. Jan 08 05:08:29 Okay. I will use S4 now. Jan 08 05:08:44 and I have no idea what you're talking about. if you're asking things about a specific piece of software, state what software you're using and what documentation/example calls for an address Jan 08 05:09:00 i.e. 0xff? Jan 08 05:09:18 pysabertooth Jan 08 05:09:40 I tried Adafruit_BBIO but I am not well versed in their uart examples. Jan 08 05:09:56 oh you're suddenly talking about the sabertooth. then why are you using an uart rx pin? the sabertooth does not have a serial output Jan 08 05:10:46 No, I was going to try and use that library w/ the uart example I was going to make. Jan 08 05:11:43 i.e. you want to use pyserial, not pysabertooth Jan 08 05:12:06 (pysabertooth itself uses pyserial too, and I think Adafruit_BBIO does too) Jan 08 05:12:26 Oh. Jan 08 05:12:29 Okay. Jan 08 05:12:33 I will just test it. Jan 08 05:12:43 the "address" that pysabertooth wants is a thing specific to the Sabertooth module, it has nothing to do with uarts in general Jan 08 05:14:02 Oh. Jan 08 05:14:07 Okay. No issue. Jan 08 05:14:17 I will just test uart w/ Adafruit_BBIO. Jan 08 05:18:57 no, pyserial. Jan 08 05:19:41 Adafruit_BBIO's serial = pyserial + some crap that iirc is broken (unless that's been fixed) Jan 08 05:19:51 just use pyserial directly Jan 08 05:21:38 Okay. Jan 08 07:44:38 Hello Experts Jan 08 07:45:32 We bought AM5718 IDK from TI came with Arago distribution by default Jan 08 07:46:12 Is it possible to use debain linux distribution for AM5718 IDK? Jan 08 07:47:00 If so please point to me the reference documents Jan 08 07:51:48 well, not within 5 minutes **** BEGIN LOGGING AT Tue Jan 08 19:32:36 2019 Jan 08 20:13:52 is gcc 8.2 okay for the BBB debian builds we have currently? **** BEGIN LOGGING AT Tue Jan 08 20:53:40 2019 Jan 08 21:36:55 Gourav: is there a reason you don't want to use their Arago distribution? Jan 08 21:54:20 set_: sure, we use 8.2. why wouldn'ti t? Jan 08 22:13:11 raffo: ehh, he's not here, he left almost immediately after asking his question (hence my remark) Jan 08 22:17:16 He's stuck w Arago unless there's a separate debian project for it. I tried using Arago, didn't have X, which I need. That was the end of it for me. Jan 08 22:19:17 I don't see any reason to think there'd be a problem in using debian Jan 08 22:20:21 unless maybe it has very little storage Jan 08 22:20:52 wouldn't the particulars of the board configuration, tuning the device tree, be potentially problematic? Jan 08 22:22:43 no? Jan 08 22:22:49 what do you mean Jan 08 22:24:30 no need to "tune" the DT unless there's a problem with the am571x-idk DT, but presumably yocto simply uses the one from mainline linux too Jan 08 22:25:09 I wouldn't be surprised if the bbx15 image works without any modification, or at most it might need a replacement u-boot Jan 08 22:26:17 okay, space is definitely not an issue (16 GB of eMMC) Jan 08 22:28:39 sorry I don't mean mainline (although it probably works too), yocto presumably uses ti's kernel tree, but that's also what rcn uses to base his kernel packages on Jan 08 22:28:46 I mean get a device tree for u-boot and the kernel for this board for the Debian distro they want. They could copy the one from the Arago image and go from there. Jan 08 22:29:24 zmatt: I have -v 6.2 on my Debian Image. Jan 08 22:29:27 I was just wondering. Jan 08 22:29:38 sorry. gcc -v 6.2. Jan 08 22:31:04 Only 1 GB of RAM. Jan 08 22:31:39 raffo: the kernel used on the beagleboard-x15 debian image should be fine for the am571x idk too, and its DT is already included Jan 08 22:31:43 beaglebone has 512M Jan 08 22:34:55 my bbx15 debian system currently has 1.4G of its 2G ram free, and 488M of the ram used is being used as disk cache Jan 08 22:36:51 okay, a I suspected u-boot is fine too, there aren't even separate defconfigs for the various am57xx boards Jan 08 22:37:12 I think the beagleboard-x15 debian image will work on the am571x idk without any modification whatsoever Jan 08 22:37:57 u-boot will automatically load the correct DT based on the board identification eeprom Jan 08 22:40:44 also I'm curious, why do you need X ? I've never felt a need to run X on a beaglebone, not even those that are used for a gui Jan 08 22:42:39 It's a requirement for our project. Our gui X-based. Jan 08 22:43:21 unfortunate Jan 08 22:44:21 what gui platform do you use? Jan 08 22:44:25 wqt5 Jan 08 22:44:29 qt5 Jan 08 22:45:35 is it a windowing interface? Jan 08 22:45:38 I put a bit of effort into making the eglfs qpa work, although the linuxfb one works too Jan 08 22:45:55 no, single-window-fullscreen Jan 08 22:46:19 although for windowing I'm pretty sure qt5 is fine with wayland too Jan 08 22:46:32 haven't used wayland yet myself though Jan 08 22:48:40 The TI Arago/yocto that comes w their AM572X EVM (bbx15) comes w wayland. It'd a significant investment of resources to re-write the gui on something else. Jan 08 22:50:01 well, not when using qt5, it lets you pick whether to use X11 or wayland via an environment var (if it doesn't already just autodetect) Jan 08 22:50:23 things may be different with other toolkits Jan 08 23:13:29 wayland fails to start on the bbx15 image. Jan 08 23:15:22 which wayland? I know TI uses a custom branch Jan 08 23:15:58 and do you have the sgx driver operational? otherwise wayland definitely won't work Jan 08 23:16:08 The RCN image. Debian 9. Jan 08 23:16:22 it includes wayland? since when? Jan 08 23:16:47 I'm not sure if I have it loaded. How do I test? Jan 08 23:16:59 if you're not sure then you don't Jan 08 23:17:02 It's in the debian repository. Jan 08 23:18:01 yeah but the one in the debian repository is not going to work. I do wonder why not exactly, and what TI patched, but I haven't dug into it Jan 08 23:19:57 it would definitely be nice if this stuff were to get properly packaged so you can have the sgx drivers and wayland operational with a simple apt-get install, but so far nobody has had enough motivation to put in the effort it seems Jan 08 23:20:03 "apt install weston" it installed w/o complaint about missing dependencies. Jan 08 23:21:18 sure, with its dependencies being met by mesa's software renderer. be glad it doesn't start, it would probably be excruciatingly slow :) Jan 08 23:22:02 yeah, and no, I don't have the sgx driver loaded. looks like one can build it for the linux 4.4.x branch. (https://elinux.org/BeagleBoardDebian) Jan 08 23:22:46 4.4 is obsolete, as are those wiki instructions Jan 08 23:25:54 iirc someone recently put in the effort to get weston running on a bbb, lemme grep the irc logs Jan 08 23:29:34 yeah, see near the end of http://logs.nslu2-linux.org/livelogs/beagle/beagle.20181222.txt and continuing on the next day Jan 08 23:33:21 he already had the sgx drivers working at that point, the relevant irc logs for that are on 20181119 - 20181120 Jan 08 23:39:36 I'm checking it out. Does this sgx driver require the EVE devices to work? Jan 08 23:40:21 eh what? EVEs have absolutely nothing to do with it (also, they're not supported on the bbx15) Jan 08 23:40:50 I haven't tried to get sgx working on the x15 yet, aforementioned was on a beaglebone Jan 08 23:40:51 on my x15 board, /usr/share/ti/examples/opencl/platforms/platforms reports 4 of them. They were mentioned in the irc logs above. Jan 08 23:41:07 I was curious. Jan 08 23:43:18 there are 4 EVEs on the die, but on the part that's on my bbx15 (marked "AM5729BABCXEA") only one is actually available (the other three cannot be enabled in prcm) Jan 08 23:43:28 I don't know if any EVE is available on production AM5728 parts Jan 08 23:49:39 Same here on my bbx15. I have a custom board with the AM5728BABCXEA, but on this board no EVE devices are listed with the platform utility, only the DSP. Jan 08 23:51:47 okay, so the enabled EVE is an actual difference between the am5728 and this magical am5729 that officially doesn't seem to exist Jan 08 23:52:43 from a 2016 TI E2E thread, the AM5729BABCXEA was "used for a limited run of the EVM". I don't know why they're used for the x15, I bought this x15 only a few weeks ago. Jan 08 23:54:36 time to go home. ttyl. Jan 08 23:54:58 I got mine in may Jan 08 23:55:56 maybe that "limited run" is the entire beagleboard-x15 stock, who knows :P Jan 08 23:58:31 it's possible they got them donated to them. isn't beaglebone a non-profit? (yes, I'm still here, putting my coat on) Jan 08 23:59:07 leaving for real now. Jan 09 01:08:42 Hello zmatt. I amtrying to use your show-pins on BBB and I get: Jan 09 01:09:03 root@beaglebone:/usr/local/sbin# ./show-pins Caution: Uses peripheral names from . See README there for details. Can't open /sys/kernel/debug/pinctrl/4a003400.pinmux/pinmux-pins: No such file or directory at ./show-pins line 56. Jan 09 01:11:16 ehh, you're trying to use the bbx15 version Jan 09 01:11:48 use master branch, not bbx15-experimental branch Jan 09 01:13:50 also, when you install something into /usr/local/sbin you can just invoke it as a command ("sudo show-pins", or just "show-pins" if you're already root) Jan 09 01:14:26 Thanks! Jan 09 01:14:54 Oh, you are right. I already started to fixing your script :) Jan 09 01:17:04 master branch is for the BBB, and I have a bunch of different branches for various other beaglebone variants and for the bbx15 Jan 09 01:17:09 Works! thanks! Jan 09 01:17:23 the bbx15 one is totally incompatible, the other ones basically just differ in pin descriptions Jan 09 01:41:50 zmatt, if you do me a favor. I am following the example about PRU from Exploring BeagleBone. I appologize, I still did not have a chance to learn about device trees. From the companion to the book I have loaded the following dt: https://pastebin.com/giguRhHu Jan 09 01:42:08 But build command fails with: Jan 09 01:42:30 you realize that on modern images you don't actually need to mess with overlays? Jan 09 01:43:20 I do not realize :) I am just following the example ... Jan 09 01:43:26 just make sure the right pru overlay is enabled in /boot/uEnv.txt (either the uio-pruss one or the remoteproc one for your kernel series, depending on which of the two you want to use) and if you want to use pru pins use config-pin Jan 09 01:44:35 unfortunately technology books tend to get outdated very quickly Jan 09 01:46:42 so basically, in /boot/uEnv.txt undo whatever you did and make sure the uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo line is uncommented and not one of the other uboot_overlay_pru lines Jan 09 01:48:19 and you can configure the two pru pins from your example with: config-pin P9_27 pruout && config-pin P9_28 pruin Jan 09 01:48:40 (note: the effects of config-pin are not persistent across reboot) Jan 09 01:49:35 I have not modified uEnv yet. The only .dtb0 line uncomented is: Jan 09 01:49:36 uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo # Jan 09 01:49:44 okay, so since you' Jan 09 01:50:01 okay, so since you're presumably trying to use uio-pruss, comment out the RPROC line and uncomment the UIO one Jan 09 01:51:02 you mean to uncomment: Jan 09 01:51:03 uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo Jan 09 01:51:33 also, just curious, what error did you get? I don't see an immediately obvious problem with your overlay, apart from being as hideous as DT overlays tend to be (especially when not making use of macros) Jan 09 01:51:41 yes that's what I explicitly said earlier Jan 09 01:52:24 https://pastebin.com/PPKYuZbK Jan 09 01:52:38 warnings Jan 09 01:54:19 oh you could just have ignored those, or explicitly suppress them using the -Wno-unit_address_vs_reg flag for dtc Jan 09 01:55:01 I do not have enough knowledge to ignore this Jan 09 01:55:19 but on the bright side, asking about it gave you the opportunity to learn that things can be done more easily these days ;) Jan 09 01:55:33 overlays still have their use, but for quick experiments using config-pin is definitely more convenient Jan 09 01:55:41 yeah I understand Jan 09 01:55:54 So basically you are saying that the new image has a bunch of compiled .dtb0 trees, so I do need to compile them. Correct? Jan 09 01:57:27 it has both standard overlays, for example the ones to enable pruss itself (using UIO or remoteproc kernel drivers) Jan 09 01:57:50 and a "universal" overlay which lets you select pin functions per pin at runtime, using the config-pin utility Jan 09 01:57:59 the universal overlay is enabled by default Jan 09 01:59:04 Oh, I see. the difference is that nowadays the pins can be configured dynamically without rebooting. Jan 09 01:59:04 the universal overlay also enables most peripherals, regardless of whether any pins are configured for them, which is why you see a bunch of i2c and spi devices in /dev/ Jan 09 01:59:15 yeah, and without having to write an overlay Jan 09 02:00:44 But on x15 I believe the reboot still requires. Corerct? Jan 09 02:01:43 will continue tomorrow. Thanks! Jan 09 02:02:09 the x15 is a totally different story and much more complicated Jan 09 02:15:14 i'm new with beaglebone Jan 09 02:15:56 i want to know how to interface industrial temperature sensor with output 0 to 10V into beaglebone black Jan 09 02:18:05 you could use a voltage divider to bring it down to 0 - 1.8V range of the adc inputs, just be careful to never drive a voltage into the beaglebone when it is powered off. there are many other ways of course, such as using an opamp or an external adc Jan 09 02:23:24 do you know a reference for an external adc? Jan 09 02:24:06 or is there a specific component for a voltage divider, i don't know very well all eletronic components Jan 09 02:24:46 a voltage divider consists of two resistors Jan 09 02:24:59 just google "voltage divider" Jan 09 02:25:25 ok i found some diagram with google Jan 09 02:25:57 but i was thinking if it already exist in the market at newark farnell or digikey Jan 09 02:26:15 you will find resistors there yes Jan 09 02:26:53 for resistors i can find anywhere yes Jan 09 02:29:03 to scale from 0-10V to 0-1.8V you'd need two resistors with values in ratio 9 : 41 Jan 09 02:30:27 you could use a usb voltage-measuring device. something like http://www.yoctopuce.com/EN/products/usb-electrical-sensors/yocto-volt would protect the beagleboard from nasty voltages Jan 09 02:30:44 the actual values to pick is subject to a variety to trade-offs: smaller resistors means you draw more current from the sensor's output, which may adversely impact the accuracy or be outright forbidden Jan 09 02:31:13 larger resistors increase noise and minimum required sampling time Jan 09 02:31:43 ok Jan 09 02:32:09 yeah if you have absolutely zero experience with analog electronics, and don't want to have to dig into it, you could use an external adc Jan 09 02:32:36 i prefer to use an external adc Jan 09 02:33:20 I don't have any concrete suggestions though Jan 09 02:33:30 the one artag linked to is pretty fancy, but excessively expensive Jan 09 02:33:31 i would like to make an electronic circuit card properly to be used with the beaglebone Jan 09 02:33:33 plus it's usb Jan 09 02:33:53 yeah, I looked for a usb one because it's fairly foolproof Jan 09 02:34:03 there are probably also ones you can connect via i2c or spi Jan 09 02:34:10 i want to use something expensive Jan 09 02:34:44 because i'm using an industrial temperature sensor PT100 with a temerature sensor conditioner Jan 09 02:35:08 pico technology do some good stuff but mostly intended for use with their own software. the data they put onto USB might not be easy for you to read Jan 09 02:35:18 ian__: you can't find a industrial temperature sensor with digital output? 10V analog is really annoying to deal with Jan 09 02:36:33 it might be an existing bit of equipment. 0-10V, 0-5V and 4-20mA are very common on older gear Jan 09 02:36:37 no i didn't find, all are with 0-10V and 4-20mA Jan 09 02:38:20 there are definitely fancy 10V adcs with spi interface Jan 09 02:38:43 but honestly I don't feel like doing the googling for you ;) Jan 09 02:38:55 no dont, i will Jan 09 02:39:07 yeah, but they won't have isolation like a usb or rs232 one Jan 09 02:39:11 and since I don't have experience with any particular part, I can't recommend anything specific Jan 09 02:39:40 ehm, how is usb or rs232 more "isolated" than spi or i2c ? Jan 09 02:40:26 it's not inherently, but once they've gone to the trouble of putting the necessary parts ion it, it's common to find they isolate it too Jan 09 02:40:45 spi and i2c are component-level parts, not board-level Jan 09 02:40:56 so you have to do more to make them useful Jan 09 02:41:16 I don't expect any isolation in an usb device unless it's advertised as a major feature Jan 09 02:41:37 I fully expect the usb connection to tie the ground planes of the devices together Jan 09 02:41:45 i just need a board Jan 09 02:41:46 agreed, but an an industrial adc is exactly where they might advertise that Jan 09 02:41:50 not with usb Jan 09 02:41:53 ok sure Jan 09 02:43:41 this might do. http://audonelectronics.blogspot.com/2006/11/usb-mypclab-daq-units-has-universal.html Jan 09 02:44:04 I've had rs422 converters from them which were nice Jan 09 02:44:53 so there is nothing at farnell nor digikey, if i understanf i need to make by myself Jan 09 02:45:39 from a basic volatge divider circuit found in google Jan 09 02:46:58 farnell do lots of ready made stuff. https://uk.farnell.com/c/test-measurement/data-acquisition-data-logging/prl/results might have something Jan 09 02:47:24 but should also have spi adcs and so on if you want to make it yourself Jan 09 02:47:35 maybe this one https://www.lucid-control.com/usb-rtd-input-module-temperature-measuring-devices/ Jan 09 02:48:07 yeah, that should be fine Jan 09 02:48:25 since you evidently have no electronics experience, if accuracy and reliability is important (as well as avoiding the risk of frying the beaglebone), you may not want to hack something together yourself using a voltage divider Jan 09 02:49:14 i have experience in electronics Jan 09 02:49:24 but you didn't know what a voltage divider was? Jan 09 02:49:29 was long time ago Jan 09 02:53:03 i think i found with lucidcontrol Jan 09 02:53:25 i will try to make one by myself a voltage divider before Jan 09 02:55:47 thank you very much Jan 09 02:59:51 i have another question: is beagleboard-X15 is still manufactured? **** ENDING LOGGING AT Wed Jan 09 02:59:57 2019