element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
FPGA
  • Technologies
  • More
FPGA
Blog XXICC (21st Century Co-design) release 0.0r
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join FPGA to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: johnbeetem
  • Date Created: 24 Aug 2017 9:29 PM Date Created
  • Views 3098 views
  • Likes 3 likes
  • Comments 10 comments
  • galaxc
  • icestorm
  • fpga
  • flavia
  • xxicc
Related
Recommended

XXICC (21st Century Co-design) release 0.0r

johnbeetem
johnbeetem
24 Aug 2017

Here is the new release 0.0r of XXICC.  I've been horrifically busy with work and family obligations over the last two years so I wasn't able to keep up with XXICC.  Also, 0.0r is a major release since it adds integer nets and operators to GCHD, and can now program Lattice iCE40 FPGAs using the open-source IceStorm tools.  So there was lots of testing and documentation updates.

 

XXICC (21st Century Co-design) is a not-for-profit research project which attempts to bring digital hardware/software co-design into the 21st Century using an improved programming language and a Reduced Software Complexity philosophy.  Its goal is to make it easier and more enjoyable to write and maintain digital hardware and software. XXICC is pronounced "Chicken Coop", so-called because it has so many layers.

 

For an overview of XXICC, see XXICC: 21st Century Co-design.  For details on the GalaxC programming language, XXICC Object Editor, and GalaxC extensions for Hardware Design (GCHD), here are the latest documents and source code:

 

Release notes for XXICC rev 0.0r

Programming in the GalaxC Language rev 0.0r: reference and user guide for the GalaxC programming language.

The XXICC Anthology rev 0.0r : collection of miscellaneous XXICC topics, including user guides for the XXICC Object Editor, GCHD, Flavia, and IceStorm.

XXICC code release 0.0r : source code for XXICC.

XXICC source code listing rev 0.0r: source code listing as PDF.

XXICC executable binary for Windows rev 0.0r : XXICC executable binary for Microsoft Windows.

GalaxC sample/demo programs rev 0.0r: sample GalaxC programs and GCHD logic libraries.

GalaxC sample/demo program listings rev 0.0r: PDF listing of the sample GalaxC programs and GCHD examples.

Installing and Running XXICC rev 0.0q: Document describing how to install and run XXICC, unchanged for 0.0r.

Compiling and Running GalaxC Programs rev 0.0k: Document describing how to compile and run your own GalaxC programs, unchanged for 0.0r.

Editable XXICC documentation files rev 0.0r: editable XOE files for XXICC documentation.

GCHD examples for IceStorm rev 0.0r: these are for generating Lattice iCE40 FPGAs using IceStorm, using either a Lattice iCEstick or Nandland Go Board as the target.

Data files for FlaviaP40 release 0.0r for Papilio One 250K: Data files for the FlaviaP40 implementation of the Free Logic Array.

Data files for FlaviaP60 release 0.0r for Papilio One 500K: Data files for the FlaviaP60 implementation of the Free Logic Array.

Data files for FlaviaPD59 release 0.0r: Data files for the FlaviaPD59 implementation of the Free Logic Array for Papilio DUO.

Data files for FlaviaLP60 release 0.0r for LOGI-Pi: Data files for the FlaviaLP60 implementation of the Free Logic Array for the ValentF(x) LOGI-Pi.

Data files for FlaviaLB60 release 0.0r for LOGI-Bone: Data files for the FlaviaLB60 implementation of the Free Logic Array for the ValentF(x) LOGI-Bone.

Taming the Wild Bitstream (unchanged for 0.0r): Supplement to Flavia: the Free Logic Array.

 

I've tested XXICC 0.0r on GNU/Linux (Ubuntu on x86 PCs and ODROID-C1 Ubuntu).  I haven't tested it yet on Raspberry Pi Raspbian or BeagleBone Debian.  I tested it on Windows 2000 and 7.  My main machine is Ubuntu, so the others are more likely to have anomalies.  Constructive comments and suggestions are most welcome.  I'd especially like to find out how to reproduce some of the bugs that have been eluding me.

 

