**** BEGIN LOGGING AT Mon Jul 06 03:00:57 2020 **** BEGIN LOGGING AT Mon Jul 06 03:07:43 2020 **** BEGIN LOGGING AT Mon Jul 06 06:29:51 2020 **** BEGIN LOGGING AT Mon Jul 06 06:43:26 2020 **** BEGIN LOGGING AT Mon Jul 06 10:25:02 2020 Jul 06 11:15:33 Abhishek: can you please share the link to new beaglelogic image. i want to try it **** BEGIN LOGGING AT Mon Jul 06 11:50:28 2020 Jul 06 13:44:46 hey deepankarmaithani any update? Jul 06 14:34:19 Hey Abhishek I tried using RPMSG, is there any way i can send message to arm core first. Like all examples first received data from ARM, then populated src, dst, which was used to send data back to arm core. Jul 06 15:11:34 set up the hardware Jul 06 15:11:48 trying to translate the TRUTH table into code Jul 06 16:01:04 vedant16: Hey Jul 06 16:04:37 Hey pratimugale Jul 06 16:06:40 Hey Abhishek hendersa Jul 06 16:06:50 * hendersa waves. Jul 06 16:07:04 Please check my progress report. Jul 06 16:09:02 I am trying to do this, right now. Is this possible to do ? or i would need a kernel module to do so. Jul 06 16:10:42 Are all of your primitives and control flow structures now implemented? Jul 06 16:10:57 Yes, they are done. Jul 06 16:11:31 https://github.com/VedantParanjape/simpPRU/tree/master/examples these are the examples i have implemented and tested on pocketbeagle. Jul 06 16:11:32 So you could, in theory, write any program within the limits of SimpPRU and it definitely will work? Jul 06 16:11:46 Yes Jul 06 16:11:57 vedant16: So currently you manually assemble and load the program> Jul 06 16:11:59 ? Jul 06 16:12:40 No, I have used system() command in the binary, so it automatically calls PRU GCC and generates a elf binary Jul 06 16:13:08 This is what i do: https://github.com/VedantParanjape/simpPRU/blob/e0e8894ccb00aab432c358a913c38dfb91bfe0f2/src/parser.y#L730 Jul 06 16:13:36 Then i do load the elf binary manually Jul 06 16:13:53 vedant16: oh okay Jul 06 16:13:53 I don't have a problem with that approach, but what happens if something goes wrong? Jul 06 16:14:13 Any error checking in there at any of the stages? Jul 06 16:15:00 Error checking exists for my language, I get error messages if syntax is wrong. if generated C code has any error, PRU-GCC shows them. Jul 06 16:15:08 * Error checking exists for my language, I get error messages if syntax is wrong. If generated C code has any error, PRU-GCC shows them. Jul 06 16:15:16 * Error checking exists for in language, I get error messages if syntax is wrong. If generated C code has any error, PRU-GCC shows them. Jul 06 16:15:24 Will yyerror() just terminate if a parsing error occurs? Jul 06 16:16:11 Basically, I just want to make sure that usable error messages are pushed back up to the user. Jul 06 16:16:16 Yes, yyerror is a custom error handler. For syntax error bison takes care of that Jul 06 16:16:45 I will give a example. **** BEGIN LOGGING AT Mon Jul 06 16:19:53 2020 Jul 06 16:20:14 OK. So, the basic plumbing for feedback is there. I'd make the error messages a bit easier to read and understand, since you are expecting beginners to be using this tool. Jul 06 16:21:34 Okay, I will lookup about implementing a custom error handler. Jul 06 16:23:40 Any more language features that should be added, I have digital_read/write, delay, and ability to use the hardware counter ? Jul 06 16:24:08 I am trying to implement hardware PWM on PRU, but haven't yet understood how to do it. Jul 06 16:25:24 Well, what pinmux modes do you support? Ideally, you'd want to support ADC, PWM, etc., but those may step on the kernel driver already in place for that purpose. Jul 06 16:26:15 You want a tool that will work in any system, so having the PRU fight with the kernel over those features needs to be avoided. Jul 06 16:26:39 But these are not a part of PRU subsystem, so setup the use through OCP ? Jul 06 16:26:57 currently, pruin and pruout only. Jul 06 16:27:19 OK, so it sounds like you're restricting yourself to GPIOs for now. Jul 06 16:28:07 I recommend that you focus on parsing/compiling SimpPRU (which looks good now), better error messages, documentation, etc. Jul 06 16:28:26 Test and polish. Make it as easy to use and as useful for beginners as possible. Jul 06 16:29:10 For example, someone might write some logic in SimpPRU, build it, and then take the generated C code as a base for the project. Jul 06 16:29:39 Auto-commenting the generated C code would be good for this, if possible. Jul 06 16:31:15 since, i haven't added float support, I will put ADC aside, rather try adding PWM. Jul 06 16:31:56 Alright, sounds great. I will start with docs, and error messages part. Currently i was trying to add rpmsg support Jul 06 16:32:59 Unfortunately, I have a meeting that I have to go to here at work, so I have to leave for now. Jul 06 16:33:12 It looks like you are making good progress. Keep it up! Jul 06 16:34:51 Thanks :) Jul 06 16:35:00 Bye ! Jul 06 16:40:10 Hey pratimugale tried using RPMSG, is there any way i can send message to arm core first. Like all examples first received data from ARM, then populated src, dst, which was used to send data back to arm core. **** BEGIN LOGGING AT Mon Jul 06 19:25:31 2020 Jul 06 22:12:10 jkridner: Here is my weekly progress report for last week: https://groups.google.com/d/msg/beagleboard-gsoc/QwMJGBXj8DQ/gnciCYBPBQAJ. I also tried to port CTAG Face drivers to 5.4-rt, but sadly the spi bitbang driver is not loading, I will try again when I am in front of schedule but this week I will start on AVB implementation. **** BEGIN LOGGING AT Tue Jul 07 02:52:41 2020 **** ENDING LOGGING AT Tue Jul 07 02:59:58 2020