From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harshitha S Date: Sat, 28 Aug 2021 22:47:42 +0530 Subject: [OpenRISC] Continue OpenRISC contibution In-Reply-To: References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: openrisc@lists.librecores.org Hello Stafford, I want to start with a simple one. I have updated the Mor1kx Formal in the readme. Let me know if anything else to be included. https://github.com/Harshitha172000/mor1kx/commit/e192b83ce01cd4b467ce74fe65b2f3a7ced7a22d I will try fixing the bugs and also work on or1kx-formal. Meanwhile, I'm thinking of exploring OpenOCD/GDB for mor1kx CPU debugging but having no idea where to start. Can you guide me beginning with CPU debugging? -Harshitha On Fri, Aug 27, 2021 at 5:11 AM Stafford Horne wrote: > On Thu, Aug 26, 2021 at 10:17:17PM +0530, Harshitha S wrote: > > Hello, > > > > I'm thinking of continuing my contribution to the OpenRISC project. With > my > > GSoC project, I have learned too many new skills and wish to keep this > > learning pace. I would be happy to learn and explore new skills. Please > let > > me know what I can work upon. > > Hi Harshita, > > (CCing list) > > Glad to hear you are still interested. I think there are always plenty of > things, some things on the top of my head: > - Simple - update the mor1kx/readme.md to explain we support formal > - Medium - fix the bugs that you raised > - Bigger - or1k-formal (like riscv-formal, formally verify each > instruction) > > -Stafford > -------------- next part -------------- An HTML attachment was scrubbed... URL: