**** BEGIN LOGGING AT Thu Feb 25 02:59:59 2016 Feb 25 16:16:15 hi Feb 25 16:52:05 moin Feb 25 20:37:04 hey alexhiam, i tried working on the PRUICSS, and have now reached to program the PRUs. I have limited experience with assembly( did 8051 long ago ) should I use C or is it compulsory to get understanding of Assembly ? Feb 25 20:41:53 * ZeekHuge is also trying to understand the PRU architecture. Feb 25 21:49:52 ZeekHuge: C is fine, though it would probably be beneficial to get a LED blinking with assembly to better understand the architecture Feb 25 21:51:13 Ohk, I have got the onboard LED blinking using assembly :) Feb 25 21:51:46 how can I show it to you alexhiam ? Feb 25 21:52:26 best to push any code you want us to look at to github Feb 25 21:52:33 put the code on github? Feb 25 21:53:31 yeah but that code is based upon the examples in the am355x_pru_package. Feb 25 21:53:50 a README with install instruction? Feb 25 21:53:54 s Feb 25 21:54:30 call it am355x_pru_examples then Feb 25 21:54:48 code+readme+license Feb 25 21:55:01 yeah, keep their copyrights and license and what not and make note of changes you've made Feb 25 21:55:32 Ohk :) Will do. Feb 25 21:55:48 Note: beagleboard.org "encouraging" better habits this year... Feb 25 21:56:26 I have used prussdrv. Is there a need to use remoteproc ? or give it a try ? Feb 25 21:56:35 e.g. pushing to github upwards of daily, targeting merges to upstream repositories, etc. Feb 25 21:57:03 remoteproc seems to be quite complex .... Feb 25 21:57:08 hopefully remoteproc will replace prussdrv in the not too distant future, so best to be working with it instead Feb 25 21:57:25 yes, maximum self-flagellation Feb 25 21:58:06 file issues on yourself, make pull requests for your "feature" branches... Feb 25 21:58:27 +1 Feb 25 21:58:49 oh, and setup travis-ci/code-smell on your buildable repos Feb 25 21:58:49 would be great to require using the issue tracker this year Feb 25 21:59:16 i.e. separate all goals into discrete issues and milestones Feb 25 21:59:21 at the start Feb 25 21:59:24 what do you mean "would be great"? i thought we were already doing that Feb 25 21:59:37 are we? good! Feb 25 21:59:44 I should use remoteproc ?.. ohk. but almost all resources i was able to find, was based on prussdrv. Feb 25 21:59:54 you can use issues for "tasks" with enhancement/other label Feb 25 22:00:05 with milestone dates matching the timeline Feb 25 22:00:12 yeah, labels ftw Feb 25 22:00:30 tasks in milestones with draft release targets Feb 25 22:01:01 since they need to document the damn plan anyway Feb 25 22:01:09 just do it that way Feb 25 22:01:30 * nerdboy will keep the developer clue-bats handy Feb 25 22:01:50 ZeekHuge: take a look at pru-bridge and beaglelogic, both previous gsoc projects Feb 25 22:02:07 last year had some Feb 25 22:02:18 Abhishek (who did beaglelogic) is usually around here Feb 25 22:04:17 oh right, and shubhangi's PRU-framework: https://github.com/shubhi1407/PRU-framework Feb 25 22:04:24 that might be a good place to start Feb 25 22:06:35 it's true that remoteproc isn't very beginner friendly. The goal of that pru-frmework project was to make it simpler, though I feel like that ended up going in a different direction than was originally planned... Feb 25 22:18:47 ZeekHuge: this thread has some useful info: https://groups.google.com/forum/#!searchin/beagleboard/prussdrv$20to$20remoteproc/beagleboard/itNNvLeSLGs/usYudoFVh_cJ Feb 25 22:34:14 ohk. Thank you alexhiam :) Feb 25 22:42:21 alexhiam, can i use PRU_framework ? or should I dig, myself into remoteproc ? Feb 25 22:48:06 ZeekHuge: that framework might be a good way to start figuring out remoteproc **** ENDING LOGGING AT Fri Feb 26 02:59:58 2016