All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harshitha S <harshithasridhar172000@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Continue OpenRISC contibution
Date: Tue, 31 Aug 2021 22:23:36 +0530	[thread overview]
Message-ID: <CADGJwMyrBUCb8gLbDZpCgor0BTV5Ouy1N8v=2Dua7cueg=iVfg@mail.gmail.com> (raw)
In-Reply-To: <3353f448aa67d1d6bf61eaa37256c90d1377bb74.camel@ieee.org>

Hello Dan,

I have used chparam everywhere in the SBY files because an error occurred
while decoding string parameters using pycode.
Here is the small snippet where I found the error.

Code:

--pycode-begin--
cmd  = "hierarchy -top mor1kx"
cmd += " -chparam FEATURE_INSTRUCTIONCACHE %s "  %("ENABLED")
output(cmd)
--pycode-end--

Error:

[image: image.png]

How can I avoid this error? Can I use hierarchy -chparam without using
pycode?

On Tue, Aug 31, 2021 at 9:00 PM Dan <dan.gisselquist@gmail.com> wrote:

> Harshita,
>
> I would recommend replacing the "chparam" commands in your SBY files with
> "hierarchy" commands.  "chparam" forces the synthesis tool to re-read the
> design each time the command is issued, and may lead to changes that are
> inconsistent along the way.  "hierarchy" has a "-chparam" option that can
> be used to re-read the design once, setting all of the parameters in the
> design to a consistent usage.
>
> Dan
>
> On Tue, 2021-08-31 at 22:47 +0900, Stafford Horne wrote:
>
> The commit looks good, can you make a PR for it?
>
>
> On Sun, Aug 29, 2021 at 2:16 AM Harshitha S
>
>
> <
>
> harshithasridhar172000 at gmail.com
>
> > wrote:
>
>
> 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 <
>
> shorne at gmail.com
>
> > 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
>
> _______________________________________________
>
> OpenRISC mailing list
>
> OpenRISC at lists.librecores.org
>
>
> https://lists.librecores.org/listinfo/openrisc
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20210831/247bc649/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 111049 bytes
Desc: not available
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20210831/247bc649/attachment-0001.png>

  reply	other threads:[~2021-08-31 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADGJwMwapL_eB_ZqKmaDsoFxCY_3qvKu=0BfdSGQZaC5GEjP1Q@mail.gmail.com>
2021-08-26 23:41 ` [OpenRISC] Continue OpenRISC contibution Stafford Horne
2021-08-28 17:17   ` Harshitha S
2021-08-31 13:47     ` Stafford Horne
2021-08-31 14:02       ` Harshitha S
2021-08-31 15:30       ` Dan
2021-08-31 16:53         ` Harshitha S [this message]
2021-08-31 17:07           ` Dan
2021-08-31 17:08           ` Dan
2021-08-31 18:22             ` Harshitha S
2021-09-01 13:26     ` Stafford Horne
     [not found]       ` <CADGJwMzCa_u2+V3Tu-pp92GgxubwiU0HQo0Dy5G3b0sAO2xzFw@mail.gmail.com>
2021-09-01 21:06         ` Stafford Horne
     [not found]           ` <CADGJwMxxEp4YFTe4271LJHoc4sJo2P6mtNOFhx+w6+phF25xDQ@mail.gmail.com>
2021-09-02 12:02             ` Stafford Horne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADGJwMyrBUCb8gLbDZpCgor0BTV5Ouy1N8v=2Dua7cueg=iVfg@mail.gmail.com' \
    --to=harshithasridhar172000@gmail.com \
    --cc=openrisc@lists.librecores.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.