**** BEGIN LOGGING AT Sun Jul 05 03:01:09 2020
Jul 05 05:28:14 <Abhishek[m]_> vedant16: yes
Jul 05 13:28:23 <vedant16[m]> > vedant16: yes
Jul 05 13:28:23 <vedant16[m]> I wanted a opinion: in the digital_write function, i current pass R30 register bit. Should i keep it that way, or do something like pass it pin name, like `digital_write(P1_30, true)`
Jul 05 14:16:05 <vedant16[m]> > > vedant16: yes
Jul 05 14:16:05 <vedant16[m]> > I wanted a opinion: in the digital_write function, i current pass R30 register bit. Should i keep it that way, or do something like pass it pin name, like `digital_write(P1_30, true)`
Jul 05 14:16:05 <vedant16[m]> @abhishek_:matrix.org @pratimugale:matrix.org @hendersa:matrix.org
Jul 05 14:17:58 <Abhishek[m]_> Pin names are gonna change across platforms. If you can build it carefully, go ahead.
Jul 05 14:19:15 <vedant16[m]> I am going to check platforms through sysfs class, accordingly have pin mapping.
Jul 05 18:22:28 <vedant16[m]> <Abhishek[m]_ "Pin names are gonna change acros"> Okay, completed this, i simply added the pin names in the symbol table, and stored them as constants. i have defined a json file which hosts info about header pin <--> pru pin connections, it cross checks from that json file. Right now, i have made such a table only for pocketbeagle, i will soon add for BBB black, and bbb wireless.
Jul 05 18:24:16 <vedant16[m]> dumped the json object as string, and stored it in a macro (https://github.com/VedantParanjape/simpPRU/blob/e0e8894ccb00aab432c358a913c38dfb91bfe0f2/src/pin_config.h#L9). Used cJSON to handle reading it.
**** BEGIN LOGGING AT Sun Jul 05 19:04:30 2020
Jul 05 19:27:48 <vedant16[m]> Abhishek: pratimugale hendersa cwicks My progress report for week 5: https://groups.google.com/d/msg/beagleboard-gsoc/ejF6F3EdE48/gYtmS8f3BAAJ
**** BEGIN LOGGING AT Mon Jul 06 03:00:09 2020
**** ENDING LOGGING AT Mon Jul 06 03:00:56 2020