I'm desperately waiting for an HDMI or VGA shield to purchase your new boards. Could you tell me when they will be available?

Your boards have great potential. Your simple design remembers me of the success of Arduino. The only lacking part is that there are few tutorials and there are few shields too. Please provide more.


Thanks

Accessing the Au board from the alchetry-labs IDE works great. 
But, neither the GUI loader, nor the standalone CLI (*) detect the device. The OS recognizes the USB board (see usb-devices).

Any pointers?

Thanks!!

(*) rebuilt version from Github with "$ g++ -o loader src/*.cpp -L ./lib/linux/ -lftd2xx -lpthread -std=c++11"

(10-25-2019, 03:49 AM)oter Wrote: Accessing the Au board from the alchetry-labs IDE works great. 
But, neither the GUI loader, nor the standalone CLI (*) detect the device. The OS recognizes the USB board (see usb-devices).

Any pointers?

Thanks!!

(*) rebuilt version from Github with "$ g++ -o loader src/*.cpp -L ./lib/linux/ -lftd2xx -lpthread -std=c++11"

Code:

$ loader -l
No devices found!
No devices found!
Couldn't find device!

# plug in

$ loader -l
Devices: 
  0: Unknown
  1: Unknown
Couldn't find device!

# OS sees device 
$ usb-devices 
...
T:  Bus=03 Lev=02 Prnt=05 Port=00 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0403 ProdID=6010 Rev=07.00
S:  Manufacturer=Alchitry
S:  Product=Alchitry Au
S:  SerialNumber=FT3KRFFN
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio

# rule is there
$ cat /etc/udev/rules.d/99-alchitry.rules 
SUBSYSTEM!="usb|usb_device", GOTO="ft2232_rules_end"
ACTION!="add", GOTO="ft2232_rules_end"

ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0666", GROUP="dialout"

LABEL="ft2232_rules_end"

# right group
$ groups `whoami`
... dialout ...

Hi,

I have a mojo v2, and a little while ago I acquired the official HDMI hat with built-in SDRAM. I'd been playing with the HDMI output quite happily, but recently tried to use the SDRAM and the example configurations don't seem to work.

The SDRAM demo just instantly lights up the LEDs to signal errors, and my custom project to read/write to the SDRAM based on UART communication always returns back the last thing I wrote to it, as if the address lines were ignored.

Are there any known issues with the SDRAM hat and the v2 of the mojo board? I thought the differences between v2 and v3 were purely around securing the USB connector better?

Does anyone have any recommendations for trying to diagnose if there's a problem with the SDRAM?

Thanks.

For better or worse I am determined to learn to use all of the Vivado tool suite. To that end I have created a set of board files that will add the Au board to Vivado's set of available boards, so that I can use the block design tools. 

To use: unzip the contents of the attached zip into: C:\Xilinx\Vivado\2019.1\data\boards\board_files\alchitry-au\1.0  (for windows users)  and restart the Vivado gui. 

Currently this includes components for: clock, reset, leds, uart, spi flash, DDR3 SDRAM, and GPIO Banks A-D.

GPIOs are implemented as interfaces on the FPGA. This looks like Vivado will treat this like a bus. I am undecided if I will leave it like this or re-implement as connectors. 

At this point I can only confirm that Vivado will create a project from this and allow the creation of a block design with the aforementioned components. I have not yet tested any projects using this set of files yet. 

While reasonable care was taken to get the pin mappings right, this was done late at night so YMMV. If you find an error, please let me know.

This was heavily modeled on (appropriated from) the Arty A7 board files.

Also attached is the spreadsheet I used to to generate the pin mapping entries for the pin file and the board file along with the Xilinx pinout. Hopefully I will have a master xdc file generated tomorrow. 

Suggestions are welcome.

Attached Files

  xc7a35tftg256pkg.xlsx (Size: 37.49 KB / Downloads: 4)
  Au_Vivado_Board_Files.zip (Size: 8.29 KB / Downloads: 4)

Greetings,

I have the transpiled Verilog source of the Lucid Counter component, but the Verilog is using constant values instead of the parameters. Does anyone know what the replacements for the parameters (SIZE, DIV, TOP, UP) would be in the following Verilog source? The biggest confusion I'm having is the use of hex 0x00, because two parameters use that value (DIV and TOP).

Hello all,
I'm wondering if there is some product out there that can connect one of the data banks to a protoboard. Honestly, I'm surprised this isn't offered as a basic product given the likelihood that one will connect to external hardware. What I'm hoping to find is something like this one that is available for the Raspberry Pi GPIO bank:
https://www.adafruit.com/product/2028

