**** BEGIN LOGGING AT Fri Apr 17 02:59:57 2020 Apr 17 05:41:09 > the PRU is simple enough you can almost work it out w/pencil and paper Apr 17 05:41:10 I mean i have never worked with the system, even though worked with other such processors. So, just wanted a hands-on. Apr 17 06:40:33 jkridner: https://github.com/beagleboard/cloud9-examples/blob/v2020.01/PocketBeagle/pru/.work-in-progress/pruspeak.pru0.c, this seems pretty interesting. Is it you implementing a botspeaks firmware? Apr 17 07:28:05 jkridner: Okay, thank you :) Apr 17 07:31:08 jkridner: Does PRUspeak need to reimplemented with rproc and rpmsg, as in should i add it as a task in my proposal Apr 17 07:45:15 vedant16: Have you made any changes to the elinux site combining the milestones? Apr 17 07:45:49 I was thinking about it too. Apr 17 07:45:54 pratimugale: Not complete yet. I am working on it right now Apr 17 07:46:08 Thanks for the link. I will look into it Apr 17 07:46:17 I will complete in a few days. Apr 17 08:05:52 vedant16: It would really be good if you are able to do it earlier. Keep the updates that you make and your queries posted here Apr 17 08:06:18 pratimugale: Yes, i'll keep that in mind Apr 17 08:09:56 I will complete earlier Apr 17 09:51:28 vedant can you also add more details in your elinux page regarding your repl implementation Apr 17 09:55:08 > vedant can you also add more details in your elinux page regarding your repl implementation Apr 17 09:55:08 I have added OPCODE list, you mean i should add the interpreter logic? Apr 17 10:09:35 yup Apr 17 10:10:29 interpreter logic,screenshots of sample code if any. what kind of approach decision was taken wrt to repl and why Apr 17 10:11:05 all commands of the repl broken into subparts/descriptions Apr 17 11:22:02 > interpreter logic,screenshots of sample code if any. what kind of approach decision was taken wrt to repl and why Apr 17 11:22:02 I was told only to comeup with opcodes. I'll make sure to update it. Apr 17 12:24:51 vedant16: I'm a novice at bison/flex and the grammar I wrote is very weak, using string identifiers rather than acually parsing opcodes. https://github.com/jadonk/pruspeak/commit/bdc9abc8213f52390cf73ceeb8d86ee2d5b00019 Apr 17 12:25:30 just trying to get something started that can be small, fast and flexible. Apr 17 12:26:19 my goal would be to have it spit out binary opcodes. Apr 17 12:26:42 I need to decide if I'm going to turn identifiers into actual tokens first. Apr 17 14:07:06 You mean this would not run on the PRU? rather on beaglebone linux core and pass opcodes to the PRU via RPmsg. Apr 17 18:17:11 vedant16: or just by direct memory writes. Apr 17 18:17:42 vedant16[m]: yes, I thought you saw I'd started a different implementation than deepak's. **** ENDING LOGGING AT Sat Apr 18 02:59:57 2020