**** BEGIN LOGGING AT Mon May 21 03:00:05 2018
May 21 11:30:21 <abhishek_[m]> muneeb17: How's it going?
May 21 11:34:55 <muneeb17[m]> abhishek_: Hi. Sorry for not being active. I fell ill last week and took two days off. I was just about to upload the weekly report. Also I'll start giving daily updates on the channel from now on. I'm done with remoteproc, rpmsg and prumem functions. I'm stuck at the ddr access.. like how to know the starting address of the ddr and all.
May 21 13:21:23 <abhishek_[m]> muneeb17: What do you want to know there?
May 21 13:21:35 <abhishek_[m]> How can we help you get unstuck?
May 21 13:22:54 <abhishek_[m]> muneeb17: Taking a look at your code now
May 21 13:23:09 <abhishek_[m]> I see here in the https://github.com/MuneebMohammed/pypruss/tree/master/examples
May 21 13:23:20 <abhishek_[m]> You have provided binary file for the PRUs
May 21 13:23:59 <abhishek_[m]> It is not usually a good idea to put binary files in version control, especially when those can be recompiled from source
May 21 13:24:08 <abhishek_[m]> Provide the source code for the examples as well
May 21 13:24:13 <abhishek_[m]> and build instructions
May 21 13:44:40 <muneeb17[m]> abhishek_:  With the uio_pruss, we could find the ddr address and quite easily as here https://bitbucket.org/intelligentagent/pypruss/src/6a6ec5c3435e26bc4e2304c0559693777e7dad76/pypruss/pypruss.c?at=master&fileviewer=file-view-default#pypruss.c-251  I was wondering how to access it now. Should it start at 0x80000000 ?
May 21 13:44:54 <muneeb17[m]> abhishek_: about the bin files, I'll include the source as well now
May 21 13:45:31 <abhishek_[m]> muneeb17: The current version of rpmsg uses vrings
May 21 13:45:47 <abhishek_[m]> Wherein the DDR is managed fully by the kernel driver
May 21 13:46:23 <abhishek_[m]> So while you will be able to mmap the SRAM region of the PRUs as well as the shared memory region, you won't be able to access the DDR directly
May 21 13:47:56 <muneeb17[m]> abhishek_:  Oh! . So, should the function be omitted now?
May 21 13:48:56 <abhishek_[m]> Have to leave in a bit, ask ZeekHuge when he is online.
May 21 13:49:40 <abhishek_[m]> zeekhuge: Please address muneeb17's query above ^
May 21 15:22:03 <zeekhuge> muneeb17: You do not need to do anything directly for the DDR. You have to use `rpmsg` for it
May 21 15:22:40 <zeekhuge> `rpmsg` does everything and sends the message from PRU to DDR (i.e. makes PRU to write it to DDR).
May 21 15:23:34 <zeekhuge> muneeb17: take a look at this - https://github.com/ZeekHuge/BeagleScope/blob/port_to_4.4.12-ti-r31%2B/examples/firmware_exmples/pru_pin_state_reader/PRU_PIN_STATE_READER/main.c#L88
May 21 17:16:14 <muneeb17[m]> zeekhuge:  Thanks!
May 21 17:43:27 <jkridner> vaishnav98_: the issues you plan to fix still aren't marked as gsoc-2018 or assigned to you.
May 21 17:43:34 <jkridner> vaishnav98_: have you tried to self-assign them?
May 21 17:44:02 <jkridner> ravikp7: can you do something similar for node-beagle-boot and BeagleBoot to help us track?
May 21 17:48:40 <vaishnav98_> jkridner: I tried to do it , but it looks like with read only permission, I can't assign the issues to myself, I did try to inform you and anujdeshpande[m] about this before the coding period started.I will move the examples to /bone101/..  as you said.
May 21 17:50:39 <jkridner> re: bone101...  not the directory, the project. hope that is clear.
May 21 17:53:06 <jkridner> vaishnav98_: for the remote access thing, be sure to examine https://github.com/beagleboard/bonescript/blob/7e1e6ce67a9d48a5f454b6d11e34e2dfbef069d2/test/TODO/remote_bonetest.js
May 21 17:53:38 <vaishnav98_> jkridner: do you have any update regarding the shipping status of the boards send, is everything okay? I haven't received any calls for submitting KYC documents yet.
May 21 17:54:02 <jkridner> if we could add some proper security, we could setup some various devices to run the travis-ci tests triggered by RPC calls from the test server.
May 21 17:54:12 <jkridner> vaishnav98_: just got shipping confirmation this morning...
May 21 17:54:17 <jkridner> still don't have a tracking #.
May 21 17:55:27 <vaishnav98_> jkridner: yes I meant that only ... bone101/examples/extras/c-from-js/mraa (or similar)  to be exact
May 21 17:59:56 <vaishnav98_> jkridner: sure , I will go through it , currently i am working on the 'pwm-zero duty cycle spikes' issue , was able to test the issue, still exists giving spikes ( peak ~ 0.98V) could find some temporary solutions trying for a better fix now.
May 21 18:02:38 <vaishnav98_> jkridner: would be very nice if We could implement it ,then most of the code can be covered.
May 21 18:03:11 <vaishnav98_> jkridner: Thanks , I just wanted to know if everything is okay
May 21 18:22:21 <jkridner> ?
May 21 18:22:37 <jkridner> I'm happy with the C/FFI stuff.... I'd like to move on if you and anujdeshpande[m] are happy with it.
May 21 18:38:47 <jkridner> https://github.com/beagleboard/bonescript/issues?q=is%3Aissue+is%3Aopen+label%3Agsoc-2018
May 21 18:38:51 <jkridner> let me know if I missed any.
May 21 19:10:18 <vaishnav98_> jkridner: sure , I have started working on other issues. anujdeshpande[m] : waiting for your opinions too.
May 21 19:11:00 <vaishnav98_> jkridner: you have covered all of the relevant open issues.
May 22 01:16:09 <ravikp7> jkridner: sure, I'll mark the issues
**** ENDING LOGGING AT Tue May 22 03:00:04 2018