LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Shehryar Shaheen <shehryar.shaheen@u...>
    Date: Tue, 27 May 2003 17:58:05 +0100
    Subject: Re: [oc] Verilog coding style for Open Cores-RTL - Case in point SHA1
    Top

    So what would Sytem Verilog have in the offing that
     SystemC doesn't ?
    
    Would you think that the reason that SystemC is not popular is
     cause the learning curve associated with a new language tends
     to put off many users who already have a firm grip over current
     HDLs ?
    
    
    ----- Original Message -----
    From: "Joachim Strömbergson" <Joachim.Strombergson@I...>
    To: <cores@o...>
    Sent: Tuesday, May 27, 2003 3:51 PM
    Subject: Re: [oc] Verilog coding style for Open Cores-RTL - Case in point
    SHA1
    
    
    Aloha!
    
    Shehryar Shaheen wrote:
    > SystemC is more for system modeling (HW+SW) some
    >  complex SoCs like the E-GOLD GSM Chipset from Infenieon
    >  used SystemC in it's design process.
    >
    > Siemens has also been using SystemC for ATM chipsets.
    
    ATM - Which is also a dead technology BTW. ,-)
    
    (Sorry couldn't resist)
    
    > Sysnopys already has the CoCentric compiler for SysyemC synthesis
    >  and also at the DAC 2003 Synopsys would be showing up at the
    >  SystemC booth.
    >
    > If you look at the RTL subset of SystemC you'll notice that it's very
    > similar
    >  to VHDL or Verilog RTL subset. So in terms of syhthesis people who don't
    > have
    >  experience with pure HDLs won't be able to just write some code in C++
    and
    >  turn it into hardware.
    >
    > But we'll probably see more executable specifications for SoCs being
    written
    >  in SystemC.
    
    Trust me, I have used basically basically all tools available on the market
    for SoC-modelling (they generally suck pretty badly) and been involved in
    writing a few proprietary models and tools myself.
    
    I'm also aware that there are places where SystemC is used. What I refer to
    is
    that among peers (according to stats from DAC, comments in ESNUG etc),
    SystemC
    is not popular. And even more importantly among peers, SystemC doesn't seem
    to
    solve problems in a way more productive way that people are doing today.
    
    What have also become quite clear is that many sites that have been using or
    are using SystemC are doing so because high-level management have decided on
    using SystemC, not because the engineering department have asked for it.
    
    I have also been on presentations by EDA vendors where the argument *for*
    SystemC have been that by using SystemC, "cheap SW designers" (as in low
    salaries) can build ASICs. That have been the argument and some managers are
    buying in to that.
    
    It's a similar to the argument used by some to promote graphical design
    entry
    tools, where knowledge about hardware somehow is not needed when you can
    draw
    FSMs, flowcharts etc.
    
    --
    Med vänlig hälsning, Yours
    
    Joachim Strömbergson - Alltid i harmonisk svängning.
    VP, Research & Development
    ----------------------------------------------------------------------
    InformAsic AB / Hugo Grauers gata 5B / SE-411 33 GÖTEBORG / Sweden
    Tel: +46 31 68 54 90  Fax: +46 31 68 54 91  Mobile: +46 733 75 97 02
    E-mail: joachim.strombergson@i...  Home: www.informasic.com
    ----------------------------------------------------------------------
    
    
    
    
    
    
    

    ReferenceAuthor
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in pointSHA1Marco Antonio Simon Dal Poz
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in pointSHA1Joachim
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in point SHA1Shehryar Shaheen
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in pointSHA1Joachim
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in point SHA1Shehryar Shaheen
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in pointSHA1Joachim

    Follow upAuthor
    Re: [oc] Verilog coding style for Open Cores-RTL - Case in point SHA1Tom Hawkins

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.