Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 609
» Latest member: haileyhazeel
» Forum threads: 189
» Forum posts: 546

Full Statistics

Online Users
There are currently 13 online users.
» 0 Member(s) | 12 Guest(s)

Latest Threads
Could not detect an Au!
Forum: General Questions
Last Post: satheesh_s
07-23-2021, 01:51 AM
» Replies: 6
» Views: 2,074
LEDs on Io Breakout Board...
Forum: Tips and Tricks
Last Post: alchitry
07-22-2021, 02:35 PM
» Replies: 2
» Views: 155
Alchitry labs crashes Moj...
Forum: General Questions
Last Post: alchitry
07-22-2021, 02:33 PM
» Replies: 1
» Views: 546
DDR3 speed in example
Forum: General Questions
Last Post: alchitry
07-22-2021, 02:31 PM
» Replies: 3
» Views: 1,108
Question Shield Mojo to A...
Forum: General Questions
Last Post: alchitry
07-22-2021, 02:29 PM
» Replies: 5
» Views: 1,586
DDR3 speed of READ comman...
Forum: General Questions
Last Post: alchitry
07-22-2021, 02:27 PM
» Replies: 1
» Views: 570
Alchitry Loader - Could n...
Forum: General Questions
Last Post: alchitry
07-22-2021, 02:19 PM
» Replies: 2
» Views: 121
Constraints files
Forum: General Questions
Last Post: TechPaula
07-18-2021, 01:01 PM
» Replies: 2
» Views: 863
Au plus and DDR3 Tutorial
Forum: General Questions
Last Post: howdyrichard
07-07-2021, 05:55 PM
» Replies: 0
» Views: 76
Forum: General Questions
Last Post: D22
07-04-2021, 04:57 PM
» Replies: 0
» Views: 59

  Alchitry Cu tutorial not working
Posted by: ekellmyer - 04-30-2021, 09:25 PM - Forum: General Questions - Replies (1)

Absolute beginner to FPGA programming here. Trying to do the tutorial for my first FPGA project for the Cu, but my project won't build. I keep getting the message "Bin file (C:\Users\User\Documents\Alchitry\LED\work\alchitry_imp\sbt\outputs\bitmap\cu_top_0_bitmap.bin) could not be found! The build probably failed."
I'm on Labs version 1.2.6 and iceCube2 version 2017.1 on Windows.

Any help would be greatly appreciated.

  BR shield short?
Posted by: usherman20 - 04-30-2021, 06:27 AM - Forum: General Questions - Replies (1)

Hi all,

I'm currently playing with my new CU and BR boards. I am running into a strange issue though: I can program the bare CU board fine, but cannot upload when the BR board is mounted. I uploaded the counter example and the builtin leds blink fine. I also have the IO shield. The IO shield example program works as expected, and I can program with the IO shield mounted. Trying to program the CU with the bare BR board fails with this error:

Extended device string lenght is 0xff. This is likely an error. Ignoring...
com.alchitry.labs.hardware.usb.ftdi.Mpsse$MpsseException: Flash ID was 0xFFFFFFFF expected 0xEF401600
    at com.alchitry.labs.hardware.usb.ftdi.LatticeSpi.flashReadId(LatticeSpi.java:150)
    at com.alchitry.labs.hardware.usb.ftdi.LatticeSpi.writeBin(LatticeSpi.java:284)
    at com.alchitry.labs.hardware.loaders.CuLoader.program(CuLoader.java:54)
    at com.alchitry.labs.hardware.loaders.ProjectLoader.load(ProjectLoader.java:61)
    at com.alchitry.labs.project.Project$load$1.invokeSuspend(Project.kt:1297)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
Both pins D36 and D39 (config reset, reset) are high. One further complication - if I mount the BR board on the CU while the CU counter led blink program is running, it continues to run fine (and probing the led pads on the BR match the lights fine). However, if I remove power and plug it back in while the BR is mounted, the loaded program _will not run_. Instead, I only see the on board leds shining very dimly. I don't feel any obvious hot spots in the board to indicate shorts, and I've probed 3.3V, 5V, and Gnd for shorts, and come up with nothing. Any other ideas??
Thanks, Jarrett

  routing DDR3 fails with invalid clock parameters
Posted by: agemoz - 04-20-2021, 07:37 PM - Forum: General Questions - Replies (2)

Has anyone gotten the DDR3 module to work with the alchrity AU+ board?  I followed the tutorial at


and also just ran a pure verilog version on Vivado, neither one of which appears to work. Lot's of other stuff is working on this board, but I've had no luck with the DDR3.

I have the xilinx DDR3 module instantiated, along with a MMCM clock synthesis generating 100Mhz input, 100Mhz to sys_clk_i and 200Mhz to clk_ref_i.  Vivado synthesizes without error, but routing DRC complains about this:

[DRC PDRC-34] MMCM_adv_ClkFrequency_div_no_dclk: The computed value 200.000 MHz (CLKIN1_PERIOD, net pll_clk3) for the VCO operating frequency of the MMCME2_ADV site MMCME2_ADV_X0Y2 (cell i_mig_7series_0/u_mig_7series_0_mig/u_ddr3_infrastructure/gen_mmcm.mmcm_i) falls outside the operating range of the MMCM VCO frequency for this device (600.000 - 1200.000 MHz). The computed value is (CLKFBOUT_MULT_F * 1000 / (CLKINx_PERIOD * DIVCLK_DIVIDE)). Please run update_timing to update the MMCM settings. If that does not work, adjust either the input period CLKINx_PERIOD (40.000000), multiplication factor CLKFBOUT_MULT_F (8.000000) or the division factor DIVCLK_DIVIDE (1), in order to achieve a VCO frequency within the rated operating range for this device.

Looks like the internals of the Xilinx DDR3 module expects something different for the sys_clk_i and clk_ref_i frequencies.  It suggests updating timing (Vivado wont allow me to do this), and setting the CLKIN1_PERIOD and other parameters manually is grayed out. 

Any suggestions? I tried to do an example with Lucid following the tutorial, but that failed as well--it is getting confused what the top level file is--never finds it--and never builds.

Here's the top level source instantiation

mig_7series_0 i_mig_7series_0
   .ddr3_dq             (ddr3_dq),
   .ddr3_dqs_n          (ddr3_dqs_n),
   .ddr3_dqs_p          (ddr3_dqs_p),
   .ddr3_addr           (ddr3_addr),
   .ddr3_ba             (ddr3_ba),
   .ddr3_ras_n          (ddr3_ras_n),
   .ddr3_cas_n          (ddr3_cas_n),
   .ddr3_we_n           (ddr3_we_n),
   .ddr3_reset_n        (ddr3_reset_n),
   .ddr3_ck_p           (ddr3_ck_p),
   .ddr3_ck_n           (ddr3_ck_n),
   .ddr3_cke            (ddr3_cke),
   .ddr3_cs_n           (ddr3_cs_n),
   .ddr3_dm             (ddr3_dm),
   .ddr3_odt            (ddr3_odt),

   .sys_clk_i           (sysclk),
   .clk_ref_i           (sysclk_2x),
   .app_addr            (dev_ddr3_addr),
   .app_cmd             ({2'h0,~dev_ddr3_wr}),
   .app_en              (dev_ddr3_en),
   .app_wdf_data        (dev_ddr3_wdata),
   .app_wdf_end         (1),
   .app_wdf_mask        (0),
   .app_wdf_wren        (dev_ddr3_wr),
   .app_rd_data         (dev_ddr3_rdata),
   .app_rd_data_end     (1),
   .app_rd_data_valid   (dev_ddr3_rd_data_valid),
   .app_rdy             (dev_ddr3_rdy),
   .app_wdf_rdy         (dev_ddr3_wdf_rdy),
   .app_sr_req          (0),
   .app_ref_req         (0),
   .app_zq_req          (0),
   .app_sr_active       (dev_ddr3_sr_active),
   .app_ref_ack         (dev_ddr3_ref_ack),
   .app_zq_ack          (dev_ddr3_zq_ack),
   .ui_clk              (clk_ddr3_ui),
   .ui_clk_sync_rst     (ui_clk_sync_rst),
   .init_calib_complete (init_calib_complete),
   .device_temp         (device_temp),
   .sys_rst             (nrst)

clk_wiz_0 i_clk_wiz_0
   .reset             (~nrst),
   .clk_in1           (clk),
   .clk_out1          (sysclk),
   .clk_out2          (sysclk_2x),
   .locked            (locked)

  Alchitry a dying project?
Posted by: wdautrem - 04-19-2021, 06:35 PM - Forum: General Questions - Replies (1)

I'm looking to get into FPGA development and was interested in the Alchitry dev board.  Unfortunately, it looks like this product is running out of steam.  Nearly all hardware is out of stock or backordered.  No blog posts for years.  Only a hand full of forum posts this year.  No new element boards being released (HDMI board).  Am I seeing this correctly, or is there another reason for the lack of activity?

  Using Alchitry Labs with Au+
Posted by: howdyrichard - 04-18-2021, 01:11 PM - Forum: General Questions - Replies (1)

Alchitry Labs with Au+, does it work together???

  Compatible boards
Posted by: tagsense - 04-09-2021, 03:19 AM - Forum: General Questions - Replies (1)


I see that none of the development boards - Alchitry CU/AU and Mojo - are available for sale.
Are there other compatible boards one can use for learning? kindly let me know. thank you!

the reason i am asking is I just got the FPGA book (Learning FPGAs: Digital Design for Beginners with Mojo and Lucid HDL).
the book uses Mojo as the FPGA development board.

  Absolutely no way to flash CU
Posted by: DMoore127 - 04-09-2021, 03:02 AM - Forum: General Questions - Replies (1)

I've been attempting to get a .bin file onto my Cu for some time now, to no avail. I'm using IceStorm for synthesis (with success), but I can't for the life of me get that bin file onto my board. Alchitry Loader immediately crashes (hangs on starting) when attempting to flash to a Cu on my instance of Ubuntu and both of my instances of Windows 10. The command line utility for MacOS can find my Cu with -l on device 0, but states it can't find a device. When I use Alchitry Labs with Ubuntu, I'm able to synthesize and construct a net list/bin file perfectly with IceStorm, but it insists that it cannot find a Cu, even though I can confirm that I see the device on ttyUSB0 and ttyUSB1.

This is starting to get quite frustrating for something that is marketed as so simple. Is there something I'm missing or something that I need to do?

For context, I'm running MacOS with Parallels for Ubuntu and one instance of Windows 10, with an instance of Windows 10 running on a desktop; all 4 to no avail.

  Alchitry Labs not playing nicely with Vivado
Posted by: Tyrving - 04-03-2021, 11:11 PM - Forum: General Questions - Replies (6)

Hello! Loving my AU, but I've been having some issues. When I first tried using Alchitry Labs, it wouldn't get past "Starting Vivado..."
I decided to just learn verilog, and use plain ol Vivado with the loader, which works fine. However, now that I find myself wanting to do more with complex AU features, like the IO module 7-segs and RAM. I dont want to design my own memory controller, and verilog has been pretty confusing - two problems I can solve via Alchitry Labs with lucid. I ported the I/O files into Vivado from Labs for the buttons/DIP row/LED row, which has been enough for my projects until now. I did some investigation through task manager, and it seems that Labs will spawn a Vivado process, which will start eating up one of my processor threads, until after a few minutes, then it will disappear. Upon cancelling the build, Labs reports there is no .bin file found in the destination directory - '\working\dir\.runs\impl_1\au_top_0.bin) could not be found! The build probably failed.' I am using Labs 1.2.6, and Vivado 2020.2. I have validated my Vivado files through help -> add design tools or devices. I have been troubleshooting with the led to button sample project. Running Windows 10.

Any help would be appreciated.

P.S. I found alchity2.com, and I gotta complement the UI design, except for the miniscule drop-down menus.

  Issue loading Vivado bins onto AU+
Posted by: Electrick - 03-31-2021, 08:28 PM - Forum: General Questions - Replies (1)

Hi all,

I just got my AU+ board in a couple of days ago, and as a career EE I was hoping to do some more advanced development with it. After dinking around with my setup for a few hours I finally got the first Lucid tutorial working, flashed to the AU+ and everything. However, when I finished up  the Verilog tutorial and loaded the bin with the alchitry-loader, the LEDs wouldn't light up at all. Also, nothing seems to happen when I press the rst button.

I also notice that when the alchitry-loader is finished flashing the board, the "DONE" LED doesn't light up like it did with the Lucid tutorial.

I'm operating on a 2015 Macbook running the latest Ubuntu 20.10 and openjdk 11.0.10

Any help would be much appreciated!

Exclamation Trouble programming Mojo v3 with Alchitry Labs (& Loader)
Posted by: gr3mlin - 03-28-2021, 01:06 PM - Forum: General Questions - Replies (5)

Good morning. I've dusted off a genuine Mojo v3 I purchased a while back and setoff determined to burn through tutorials this weekend. I've come hat in hand for help as I've exhausted every avenue I know of to troubleshoot programming the board.

My setup:
Windows 10 Pro version 2004 (latest updates) in a Parallels VM running on MacOS Big Sur 11.2.3
Parallels is set to permanently assign the Mojo device within USB settings to my Windows VM.
Windows device manager sees "Mojo V3" under Ports (COM & LPT). It's assigned to COM5 or COM3 depending on the reboot attempt.
Running Alchitry Labs v1.2.5 on the Windows VM. Installed both ways, the .msi and the zip file. Found that the zip file only contained the dpinst-amd64.exe which I ran, confirmed that the driver is installed.
Installed ISE and licensed everything, can build tutorials without any problems.
I'm running JRE 8u281 on the Windows VM.
I also attempted all steps with JDK 16 on the Windows VM before uninstalling that and just trying the JRE.
CMD java -version returns java version "1.8.0_281"

1) When running alchitry-loader, wether I select Erase or Program, the problem completely hangs unresponsive saying "Connecting". I can't grab the window and move it, close it, etc.
2) When running alchitry, following a successful build, an attempt to program lands me at "Connecting" in the status window.
3) Alchitry crashes when I attempt to open the Serial Port or attempt to Register Device.

I read on the forums and github that 1.2.5 was supposed to resolve the Serial Port crashing issue, and question if I have some java issue. I havn't gone so far as to attempt to edit code and debug with print statements. Hopefully someone can set me straight before going scorched earth.

Appreciate any assistance! I'm excited to get my Mojo working.