**** BEGIN LOGGING AT Thu Apr 09 02:59:57 2020 Apr 09 03:01:59 Dang it. Sure. Apr 09 03:02:20 There is 200 more files on the rc 4 compared to the older rc. Apr 09 03:02:33 Long, long, and long. Apr 09 03:04:56 Good night Apr 09 03:05:04 Peace to you. Apr 09 03:16:52 Well, all in all, it has been a good day. I got my bot back in order w/ vision to/from the bot. No more rougeness. Apr 09 14:29:04 Why are there am335x-bone-common-univ.dtsi and am335x-bone-common-universal.dtsi? Aren’t they basically the same thing? Apr 09 14:30:48 ah, guess the *univ also sets up the pimux-helper whereas *universal are just plain pin defintions Apr 09 16:34:57 buckket: neither is used anyway (since cape-universal is an overlay), but it's still a good question Apr 09 16:36:07 -universal appears older.. it uses magic hex constants instead of macros, and includes fewer pins Apr 09 16:37:17 (-univ also defines an additional "gpio_input" mode even though it is exactly identical to plain "gpio") Apr 09 16:39:09 and -universal doesn't enable the peripherals, it just defines the pinmux helpers and gpio helper Apr 09 16:40:14 so I guess they just exist for some historical reason Apr 09 16:57:11 zmatt: ok thanks for clarifying Apr 09 17:23:11 @zma Apr 09 17:52:23 Is it true that if we power beaglebone black wireless using lipo at 3.3v , the wifi and bluetooth doesnt work? Apr 09 17:53:54 don't try to use the battery header of the beaglebone Apr 09 17:54:41 it is not officially supported, and has too many problems to be usable in practice (with rare exceptions) Apr 09 17:55:12 also, using the battery headers of the BBB safely requires a patch, and this patch isn't possible on the beaglebone black wireless Apr 09 18:06:33 What about pocketbeagle can i use the battery with it. Also there is a temp pin just next to Battery input . What is it used for? Apr 09 18:07:15 no I'm pretty sure it has the same issue Apr 09 18:07:53 but I'm not 100% sure, I'd need to check Apr 09 18:08:27 it would still have a bunch of limitations regardless though (like no working usb host port) Apr 09 18:08:42 and the temp pin is for the battery temperature sensor Apr 09 18:09:14 (to ensure the pmic won't attempt to charge the battery when it's too warm or too cold) Apr 09 18:10:18 okay thanks. What would be the best way to power a cape sitting on pocketbeagle. The Vout can supply 250mA on pocket beagle if i am not wrong Apr 09 18:11:00 depends on the cape Apr 09 18:11:42 there's no single "best way" to design a power scheme, it depends on requirements and constraints of the application Apr 09 18:12:35 I understand but by best i meant more widely used approach on different capes Apr 09 18:12:47 but in general try to use the 3.3V from the pocketbeagle to power your cape's logic, that minimizes risks of power domain violations Apr 09 18:13:22 okay thats what i was asking. thanks Apr 09 18:15:26 if you need a 5V supply for something, use sys_5v (P1.24 / P2.13), though in general when using any supply other than the 3.3V from the beaglebone for any purpose you need to pay careful attention to what you're doing Apr 09 18:16:43 *pocketbeagle Apr 09 18:17:24 in general the most important thing is to avoid exposing any I/O of the pocketbeagle to voltages above its 3.3V supply, and that's kind of automatic if you just use that 3.3V supply for your own logic Apr 09 18:18:35 (whereas interconnecting logic that uses independent supplies requires great care to avoid causing damage during power-up or power-down) Apr 09 18:21:10 OK my concern here is current parameter. I am going to use 3.3v but how much current i need for my peripherals on the cape is something that i am pondering upon and then if this current can be suppled by pocket beagle or not Apr 09 18:21:40 yeah if you need a lot of current then your situation may get more complicated Apr 09 18:22:08 but appropriate solutions to that will be situation-specific Apr 09 18:24:31 true thanks Apr 09 19:01:25 anyone know how to figure out the address for a am3358 pad control register based on http://www.ti.com/lit/ug/spruh73q/spruh73q.pdf ? Apr 09 19:01:43 I thought it would have been Apr 09 19:01:46 "2.1 ARM Cortex-A8 Memory Map" Apr 09 19:02:15 pdp7 would a library be a better method to access it? Unless you are considering methods of hacking. Apr 09 19:02:37 yes, I'm just trying to figure out how the correlation is made Apr 09 19:02:52 like I know this works: Apr 09 19:02:52 AM33XX_PADCONF(AM335X_PIN_MMC0_DAT1, PIN_INPUT_PULLUP, MUX_MODE0) Apr 09 19:03:09 hmm that works through the kernel likely. Apr 09 19:03:17 I was just trying to reconstruct those values from the datasheet Apr 09 19:03:21 include/dt-bindings/pinctrl/am33xx.h:#define PIN_INPUT_PULLUP (INPUT_EN | PULL_UP) Apr 09 19:03:26 include/dt-bindings/pinctrl/omap.h:#define PULL_UP (1 << 4) Apr 09 19:03:42 I think that corresponds to: Apr 09 19:03:42 9.2.2 Pad Control Registers Apr 09 19:03:59 I remember seeing the definitions but nary the addresses Apr 09 19:04:07 I'm wondering now how to know this part: Apr 09 19:04:07 include/dt-bindings/pinctrl/am33xx.h:#define AM335X_PIN_MMC0_DAT1 0x8f8 Apr 09 19:09:57 ah, robert nelson showed me this http://www.ti.com/lit/ds/symlink/am3358.pdf Apr 09 19:13:20 ah so turns out Apr 09 19:13:28 https://www.irccloud.com/pastebin/nwiAsvSt/ Apr 09 19:13:38 "AM335x SitaraTM Processors Technical Apr 09 19:13:38 Reference Manual", Section 9.3.1 CONTROL_MODULE Registers, based on the Apr 09 19:13:38 file autogenerated by TI PinMux. Apr 09 19:19:59 obviously its documented somewhere Apr 09 19:26:44 You likely can find the base offset in a header file the TERM has the memory map based on the base offset see 25.4.1 as for what the offset is it is likely dependant on the processor hence the offset method (IE create a C/C++ structure with volatile keyword etc.) Apr 09 19:26:54 TERM = TRM Apr 09 19:42:07 pdp7: those names ("AM335X_PIN_MMC0_DAT1") are silly anyway, I would advise against using them since they're more likely to be confusing than enlightening Apr 09 19:44:09 pdp7: on the BBB there are constants that reference the expansion header pins, which are more useful. in general you'd either use TI's pinmux tool or look up the index for a pin, for example in my pins spreadsheet (which summarizes data from the am335x datasheet and TRM, and also has tabs specific to the BBB and some other beaglebone variants): https://goo.gl/Jkcg0w Apr 09 19:44:35 the "Pin" column is the index into the padconf array of the control module Apr 09 19:46:23 (so the address would be 0x44e10800 + 4 * pin) Apr 09 19:58:26 thanks Apr 09 22:28:10 Quick question: I’m currently writing a custom dts file for the BBB and I defined some GPIO pins (e.g. with pullups enabled) and used the "bone-pinmux-helper" to set those mux modes, but when booting the pullups are not enabled. Is this to be expected? Meaning the only way to have those pullups active from the get go is to use the long route by explicitly defining those GPIOs via the gpio-keys or Apr 09 22:28:12 gpio-leds binding? Apr 09 22:29:23 buckket: the purpose of bone-pinmux-helper is to allow runtime selection of pinmux states. if that's not your goal then it's probably not the right tool for the job Apr 09 22:30:05 it should still activate your pinmux though, so if it doesn't then there's either something wrong with your declaration or some sort of pinmux conflict happening Apr 09 22:30:41 typically for gpios you'd attach the pinmux nodes to the gpio-of-helper device that sets up the gpios themselves Apr 09 22:32:37 see https://github.com/mvduin/overlay-utils/blob/master/gpio-demo.dtsi for an example of a gpio-of-helper device (but beware that this project uses different macros/constants than those in the linux kernel, especially for pinmux) Apr 09 22:33:33 buckket: you should only use gpio-leds or gpio-keys is that's appropriate for your application Apr 09 22:33:42 *if that's appropriate Apr 09 22:36:38 pinmux nodes work exactly the same for every device, regardless of whether that's a gpio-keys, gpio-leds, gpio-of-helper, bone-pinmux-helper, or any other kind of device. the only difference is which pinctrl-names might be used: typically you'd only use "default" (though two other generic states exist: "init" and "sleep"), some specific devices might define additional custom pinmux states, and ... Apr 09 22:36:44 ...bone-pinmux-helper allows userspace to select any state (that's in fact its entire purpose) Apr 09 22:37:54 to debug your pinmux configuration you may find my show-pins utility helpful: https://github.com/mvduin/bbb-pin-utils/#show-pins it also shows the name of the pinmux node that has claimed a pin Apr 09 22:38:54 Okay, will give gpio-of-helper a try. Thanks for pointing me in the right direction, really didn’t need runtime selection anyway. I have studied a few of the other beaglebone dts/dtsi files an saw it beeing used for static pinmux configurations, that’s what got me started on that idea. :D Apr 09 22:39:42 yeah there's some pretty confused DT sources out there... iirc the one for the beaglebone blue was downright bizarre Apr 09 22:40:06 in general pinmux should be attached to whichever device it belongs to Apr 09 22:44:49 what packages would you need to add to a flasher images to run a LCD Cape Apr 09 22:46:04 MattB0ne: ehh, if it's a standard lcd cape (supported by cape autodetection) then it should work plug&play for any of the images available Apr 09 22:48:35 (if the cape is custom or otherwise not supported by autodetection then a suitable custom overlay needs to be provided and configured into /boot/uEnv.txt, again regardless of the image used) Apr 09 22:56:22 ok i was going to stick with my image that just uses the EMMC, good to know it will work regradless Apr 09 22:56:50 outside of faster boot time, any other advantage of EMMC vs Sd card? Apr 09 22:57:34 it doesn't use the card slot, and eMMC reliability should be better than that of consumer SD cards Apr 09 22:58:24 also, since the sd card isn't latched into place, using it is probably inappropriate for devices that may be subject to mechanical impact or vibration Apr 09 23:07:32 Like my BBBlue Drone! Apr 09 23:10:00 eMMc has roughly 10 to 100 times the wear durability of SD Apr 09 23:10:24 high durability SD cards are pretty pricey by comparison Apr 09 23:11:43 and you can reconfigure it into SLC mode (which is what we do) to get more reliability at the expense of sacrificing 50% of its capacity (which doesn't matter for us since we only use about 400-500 MB anyway) Apr 09 23:18:40 zmatt: what image is that proprietary? Apr 09 23:18:52 ? Apr 09 23:20:13 you mean the system we're running? yeah that's just a debian buster system customized for our application Apr 09 23:25:23 ok Apr 09 23:32:06 any opinions on the latest images Apr 09 23:32:13 see they updated beaglebone.org Apr 09 23:37:10 Fast... Apr 09 23:37:31 I have found that i need to update the time/date for the updates to work. Apr 09 23:37:47 for debian? Apr 09 23:37:52 Yep. Apr 09 23:37:59 At least on my end. Apr 09 23:38:05 hmm let me check something Apr 09 23:38:08 Okay. Apr 09 23:38:48 I am going to update the drone idea soon on hackster.io. I think the new image does it justice. Apr 09 23:40:43 So will it be a fire fighting drone, a pest drone or just Yet Another Drone (YADa) Apr 09 23:42:16 Another! Apr 09 23:42:35 I can add hardware to it if necessary. Apr 09 23:42:40 Maybe a party drone? Apr 09 23:42:55 Well looks like update and upgrade work on my last image so that works. Apr 09 23:43:09 never set the time date either... hmm Apr 09 23:43:21 It works but sudo dpkg-reconfigure tzdata needs to be run. Apr 09 23:43:30 For the new images, i.e. at least on my side. Apr 09 23:46:14 I think I'm in stretch and you are abusing buster Apr 09 23:46:41 Right Apr 09 23:48:11 still updating but doesn't seem to be anything problematic Apr 09 23:52:33 Hmm. Well, blame me, I guess but the drone is in action. Apr 09 23:53:49 I just need to figure out how to apply the props on this thing. Let us see. four props on four prop holders that can be turned either rightside up or the other way. There are too many routes to take. Apr 09 23:54:19 ... Apr 09 23:54:24 That is the only issue so far. Apr 09 23:56:17 assemble first and then ask questions Apr 09 23:59:52 It is. The assembly has been done. And may I say, "Over and over!" Apr 10 00:00:08 I cannot figure out the dang props on this bot/drone. Apr 10 00:00:38 I have four props. Luckily, two are red and two are yellow. Apr 10 00:01:00 This cuts down the amount of time of looking things over. Apr 10 00:01:17 But...they are not labeled. Apr 10 00:01:32 Front right or left back and so forth... Apr 10 00:02:32 I have four motors. Okay. They either move cw or ccw. Apr 10 00:02:42 Or both? Apr 10 00:03:43 I should have invested in a better bot. This was my first and I knew nothing just like now. So, off to gather bogus ideas. Apr 10 00:05:10 Now, the source works and it is vast! Apr 10 00:12:15 GenTooMan: Do you want a video? Apr 10 00:12:31 I can show slow motion if I get the right software. Apr 10 00:13:22 a cw and or ccw prop can be reversed and used the other direction just not as well. As for which way they turn the concave side of the prop is generally in the direction of air flow Apr 10 00:13:53 I know. I read it. Apr 10 00:14:00 Wait. Apr 10 00:15:11 you may have cw and ccw proper also that helps counter rotational torque issues leading to better stability. Many motors run the same in either direction so that works fine. Apr 10 00:18:52 https://download.ardupilot.org/downloads/wiki/pdf_guides/APM2_Quad_Setup_3.pdf Apr 10 00:18:54 Like that idea? Apr 10 00:19:31 I found it shows some ideas for motor and propeller format. Apr 10 00:20:22 That is the only thing that is not covered. I will have to keep testing. Apr 10 00:20:32 So, maybe one motor at a time? Apr 10 00:21:11 If it pops up on the leg/arm with that one motor turning w/ the attached prop, it could be worth that fascination. Apr 10 00:21:39 let me repeat what I said if you look at page one it confirms they use contra rotating props by the way. So likely each color is a different direction. That said I doubt which layout on page 1 makes a difference at all. Apr 10 00:22:41 Okay. Apr 10 00:22:50 Hey man, I just got a reply from someone. Apr 10 00:23:03 This person thinks that the motors are turning in the incorrect direction. Apr 10 00:23:24 But, which one? You know. Apr 10 00:23:29 How would I test that? Apr 10 00:24:21 So, I apply the cw rotation via controller but it moves ccw instead. That is the theory from this person online. Apr 10 00:26:56 some motors have what's termed bias. That is they are designed to rotate in one direction more efficiently. As for the direction of the motors I suggest looking at the wiring and it's coloration. Often blue red and black are used for 3phase brushless motors and red black are used for brushed motors. Check the polarity. With 3 phase motors swapping 2 wires reverses it's directions. Apr 10 00:28:33 All black. Apr 10 00:28:47 My 3phase motors have all black wiring. Ha. Apr 10 00:29:15 I will switch two of the wires. I think I just learned something. Apr 10 00:29:26 Odd. Problem solving. Apr 10 00:30:48 So, each motor should be turning, all four, cw at the same time to move upward, i.e. even w/ props positioned/mfg. differently. Nice! Apr 10 00:31:08 read page 1 again. Apr 10 00:31:11 Fine. Apr 10 00:32:12 I am off to solder something! Apr 10 00:32:28 or look at ... notice in both diagrams the motors are rotating contrary to each other adjacently and the same direction on opposite sides. This is to do what I mentioned earlier and prevent torque imbalance from rotating the drone Apr 10 00:33:10 Okay. I understand that idea but if one of my motors is turning in the opposite direction when cw is applied, it is pointless. Apr 10 00:33:43 I need to study. brb or bbl. Apr 10 00:33:54 are all the blades cw or ccw probably not. Apr 10 00:34:18 Two are cw and two are ccw, I think. I have no idea. Apr 10 00:36:59 GenTooMan: Let me see if I can find the schematic. Apr 10 00:39:25 Anyway, that is a mechanic schematic and has not info. Apr 10 00:41:25 well you can tell the props by looking at the leader and trailing edge on them which direction they turn. Apr 10 00:48:30 as for which motors do which that is a bit more challenging. However the diagram page of APM2 quad setup is more than just a big hint read page 2 for hints as to which goes where section E gives instructions on prop setup also. I suppose you could just follow the directions? :D Apr 10 00:51:22 GenTooMan: That is a generic page for the ideas. Apr 10 00:51:50 I got that from the ArduPilot website. Apr 10 00:52:26 I have a video now. Do not laugh. Apr 10 00:52:34 I am not a videographer. Apr 10 00:55:47 Forget it. I must have messed up the video too. Apr 10 00:57:06 I am out of room on my card. Apr 10 00:57:08 Blah. Apr 10 00:59:14 Nope, I just do not get how to wait. Patience. Patience. Apr 10 00:59:26 I will get the video up and running soon. It will take time. Apr 10 01:00:40 set_ it says basically what I said before just read it as it has a good chance of getting things working correctly before you try to fly. Apr 10 01:03:53 I understand what you are saying. I am not going against you. One of my motors makes the propeller, by default, blow in my face. Ha. Apr 10 01:04:20 This means, that it is not catching air but trying to dive constantly while I am commanding it to lift. Apr 10 01:10:28 well you know the order of the props based on that Apr 10 01:11:00 dang it. I know nothing right now. Blah. Apr 10 01:13:26 it is the wrong direction prop so you put the opposite one on and stagger according to the digarm on page 1 Apr 10 01:13:34 Fine. Apr 10 01:13:39 My camera broke. Apr 10 01:13:44 I will try it out. Apr 10 01:21:12 Does anyone know if the Beagle Bone AI supports 4 Quadrature encoders? Apr 10 01:22:18 eqep? Apr 10 01:22:27 Look here: https://docs.google.com/spreadsheets/d/1mSqEpV_BAUHfeNApytxHcGhgTZwypy564GyOr66Nphs/edit?pli=1#gid=854495639 Apr 10 01:22:48 That is @zmatt's pin out. Scroll down. It shows the eqep's available. Apr 10 01:23:14 On the bottom on the page is the different boards from beagleboard.org. Apr 10 01:36:34 Parker: did you see the link? I will check which lines the eqeps are referenced. Apr 10 01:37:45 So, line 54, 56, 86, and 87. Apr 10 01:37:55 I think those four will help you. Apr 10 01:38:59 thanks set, what is Vayu? just wondering Apr 10 01:42:50 No clue. Apr 10 01:43:01 I see QEP 0-2 which makes me thing there are only 3 :( Apr 10 01:43:27 I know on the beaglebone blue they had 3 and then implemented on in the PRU Apr 10 01:43:40 Oh. Let me check again. I am sure there has to be more than three. Apr 10 01:46:01 I am dealing w/ the BBBlue right now. Apr 10 01:47:29 I have one, but the encoders are only 3.3V I think and they didnt have enough current for the motors I have Apr 10 01:47:58 I see one is labeled as a strobe. I am not completely sure what that entails. Apr 10 01:48:02 Oh. Apr 10 01:48:26 I feel like TI just puts 3 QEP in Apr 10 01:48:44 I just want 4!!! Apr 10 01:49:08 Hmm. I would not know. Maybe another person would jump in at some point. I usually do not mess w/ eqeps. Apr 10 01:49:39 What I am working with right now is an Odroid X4 and a custom M7 board based on a SAMS70 which supports 4 encoderes Apr 10 01:49:48 Oh. Apr 10 01:50:08 There are capes you can use for Motor Movement. Apr 10 01:50:21 One comes to mind, I use it, the MotorCape. Apr 10 01:50:26 I need the USB3 for my realsense Apr 10 01:50:38 Oh. Apr 10 01:50:51 Yeah, the motor movement isn't the problem, its the encoders Apr 10 01:51:22 Okay. I do not know the answer. I usually just spread the word or have my own issues. Apr 10 01:51:38 If I rev B my custom board it will probably be perfect! missed a couple pullups... Apr 10 01:52:17 Let me keep reading. I know there is a github.com wiki for the AI. Apr 10 01:52:22 Let me see if that has any info. Apr 10 01:53:33 I saw the AI with Vision engines, USB 3 and in a beagle bone platform... Apr 10 01:53:41 nope. Not yet. I think those fellows have been busy pushing a new image. Apr 10 01:53:56 TODO is listed under eQEP. Apr 10 01:54:16 Yeah, it's pretty bare over there, I get it though Apr 10 01:54:25 Hmm. I guess the schematic is next. Apr 10 01:54:29 Do you have time? Apr 10 01:54:34 yep Apr 10 01:54:38 I can check the schematic too. Apr 10 01:54:40 Please hold. Apr 10 01:54:47 I'll take a look again Apr 10 01:57:45 I looked up eQEP on the schematic. I came up w/ four options only. Does two eQEPs make up on module? Apr 10 01:58:56 on = one Apr 10 02:00:56 GenTooMan: I changed out two of the props. Apr 10 02:00:57 there are 2 or 3 pins per module. A and B are always there, some times there is ans ID pin Apr 10 02:01:09 Oh. Apr 10 02:01:10 Okay. Apr 10 02:02:09 "Getting my goggles on and some ties." Apr 10 02:03:20 Well thanks for the help Set Apr 10 02:04:00 I may switch to a BBAI and custom M7 cape Apr 10 02:11:26 No go. Apr 10 02:11:41 Dang it. The same two motors are giving me issues. Apr 10 02:13:16 I switched the props and they are still blowing wind upward. Apr 10 02:19:13 Hey. I got the video to work. My cam is working again! Apr 10 02:25:57 please excuse the profanity. I made a bleep once. Sorry. Apr 10 02:27:27 Well, it will take some time to upload it. Please bear w/ me. Apr 10 02:44:28 https://drive.google.com/file/d/1ufP0PlhI3H-AlJvp2AgvenurxVmHt48V/view?usp=sharing should be it. Enjoy! Apr 10 02:44:53 It is nothing special but it shows the board, the two questionable props on the right side, and some action. Apr 10 02:45:58 .avi Apr 10 02:49:53 It may take a while to "develop" on the google drive shared link. I cannot view it yet. Apr 10 02:55:19 Sorry for the bad video. I just watched it. Yikes. Apr 10 02:55:22 lol Apr 10 02:55:27 hahaha. Apr 10 02:55:28 i was expecting it to take off Apr 10 02:55:33 Not yet! Apr 10 02:55:52 do you need an AI for drones or you just wanted to use it for that purpose Apr 10 02:56:01 I have two bad motors working against the correct motion. Apr 10 02:56:04 It is a BBBlue. Apr 10 02:57:13 The motors move so fast. I cannot tell which way they are moving. Slow-motion time. Apr 10 02:59:10 blue is for robotics Apr 10 02:59:13 ? Apr 10 02:59:50 Yep. **** ENDING LOGGING AT Fri Apr 10 02:59:57 2020