**** BEGIN LOGGING AT Sat Jun 27 02:59:57 2020
Jun 27 10:12:36 <deepankarmaithan> jkridner:  sakethr98  ds2 Abhishek   Contributed to the pru-gcc-examples . Contribution merged upstream  https://github.com/dinuxbg/pru-gcc-examples/pull/6
Jun 27 10:14:37 <sakethr98[m]> nice :D
Jun 27 10:31:02 <vedant16[m]> > Abhishek: pratimugale http://dpaste.com//073NRMH This is my test file and compile command
Jun 27 10:31:02 <vedant16[m]> Solved this, any pru code needs resource_table.h which i was not including.
Jun 27 10:55:57 <pratimugale[m]> Yes, even if its empty resource table would be required for remoteproc to work
Jun 27 16:11:16 <vedant16[m]> Yup
Jun 27 16:11:21 * vedant16[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/qtOrdPpYPuCPIgusoxtAkzis >
Jun 27 16:11:38 * vedant16[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/DeoOIUoQqYxBmjmuVTSMgnLD >
Jun 27 16:11:50 <vedant16[m]> pru-gcc gives a error
Jun 27 16:12:06 * vedant16[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/MwVolAMKMoZOeTcblbKNGbVn >
Jun 27 16:23:49 <deepankarmaithan> Yes you cannot use the macro __R30 when compiling with PRUGCC
Jun 27 16:24:14 <vedant16[m]> ohh
Jun 27 16:24:29 <vedant16[m]> So, i can only use pru/io.h ?
Jun 27 16:24:30 <deepankarmaithan> Look at my new example that i contributed to pru-gcc-examples repo
Jun 27 16:24:35 <vedant16[m]> yes
Jun 27 16:24:52 <deepankarmaithan> It will make  the usage clear
Jun 27 16:25:48 <deepankarmaithan> <vedant16[m] "So, i can only use pru/io.h ?"> yes if you would look there there are inline asssembly instructions
Jun 27 16:26:28 <vedant16[m]> ahh okay, I macro method was good. very less external dependency
Jun 27 16:26:45 <vedant16[m]> <deepankarmaithan "Look at my new example that i co"> Why did you read r30 in the example ?
Jun 27 16:26:59 <vedant16[m]> read_r30()|LED) : ~(LED)&read_r30())
Jun 27 16:27:07 <vedant16[m]>  * ```read_r30()|LED) : ~(LED)&read_r30())```
Jun 27 16:28:07 <deepankarmaithan> Because i need to mask all other bits so that they are not affected and only the required bit which is bit 5 is only affeted
Jun 27 16:28:26 <vedant16[m]> ohh, got it
Jun 27 16:28:34 <vedant16[m]> so you are reading the current state
Jun 27 16:28:47 <vedant16[m]> i assumed you are using it to read button input
Jun 27 16:29:05 <deepankarmaithan> no
Jun 27 16:29:28 <deepankarmaithan> r30 is for outputs
Jun 27 16:29:33 <deepankarmaithan> r31 is for inputs
Jun 27 16:29:50 <deepankarmaithan> i am reading the  register responsible for output
Jun 27 16:29:51 <vedant16[m]> yup, that's why i was confused
Jun 27 16:30:42 <deepankarmaithan> i am using r31 for reading the input
Jun 27 16:31:28 <deepankarmaithan> <vedant16[m] "read_r30()|LED) : ~(LED)&read_r3"> basically   what it does is   set : clear
Jun 27 16:31:49 <deepankarmaithan> for bit no 5 in my example which is connected to LED
Jun 27 16:32:34 <vedant16[m]> <deepankarmaithan "for bit no 5 in my example which"> Ohh
Jun 27 16:32:40 <vedant16[m]> Let me try the example
Jun 27 16:32:51 <vedant16[m]> with hardware
Jun 27 16:32:59 <deepankarmaithan> sure
Jun 27 17:44:54 <vedant16[m]> Abhishek: pratimugale hendersa I added code generator, right now only adds bare minimum skeleton code, tested on PRU, it works.
Jun 27 17:45:20 <vedant16[m]> https://github.com/VedantParanjape/simpPRU
Jun 27 17:45:59 <vedant16[m]> I will complete this task by tommorow: `mplementing Language backend for variables and arithmetic operators`
Jun 27 17:46:07 <vedant16[m]>  * I will complete this task by tommorow: `Implementing Language backend for variables and arithmetic operators`
**** ENDING LOGGING AT Sun Jun 28 02:59:57 2020