**** BEGIN LOGGING AT Thu Jun 11 02:59:59 2020 Jun 11 05:55:11 * vedant16[m] uploaded an image: Screenshot_20200611-112412.png (199KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/bBUXTEwpgIYvgPbIkZRkvlsa > Jun 11 05:55:24 @jkridner:matrix.org: @cwicks:matrix.org this is the mail i got. Jun 11 07:23:10 I got a similar mail stating that the shipment will now undergo x-ray scan Jun 11 13:39:51 Did you get any update ? Jun 11 14:22:14 the mail said the x-ray scan process will take 48 hours Jun 11 14:33:04 Hello everyone Jun 11 14:33:12 saketh: are you there? Jun 11 14:35:15 deepankarmaithan: you here? Jun 11 14:37:38 yes Jun 11 14:38:25 I started with writing bitbanging SPI code for Shift register. The main blocket is i am still not able to acquire the signals on the beaglelogic Jun 11 14:39:21 which IC? xx295 right Jun 11 14:39:32 It seems if we are going to implement a SPI bus then directly switching to SPI based driver is better Jun 11 14:39:40 74HC595 Jun 11 14:40:09 yeah sorry! okay Jun 11 14:40:46 jkridner/ds2 you here? Jun 11 14:40:57 the other one is 299 that is a little more harder to interpret so i am starting with 595 also it is widely used IC among hobbiest and is easily avialble so it would be benifical to the community Jun 11 14:41:09 okay. Jun 11 14:41:12 Will abhishek be coming Jun 11 14:41:29 he might not be able to. Jun 11 14:41:37 hi. my power and wifi are out. using limited access via phone. Jun 11 14:42:04 hello jkridner Jun 11 14:42:05 jkridner[m]: <..>okay Jun 11 14:42:21 deepankar lets fix the beaglelogic part first. Jun 11 14:42:40 are you able to connect to the BB-Wireless via the tcp mode on pulseview? Jun 11 14:42:47 Yes it is connected to my system Jun 11 14:42:53 usb? Jun 11 14:42:55 the PRU code is also runnign Jun 11 14:43:06 connected on wifi Jun 11 14:43:14 okay. we're where we were yesterday Jun 11 14:43:17 right? Jun 11 14:43:20 yes Jun 11 14:43:29 pru code runs but doesn't show up on beaglelogic Jun 11 14:43:29 okay Jun 11 14:43:37 doing a quicksearch Jun 11 14:44:07 so jkridner we all agree on SPI driver ? Jun 11 14:44:19 ok. Jun 11 14:45:31 Also I did compile some codes on PRU using clpru and now i understand the r30 and r31 and how to manupulate them to toggle pins Jun 11 14:45:36 i thought starting with gpio. (with parallel access) Jun 11 14:46:51 +1 on gpiochip, because it would be a step towards having an external device/io interfaced using the shift register Jun 11 14:47:14 I went through both gpio and SPI and it appears to me that gpio driver is going in different direction and SPI is differnt implementation Jun 11 14:47:33 But as you suggest Jun 11 14:48:26 can you see beaglelogic on /dev on the wireless? Jun 11 14:49:09 No Jun 11 14:49:52 are you sure that the bb has booted from the SD card and not eMMC? Jun 11 14:50:27 yes i am sure because only sd card version has begale logic and golang and that is why i can connect to port 5555 Jun 11 14:50:41 https://www.youtube.com/watch?v=QA0_2MOuO5o Jun 11 14:51:32 just to be sure. By parallel access you mean reading the shift register pins parallel. correct Jun 11 14:52:37 No I haven't, which symbol failed? Jun 11 15:02:00 :4"> yes i can see Jun 11 15:02:15 > <@jkridner:matrix.org> @lorforlinux did you work out that a symbol didn’t match, so the overlay failed? Jun 11 15:02:16 * No I haven't, which symbol didn't match? Jun 11 15:02:42 deepankarmaithan: can you try using the beagle logic interface and select your pru pins there/ Jun 11 15:03:37 sure Jun 11 15:07:03 jkridner: the __overlay__ symbol? Jun 11 15:07:21 lorforlinux, not sure, but that’s the error. i’ll need to look at the base and overlay. Jun 11 15:07:46 got the signal Jun 11 15:08:30 jkridner: I used the new format for that overlay and I am suspicious of the &{/choosen} node. Jun 11 15:11:19 try removing it as it is only informative Jun 11 15:11:38 okiee will try that today Jun 11 15:12:53 deepankarmaithan: try fiddling with the delay time in the sample program to match frequency of capture Jun 11 15:14:35 Also, in the uEnv.txt I am putting this to load the overlay Jun 11 15:14:35 enable_uboot_overlays=1 Jun 11 15:14:35 uboot_overlay_addr0=/lib/firmware/src/BBAI_BB-BONE-LCD4-01-00A1.dts.dtbo Jun 11 15:14:44 From a software and far-side hardware perspective, it would look parallel. In the middle, the PRU would shift the data out serially to the SIPO shift register. Jun 11 15:14:44 If i use `dtb_overlay=/lib/firmware/src/BBAI_BB-BONE-LCD4-01-00A1.dts.dtbo` It doesn't work. Jun 11 15:16:35 @jkridner:matrix.org: stackable headers just arrived Jun 11 15:16:41 I get confused on the circuit on this project. I think of it mostly as serial to PRU and parallel to external hardware. Jun 11 15:17:02 * Also, in the uEnv.txt I am putting this to load the overlay Jun 11 15:17:02 enable_uboot_overlays=1 Jun 11 15:17:02 uboot_overlay_addr0=/lib/firmware/BBAI_BB-BONE-LCD4-01-00A1.dts.dtbo Jun 11 15:17:36 Is .dts part of the output dtbo filename? Jun 11 15:18:14 why is /src part of the path? Jun 11 15:18:30 @jkridner:matrix.org: will you join zoom meeting today? Jun 11 15:18:44 sorry I copied the name from bb.org-overlay that's why It got messed up Jun 11 15:19:08 it's not from /src and it doesn't contain the .dts on BBAI uEnv.txt Jun 11 15:19:13 not by zoom. only phone+riot today. no power or wifi. Jun 11 15:19:37 allright i keep you informed with results Jun 11 15:19:42 * Also, in the uEnv.txt I am putting this to load the overlay Jun 11 15:19:42 enable_uboot_overlays=1 Jun 11 15:19:42 uboot_overlay_addr0=/lib/firmware/BBAI_BB-BONE-LCD4-01-00A1.dtbo Jun 11 15:19:53 * If i use `dtb_overlay=/lib/firmware/src/BBAI_BB-BONE-LCD4-01-00A1dtbo` It doesn't work. Jun 11 15:20:21 jkridner: Just started BBAI and SPI control of coded driver is allready working :) Jun 11 15:20:32 codec* driver Jun 11 15:21:34 jkridner: that is the correct way to load the overlay right (ignore the naming here i messed it up)? I have to enable the overlay and use uboot_overlay_addr* to load the overlay? Jun 11 15:22:40 nwan: you also loaded the overlay this way right? Jun 11 15:23:26 lorforlinux: I currently implemented everything in base tree. When this is working properly I will refactor into overlay Jun 11 15:23:41 One of those entries. Sharing your steps and exact code could help in finding the issue. Jun 11 15:24:18 okiee sure, I will do that. Jun 11 15:24:55 nwan: nice, on BBAI right? Jun 11 15:25:11 nwan: it would be a good test case for lorforlinux if you can make one overlay work with both Black and AI. Jun 11 15:25:19 lorforlinux: yepp Jun 11 15:26:16 jkridner: allright but extraction into overlay is planned for next week. I will see how far I get this week. Maybe I can get ahead of time Jun 11 15:40:46 lorforlinux: where is the overlay you are trying to debug? did removing chosen help? Jun 11 15:44:13 ok hopefully if the pocketbeagle works well i would have basic PRU code done to interface IC by this weekend Jun 11 15:44:15 I am working on the am5729-beagleboneai.dts, I have not tested it by removing chosen. The dts file is at bb.org-overlay/src/arm/BBAI_BB-BONE-LCD4-01-00A1.dts Jun 11 15:44:34 will work on the overlay after this. Jun 11 15:44:54 i meant which branch/repo Jun 11 15:45:34 https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BBAI_BB-BONE-LCD4-01-00A1.dts Jun 11 15:53:13 * nwan[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/inaSAlbYIHTLEAOYthWqPSRo > Jun 11 15:55:05 jkridner: This is todays meeting protocol. It was a quick meeting, because the blocker got resolved before the meeting and first iteration of driver worked better than expected Jun 11 15:56:34 jkridner: It payed off, that I allready implemented the driver for BBB during bonding period Jun 11 15:56:42 until now... Jun 11 16:06:10 updated https://elinux.org/BeagleBoard/GSoC/2020_Projects#Milestones and https://elinux.org/BeagleBoard/GSoC/2020_Projects/Media_IP_Streaming#Timeline accordingly Jun 11 16:22:53 the /chosen does stand out. try removing that section yet? for touchscreen, some real thought is needed on how to make that section common. Jun 11 16:23:50 not yet about to finish the beagleboneai.dts work. Jun 11 16:25:17 I was thinking of the same thing, the display subsystem node of BBAI is very different than the BBB display interface node. Jun 11 16:26:22 I guess first we have to create BBAI_ overlays that relaly work for the capes then we can look into making the section common. Jun 11 16:28:45 Also, I am not able to understand the use of remotend point used here -> https://github.com/beagleboard/bb.org-overlays/blob/e94880efb124a2755059f47da491551e2fe639de/src/arm/BBAI_BB-BONE-LCD7-01-00A2.dts#L226 Jun 11 16:30:04 It creates a loop with this node https://github.com/beagleboard/bb.org-overlays/blob/e94880efb124a2755059f47da491551e2fe639de/src/arm/BBAI_BB-BONE-LCD7-01-00A2.dts#L306 Jun 11 16:30:39 I have not used that in the LCD4 overlay. Jun 11 16:34:32 jkridner: audio working also :-) Jun 11 17:30:41 Abhishek_: beagle logic on deepankars bb wireless stays on "Requesting Capture" forever. is there anything that we might be missing here? Jun 11 17:31:03 tried checking if the pru pin is set on a proper mode. it's pruin Jun 11 17:41:25 jkridner: am5729-beagleboneai.dts work is done https://github.com/beagleboard/BeagleBoard-DeviceTrees/pull/15, working on overlay now :) Jun 11 19:11:07 vedant16: Yesterday cwicks had brought up that the title "PRU Improvements" might be too generic for promotion to the rest of the community, and I agree. It may imply that you are changing the PRU in some manner. Jun 11 19:12:50 So it would be good if we can come up with a better title Jun 11 19:14:01 Actually I didnot select that name, jkridner[m] did. Jun 11 19:14:11 for youtube video ? Jun 11 19:14:41 Elinux too Jun 11 19:15:27 Ohh, I will think something. Jun 11 19:15:29 Wherever we can Jun 11 19:16:21 vedant16: Okay Jun 11 19:16:36 Thanks Jun 11 19:17:23 Yup, but i think it is kinda appropriate since i will work on getting pruspeaks working too Jun 11 19:17:28 I don't remember if title can be changed on the GSoC website Jun 11 19:17:50 Title there is REPL for PRU, which seems okay Jun 11 19:18:12 https://steemit.com/programming/@drifter1/writing-a-simple-compiler-on-my-own-using-symbol-tables-in-the-lexer i found this series, helped a lot. Jun 11 19:19:22 Is REPL still on the timeline? Jun 11 19:20:28 No, removed it from elinux Jun 11 19:20:40 Yes but the title PRU Improvements as title doesn't convey where the improvements are, like firmware side or elsewhere Jun 11 19:22:33 * Yes but PRU Improvements as title doesn't convey where the improvements are, like firmware side or elsewhere Jun 11 19:22:56 Agreed, it can be like, Simplified language for programming PRU and further improvements Jun 11 19:23:32 Right, this sounds better to me Jun 11 19:24:09 vedant16: cwicks had suggested PRU access to beginners Jun 11 19:27:21 vedant16: Think on what sounds concise to you, then we can discuss with others as well Jun 11 19:33:47 > vedant16: cwicks had suggested PRU access to beginners Jun 11 19:33:47 Pru programmers for dummies? Jun 11 21:42:00 * lorforlinux[m]1 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/rVxpKWFUTOPxOVIYFyhoNQUU > **** ENDING LOGGING AT Fri Jun 12 02:59:58 2020