**** BEGIN LOGGING AT Thu Jul 18 02:59:56 2019 Jul 18 12:30:01 zeekhuge: I made the register changes and the firmware does work properly! here is the changed code: https://gist.github.com/pratimugale/97234a8c0e5346d1dc53b8310264e582. Thanks a lot Jul 18 12:40:50 zeekhuge: I'm not clear with what JMP R3.w2 exaclty does though, couldn't find it in any docs. From what I understand, R3.w2 stores the return address of the next instruction of the c-code in the generated .asm file. is this right? Jul 18 12:42:35 had to attend college today, so starting now Jul 18 12:45:43 Tomorrow I will work during the day Jul 18 12:55:37 pratimugale: cool! Jul 18 12:56:00 Now we know how to return from a method that has been implemented in asm. Jul 18 12:56:03 That is so cool Jul 18 12:56:38 So, now we can implement parts of code in asm and call them directly, while other high level code is in C. Jul 18 12:58:19 pratimugale: yes. Thats basically the clpru implementation. You should be able to see in the generated asm code that when we invoke a method, the instruction 'JAL r3.w2, ' is used Jul 18 12:59:01 That 'JAL' instruction unconditionally jumps to the method lable, and also saves the next instruction's address in r3.w2 Jul 18 12:59:08 zeekhuge: yes, will try to call two .asm files from c-program to check if it works too Jul 18 12:59:34 If you will link them correctly, then it will work. Jul 18 12:59:50 Link = using lnkpru Jul 18 13:01:31 Will go through it to see the working Jul 18 13:01:54 Just look in the gist you sent to me Jul 18 13:02:03 What was its link? Jul 18 13:03:13 zeekhuge: link as in ? Jul 18 13:04:02 And that halt in the asm code at the end is not required. The code control is anyway jumping before that. Jul 18 13:04:08 So it never gets executed. Jul 18 13:04:30 Ok Jul 18 13:04:34 Link of the gist which had asm code generated from the C code. Jul 18 13:05:40 Oh, here https://gist.github.com/pratimugale/920e3ccec31b6379834434510fa209f0 Jul 18 13:05:46 pranav_kumar : hey! How is it going? Jul 18 13:06:18 This one was when I was using R1,2,3 registers Jul 18 13:07:59 pratimugale notice the line https://gist.github.com/pratimugale/920e3ccec31b6379834434510fa209f0#file-main_pru0-asm-L216 Jul 18 13:08:08 Hello @ZeekHuge_:matrix.org i just came from my college ,i am testing the circuits and update according on the page by today Jul 18 13:08:36 As i take leave till 22 from the college today Jul 18 13:09:10 You @ZeekHuge_:matrix.org get the most of the update by tonight Jul 18 13:09:15 pranav_kumar: okay. Can you please add me to the email threads, if any, that you send out as daily updates? Jul 18 13:09:49 Yes sure Jul 18 13:10:54 pranav_kumar: my email is "contact" at "zeekhuge" dot "me". Jul 18 13:11:20 I had whatsapp you Jul 18 13:13:50 pratimugale: does that line make it clear now? Jul 18 13:17:14 zeekhuge: Yes, so R3.w2 is used everytime a function is called (configIntc function is also present), and since the assmebly code is invoked using the start function, it is our job to jump back to the c-code for it to continue its execution Jul 18 13:19:04 in short it is used to return from a function Jul 18 14:37:18 Correct. Jul 18 16:27:09 julieng: it is interesting why there is no output from dom0 after xen output Jul 18 16:27:23 are those good bootargs: "rw root=/dev/ram rdinit=/sbin/init console=hvc0 earlyprintk=serial,ttyS2 mem=512M earlycon=xenboot" Jul 18 18:17:26 embden[m]: I am not how Linux would react with both earlyprink and earlycon. Jul 18 18:17:43 If you don't have any output then quite possibly the Dom0 kernel is stuck somewhere Jul 18 18:17:55 before the console (and even earlycon) is enabled. Jul 18 18:18:31 Do you have CONFIG_DEBUG=y selected in Xen? Also, do you have the UART working in Xen (i.e you are able to receive character) ? Jul 18 18:53:31 julieng: yes, CONFIG_DEBUG=y is enabled Jul 18 18:53:59 and the same configuration worked earlier, and xen reacts on commands (h, *, ...) Jul 18 19:39:29 julieng: ok, after some experiments I got some output, the right option for me was: "rw root=/dev/ram rdinit=/sbin/init console=hvc0 mem=512M earlycon=xenboot" Jul 18 19:46:15 So, now I have a booting kernel https://pastebin.com/f0kXGDEL with almost the same error but with working uart interrupts for xen Jul 18 19:59:40 zeekhuge: i had made enough changes so that code become readable and changes all the file type from .p to .asm and remove unwanted spaces Jul 18 19:59:58 zeekhuge: look into the branch wip Jul 18 20:00:07 for latest commits Jul 18 23:36:13 @ds2 thanks a lot for your suggestions reagarding the circuit modification . And now i can say that every time i run the program it just works fine and no problem is encountered both in input and output. https://youtu.be/Sn4NDfBu9ac Jul 18 23:37:22 I had removed the logic level shifter from the circuit and running shift register directly from bb black Jul 18 23:55:00 zeekhuge i had sent you the mail plz conform me if you had received that and added you in the email thread **** ENDING LOGGING AT Fri Jul 19 02:59:57 2019