**** BEGIN LOGGING AT Thu Dec 21 03:00:00 2017 Dec 21 04:51:02 Hello, what is the last debian image without remoteproc? Dec 21 12:08:42 though Alex_ is gone, here's the answer for the logs: assuming he was talking about remoteproc-pru specifically, in the latest images you can actually easily enable either remoteproc-pru or uio-pruss by uncommenting a line in /boot/uEnv.txt Dec 21 13:11:38 Anybody running bluetooth on a BBB Wireless? I am having trouble getting it to work. Latest 4.4 kernel 4.4.91-ti-r140, Debian GNU/Linux 9 (stretch) Dec 21 20:09:34 hello, all! I have a beagle blue, and I am trying to access the PRU-ICSS drive without using strawson's library. However, when I try to use TI's APY (prussdrv.h), the program fails because it cannot open the overlay. How do i load the overlay in the new uEnv.txt manner? Dec 21 20:09:48 *API* Dec 21 20:31:49 Guest38498: if you're using the latest image, no overlays are needed at all Dec 21 20:32:20 you can enable uio-pruss (or alternatively remoteproc-pru) by uncommenting the appropriate line in /boot/uEnv.txt Dec 21 20:38:32 (or, well, technically overlays are still involved, but u-boot applies them to the device tree before passing it to the kernel, instead of it being loaded at runtime like it used to be) Dec 21 20:43:55 That is what I thought. I must not have found the correct line. Dec 21 20:46:33 My code consists of making sure the program is run as root, then prussdrv_init call, the prussdrv_open. Am I doing something dumb there, and just do not know it? Dec 21 20:47:46 I am also using the -lprussdrv linker command when compiling. Dec 21 20:59:52 I don't know. which line did you uncomment in /boot/uEnv.txt ? what error are you getting? Dec 21 21:00:44 you haven't really given enough info to go on Dec 21 21:17:10 I understand. What info do you need? I found an article at the beagleboard's elinux wiki that said to add the line, uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo,to the uEnv.txt file. Dec 21 21:18:15 however, that is all I have done to the eEnv.txt. This is the first time I have messed with this file, and I am hesitant to change anything until I know what to do. Dec 21 21:18:47 I, obviously, do not know what I am doing. Dec 21 21:33:24 that's for remoteproc-pru, not uio-pruss Dec 21 21:34:15 also, did you literally *add* it, rather than uncomment it? Dec 21 21:35:46 if the image you're using is recent enough then there should already be two uboot_overlay_pru= lines, although one or both of them will be commented out (prefixed with a #) Dec 21 21:35:56 see e.g. lines 37-41 of https://pastebin.com/JVr005Cf Dec 21 21:36:18 if those lines aren't there already in your /boot/uEnv.txt, then the image you're using is too old Dec 21 21:36:59 if they are there, you should comment the one for rproc (i.e. put a # before it to disable that line) and uncomment (remove the #) the line for uio Dec 21 21:42:26 i added the lines, not uncomment them. Dec 21 21:42:31 cd ~ Dec 21 21:45:04 My uEnv.txt is missing the whole pruss options section. Dec 21 21:48:36 then the image you're running is not recent enough Dec 21 21:48:43 hence those options will have no effect at all Dec 21 21:51:04 What is the easiest way to update the image? Dec 21 21:51:16 Thanks for the help! Dec 21 21:51:52 I have been working on this for SEVERAL hours, and most documentation is for the cape manage, which my image does not have. Dec 21 21:52:04 *manager* Dec 21 21:53:37 you can download the latest official stretch-iot image from bbb.io/latest-images, flash it onto sd card, and turn that into an eMMC flasher by uncommenting one line in /boot/uEnv.txt to turn the sd card into a flasher-card. if you boot from that, it will reflash your eMMC Dec 21 21:53:58 you can also get the latest prebuilt flasher image for stretch-iot (and other releases) at https://elinux.org/Beagleboard:BeagleBoneBlack_Debian Dec 21 21:54:05 you don't have capemgr? that sounds unlikely Dec 21 21:54:09 why do you think that? Dec 21 21:55:13 (note that although capemgr is still around, it isn't actually used as much nowadays as it used to be) Dec 21 21:59:43 cape manager is not in my /sys/devices, which may not imply it is not on the blue. Dec 21 22:00:14 you don't have a /sys/devices/platform/bone_capemgr directory? Dec 21 22:00:43 nope Dec 21 22:00:57 that's odd Dec 21 22:01:09 what's the content of /etc/dogtag say? Dec 21 22:01:13 and /proc/cmdline ? Dec 21 22:02:19 yeah, the blue gave me an advantage of not having to get peripherals for servos, etc, but it is making it a pain programmatically. Dec 21 22:03:22 I just realized, maybe the image you're using is recent enough to use u-boot overlays (which causes bone_capemgr to disappear since it's handled by the u-boot instead) but not recent enough to have the easy toggle for pruss Dec 21 22:03:32 yeah Dec 21 22:03:56 YES! Dec 21 22:04:43 I don't know a huge deal about the blue, my understanding is that it's basically a beaglebone with a robotics cape integrated Dec 21 22:05:20 yeah. Since it is the blue, you think I should still flash the new image? Dec 21 22:05:21 and some of its standard functionality (e.g. the fourth quadrature input) relies on pruss firmware Dec 21 22:06:20 does the blue use a different image? I thought it was just the iot image, same as for other beaglebones Dec 21 22:06:33 is there a TI AArch64 SoC board yet Dec 21 22:06:36 bbb.io/latest-images includes "BeagleBone Blue" in the list Dec 21 22:06:57 kremlin: TI has no AArch64 SoC, nor announced one afaik Dec 21 22:07:05 Yes, i think it uses the IoT image Dec 21 22:07:09 damn Dec 21 22:07:11 maybe next year Dec 21 22:07:22 i have been using allwinner aarch64 board recently Dec 21 22:07:26 and god...do i miss the TI docs... Dec 21 22:07:29 I doubt it, I don't get the impression it's important for their target markets Dec 21 22:07:44 they actually recently released a new dra7 variant that has no ARM cores whatsoever Dec 21 22:07:56 no cortex-A I mean Dec 21 22:08:14 so like, custom ARM cores? Dec 21 22:08:24 the kind you have to have the most expensive ARM license to produce? Dec 21 22:08:30 no Dec 21 22:09:13 maybe i misunderstand Dec 21 22:09:22 the "fanciest" ARM core TI currently uses is the cortex-A15, which is one of the oldest cortex-A cores afaik Dec 21 22:09:47 all ARM licenses except for the topmost one allows you to manufacture cortex-* cores, right? Dec 21 22:10:03 I have no idea how ARM licensing works exactly Dec 21 22:10:22 there's 9 levels of increasing access to ARM designed cortex cores Dec 21 22:11:00 and the topmost license provides you with a robust set of tests that will determine whether a chip is a compliant ARM processor Dec 21 22:11:20 anyway, the dra78x I was referring to has two TI C6600 DSP cores, 2 cortex-M4 cores, and an EVE instance Dec 21 22:11:23 so you can tweak the internal design of the core to suit your needs, if you're making like the next iphone or something Dec 21 22:11:29 oh corex-m Dec 21 22:11:31 mmpf. Dec 21 22:12:10 the C6600 is probably the boot cpu there, but I haven't checked Dec 21 22:12:40 these SoCs are for automotive safety requirements I think, for which the cortex-A15 is.... no fun Dec 21 22:13:04 my friend at TI has been working on automotive stuff for 3 projects straight Dec 21 22:13:10 CANBUS stuff Dec 21 22:13:24 before that it was a wireless power transmitter/receiver for taillights Dec 21 22:13:42 automotive seems to be an important market for TI Dec 21 22:14:36 just the ability to have a hardened realtime controller inside of a linux host is a powerful thing in automotive Dec 21 22:15:11 oh wow, the dra78x/tda3 actually boots from the cortex-M4, hah Dec 21 22:17:03 so it's like a reaaaaaaaly big microcontroller, hehehe Dec 21 22:18:10 Guest38498: anyway, reflashing the latest image should be fine then Dec 21 22:18:31 Guest38498: then you can easily disable remoteproc-pru and enable uio-pruss instead Dec 21 22:19:45 thank you for the help Dec 21 22:19:49 note that obviously that means you'll lose whatever functionality is normally provided by the pruss firmware on the blue (at least, I'm assuming it uses remoteproc, haven't actually ever checked) Dec 21 22:21:00 I should be able to just flash to the back to the current version to get everything back. Right? Dec 21 22:21:30 what do you mean? Dec 21 22:22:07 you can switch between remoteproc-pru and uio-pruss at any time just by changing /boot/uEnv.txt Dec 21 22:22:26 true. duh... Dec 21 22:22:27 I'm tempted to send zmatt a bbblue just for reference :P Dec 21 22:22:53 pack of peripheral pigtails, maybe a handful of servos... Dec 21 22:22:58 he can have mine if he can get it working correctly, lol Dec 21 22:23:15 myself: lol, why? Dec 21 22:25:04 because you're like the model example of sharing your knowledge of all the things you're familiar with Dec 21 22:25:14 so by giving you more hardware to be familiar with, everyone would benefit Dec 21 22:27:28 :) owning a piece of hardware doesn't necessarily motivate me to get familiar with it though. typically I'm motivated *before* I acquire a piece of hardware Dec 21 22:27:39 that's what the servos would be fore Dec 21 22:27:42 for* Dec 21 22:27:54 potential of hilarious waggling displays and such Dec 21 22:28:15 ooh, I should do that. Some of those little round OLEDs on actuated eye-stalks.. hmm Dec 21 22:28:49 also, my knowledge of the am335x is deep enough that I often approach things in ways that are not necessarily useful for newbies Dec 21 22:29:18 I'm like that with solder.. Dec 21 22:29:21 e.g. although I've slowly acquired some knowledge of how things like cape-universal and u-boot overlays work, I don't actually use either of them myself Dec 21 22:30:39 what are you calling servos? Dec 21 22:31:01 e.g. telling Guest38498 about the pru toggle isn't based on me having tested it, I just know the toggle is there because someone pastebinned their uEnv.txt and it seems to work based on user reports Dec 21 22:31:11 the big industrial stuff or the PWM based RC things? Dec 21 22:31:14 little hobby micro servos, PWM-driven things Dec 21 22:31:19 the ones I can get for $2 :) Dec 21 22:31:47 oh those... that's braindead simple Dec 21 22:32:02 Yeah, they're nice to have a pack of around: https://www.ebay.com/itm/222669450312 Dec 21 22:32:23 driving the big industrial ones are more "interesting" Dec 21 22:33:10 what issues are you having with the RC servos? Dec 21 22:33:26 I had a couple Fanuc motors and drives fall into my lap, and haven't figured out what sort of signal the drives expect as input Dec 21 22:33:29 no issues Dec 21 22:33:53 those thing seems to be all over the place Dec 21 22:35:06 Oh. And apparently there's a linuxcnc thread since last I looked. I may have just figured out how I'm spending my vacation.. :) Dec 21 22:35:20 heheh Dec 21 22:35:26 what kind of machine are you thinking of using it for? Dec 21 22:35:47 kremlin: anyway, I've not seen any sort of public indication that TI is working on implementing newer ARM cores. They might be, but I haven't seen any hint towards it. All three cortex-A cores they're using were implemented while they were still in the cellphone market, which was driving the pressure towards newer ARM cores. That pressure is now gone. Dec 21 22:36:11 that's a shame Dec 21 22:36:27 it's too bad cars don't need to address huge amounts of memory or process a lot of data Dec 21 22:36:54 automotive vision obviously does involve processing a lot of data, but they're not using ARM cores for that Dec 21 22:37:12 instead they have dedicated vision subsystems Dec 21 22:37:25 infotainment, especially mapping, is pretty heavy Dec 21 22:38:00 but yeah, the vision processing is handled elsewhere. Lately it seems everyone's just buying Mobileye's hardware for that instead of developing locally Dec 21 22:38:41 ds2: The obvious next machine to fill a gap in the shop would be a plasma cutter, but I have 2 small motors and one giant one, which sorta suggests a lathe. I dunno. Dec 21 22:39:09 myself: plasma? what do you make in your shop? Dec 21 22:39:38 a CNC lathe would new but nice but do you have enough jobs for a CNC lathe ? Dec 21 22:39:39 Everything. https://www.i3detroit.org/wiki/Category:Zones Dec 21 22:39:52 I'm constantly dreaming up uses for a CNC lathe. Dec 21 22:40:35 i find the setup time not worthwhile - CNC is good for profiles and threading...everything else is quicker manually Dec 21 22:40:55 kremlin: TI uses EVE (Embedded Vision Engine) subsystems, which contains an ARP32 risc core together with a vector coprocessor (8x SIMD), DMA, and a very wide interface to the main interconnect Dec 21 22:41:07 Mmmmmm Haas mills Dec 21 22:41:20 no waterjet? Dec 21 22:41:35 kremlin: along with a software solution obviously, of which I know basically nothing Dec 21 22:42:06 no waterjet, lots of reasons. Let's --> #hackerspaces for this :) Dec 21 22:42:28 :) Dec 21 22:48:08 oof, yeah Dec 21 22:48:14 that sounds like some high proprietary stuff Dec 21 22:53:31 kremlin: well, there's a marketing material, and TI regularly manages to put stuff on their site unprotected that's marked "confidential" or otherwise looks like they probably didn't mean to make it public ;) Dec 21 22:53:43 haha Dec 21 22:53:46 I wonder about that sometimes Dec 21 22:53:47 https://training.ti.com/sites/default/files/docs/CVPR_CV_FOR_ADAS_2016_v3.pdf looks interesting Dec 21 22:54:09 it's probably a huge pain to remove a watermark from a pdf Dec 21 22:55:33 not really, pdf is mostly just postscript in a wrapper, so you can manipulate it with sed and awk :P Dec 21 22:55:46 or like, pdf editors Dec 21 22:56:28 myself: often pdfs contain compressed streams though, plus it relies on an object index that uses byte-offsets from the start of the file Dec 21 22:56:51 the qpdf utility makes it easier to mess with pdf files though Dec 21 22:56:54 really? I wonder if old versions don't have that index or something... hmm Dec 21 22:57:01 no, it's always been there Dec 21 22:57:12 huh, ok. Dec 21 23:31:38 ohey, CCS is free these days (even without xds100v2), and 64-bit Dec 21 23:31:49 didn't know that Dec 21 23:32:10 Oh zmatt CCS is free ... well certain processors aren't I think. Dec 21 23:32:21 msp430 and ARM are. Dec 21 23:33:50 Licensing: CCSv7 is now Technology Software Publicly Available (TSPA) compliant. This means that it does not require a paid license. Dec 21 23:33:56 With the release of CCSv7 all previous v4, v5 and v6 releases are free of charge. Dec 21 23:34:26 That's pretty snazzy Dec 21 23:45:37 I feel annoyed we bought CCSv5 Dec 21 23:45:58 Of course that was 2012 Dec 21 23:46:39 so why be annoyed about it? Dec 21 23:47:04 look at it differently: if you're still using CCS, and want to have a modern version, now you don't have to spend money *again* to get v7 Dec 21 23:47:25 (I'm assuming upgrades aren't free) Dec 21 23:48:09 thanks for helping fund the development of the tool that was ultimately released to the world :) Dec 21 23:50:42 hehe Dec 21 23:53:53 Now you understand the annoyance part. Well I remember they took over the GCC variant of the MSP430 that was an indication of there plans I suspect. **** ENDING LOGGING AT Fri Dec 22 03:00:01 2017