**** BEGIN LOGGING AT Mon Sep 23 02:59:57 2019 Sep 23 07:34:24 HI! Sep 23 07:35:10 =D Sep 23 10:42:40 Question. Does anybody know what the core clock of the SGX544 in the http://beagleboard.org/ai is? The question mostly stems from pure curiosity rather than a use case that needs the information. Sep 23 11:35:08 Eric_Sweet: should be the same as on the bbx15 Sep 23 11:35:32 so 532 MHz Sep 23 11:37:05 OK, thanks! Sep 23 11:37:09 :) Sep 23 14:28:22 Hi all, Can somebody guide how can i update my eMMC with debian from SD card, as I am using BBB rev b with 2GB eMMC Sep 23 14:29:25 ali: install etcher.io, grab microSD, flash one of the 2GB images.. Sep 23 14:32:57 I have already tried with win32diskimager for 2GB umages , linux starts from SD card but when i tried to transfer it in eMMC error appears Sep 23 14:33:28 Re-reading the partition table ... Sep 23 14:33:29 fdisk(8).) Sep 23 14:33:49 the above are last statements Sep 23 14:35:15 do you have any idea about it Sep 23 14:35:19 "when i tried to transfer"... how are you starting the transfer, your own script or what? Sep 23 14:36:12 no not my own it is alredy there in /opt/script/tools/eMMC Sep 23 14:36:49 ali: details.. there are lots of scripts under their, which one exactly? Sep 23 14:37:25 i run this beaglebone-black-make-microSD-flasher-from-eMMC.sh Sep 23 14:37:40 as this is the only one present Sep 23 14:37:59 ali: "make microSD flasher from eMMC" ... that's eMMC -> microSD.. Sep 23 14:38:26 ok Sep 23 14:38:58 Just grab the eMMC flasher from here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Stretch_Console_Snapshot Sep 23 14:39:00 so in which directory can i find it , microSSD-> eMMC Sep 23 14:39:06 use etcher.io to write it to a microSD.. Sep 23 14:40:14 and it will directly load the image in eMMC from SD Sep 23 14:40:28 or do i need to rum any script for it Sep 23 14:40:55 it'll do all the work, and shtudown when finished.. should take 5-8 minutes max.. Sep 23 14:41:29 you may have to hold the "boot" button before poweron, depending on old the emmc bootloader is.. Sep 23 14:42:44 (more accurately "during" power-on. you can let go once any led turns on, and it's recommended to let go within a few seconds) Sep 23 14:43:21 okthanks i try it Sep 23 14:56:21 actually the fact that you've been able to boot from sd card implies that the boot button is unnecessary in your case Sep 23 16:14:50 thanks rcn-ee[m] ,it works for me . image has been successfully flashed into eMMC and working Sep 23 17:11:18 Hello all, not sure if this is the right spot to ask this but do any of you have drawings for the Pocket Beagle? Sep 23 17:13:13 I am trying to make a PCB for it and searched through the github documentation and got a 3d model of it. I just measured it with a caliper and i got .9 inches between the two inner most pins of the GPiO header. (900mills (imperial), 22.86mm (metric). Can anyone confirm this is the correct distance? Sep 23 17:19:53 chris24: pretty sure the pitch (distance between centers of adjecent pins) of the gpio header in 0.1 inch, at least it is on the beaglebone Sep 23 17:21:08 So, you are right. That is pitch distance between other pins in the same header. However, in the pocket beagle there are two headers on opposite sides of the board, and it's the distance between these two headers I am trying to find. Sep 23 17:29:02 chris24: if I import KiCAD/plots/PocketBeagle-DigitalGND.pdf in gimp, the result appears to be exactly to-scale (if I specify a resolution of 1000 pixels/inch, the distance from the left edge of one pin to the next is exactly 100 pixels, and from pin 1 to pin 35 is 1700 pixels (1.7 inch)) Sep 23 17:30:31 distance from P1.01 to P2.01 is 1 inch Sep 23 17:30:47 zmatt you are amazing! Sep 23 17:31:02 :) Sep 23 17:32:00 so conveniently both headers align to a shared 0.1 x 0.1 inch grid Sep 23 17:32:03 This is awesome, thank you so much for taking the time out of your day to help me! Are the raw KiCAD files available for me to view? Or is that proprietary? If so, could you please link them? Sep 23 17:32:58 are they not simply in the KiCAD directory? I'm not responsible for any of these files Sep 23 17:33:15 (I don't work for beagleboard.org, I'm just a random beaglebone user) Sep 23 17:33:22 P1.01 to P2.01 is exactly what I was looking for. Sep 23 17:34:02 Let me check, I may have glossed over it. Sep 23 17:34:54 I've never used KiCAD but "PocketBeagle.kicad_pcb" sounds like it would be the pcb :P Sep 23 17:35:52 It is! KiCAD is my primary PCB package. You are awesome! This will help me massively. Thank you so much again. I cannot believe I didn't see that resource. Sep 23 17:37:40 you're welcome Sep 23 21:59:32 I see someone posted some new images. Nice! Sep 23 23:23:08 Okay, the Cape came in. This is where it is located: https://www.seeedstudio.com/5-Inch-BeagleBone-Green-LCD-Cape-with-Resistive-Touch-p-2642.html. Sep 23 23:23:10 ... Sep 23 23:23:27 Can I use the Cape w/out a keyboard or do I need to use a keyboard to operate this Cape? Sep 23 23:24:15 "operate" a cape? :P Sep 23 23:24:28 Yes. I know it sounds funny. Sep 23 23:24:59 this cape is a touchscreen and 5 buttons (not counting the power button)... what you do with that is not the cape's problem Sep 23 23:25:14 Okay. Sep 23 23:25:32 There is some sort of sign in screen right now but I cannot find out how to get to it. Sep 23 23:25:34 if for your application you want more than 5 button then you'll need to connect some additional input device. if you don't, then you don't Sep 23 23:25:58 I guess, keyboard action time. Sep 23 23:25:59 Sheesh. Sep 23 23:26:20 There is a three switch device on the back of the cape. Sep 23 23:26:50 if you intend to use a standard desktop environment on a beaglebone (whether with lcd cape or external display) then... well mostly I feel sorry for you, but also you'll probably want a keyboard yes Sep 23 23:27:11 That is the only configuration I could figure out. Sep 23 23:27:14 probably for the cape i2c address? Sep 23 23:27:21 Back to the keyboard. Sep 23 23:27:22 Oh. Sep 23 23:27:25 in case you have multiple capes stacked Sep 23 23:27:31 Aw! Sep 23 23:27:37 that's just my guess Sep 23 23:27:48 I am pretty sure you may just be correct. Sep 23 23:28:05 I am searching for the schematic now. Sep 23 23:28:14 http://statics3.seeedstudio.com/assets/file/bazaar/product/5INCH_BBG_00A2_SCH.pdf Sep 23 23:28:55 lol, this is the schematic their sit elinks to Sep 23 23:29:28 but this can't be right... there's no switch there, also no eeprom Sep 23 23:29:42 I found this one earlier. Sep 23 23:29:47 Thank you. Sep 23 23:30:14 It had some Chinese and English on it. Sep 23 23:30:57 and they link to the wrong forum category... nice site seeed Sep 23 23:31:18 Ha. They are always doing something. Sep 23 23:31:21 Oh well. Sep 23 23:31:30 I will email them directly. Sep 23 23:31:43 Now...the Cape works. Sep 23 23:32:00 It is powered on and the sign in screen is available. Sep 23 23:32:19 I will just use the keyboard to get to my xfce4 desktop. Sep 23 23:33:05 Off to find a keyboard. Sep 23 23:33:08 Boy! Sep 23 23:37:59 oh lol there's no need to guess what the switch does, it's written right there on the silkscreen Sep 23 23:40:11 Where? Sep 23 23:40:34 looks like this cape unfortunately uses the wrong pins for 5V power, so you won't have a working backlight if you power the beaglebone via usb Sep 23 23:40:49 Dang it. Sep 23 23:41:27 I can get around that. Sep 23 23:41:35 That is fine, actually. Sep 23 23:41:37 though you could power the beaglebone from the cape by using the microusb connector on the cape Sep 23 23:41:42 Right! Sep 23 23:41:51 That was my first step. Sep 23 23:42:14 (but if you do, be sure to not simultaneously power the beaglebone via its barrel jack) Sep 23 23:42:21 Oh? Sep 23 23:42:45 Okay. Sep 23 23:43:27 anyway, "< set_> Where?" .. there isn't that much text on the pcb :P Sep 23 23:43:41 I know. Sep 23 23:43:43 "SW1 sets the Cape I2C Address:" Sep 23 23:43:55 oh. Sep 23 23:44:38 anyway, it only matters if you have more than one cape attached at the same time (since each cape should have a different address in that case) Sep 23 23:45:06 Okay. I was thinking of putting the MotorBridgeCape on it but not right now. I am not close to ready for that idea. Sep 23 23:45:14 and that's something that requires a bit of care anyway Sep 23 23:45:30 From what you are typing, I am seeing that right now. Sep 23 23:45:40 "a bit of care." Sep 23 23:46:12 be sure to double-check that the capes don't conflict, e.g. first connect one at a time and check the pin usage using my show-pins utility, and compare those two outputs side-by-side Sep 23 23:46:53 (I'm not sure whether u-boot will do this check for you, although it ought to) Sep 23 23:47:01 (I suspect it doesn't) Sep 23 23:47:24 Oh. Okay. Sep 23 23:47:55 Hey. Is it the I/O section on the schematic? Sep 23 23:48:04 set_: ? Sep 23 23:48:14 Well. Sep 23 23:48:33 there is no schematic as far as I can tell, since they schematic they linked to clearly doesn't match the cape Sep 23 23:48:44 *the schematic they linked to Sep 23 23:48:45 Oh. Sep 23 23:48:47 ! Sep 23 23:48:50 I got you now. Sep 23 23:48:53 I did not understand. Sep 23 23:49:09 So, I will contact them about their Cape schematic. Sep 23 23:49:35 and yeah you could statically check the cape-overlays for the two capes, but I think that's more error-prone than comparing the show-pins output for the two capes side-by-side Sep 23 23:49:48 Okay. Sep 23 23:49:57 It sounds like work but it might be fun! Sep 23 23:50:32 uhh, does the motor bridge cape have an overlay? I'm not seeing one in the bb.org-overlays repository Sep 23 23:50:43 Anyway, thank you for your ideas and instruction. I will follow the guide. Sep 23 23:50:45 I do not think so. Sep 23 23:50:51 I cannot remember one. Sep 23 23:51:05 great Sep 23 23:51:18 So, now what? There is no way to tell what is what? Sep 23 23:53:03 It has a co-processor on it. Sep 23 23:55:02 BB-UART2-00A0.dtbo is the u-boot overlay. Sep 23 23:55:53 hmm, looks like there's one potential pin conflict Sep 23 23:56:02 You already searched it? Sep 23 23:56:14 Dang. Speedy. Okay. Sep 23 23:56:35 So, I can make pin conflicts but I will be careful. Sep 23 23:56:43 Nice! Sep 23 23:57:49 P9.23 (gpio 1.17) is used by the motorbridge cape as reset signal and by the lcd cape as "right" button.. which means that if you press that button on the lcd cape, the processor on the motor bridge cape will reset Sep 23 23:58:02 Ha. Sep 23 23:58:13 I know it is not funny but it is. Sep 23 23:58:24 but as long as you don't press that button on the lcd cape there's no issue Sep 23 23:58:32 Okay. Sep 23 23:59:01 So, I guess I can use three other buttons to work the Cape. Sep 23 23:59:11 four Sep 23 23:59:18 Oh yea. right. Sep 23 23:59:24 And Enter. Sep 23 23:59:24 and it wouldn't be too hard to patch the lcd cape to work around this Sep 23 23:59:32 I know. Sep 23 23:59:37 I have already been thinking of ideas. Sep 24 00:00:07 Instead of pushing the cape in, I could use wires to attach the cape to another portion of the headers pins. Sep 24 00:00:33 I then can change the u-boot overlay and reboot, right? Sep 24 00:00:35 e.g. connect P9.23 to the neighbouring P9.24 on the lcd cape, and break off the pin for P9.23 on it Sep 24 00:00:43 and change the overlay to match Sep 24 00:00:49 Okay. Sep 24 00:00:56 Let me write this down. Sep 24 00:01:19 for reference, the motor bridge cape uses P9.21/22 (uart), P9.23 (reset), P9.25 (boot0) Sep 24 00:01:31 Okay. Sep 24 00:01:50 the latter two are basically only used for updating the firmware, but even if you don't use them normally they're still a risk for conlicts Sep 24 00:02:55 Wait. Sep 24 00:03:37 @zmatt: You said connect p9.23 to p9.24 and break off p9.23. Sep 24 00:03:45 yes Sep 24 00:03:57 I am not quite sure I understand. Sep 24 00:04:09 already grabbing pen and paper Sep 24 00:04:21 I could just clip the p9.23 pin. Sep 24 00:04:23 Off the cape. Sep 24 00:04:44 I can still count. Sep 24 00:04:48 Sort of. Sep 24 00:05:01 that will fix the conflict but it means the "right" button won't work Sep 24 00:05:08 Oh. Sep 24 00:05:23 I could just desolder the right button off the board. Sep 24 00:05:39 It is a basic push button. Sep 24 00:05:48 4-pin. Sep 24 00:05:58 that sounds like a much worse idea than breaking off the pin Sep 24 00:06:03 Okay. Sep 24 00:06:10 Both are pretty obvious. Sep 24 00:06:21 Obvious and odd. Sep 24 00:06:25 That is all. Sep 24 00:06:27 since 1. it requires soldering 2. it means you can't patch around it later to make the button working again Sep 24 00:06:37 Oh. Sep 24 00:07:36 Maybe I can just dull out the p9.23 pin somehow, i.e. rubber sleeve? Sep 24 00:07:54 no Sep 24 00:07:58 Fine. Sep 24 00:08:30 patching the motor bridge cape would be another option, but probably a lot harder... it would require cutting the right pcb trace Sep 24 00:08:39 That is if I wanted to use this LCD Cape w/ the Motor Bridge Cape, only. Sep 24 00:08:41 Yikes. Sep 24 00:08:54 pcb traces. Not for me. Sep 24 00:09:18 W/ an x-acto knife or something? Sep 24 00:09:41 yeah.. I'm not recommending it Sep 24 00:09:49 Okay. Sep 24 00:09:50 No issue. Sep 24 00:10:13 hold on lemme check something Sep 24 00:10:38 OKay. Sep 24 00:19:33 ok I'm honestly confused how the motor bridge cape can possibly boot at all... Sep 24 00:20:07 @zmatt: Stop your thoughts for now, please sir. I am off to another place real quickly. bbl. Sep 24 00:20:10 Sorry. Sep 24 00:25:25 ohh maybe I do... namely how? => by pure accident Sep 24 00:25:51 and it probably wouldn't anymore with the lcd cape attached Sep 24 00:29:23 Well both capes have an I2C EEPROM in it right? Sep 24 00:30:19 is the eMMc interfered with by the IO of the bridge cape? Sep 24 00:36:51 no idea whether or not the motor bridge cape has an eeprom :P Sep 24 00:37:05 no they just conflict with each other on one gpio Sep 24 00:42:03 set_: here's a bad drawing of the patch I'd suggest => https://photos.app.goo.gl/gFzNseSkUPfU97hE9 (this is a side-view of the two capes stacked together) Sep 24 00:43:44 note that unlike what the drawing seems the suggest, it would probably require a fairly long patch wire to go all the way around the gpio connector... so it might actually be better to patch it to some unused (by both capes) odd-numbered pin of P9 instead of to P9.24 .. unfortunately the two neighbours (P9.21 and P9.25) are both in use Sep 24 00:49:28 oh wow, are the pins actually this long? https://botland.com.pl/60509-thickbox_default/touch-screen-seeed-studio-resistive-lcd-5-800x480px-for-beaglebone.jpg that makes things a lot easier actually Sep 24 00:52:51 since they won't be able to fully insert anyway you won't have to cut the pin at its base, you can leave a bit to solder to.. which means you could definitely patch it to P9.24 Sep 24 00:53:15 anyway, this won't matter until you want to 1. use both capes at the same time and 2. want to be able to use the "right" button on the lcd cape Sep 24 01:12:57 Hey at least he now knows (theoretically anyhow) Sep 24 01:13:08 yup Sep 24 01:44:04 Yea. Sep 24 01:44:12 The pins are actually way longer than expected. Sep 24 01:44:23 I thought at first it was just me. Sep 24 01:46:03 Well, I can always wait until I have a nice set up to progress into the clipping of the extra-long header pins. Sep 24 02:14:08 wait ... do you need to clip then first? Sep 24 02:15:19 ??? Sep 24 02:16:02 I presume he meant clipping the P9.25 pin? Sep 24 02:16:59 he did use a plural (pins) so I was wondering suddenly. Sep 24 02:26:56 Oh. Sep 24 02:27:14 I was supposed to just clip the pin p9.23, right? Sep 24 02:27:39 23 sorry yes Sep 24 02:27:46 Right-o! Sep 24 02:28:00 <<<< understood and made notes! Sep 24 02:28:18 I saw the photo too. Nice art. Sep 24 02:28:41 It almost looks like a root canal but for a LCD Cape for the BBG. Sep 24 02:36:34 I typed the incorrect wording there in that sentence. header pins = p9.23. Sorry. **** ENDING LOGGING AT Tue Sep 24 02:59:59 2019