**** BEGIN LOGGING AT Fri Apr 06 03:00:01 2018 Apr 06 03:00:20 and for my "base station" (my computer), I would use ping ? Apr 06 03:00:58 That is odd but very understood. Thank you. Apr 06 03:02:13 I was using ping all wrong and w/ arguments, too. Apr 06 03:02:23 Weird. Anyway, thank you. Apr 06 03:05:01 I knew I should have cross-compiled. This 1 GHz is grooving but slowly. Apr 06 03:06:02 1340 files of .h, .c, and .cpp and this BBBlue is taking some heat. Apr 06 03:10:57 oof Apr 06 03:11:09 oof is right! Apr 06 03:11:44 does oof = free time b/c my BBBlue has an appt. right now. Apr 06 03:17:03 Kitlith: in case you're interested, here's the dma setup I used (more or less): https://pastebin.com/raw/SNaS7D1w Apr 06 03:20:12 Kitlith: beware btw that this: cc.dma_job[ dma_ch0 ] = (u32) &jobs[1]; is only valid because I ensure edma is mmap()ed at a 16KB-aligned address (my Job::Link class relies on this too) Apr 06 03:25:00 and I should have phrased the comment above write_barrier(cc); differently... it's merely a compiler-barrier Apr 06 03:33:56 Kitlith: what exactly are you trying to do with dma? Apr 06 03:51:37 dma from pru to pinmux, to have more direction switchable pins on the pocketbeagle. Apr 06 03:57:31 I think I can find the logs of our initial conversation about this if it would help Apr 06 04:09:29 ah Apr 06 04:15:59 I vaguely remember yes Apr 06 04:18:23 zmatt: When files are green, they basically just mean that they are executable, right? Apr 06 04:18:45 i.e. ./ is executable. My memory is shot. Apr 06 04:18:59 the default color scheme for ls colors executables green yes Apr 06 04:19:11 Aw...thank you, sir. Apr 06 04:25:21 afk for a bit Apr 06 04:25:43 Otay! Party time! Apr 06 05:47:09 Bing dong...I got it. Apr 06 05:47:23 myself: I am connected to MavLink and Mission Planner now. Apr 06 05:47:42 The Blue resides in the sky. Well, until I get the necessary parts. Apr 06 07:40:49 is there a way to set ehrpwm pins to high for some time and then do some pwm output on the pins afterwards? (is there a way to use it as a normal gpio and then run pwm functionality on the same pin)? Apr 06 08:05:09 microdevel: isn't that just changing the pinmuxing? if you're running cape universal that should be easy Apr 06 08:07:29 background is i need to initialize device which is connected to ehrpwm1a by pulling it high for 1 second and then apply pwm signal trough the same pin Apr 06 12:57:14 zmatt: so I tried installing the thing Apr 06 12:57:29 Will have to get back to you on it though since you're probably asleep. Apr 06 14:15:35 Hello! Apr 06 14:17:23 jkridner: I got the BBBlue working w/ MavLink and Mission Planner! Apr 06 14:17:45 Now...I just need to set up hard ware and get the software to work w/ it. Apr 06 14:18:34 myself: Did you see that post? Apr 06 14:20:14 I will most likely make a post on Hackster.io and Hackaday.io, too. I have to wait for some items to show but I should be able to get things "kicking." Apr 06 17:23:01 Could anyone help me with reading the analog pins? I'm using 4.14.16-ti-r30 and I'm using this overlay for SPI https://github.com/mvduin/overlay-utils/blob/master/spi0-gpio-cs.dtsi. Apr 06 17:25:36 I guess you might need to add another overlay to mux the ADC pins Apr 06 17:26:31 so because I'm using the spi overlay I have to also have an overlay for analog? Apr 06 17:27:45 i2c works with the SPI overlay without an overlay for i2c Apr 06 17:27:56 dunno Apr 06 17:28:44 zmatt mentioned that if you load an overlay then cape universal goes away. Apr 06 17:28:55 but I haven't played with recent images Apr 06 17:30:01 yeah. I know i2c is still functional just not sure if analogs are or if I need another overlay like you said, or if I'm doing something else wrong Apr 06 17:31:10 i see /dev/iio:device0, but I'm not sure if that is the correct file or if that is the only one that shows up when the analogs are not configured Apr 06 17:33:11 i can also do config-pin -l or -q and see that the pins are the AINX Apr 06 17:34:56 agafford: i2c-2 is special, since it is configured for cape detection, so is always active Apr 06 17:35:27 agafford: I don't think iio:device0 is related to analog inputs, IIRC that's just some internal voltage sensor Apr 06 17:36:01 ah ok. I saw a post mention the analogs are iio devices Apr 06 17:36:17 so seems like i need another overlay Apr 06 17:37:21 agafford: The overlay you posted seems to enable spi0 and map its pins, and contains some example SPI slave device specs that do not actually match any hardware I think. I don't think that dtsi file is inteded to work as-is. Apr 06 17:37:52 agafford: I'm not sure how the analog pins work on the BBB though. Is there an external SPI ADC? Or why are you messing with SPI in the first place? Apr 06 17:38:07 zmatt made is special for me :-) and it works for my setup Apr 06 17:38:26 ive got 2 MEGA 2560s connected to it Apr 06 17:38:39 needed spi0.1 to be on that pin Apr 06 17:38:51 for the second MEGA Apr 06 17:38:56 Ah, right, this overlay is not intended to make analog pins work, right :-) Apr 06 17:39:08 no it was just for the spi Apr 06 17:40:55 agafford: If you do not load any overlays in uboot, you get the cape universal overlay, which enables a lot of hardware modules and allows setting up pin modes using the "config-pin" tool. If you load some overlay, this stuff stops working, so you should instead set up pin modes using an overlay. I don't really know how though (also I'm not sure if just the pin mode is sufficient, or perhaps the ADC should be Apr 06 17:40:57 enabled or other setup is required) Apr 06 17:40:59 * blathijs is off for dinner, though Apr 06 17:41:45 ok, well thanks for the help, i think i know what needs to happen now Apr 06 18:52:29 yeah, add the adc overlay to the list Apr 06 19:48:00 blathijs: the adc pins don't have any pinmux. the overlay is just responsible for configuring and enabling the adc Apr 06 20:17:32 zmatt: you around? Apr 06 20:18:50 also are you willing to help me :P Apr 06 21:17:53 zmatt: could you help me get the adc configured in the SPI overlay you gave me? Apr 06 21:18:18 Also, would the GPIO pins need to be configured as well? Apr 06 22:24:38 agafford: looks like we're both waiting, eh? Apr 06 22:49:06 FL4SHK: yup Apr 06 22:50:36 I've got a plan for what to do with my BBB Apr 06 22:50:44 I'm trying to get hardware accelerated graphics Apr 06 23:20:07 FL4SHK: how is the hard. accel. graph. coming along? Apr 06 23:21:51 set_: I'm following the instructions I can Apr 06 23:22:06 waiting on a certain person to respond back to me with what to do next :P Apr 06 23:28:22 I'm going to want to look up how to use the GPIO in a C++ program. Apr 06 23:28:27 ...or, heck, even C Apr 06 23:28:39 if it works in C I'll be able to use it from C++ anyway. Apr 06 23:28:39 https://pastebin.com/aCWdnFC2 Apr 06 23:28:56 ooooh Apr 06 23:29:14 as for gpio in C++, https://gist.github.com/mvduin/578509d458da8948ae3a14a81dc639e4 Apr 06 23:30:37 agafford: why not just ask u-boot to load the usual adc overlay? (BB-ADC-something) Apr 06 23:31:12 can I do that and still use spi0-gpio-cs.dtsi? Apr 06 23:31:44 u-boot can load a few overlays, there are a bunch of variables for them Apr 06 23:31:49 BB-ADC-00A0.dtbo is in /lib.firmware Apr 06 23:32:33 what would I put in uEnv.txt to tell it to also load BB-ADC-00A0.dtbo? Apr 06 23:33:27 do the uboot_overlay_addr0 through addr7 ones need an i2c device at boot telling them to load or can i just uncomment one and use the ADC one? Apr 06 23:33:35 yeah you can use any of those Apr 06 23:33:55 0-3 are only special in the sense that they override the overlays for auto-detected capes, if any Apr 06 23:34:02 zmatt: Not seeing ti335x in target/ Apr 06 23:34:06 what happens if a cape is connected that has an i2c device on one of those addresses? Apr 06 23:34:50 then u-boot will prefill uboot_overlay_addr0/1/2/3 (depending on eeprom address) with the value specified by eeprom Apr 06 23:35:24 FL4SHK: yes there is... https://github.com/rcn-ee/ti-omap5-sgx-ddk-um-linux/tree/ti-img-sgx/1.14.3699939/targetfs/ti335x Apr 06 23:35:39 oh, wait a minute Apr 06 23:35:58 I may have installed the wrong thing. Apr 06 23:37:01 I need a different branch? Apr 06 23:37:26 it helps if you read what I said Apr 06 23:37:54 Huh? Apr 06 23:37:57 What didn't I read? Apr 06 23:38:19 I explicitly gave two suggestions w.r.t. which branch to try Apr 06 23:38:37 oh Apr 06 23:38:40 Yes, yes you did. Apr 06 23:40:54 ok i used the addr7 one and rebooted. How can I tell if the analog pins are working now? What will their path be? Apr 06 23:41:12 uh something in /sys/bus/iio/devices Apr 06 23:41:23 or /dev/iio* Apr 06 23:41:35 for the sysfs information and iio device respectively Apr 06 23:41:53 i still only see /dev/iio:device0 Apr 06 23:41:53 let me check sys Apr 06 23:42:04 well then that is probably the adc Apr 06 23:42:19 it was there before loadign the overlay Apr 06 23:42:39 oh, and you're sure it's not the adc anyway? Apr 06 23:42:50 I mean I assumed the adc wasn't enabled to begin with since you asked how to enable it Apr 06 23:43:33 but it seems perfectly plausible to me that u-boot loads the adc overlay regardless of whether cape-universal is loaded or not Apr 06 23:43:48 no im not sure but i was not able to get a reading from any pins Apr 06 23:43:59 zmatt: okay got it installed. Apr 06 23:44:46 pastebin! Apr 06 23:49:20 uh, see if initialization seems to work? try gles2test1 ? Apr 06 23:49:39 I need to install the udev thing first Apr 06 23:50:27 ... try actually getting as far as possible on your own with the information available to you? Apr 06 23:50:34 I'm doing that Apr 06 23:50:42 Notice that I haven't asked you how to do that :P Apr 06 23:50:52 I put your udev rule in /lib/udev/rules.d Apr 06 23:51:19 called it hardware_accelerated_graphics.rules Apr 06 23:51:20 sorry, I guess I shouldn't have interpreted your remark as a query for a next step Apr 06 23:51:27 oh oops Apr 06 23:51:34 Yeah I can see how you might have done that. Apr 06 23:51:40 since I didn't give further info. Apr 06 23:51:49 agafford: how were you trying to read the adc pins? Apr 06 23:52:13 i was trying to follow this but changing the path... https://embedded-basics.blogspot.com/2014/10/beaglebone-black-analog-input-pins.html Apr 06 23:52:19 its a bit old tho Apr 06 23:52:34 2014 is ancient history Apr 06 23:52:39 lol yeah Apr 06 23:53:01 is there a command i can type just to see if they are working? Apr 06 23:53:05 iirc you can read the adc values directly from sysfs Apr 06 23:54:12 zmatt: gles2test1 can't find a specific library Apr 06 23:54:16 libgbm Apr 06 23:54:23 oh right Apr 06 23:54:37 I looked for a package Apr 06 23:54:43 and I found something that was probably not it called "gbm" Apr 06 23:54:43 https://github.com/mvduin/libgbm Apr 06 23:54:45 oooh Apr 06 23:55:05 you need a specific libgbm anyway, not the one from mesa Apr 06 23:55:14 I see. So should I remove mesa then? Apr 06 23:55:38 having mesa installed at the same time is a recipe for pain Apr 06 23:55:45 then I'll get rid of it. Apr 06 23:56:14 oh Apr 06 23:56:20 there are packages that want mesa Apr 06 23:56:26 such as? Apr 06 23:56:41 gtk3, retroarch, gst-plugins-base-libs Apr 06 23:56:46 specifically I want to be able to run retroarch Apr 06 23:56:55 I could just make my own package though. Apr 06 23:57:12 weston Apr 06 23:57:17 weston wants mesa installed Apr 06 23:57:40 I'll probably have to build that from source I guess? Apr 06 23:58:00 Oh there is a way I can get rid of those dependencies on the mesa package Apr 06 23:58:07 I know an Arch specific way to do it. Apr 06 23:58:41 this is why on debian I made my own package for the libs that Provides: libgles1, libgles2 Apr 06 23:59:03 I'm goign to instead remove the dependencies on mesa Apr 06 23:59:15 other packages typically don't depend on mesa specifically, just *some* libgles1/2 Apr 06 23:59:22 at least that's the case on debian Apr 06 23:59:56 shoot Apr 07 00:00:09 I need to make a package that provides libgl then. Apr 07 00:00:14 or like, a dummy package. Apr 07 00:00:19 gles Apr 07 00:00:31 the sgx libs do not provide gl Apr 07 00:00:40 the package is called "libgl" here Apr 07 00:00:44 it's still gles Apr 07 00:00:54 what? then what's the gl package called? Apr 07 00:00:58 gl and gles are not the same thing Apr 07 00:01:05 different distro though Apr 07 00:01:13 that doesn't affect my question Apr 07 00:01:26 gl and gles are both things that exist Apr 07 00:01:26 GL and GLES aren't the same thing, no. Apr 07 00:03:36 yes, yes they are. Apr 07 00:10:26 Maybe I should just switch this thing to Debian. Apr 07 00:10:35 lol Apr 07 00:13:13 I think I will go ahead and do that. Apr 07 00:13:16 I'll make a backup of this sytem. Apr 07 00:13:31 It'd end up being easier lol Apr 07 00:13:37 I want the hardware accelerated graphics, darn it. Apr 07 00:14:03 I hope you're not expecting too much from it, it's a pretty low-end gpu :P Apr 07 00:14:20 for my purposes it's probably fine Apr 07 00:33:56 zmatt: would you suggest using the micro SD card or installing to eMMC? Apr 07 00:34:57 I always run from eMMC Apr 07 00:35:07 How can I install to the eMMC Apr 07 00:35:37 I guess I'll do the micro SD card actually. Apr 07 00:35:39 That should be fine. Apr 07 00:36:01 there's a paragraph about it on https://beagleboard.org/latest-images Apr 07 00:36:32 you prep the flash card in the same way for both options anyway... you just uncomment a line in /boot/uEnv.txt to turn a standalone bootable sd card into an eMMC-flasher Apr 07 00:36:40 Okay. Apr 07 01:41:54 hi Apr 07 01:42:39 pyzip guy cannot recognize my board Apr 07 01:42:53 pyzip gui cannot recognize my board Apr 07 01:43:13 on ubuntu **** ENDING LOGGING AT Sat Apr 07 03:00:00 2018