**** BEGIN LOGGING AT Mon Jun 15 02:59:58 2020
Jun 15 05:01:55 <saketh> I will be using sakethr98 for the time being. Losing messages with my current bouncer.
Jun 15 05:04:21 <deepankarmaithan> sakethr98:  we need to resolve the issue with my code today
Jun 15 05:08:26 <deepankarmaithan> sakethr98:  https://github.com/deebot/Beaglebone-BidirectionBus/blob/master/PRUDummyShift.c    here is the one that has same fuctionality as we need in the PRU but doesnot use the macros specific to PRU  and runs well on my ubuntu
Jun 15 05:08:48 <deepankarmaithan> The problem is in the PRU the code  is not performing the Tasks
Jun 15 05:09:12 <deepankarmaithan> The PRU version uses the __R30 macro to  address the right register
Jun 15 05:39:59 <vedant16[m]> > sakethr98:  https://github.com/deebot/Beaglebone-BidirectionBus/blob/master/PRUDummyShift.c    here is the one that has same fuctionality as we need in the PRU but doesnot use the macros specific to PRU  and runs well on my ubuntu
Jun 15 05:40:00 <vedant16[m]> Its __R31 and __R30
Jun 15 05:40:52 <vedant16[m]> > sakethr98:  https://github.com/deebot/Beaglebone-BidirectionBus/blob/master/PRUDummyShift.c    here is the one that has same fuctionality as we need in the PRU but doesnot use the macros specific to PRU  and runs well on my ubuntu
Jun 15 05:40:52 <vedant16[m]> It should be volatile *** "__R30"
Jun 15 05:56:12 <deepankarmaithan> This is just  a test code that  i wrote once the code was not running on PRU. Uploading the code with PRU macros  that can be compiled with CLPRU
Jun 15 06:13:04 <deepankarmaithan> vedant16:  here is the PRU variant which compiles with no problems  but doesnot blink the LED. I have added my own  functions to bitread and bitwrite on the r30 register
Jun 15 06:13:41 <deepankarmaithan> https://github.com/deebot/Beaglebone-BidirectionBus/tree/master/blinkLED
Jun 15 06:14:53 <vedant16[m]> > vedant16:  here is the PRU variant which compiles with no problems  but doesnot blink the LED. I have added my own  functions to bitread and bitwrite on the r30 register
Jun 15 06:14:53 <vedant16[m]> Ohhk, you could use helper header files for input outputs too
Jun 15 06:16:44 <deepankarmaithan>  vedant16: Did you figure out where is this file if you worked with Prugcc.  I need to look inside it to know how the fuction is working in the background
Jun 15 06:18:31 <deepankarmaithan> when the PRU code dint do what it had to i slightly modified it and wrote the code that i can run on unbuntu. Just created  a uint32_t type of variable to represent r30 and did the bit operations using my fuctions and i was getting correct results here
Jun 15 06:29:58 <vedant16[m]> >  vedant16: Did you figure out where is this file if you worked with Prugcc.  I need to look inside it to know how the fuction is working in the background
Jun 15 06:29:58 <vedant16[m]> I think it is installed in root directory
Jun 15 06:30:03 <vedant16[m]> I will have to check once
Jun 15 06:39:16 <vedant16[m]> https://www.phoronix.com/scan.php?page=news_item&px=GCC-10-TI-PRU-Target
Jun 15 06:39:16 <vedant16[m]> GCC 10 ships with support for PRU
Jun 15 06:55:12 <deepankarmaithan> sakethr98:   i found it   /usr/lib/pru/include/pru/io.h
Jun 15 06:55:38 <deepankarmaithan> two folders named pru in the path :P
Jun 15 07:07:08 <vedant16[m]> <deepankarmaithan "two folders named pru in the pat"> cool
Jun 15 07:52:19 <deepankarmaithan> Hello everyone i am trying  to understand a assembly snippet
Jun 15 07:52:29 * deepankarmaithan sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/VBTDoJQomKNXNqzttTiwHRHW >
Jun 15 07:52:49 <deepankarmaithan> what are the ::  doing here . can anyone explain it
Jun 15 07:57:41 <vedant16[m]> Check this: http://www.cs.fsu.edu/~baker/devices/restricted/GCC-Inline-Assembly-HOWTO.html
Jun 15 07:58:28 <deepankarmaithan> thanks
Jun 15 08:01:46 <vedant16[m]> welcome :0
Jun 15 08:01:51 <vedant16[m]>  * welcome :)
Jun 15 13:49:14 <jkridner[m]> lorforlinux: https://github.com/beagleboard/bb.org-overlays/pull/173#pullrequestreview-423739382
Jun 15 13:55:28 <lorforlinux[m]1> jkridner: I have updated the DT file please review this -> https://github.com/beagleboard/bb.org-overlays/pull/174
Jun 15 14:27:16 * lorforlinux[m]1 uploaded a video: VID_20200615_195413895.mp4 (17617KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/PJhENZvhfClFSJuWRrNepKAD >
Jun 15 14:28:33 <lorforlinux[m]1> My BeagleBone wireless refuses to boot sometimes until i provide power through barrel jack, anybody else facing this problem?
Jun 15 14:30:24 <lorforlinux[m]1> <lorforlinux[m]1 "After the power led becomes soli"> It was happening from Day1 when I tried using 4DLCD4 cape with it, first i thought it's because of the cape but not sure now.
Jun 15 14:34:38 <vedant16[m]> <vedant16[m] "Abhishek_: pratimugale hendersa "> Solved this issue too. Looking forward to today's meet.
Jun 15 14:35:08 <vedant16[m]> > <@vedant16:matrix.org> Abhishek_: pratimugale hendersa https://ve0x10.me/gsoc2020/2020/06/15/week2.html check my progress for this week. Current blocker is implementing scoped symbol table, all previous blockers were solved.
Jun 15 14:35:09 <vedant16[m]>  * Solved this issue too. Looking forward to today's meet. Abhishek_ pratimugale hendersa
Jun 15 15:50:13 <vedant16[m]> https://groups.google.com/d/msg/beagleboard-gsoc/ejF6F3EdE48/fFicO9WqAQAJ Abhishek_ @pratim
Jun 15 15:50:56 <vedant16[m]>  * https://groups.google.com/d/msg/beagleboard-gsoc/ejF6F3EdE48/fFicO9WqAQAJ Abhishek_ pratimugale hendersa cwicks jkridner  Updated progress of week 2 on mailing list thread.
Jun 15 16:01:03 <pratimugale[m]> Hi all
Jun 15 16:05:42 <vedant16[m]> Hi @pratimugale:matrix.org
Jun 15 16:06:00 <pratimugale[m]> hendersa Abhishek Are you around?
Jun 15 16:06:11 <pratimugale[m]> vedant16: What are you working on next?
Jun 15 16:07:11 <vedant16[m]> > vedant16: What are you working on next?
Jun 15 16:07:11 <vedant16[m]> Implementing functions
Jun 15 16:09:53 <jkridner[m]> gm all
Jun 15 16:12:25 <pratimugale[m]> jkridner: Good morning!
Jun 15 16:13:11 <pratimugale[m]> vedant16: Did you try out your language on the PRU?
Jun 15 16:14:52 <pratimugale[m]> With the backend / code generation
Jun 15 16:18:19 <vedant16[m]> gm jkridner
Jun 15 16:18:21 <vedant16[m]>  * good morning jkridner
Jun 15 16:18:35 <vedant16[m]> <pratimugale[m] "vedant16: Did you try out your l"> not yet, I want to finish front end part first.
Jun 15 16:18:53 <vedant16[m]> > <@pratimugale:matrix.org> vedant16: Did you try out your language on the PRU?
Jun 15 16:18:53 <vedant16[m]>  * not yet, I want to finish front end part first. which i will this week.
Jun 15 16:19:35 <vedant16[m]> start working on LLVM backend then. before that i have to implement, abstract syntax tree too.
Jun 15 16:19:54 <vedant16[m]>  * I will start working on LLVM backend then. before that i have to implement, abstract syntax tree too.
Jun 15 16:23:03 <pratimugale[m]> vedant16: How much is left on the frontend part? As Abhishek said, a demo with the backend would be good
Jun 15 16:25:04 <vedant16[m]> <pratimugale[m] "vedant16: How much is left on th"> Implementing functions
Jun 15 16:25:42 <pratimugale[m]> Okay
Jun 15 16:26:04 <vedant16[m]> demo with llvm will be tough
Jun 15 16:26:38 <vedant16[m]> Once syntax tree stuff is done, demo will be easy
Jun 15 16:27:41 <pratimugale[m]> Okay, have you tried out PRU assembly, or any other PRU programs?
Jun 15 16:28:28 <vedant16[m]> yup basic stuff
Jun 15 16:28:31 <vedant16[m]> LED blink, button led blink
Jun 15 16:29:28 <vedant16[m]> <pratimugale[m] "Okay, have you tried out PRU ass"> I tinkered with it, I can say i am bit confident with PRU C/asm
Jun 15 16:35:25 <pratimugale[m]> Okay, keep working on it, having a working demo at the earliest would be good
Jun 15 16:35:55 <vedant16[m]> <pratimugale[m] "Okay, keep working on it, having"> I could make it happen soon.
Jun 15 16:36:12 <vedant16[m]> but it will be like, I output relevant snippets in asm.
Jun 15 16:36:25 <vedant16[m]> discrete snippets.
Jun 15 16:38:22 <pratimugale[m]> vedant16: Discrete as in?
Jun 15 16:38:43 <pratimugale[m]> vedant16: As long as it is correct
Jun 15 16:38:45 <pratimugale[m]> should do
Jun 15 16:38:52 <vedant16[m]> like for defining variables, one snippet, for loops another snippet.
Jun 15 16:39:22 <pratimugale[m]> Oh, combining them is difficult?
Jun 15 16:39:56 <vedant16[m]> <pratimugale[m] "vedant16: As long as it is corre"> It will be correct, but I'd rather output code in C, as such a approach won't give optimised code.
Jun 15 16:40:14 <vedant16[m]> <pratimugale[m] "Oh, combining them is difficult?"> Yes, for complex programs it won't work, for simple hello world yes.
Jun 15 16:42:30 <pratimugale[m]> vedant16: Okay
Jun 15 16:42:31 <pratimugale[m]> Need to go
Jun 15 16:42:53 <vedant16[m]> Okay, I will keep you updated.
Jun 15 16:43:11 <vedant16[m]> GCC-10 has official support for PRU
Jun 15 16:43:18 <vedant16[m]> should i use that ?
Jun 15 16:43:26 <vedant16[m]> or the one on github
Jun 15 16:43:35 <pratimugale[m]> Thanks, if you see Abhishek around, discuss the milestones for next two weeks too
Jun 15 16:44:29 <vedant16[m]> <pratimugale[m] "Thanks, if you see Abhishek arou"> Okay.
Jun 15 16:44:39 <vedant16[m]> > <@pratimugale:matrix.org> Thanks, if you see Abhishek around, discuss the milestones for next two weeks too
Jun 15 16:44:39 <vedant16[m]>  * Okay :)
Jun 15 16:46:39 <pratimugale[m]> <vedant16[m] "GCC-10 has official support for "> vedant16: I don't have much knowledge regarding this, please ask Abhishek
Jun 15 16:47:10 <vedant16[m]> <pratimugale[m] "vedant16: I don't have much know"> Alright
Jun 15 16:47:30 <vedant16[m]> Abhishek_: GCC-10 has official support for PRU
Jun 15 16:47:30 <vedant16[m]> should i use that ?
Jun 15 16:47:30 <vedant16[m]> or the one on github
Jun 15 16:47:31 <pratimugale[m]> I was supposed to complete my complers course this sem, got cancelled due to covid
Jun 15 16:48:09 <vedant16[m]> <pratimugale[m] "I was supposed to complete my co"> Ohhh
Jun 15 16:48:32 <vedant16[m]> I did watch gate academy playlist for compiler design.
Jun 15 16:52:00 <pratimugale[m]> Cool, will try to read and get back to you regarding GCC-10
Jun 15 16:54:38 <pratimugale[m]> vedant16: Have to go, see you
Jun 15 16:55:04 <vedant16[m]> Ok, bye
Jun 15 17:00:44 <Abhishek[m]_> vedant16: Give GCC 10 a shot
Jun 15 17:08:35 <vedant16[m]> <Abhishek[m]_ "vedant16: Give GCC 10 a shot"> Ohk
Jun 15 17:08:55 <vedant16[m]> https://pp.ipd.kit.edu/firm/Introduction.html I found this better documented for backend, I will try this Abhishek
Jun 15 17:09:31 <lorforlinux[m]1> jkridner: I have ordered MCP2515 CAN Module to test comms cape, HV230Q modules are not available.
Jun 15 17:14:37 <jkridner[m]> lorforlinux: cool
Jun 15 17:23:41 * lorforlinux[m]1 sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/PnnVZgCLZEBeJaYtRjBuwzaz >
Jun 15 17:26:17 <lorforlinux[m]1> Also, i am using IoT image and don't have lightdm installed. I will be using keyboard inputs to test the board, that's fine right?
Jun 15 17:30:46 <jkridner[m]> hmmm.... I think that could be the user button. Not sure what other input devices there might be.
Jun 15 17:31:01 <jkridner[m]> can you share a full log?
Jun 15 17:31:38 <lorforlinux[m]1> yes, I have just rebooted it.
Jun 15 17:33:58 <lorforlinux[m]1> here is the fill log -> https://pastebin.com/zfyu0e2W
Jun 15 17:48:58 <lorforlinux[m]1> jkridner: as you said beagle-tester will be used to test current and new capes, I think we should have some generalized way access buses. Like if we want to test i2c device on our new cape we can specify what i2c bus we want to acquire and beagle-tester will enable that bus and show the details of all the device connected and then you can choose what device you are interested in and then after checking everything
Jun 15 17:48:58 <lorforlinux[m]1> we can go on to create a new DT for the cape. Even better would be to generate the DT overlay automatically.
Jun 15 17:55:32 <jkridner[m]> <lorforlinux[m]1 "jkridner: as you said beagle-tes"> can you break that down a bit?
Jun 15 17:55:50 <jkridner[m]> why would beagle-tester be so generic?
Jun 15 17:56:08 <jkridner[m]> it's goal is to test each board and each cape.
Jun 15 17:56:28 <jkridner[m]> I guess it could be augmented to easily test new capes, but I'm not clear on how you are proposing that.
Jun 15 18:01:41 <lorforlinux[m]1> I was thinking If we have created a new cape and wanted to test it we have to write new code into beagle-tester what if we could just specify the hardware we have on the cape just to know everything is working. Maybe that's not a good idea, I will focus to work on testing each board and each cape.
Jun 15 18:09:17 <jkridner[m]> <lorforlinux[m]1 "here is the fill log -> https://"> I guess this was run on PocketBeagle?
Jun 15 18:09:47 <lorforlinux[m]1> No, on BeagleBone Black Wireless.
Jun 15 18:10:02 <jkridner[m]> odd. I should probably have it print more base platform information.
Jun 15 18:11:04 <lorforlinux[m]1> I have corrected the /sbin/bb-connect-ap -> /usr/sbin/bb-connect-ap
Jun 15 18:13:57 <lorforlinux[m]1> jkridner: do you have any guide on how to use it with a keyboard?
Jun 15 18:16:00 <lorforlinux[m]1> This message `Unable to write to /dev/fb0` is due to not using lightdm service right?
Jun 15 18:19:29 <jkridner[m]> <lorforlinux[m]1 "here is the fill log -> https://"> Input device comes from https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.19.x-ti/src/arm/tps65217.dtsi#L26-L30, https://github.com/beagleboard/linux/blob/7a920684860a790099061b67961d0b5ffa033fdf/drivers/input/misc/tps65218-pwrbutton.c#L57,
Jun 15 18:19:29 <jkridner[m]> https://github.com/beagleboard/linux/blob/7a920684860a790099061b67961d0b5ffa033fdf/drivers/input/misc/tps65218-pwrbutton.c#L119, https://github.com/beagleboard/linux/blob/c0c1bb5fc955015dfe71ba831cb03defd8d0f37d/include/uapi/linux/input-event-codes.h#L39,  https://github.com/beagleboard/linux/blob/c0c1bb5fc955015dfe71ba831cb03defd8d0f37d/include/uapi/linux/input-event-codes.h#L191 -- I think
Jun 15 18:20:08 <jkridner[m]> I was trying to find where the bus ID, vendor, product, and version got defined.
Jun 15 18:23:45 <jkridner[m]> hmmmm.... odd that https://github.com/jadonk/beagle-tester/blob/master/beagle-tester.c#L3136 didn't print out.
Jun 15 18:24:07 <jkridner[m]> so, that file actually exists, /dev/input/beagle-barcode ?
Jun 15 18:24:21 <jkridner[m]> seems like a bug in the udev rules if that is the case.
Jun 15 18:24:59 <jkridner[m]> to use it from a keyboard, just put the argument on the command line as mentioned previously.
Jun 15 18:25:02 <lorforlinux[m]1> can I split the code into different files? for example you have included the code common.h & common.c into beagle-tester.c
Jun 15 18:25:21 <jkridner[m]> beagle-tester <BARCODE_VALUE>
Jun 15 18:26:05 <lorforlinux[m]1> there is no beagle-barcode in /dev/input/ directory.
Jun 15 18:26:37 <nwan[m]> jkridner:  Hey Jason. I just posted my week 2 progress report. I allready finished a lot of tasks from this and next week last week, so I came up with additional tasks for this week: Documentation of the Driver and Overlays and Overlay Implementation for BBB. Here is the link https://groups.google.com/forum/#!topic/beagleboard-gsoc/QwMJGBXj8DQ
Jun 15 18:26:48 <jkridner[m]> <lorforlinux[m]1 "can I split the code into differ"> You can propose a refactoring of the code to make it more maintainable, but please don't mix refactoring commits with feature commits. I will review and approve/reject them separately.
Jun 15 18:27:39 <lorforlinux[m]1> there is nothing related to barcode in the whole  `/` directory
Jun 15 18:28:07 <jkridner[m]> <lorforlinux[m]1 "I was thinking If we have create"> I suggest not getting too distracted. If you want to propose something, doing it near the end of the project might be fine.
Jun 15 18:28:43 <lorforlinux[m]1> okay
Jun 15 18:29:48 <jkridner[m]> lorforlinux: also, I'm really confused how /dev/fb0 isn't there on Black Wireless, unless you have edited uEnv.txt to disable it.
Jun 15 18:30:02 * jkridner[m] has to go to a meeting and will be back in about 30-60 minutes.
Jun 15 18:30:58 <lorforlinux[m]1> okay thanks, I will look for solving those issues.
Jun 15 19:08:42 <lorforlinux[m]1> Sorry forgot to tell you that, I have not edited anything in uEnv.txt. What should be there to enable the `/dev/fb0` frame buffer device?
Jun 15 20:30:19 <jkridner[m]> gone longer than expected.
Jun 15 20:30:34 <jkridner[m]> There is an HDMI output on BeagleBone Black Wireless.
Jun 15 20:32:01 <jkridner[m]> what is the output of ```sudo /opt/scripts/tools/version.sh```
Jun 15 20:32:16 <jkridner[m]> lorforlinux: ^^^
Jun 15 20:34:58 <lorforlinux[m]1> on BBAI, booting the BBWL board, 2 minutes please.
**** ENDING LOGGING AT Mon Jun 15 20:36:34 2020

**** BEGIN LOGGING AT Mon Jun 15 20:39:11 2020
Jun 15 20:39:52 <deepankarmaithan> I wrote a new post jkridner  sakethr98  ds2  Abhishek_  pdp7_   I wrote a new post  https://deebot.github.io/PRURegisterMapping.html.  vedant16  May be you would also like to look into it as we discussed in the after noon
Jun 15 20:40:08 <lorforlinux[m]1> https://pastebin.com/vdnck4f1
Jun 15 20:40:15 <jkridner[m]> sure would be nice if we could just load the overlays at the beginning of the tests. It worked with 4.14 and https://github.com/beagleboard/linux/commit/8b581615719a3467bdb70cc63d5488fe8c4fdd9d.
Jun 15 20:40:30 <jkridner[m]> Maybe someone could forward-port the above.
Jun 15 20:41:49 <deepankarmaithan> jkridner: sakethr98 Abhishek_ ds2 pdp7_   https://groups.google.com/d/msg/beagleboard-gsoc/cjJrXAPbY7M/tcNe9jXuAwAJ   Here is the  weekly update
Jun 15 20:42:11 <jkridner[m]> <lorforlinux[m]1 "https://pastebin.com/vdnck4f1"> The 'quiet' makes this less useful, but still ok. The HDMI overlay is there. Only thing I can imagine that makes /dev/fb0 not show up is the lack of a connected monitor. Perhaps the driver recognizes the monitor isn't there and doesn't enable /dev/fb0.
Jun 15 20:43:46 <lorforlinux[m]1> or maybe it's because I am using the IoT image without any DE?
Jun 15 20:44:13 <lorforlinux[m]1> I will try xfce image
Jun 15 20:45:06 <lorforlinux[m]1> We can use LCD cape instead of a HDMI monitor right?
Jun 15 20:47:09 <jkridner[m]> sure. LCD works fine and is still at /dev/fb0
Jun 15 20:47:26 <jkridner[m]> no, gui is not needed.
Jun 15 20:49:27 <lorforlinux[m]1> jkridner: I was working on virtual cape overlays for BBAI and saw that we have aliases written in dra7.dtsi that am5729-beagleboneai.dts file uses, for example, we get i2c-0 which is i2c1 of BBAI. If I change those aliases It might affect the usability of other boards as well. what should I do other than assigning symlinks to the buses?
Jun 15 20:50:27 * lorforlinux[m]1 sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/hIycFtzkAPMPliveiFzXIeFk >
Jun 15 20:52:34 <lorforlinux[m]1> I think this makes it a double layer of confusion for users as the I2C5 of BBAI will be available as i2c-4 device but also as /dev/bone/i2c/1.
Jun 15 20:53:08 <lorforlinux[m]1> What do you suggest?
Jun 15 20:56:37 <lorforlinux[m]1> <jkridner[m] "no, gui is not needed."> okay, you said to have the production image installed to use beagle-tester and we get the Xfce image preinstalled when we get a new board does that means it is the recommended production image?
Jun 16 01:36:06 <jkridner[m]> <lorforlinux[m]1 "I think this makes it a double l"> It might be other places, but we recommend the ones under /dev/bone for consistency based on cape header locations.
Jun 16 01:36:19 <lorforlinux[m]1> they seem to change the device names, i2c1 is i2c-0  on the board.
Jun 16 01:37:09 <jkridner[m]> > <@lorforlinux:matrix.org> for I2C we have these aliases,
Jun 16 01:37:10 <jkridner[m]> > 		i2c0 = &i2c1;
Jun 16 01:37:10 <jkridner[m]> ...(truncated)
Jun 16 01:38:08 <lorforlinux[m]1> jkridner: I am trying to use uboot overlays with BBAI but no success, I also tried loading overlays on BBWL but it is not loading the overlays either.
Jun 16 01:38:55 <lorforlinux[m]1> * uboot overlays are not loading when i use uEnv.txt to load them.
Jun 16 01:39:51 <lorforlinux[m]1> Also, there is no /proc/device-tree/chosen/overlays folder on BBAI, why is that?
Jun 16 01:41:15 <lorforlinux[m]1> For BBBWL i think the problem is that the pins are already used by some other overlay.
**** ENDING LOGGING AT Tue Jun 16 03:06:37 2020