I made the shield to test the sdram, I used the same components used to build the original.

Then I ran the SDram test in Lucid and I continue to detect output errors shown by the configuration of the LEDs on the board: LEDs 6: 0 on and 7 flashing.

So I tried to use the example in verilog under ise project navigator and with the latter the test works, 7 LEDs off and one flashing.

There must be some problem with the lucid project but I couldn't identify it.

Can someone try to do the sdram test on mojo V3 with Lucid
to identify the problem?

Thank you

Hello, is it possible to make the 7 segment display on the IO element shield display letters? Obviously not all letters are possible by the 7 segment design, but those that are, is that possible?

If so, how would I go about learning to do this? It would be especially useful for one of my projects.

Thank you

It would appear the latest version (December 2020) of the Lattice iCEcube2 does not work with the Alchitry Labs application.    Lattice removed the Active-HDL component, and I perhaps a few other changes.

The new version:  
https://www.latticesemi.com/Products/Des...S/iCEcube2

You can download the previous version (2017) from the archive section:

https://www.latticesemi.com/support/softwarearchive

I'm guessing this is a known problem, but it isn't mentioned on the install page.

"iCEcube2 Version 2020.12

• Replaced Aldec™ Active-HDL™ with Mentor® ModelSim® Lattice FPGA Edition. Active-HDL Lattice Edition is still supported but not included."
  

I'm using these boards in a class.  Students either run the software on their own Windows 10 machines, on W10 VMs on their Macs, or use remote computing and a local downloader.

For one of the students with his own Windows machine, the download step  hangs.  It doesn't say "No device found".  The log window is just blank.  If he tries the standalone downloader, it just permanently hangs.

Looking at the device manager, it sees two devices called "Alchitry-Au", while my working system sees the board as an unnamed "USB Port".

We tried to uninstall or disable those devices, but it still doesn't work.

Any advice would be appreciated.

What is the bootloader used on the Mojo v3's Atmega32u4? Is it the standalone arduino bootloader? is it opensource or hosted somewhere?

Thank you.

I wanted to ask for information:
Can the I / O pins used in the SDRAM shield for the mojo be changed?
I wanted to manage a 16-bit module and a different configuration of the mojo pins is needed to achieve a good pcb design.

I checked the spartan-6 lx9 datasheet and I don't think there are any problems with the pins I'm using.

This is the pins list:
DQO -> P94
DQ1 -> P95
DQ2 -> P97
DQ3 -> P98
DQ4 -> P99
DQ5 -> P100
DQ6 -> P101
DQ7 -> P102
DQ8 -> P7
DQ9 -> P8
DQ10 -> P9
DQ11 -> P10
DQ12 -> P11
DQ13 -> P12
DQ14 -> P14
DQ15 -> P15

A0 -> P118
A1 -> P119
A2 -> P120
A3 -> P121
A4 -> P138
A5 -> P139
A6 -> P140
A7 -> P141
A8 -> P142
A9 -> P143
A10 -> P117
A11 -> P144
A12 -> P1

DQML -> 104
WE -> 105
CAS -> 111
RAS -> 112
CS -> 114
BA0 -> 115
BA1 -> 116

CLK -> P5
DQMH -> P6
CKE -> P2

schematic:
https://ibb.co/MPYdmnH

thank you

Fabio

My backordered AU starter kit just arrived, and when I plug it in, all seems well, and the LEDs do what I expect, after waiting a sec from when I plug it in. I noticed the FPGA getting toasty, although nothing painful to touch, very quickly, and am wondering if this is expected.

Assorted questions:
The default program works fine, doing the nifty (ripple? Not sure what to call this) animation. Pressing reset will make the second LED go solid for about 1/2 second, then it will begin alternating even/odd LEDs as I assume is intended. I am guessing this is from the necessary reprogramming of the (iirc volitile sram?) LUTs from the onboard flash, but I don't know a whole lot about this.
How much current can the BR drive? I don't expect it to power a relay or anything, but this would be useful to know. Forgive me if this is in the schematic or somewhere else I should have checked before posting.
Out of curiosity, what will happen to the pick and place/other tools you purchased to manufacture the boards now that Sparkfun is doing that?
Lastly, the 7-segs on the IO element have a faint glow when board is plugged in. Normal? Product of my EMI-ridden workspace?
Also, could this EMI cause any other issues potential issues using long wires and such from the BR element later on? I'm not exaggerating about the amount of EMI, it has begun to cause issues with my USB keyboard, camera, and mouse.  I've got some ferrite chokes on the way, but patience is a virtue I do not possess.

Have a wonderful day, and a preemptive thank you!

Hi I am looking for the HDMI Shield Eagle files which I know are no longer being made but many of the other shields have the eagle files available I was hping maybe they were available as well but there is only a schematic.

https://alchitry.com/products/hdmi-shield

My plan is to replace the SRAM chip on this shield to a 16bit one so it would be easier to get higher resolutions with the extra SRAM.

Thank you.

I'm starting graduate school soon, and my first class relates to learning/designing parallel computing architectures. The course is project-based, where I am free to select a programming language and platform of our choosing. I have a Mojo V3, SDRAM shield, and clock/viz shield that I purchased from (then) EmbeddedMicro a long time ago but sadly never got put to good use. I'm considering using the Mojo V3 for my coursework, but I don't know how to properly assess whether building on it or a newer platform would be the better idea.

I wasn't able to get any specific recommendations from faculty, and the university labs don't appear to have open access to FPGA development hardware at this time. I have a little experience working with Verilog, but not enough where I can claim competency on any specific platform. What would be an effective way to begin determining what FPGA architectures and/or development kits I should consider?

Hi.

When I click debug > choose the signals I want in the wave capture, I get the following error: