I was duplicating the tutorial on how to use the DDR memory on the Au, but I get a Critical Warning upon building. 
The design runs ok, but the "Critical" part of the warning worries me a bit.

I think the problems start right at the start when I add the Memory Controller. It complains about not finding an .xci file:


Compare this to exactly the same stage in the tutorial:


It makes the same complaint after I add the clock wizard core (in fact it seems to say this after generating any cores).
When I add in all the code (exactly duplicating the tutorial), it successfully builds, but gives me the critical warning:

Attached Files

  DDR tutorial Critical Warning.txt (Size: 84.02 KB / Downloads: 1)

Hi,
what is a progress of these modules production, please?

Attached Files

  EBOm1leXYAAq4Fy.jpg (Size: 497.25 KB / Downloads: 7)

So I was using Alchitry Loader fine in the beginning, both interface 0 and 1 were FTDI driver.

Then I used zadig to change Interface 0 to WinUSB, and I was able to use Alchitry Labs to interact with the board.

But then I tried to switch back to Alchitry Loader again, it seems I just can't get it working whatsoever. I tried to delete the driver from device manager, tried all kinds of drivers in Zadig, I just couldn't reset the Driver to the propriatary FTDI driver and couldn't program the board with Alchitry Loader, it always says Can't Find Device.

Any suggestions? Thanks

I am trying to see if anyone has used the PING))) Ultrasonic Distance Sensor before.

It has some interesting timing to be able to use it, as well as it's triggered as well as the return echo come back on the same pin.

PING))) Ultrasonic Distance Sensor I have a lot of these to drive and a AVR just bogs down the more you put on.

From the website:

Quote:Interfacing to a microcontroller is a snap. A single I/O pin is used to trigger an ultrasonic burst (well above human hearing) and then "listen" for the echo return pulse. The sensor measures the time required for the echo return, and returns this value to the microcontroller as a variable-width pulse via the same I/O pin.

Hi,

as I am now working with connecting the Alchitry Cu with my application I had a closer look on the FTDI-Chip. It is possible to do multiple modes as UART, SPI and parallel with it. On the schematic only two pins of the port B for communication with the FPGA are connected (usable for UART). It would be a very nice feature if the user can optionally connect the other pins to the FPGA (for example with jumpers or solder pads for 0 Ohm resistors). This would lead to a gain of data rate (if using parallel mode) if someone is trying to do something with high data throughput. Additionally communicating with SPI can be more simple to implement for beginners and makes it easier to migrate on a micro-controller application (relevant for hardware accelerators).

What do you think about it?

- RRC

Hi,

does anyone know a good VHDL to Verilog converter?

I am using the Alchitry Cu with icestorm/nextpnr. And as yosys only works with Verilog I can not apply my VHDL knowledge.

I currently write stuff in Verilog but it is not my language of choice

- RRC

Does anyone know if you can see and/or work with the Verilog code that is created from using Lucid and Alchitry Labs ?

I would like to see my code and be able to use the schematics that Vivado makes.

Thanks,
JT

Found a some good starter information..

Notes on setting up and using Alchitry FPGA boards

I'm trying to use alchitry-loader.exe or loader.exe so I can do my projects in Vivado and it cannot locate the device. This is what my command line looks like:

C:\Program Files (x86)\Alchitry\Alchitry Loader\tools>loader -l

No devices found!
 
I am, however, able to write in Alchitry Labs, so I know the drivers are working. I also downloaded the Windows Drivers in this tutorial: https://alchitry.com/pages/alchitry-loader. I have confirmed that WinUSB is installed for Alchitry AU Interface 0 and 1. 




Any help would be greatly appreciated!

The mic array seems like a pretty cool project.  Are there any plans to make the shield available?