The previous version of XXICC is: XXICC (21st Century Co-design) release 0.0q

The earliest versions of XXICC are at Google Code: https://code.google.com/archive/p/xxicc/

 

XXICC is a FLOSS (Free as in Liberty Open Source Software) project.  Software is licensed under GPLv3 and other content is licensed under Creative Commons CC-BY-SA 3.0.

  • Sign in to reply

Top Comments

  • michaelkellett
    michaelkellett over 7 years ago in reply to johnbeetem +2
    I suspect that the main issues are the real one of support (the FPGA vendor will inevitably end up having to deal with issues with third party tools and lose the ability to tweak the tool set any time…
  • Former Member
    Former Member over 7 years ago +1
    Its definitely a good idea to produce a language/compiler which feels more comfortable to work with. My recent escapades in Verilog proves so, as a basic example I was using multiple [always @] blocks…
  • Former Member
    Former Member over 7 years ago in reply to johnbeetem +1
    The way I've understood the = and the <= thing is that using = means it takes more time before it moves on to the next statement(i.e. waits for the original statement to complete before moving on ie. its…
  • johnbeetem
    johnbeetem over 6 years ago in reply to groventov

    Reynel --

     

    Thank you for the compliment.  It's nice to know that people are actually looking at XXICC.

     

    XXICC is on the back burner.  I was within a month or two of a major new release at the end of 2017.  Then 2018 dropped a bunch of family obligations on me, which are only now starting to subside.  One of the non-XXICC activities was moving from California to Colorado, and there are a bunch of house projects that I need to complete before winter.  So there are still a couple months before I can get back to XXICC.  Task 1 will be figuring out where I was at the end of 2017.  When you get back a project after a long break, it can be difficult to remember whether a feature was implemented, partially implemented, or just conceived and not implemented at all image

     

    Meanwhile, Catalin Baetoniu's The Art of FPGA Design series is doing an excellent job of pointing out why new users are daunted by the steep learning curve of standard languages like VHDL image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • groventov
    groventov over 6 years ago

    What happend to this marvelous project. No activity since one year ago!!!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • groventov
    groventov over 6 years ago

    No activity for more than one year. What happened to XXICC?

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • johnbeetem
    johnbeetem over 7 years ago in reply to Former Member

    There's a nice concise description of the difference between blocking (=) and non-blocking (<=) assignment at Nandland.com: https://www.nandland.com/articles/blocking-nonblocking-verilog.html

     

    Basically, in an "always" block the blocking assignment (=) gives you combinational logic while the non-blocking assignment (<=) gives you sequential (clocked) logic.  It's awful nomenclature IMO.  Why not call them "combinational assignment" and "clocked assignment"?

     

    When I write Verilog, I use "always" blocks exclusively for clocked logic and all the assignments in them use '<='.  I put all my combinational logic in "assign y = expr" statements or as part of a "wire" declaration: "wire x = expr".

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • rachaelp
    rachaelp over 7 years ago in reply to Former Member

    lucie tozer wrote:

     

    Its definitely a good idea to produce a language/compiler which feels more comfortable to work with. My recent escapades in Verilog proves so, as a basic example I was using multiple [always @] blocks to perform seperate tasks but later found out that wire/reg types could only be modified in 1[always @]block. This led me to re-writing the entire thing to work around the compilers constraints.

    Hi Lucie,

     

    I've not actually done much Verilog, but I have done a tonne of VHDL. Designing FPGA based hardware was my job for many years. I think what you are seeing here is because when writing HDL, you need to think about the physical hardware and how what you write will infer different pieces of available hardware and how they are connected rather than thinking of it as just like software where (multi threading aside) everything happens sequentially. If you have the same signal driven out of different registered blocks you are effectively trying to connect the Q output of two or more D types together which you wouldn't try to do if you were wiring physical devices on a breadboard. I think once you get your head round that and try to think a little more about the underlying hardware you are trying to target then it'll all become a lot easier.

     

    Best Regards,


    Rachael

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube