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

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

johnbeetem — Sun, 08 Mar 2015 19:00:28 GMT

The Papilio One works great with ODROID-C1 now. To fix the "Raspberry Pi Effect" I hooked up a USB 1.1 hub to ODROID-C1's OTG port. OTG uses a separate controller from the four USB A ports, so by keeping the high-speed USB 2.0 devices on the A ports and the low/full-speed USB 1.1 devices on the OTG port, there are no split transactions and thus no missing or repeated characters.

Connecting the Papilio One to the USB 1.1 hub fixed the slow USB transfer. I think it was slow because acknowledge packets were getting lost so the USB 2.0 controller had to recover and retransmit. By going through the USB 1.1 hub and OTG there are no packets lost and I can download the Papilio One 250K FPGA in a couple tenths of seconds just like on my x86 PC.

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

johnbeetem — Sat, 14 Feb 2015 01:28:39 GMT

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.

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

johnbeetem — Fri, 13 Feb 2015 04:30:25 GMT

XXICC rev 0.0n mostly runs on the ODROID-C1 ODroid - Oh Boy! using Hardkernel's Ubuntu v1.3 software. Here are some issues and hints. [updated item 5]

1. X11 windows don't render properly with BPP (bits per pixel) set to 32 in boot.ini. They work for me with 24 BPP.

2. I did need to get libxft-dev to compile xxicc. This is described in Installing and Running XXICC rev 0.0n, section 1.1.

3. Windows resize slowly because XXICC redraws many times as you drag the mouse instead of waiting for a pause. I'll try to fix this. Also, it's tricky to grab the lower-right corner of the window, at least with the metacity window manager.

4. To compile Flavia I needed to add a link for libftdi.so. This is described in Installing and Running XXICC rev 0.0n, section 5.2.

5. update: Flavia also works when programming over JTAG using an FTDI device. You must set FTDI permissions as described in Installing and Running section 5.3. I have tried both Papilio One 250K and LOGI-Pi (programmed over JTAG, not over the GPIO connector). LOGI-Pi compiles and downloads very quickly -- about a second for Bcount4LP. Papilio One programs very slowly. I think this is because it's downloading over full-speed USB, which may not be optimized properly on ODROID-C1. It's likely losing USB packets due to the "Raspberry Pi Effect". I program LOGI-Pi using an Adafruit FT232H breakout board, which has high-speed USB.

6. Other than the above issues, XXICC seems to work fine on ODROID-C1 [View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-c0d5bcd4-e59b-4968-a8c3-a15bf400ed1c/contentimage_5F00_1.png:16:16]

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

DAB — Tue, 20 Jan 2015 20:03:29 GMT

Nice update John.

Do you have an end project that you intend to implement with the board or are you just looking at options to make it useful?

DAB