Thanks!

Hello, newbie here.
Since I have bought the Alchitry, it would be better that I ask here.
I know this is a stupid question but is it possible to use is as FPGA and how fast?
Can it possibly interface to https://sigrok.org/ ?

I would like to suggest to add "Projects" in the forum to showcase their projects their difficulties, etc.

I made a Discord server for Alchitry Enthusiasts.
Join us at: https://discord.gg/qbmZvP

Anyone get a "Couldn't find device!" error when trying to flash a program to one of the Alchitry boards (in my case a Cu)?
Sometimes I get "Couldn't find device!" and sometimes I get:

org.usb4java.LibUsbException: USB error 5: LibUsb.open() failed: Entity not found
at com.alchitry.labs.hardware.usb.UsbDevice.usbFindAll(UsbDevice.java:218)
at com.alchitry.labs.hardware.usb.UsbUtil.getDevice(UsbUtil.java:46)
at com.alchitry.labs.hardware.usb.UsbUtil.openFtdiDevice(UsbUtil.java:91)
at com.alchitry.labs.hardware.loaders.CuLoader.program(CuLoader.java:45)
at com.alchitry.labs.hardware.loaders.ProjectLoader.load(ProjectLoader.java:48)
at com.alchitry.labs.project.Project$8.run(Project.java:1539)


I have tried two different USB-C cables, both confirmed to be data cables and every single USB port and hub on my PC.
Thanks.

Starting iceCube2...
 
C:\Program Files\Alchitry\Alchitry Labs>SET TCL_LIBRARY=C:\lscc\iCEcube2.2017.08\Aldec\Active-HDL\tcl\lib\tcl
 
C:\Program Files\Alchitry\Alchitry Labs>SET LM_LICENSE_FILE=C:\lscc\iCEcube2.2017.08\license\license.dat
 
C:\Program Files\Alchitry\Alchitry Labs>SET SYNPLIFY_PATH=C:\lscc\iCEcube2.2017.08\synpbase
 
C:\Program Files\Alchitry\Alchitry Labs>SET SBT_DIR=C:\lscc\iCEcube2.2017.08\sbt_backend
 
C:\Program Files\Alchitry\Alchitry Labs>C:\lscc\iCEcube2.2017.08\sbt_backend\bin\win32\opt\synpwrap\synpwrap.exe -prj "C:\Users\acer\Desktop\blink2\blink2\work\alchitry_syn.prj" -log "C:\Users\acer\Desktop\blink2\blink2\work\icelog.log"
Copyright © 1992-2014 Lattice Semiconductor Corporation. All rights reserved.
Error of dumping file C:\Users\acer\Desktop\blink2\blink2\work\icelog.log, 'stdout.log' is instead.
Synthesis exit by 2.
 
C:\Program Files\Alchitry\Alchitry Labs>C:\lscc\iCEcube2.2017.08\Aldec\Active-HDL\BIN\tclsh85.exe "C:\Users\acer\Desktop\blink2\blink2\work\iCEcube2_flow.tcl"
Error : can not print out log file stdout.log
 
Run edifparser ...
{C:\lscc\iCEcube2.2017.08\sbt_backend/bin/win32/opt/edifparser} {C:\lscc\iCEcube2.2017.08\sbt_backend/devices\ICE40P08.dev} {C:/Users/acer/Desktop/blink2/blink2/work/alchitry_imp/cu_top_0.edf} {C:/Users/acer/Desktop/blink2/blink2/work/alchitry_imp/sbt/netlist}  -p"CB132"  {-y} {"C:/Users/acer/Desktop/blink2/blink2/work/constraint/merged_constraint.pcf "} --devicename  iCE40HX8K
Lattice Semiconductor Corporation  Edif Parser
Release:        2017.08.27940
Build Date:     Sep 11 2017 16:51:25
 
Parsing edif file: C:/Users/acer/Desktop/blink2/blink2/work/alchitry_imp/cu_top_0.edf...
Error: ParseEDIF C:/Users/acer/Desktop/blink2/blink2/work/alchitry_imp/cu_top_0.edf failed
Kparser Unable to open C:/Users/acer/Desktop/blink2/blink2/work/alchitry_imp/cu_top_0.edf
child process exited abnormally
edifparser failed:CHILDSTATUS 9412 1
 
Bin file (C:\Users\acer\Desktop\blink2\blink2\work\alchitry_imp\sbt\outputs\bitmap\cu_top_0_bitmap.bin) could not be found! The build probably failed.