Group Actions
Engagement
  • Author Author: johnbeetem
  • Date Created: Date Created
  • Views 898 views
  • Likes 2 likes
  • Comments 5 comments
Related
Recommended

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

johnbeetem

Here is the new release 0.0n of XXICC, which adds Xilinx Spartan-6 Flavia implementations for the ValentF(x) LOGI-Pi board and LOGI-Bone.

 

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 the xxicc.org home page and wiki.  For details on the GalaxC programming language, XXICC Object Editor, and GalaxC extensions for Hardware Design (GCHD), here are the latest documents and complete code.

 

Release notes for XXICC rev 0.0n

Programming in the GalaxC Language rev 0.0j: reference and user guide for the GalaxC programming language, unchanged for 0.0n.

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

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

Data files for FlaviaP48 release 0.0n: Data files for the FlaviaP48 implementation for the Papilio One 500K.

Data files for FlaviaLP56 release 0.0n: Data files for the FlaviaLP56 implementation for the ValentF(x) LOGI-Pi.

Data files for FlaviaLB56 release 0.0n:  Data files for the FlaviaLB56 implementation for the ValentF(x) LOGI-Bone.

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

XXICC code release 0.0n: all source code for XXICC.

XXICC source code listing rev 0.0n: source code listing in PDF.

XXICC executable binaries rev 0.0n:executable XXICC binaries if you don't want to build from source code.

GalaxC sample/demo programs rev 0.0k: sample GalaxC programs and GCHD logic libraries, unchanged for 0.0n.

GalaxC sample/demo program listings rev 0.0k: PDF listing of the sample GalaxC programs and GCHD examples, unchanged for 0.0n.

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

Installing and Running XXICC rev 0.0n: Document describing how to install and run XXICC.

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

 

I've tested XXICC 0.0n on GNU/Linux (Ubuntu, Raspberry Pi Debian "Wheezy", BeagleBone Debian, and BeagleBoard Ångström) and 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.

 

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.

Parents

  • When I first tried Flavia on ODROID-C1 using my Papilio One 250K, I didn't have the permissions set as described described in Installing and Running XXICC rev 0.0n, section 5.3.  Flavia reported that it couldn't find vendor.product ID 0430.6010 or 0430.6014, which was strange because if I gave the lsusb command you could see 0430.6010.  On the other hand, Flavia could see my Adafruit FT232H breakout board which I use as a JTAG controller.

     

    Once I set the permissions as in section 5.3, Flavia could see the Papilio One 250K's FT2232D.  So why didn't Flavia see the FT2232D without permissions as it did with the FT232H?  I don't know, but I suspect it might be a "Raspberry Pi Effect" manifestation.  The FT232H is a high-speed USB device, so it doesn't need USB split transactions.  The FT2232D is a full-speed device, so it will have split transactions in a USB tree that includes high-speed devices.  We know ODROID-C1 currently has problems with keyboards losing and repeating keystrokes, with similar misbehavior for mice.  (I jokingly refer to this as the "Raspberry Pi Effect" since RasPi had those problems with early operating sustems.)  So maybe we're seeing this when libftdi tries to identify the FT2232D.

     

    Just a hypothesis for now.  If it goes away when the "RasPi Effect" is fixed, that will confirm it.

Comment

  • When I first tried Flavia on ODROID-C1 using my Papilio One 250K, I didn't have the permissions set as described described in Installing and Running XXICC rev 0.0n, section 5.3.  Flavia reported that it couldn't find vendor.product ID 0430.6010 or 0430.6014, which was strange because if I gave the lsusb command you could see 0430.6010.  On the other hand, Flavia could see my Adafruit FT232H breakout board which I use as a JTAG controller.

     

    Once I set the permissions as in section 5.3, Flavia could see the Papilio One 250K's FT2232D.  So why didn't Flavia see the FT2232D without permissions as it did with the FT232H?  I don't know, but I suspect it might be a "Raspberry Pi Effect" manifestation.  The FT232H is a high-speed USB device, so it doesn't need USB split transactions.  The FT2232D is a full-speed device, so it will have split transactions in a USB tree that includes high-speed devices.  We know ODROID-C1 currently has problems with keyboards losing and repeating keystrokes, with similar misbehavior for mice.  (I jokingly refer to this as the "Raspberry Pi Effect" since RasPi had those problems with early operating sustems.)  So maybe we're seeing this when libftdi tries to identify the FT2232D.

     

    Just a hypothesis for now.  If it goes away when the "RasPi Effect" is fixed, that will confirm it.

Children
No Data