**** BEGIN LOGGING AT Fri Jun 07 02:59:57 2019 Jun 07 03:40:50 pratimugale: well, I would suggest that you should always login into board as a root user, as far as this development task is concerned. Jun 07 03:51:51 zeekhuge: Will do that from now on Jun 07 03:58:00 pratimugale: if interested, you can send a pull request modifying the deploy script to explicitly check if the executing user is root. Jun 07 04:02:11 zeekhuge: Sure Jun 07 04:45:37 Okay, I see, according to the answer, a lot of things have changed in the newer versions. So, pratimugale , if you would send the PR, maybe make these modifications as well. Dont spend too much time on it though. And don't do it if at all if does not work at once, focus on this project task instead. Jun 07 05:52:04 zeekhuge: okay Jun 07 09:03:03 anyone can help me with this https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/beagleboard/R0cjOVwnICU/2AHU16vmBAAJ Jun 07 14:11:01 pranav_kumar[m]: Are you here? Jun 07 14:11:52 Yes Jun 07 14:15:27 I have done the part that you have explained in the first mail Jun 07 14:17:22 OK, so you have your /dev/uio0 file visible? Jun 07 14:31:01 I have closed my pc again connected it and it is there and working on second part of the maik now Jun 07 14:35:19 it is still showing the same outhput Jun 07 14:37:39 * pranav_kumar[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/bgaBpnrPYFBfMSdhubyVHkMX > Jun 07 14:39:10 because it is in the program only Jun 07 14:39:56 to give this output in the main function Jun 07 14:42:41 Is the program giving you any errors prior to starting? You have the .bin in the same directory as the a.out you are running? Jun 07 14:44:41 the .bin file of gampad is in pru directory and my compiled output is in src directory and it is running fine without any error Jun 07 14:45:07 Are you running it on a PocketBeagle? Jun 07 14:45:35 no i am running it on beaglebone wireless Jun 07 14:47:16 Keep in mind that the .asm for that gamepad example expects certain GPIOs to be available and muxed as GPIOs for interfacing. I've only checked it on the BeagleBone Black. Jun 07 14:47:29 i will check it pocket beagle also as wireless get connected to the internet easily so i tested the things on wireless Jun 07 14:47:43 You can keep working with the wireless. That's fine. Jun 07 14:47:49 Stick with that if it is easier. Jun 07 14:48:09 of i will update that to you Jun 07 14:48:55 So, take a look at the .pasm code for that gamepad example, on line 117: https://github.com/hendersa/bes/blob/v0.1/src/pru/gamepad.pasm Jun 07 14:49:24 Lines 117 and 118 are where data is copied to the shared memory location that userspace sees. Jun 07 14:50:05 one thing i want to ask is that the formatting that you have used the gamepad.pasm for running the assembly should it be the same for my code also only i have to change the assemly part of that program ???? Jun 07 14:51:03 You can use whatever formatting/style/comments for the .pasm that works best for you. We can worry about cleaning it up later. Jun 07 14:51:48 Your project has three pieces: the PRU firmware code (the .pasm), a kernel driver that talks to that PRU firmware code, and a userspace library that talks to the kernel driver. Jun 07 14:52:11 That is what is in your proposal. Jun 07 14:52:19 i think i should play with the code today and try to understand it more Jun 07 14:53:13 You need to get to the point where you can take that .pasm file, make a change or two, rebuild it using the "pasm" tool, and then load it into the PRU to test it. Jun 07 14:53:52 hmmmm Jun 07 14:55:07 There is a lot more documentation out there for the kernel and userspace parts of the project. The PRU is the trickier piece. Jun 07 14:55:16 yes the pasm tool , do i have download anything extra or it will generate .bin from build.sh file only present in the pru directory Jun 07 14:56:00 You need to download pasm. I'll find a link to it for you. Jun 07 14:56:36 am335x_pru_package-master.zip i came across with this to generate the .bin file from the site https://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone//blog/2013/05/22/bbb--working-with-the-pru-icssprussv2 Jun 07 14:57:04 That should be it. The official one is here: https://github.com/beagleboard/am335x_pru_package Jun 07 14:58:15 pasm is build as part of that project. Once I built it, I copied it into /usr/local/bin or /usr/bin or someplace that was in the path so that I could just run "pasm" to assemble .pasm files into .bin files. Jun 07 15:00:41 downloaded it earlier while working but not get clear how to work with it Jun 07 15:00:46 how to use it Jun 07 15:02:18 Review the readme files in am335x_pru_package to get the details. The package contains the source code for the pasm assembler. You'll need to build it from source, which will give you the pasm binary. Jun 07 15:02:56 i had also came across a page where it is instructed to follow step 1 from this site then do this https://elinux.org/BeagleBone_PRU_Notes as instructed Jun 07 15:05:02 That page is from 2014, so it is a bit out of date. For example, it tells you to echo BB-BONE-PRU-01 into a slots file. That's very old (like, 3.8 kernel old). Jun 07 15:05:29 This is the big problem with the PRU stuff... it has changed over time, but there are a lot of old tutorials lingering around. Jun 07 15:05:47 but this step beagle$ mv pasm pasm_2 doesnot work i think i have make my own directory name pasm2 Jun 07 15:06:08 Don't worry about the material on that page. It is out of date. Jun 07 15:07:09 Build pasm from am335x_pru_package. Get it installed on your system so that pasm is in your path. Read the readmes in the package for the details on how to build it. Jun 07 15:07:35 thats true the same problem i faced with the element14 site also as the directory structure little bit changed over kernel versions Jun 07 15:08:13 Once you have a working pasm, assemble gamepad.pasm to create a new gamepad.bin. Once you can do that, you can begin changing the gamepad.pasm and experimenting with it. Jun 07 15:10:47 i dont understand the instruction as it seems it dont have on the page https://github.com/beagleboard/am335x_pru_package/blob/master/README.txt . I think it is refering to the documentation that are linked with it.What you say??? Jun 07 15:13:07 Just run "make" and then "sudo make install" from the top-level directory. Jun 07 15:13:22 Look at the top-level makefile for the project. Jun 07 15:14:45 it is returing this Jun 07 15:14:50 * pranav_kumar[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/xjCcHnKCqmhCHsSemtXRCFDa > Jun 07 15:14:57 debian@beaglebone:~/pru_work/am335x_pru_package$ Jun 07 15:15:29 When you ran "make" first, was everything built OK? Jun 07 15:15:47 It looks like you haven't built it. You're just trying to install it. Jun 07 15:19:07 means i just run "sudo make" then sudo make install Jun 07 15:19:32 * pranav_kumar[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/OdSWeHUOtnoVRSrjhRmMMmvB > Jun 07 15:19:46 i think this time i ran fine Jun 07 15:20:03 So, try running "pasm" and see what it says. Jun 07 15:20:10 $ pasm Jun 07 15:20:50 PRU Assembler Version 0.87 Jun 07 15:20:51 Copyright (C) 2005-2013 by Texas Instruments Inc. Jun 07 15:21:04 ......... Jun 07 15:21:15 with other option Jun 07 15:21:57 OK, so it works. You should be able to use pasm to build gamepad.pasm now. Look at the build.sh in the directory with gamepad.pasm to see the arguments to run pasm with. Jun 07 15:22:44 I am at work right now and have to get back to what I was doing. You should have the tools that you need to begin experimenting. Jun 07 15:23:10 Normally, this is the sort of stuff that we get sorted out during the bonding period before the start of GSoC, but you were still finishing your classwork... Jun 07 15:23:42 You have some long hours ahead of you to get caught up on your project, and you only have two weeks before the first evaluation period. Jun 07 15:24:00 thanks very much for the guidance 🙂 Jun 07 15:24:01 upadate you soon Jun 07 15:24:17 Please update your wiki page, too, so that we can see what you've been working on. Jun 07 15:24:33 by the way it (build.sh) ran just fine with zeo error Jun 07 15:24:33 The more details on the wiki, the better. Jun 07 15:24:58 Good luck with it, and send your mentors a mail if you get stuck. Jun 07 15:25:40 are you talking about the progress page Jun 07 15:25:53 wiki page Jun 07 15:25:55 Yes, your page with the daily updates. Jun 07 15:26:46 ok maintain it today with the past two days that i have not maintained thanks Jun 07 15:27:02 going to take my dinner **** BEGIN LOGGING AT Fri Jun 07 19:32:58 2019 **** ENDING LOGGING AT Sat Jun 08 02:59:57 2019