Dose anyone know if I can program the Alchitry AU using a raspberry pi?

Total noob. Bought this last year with intent on learning fundamentals on hardware implementation in logic. Having trouble getting started and I'm not sure where things are going wrong.

• Mojo v3 recognized as COM 5 in Windows
  
• Xilinx 14.7 Web Pack
  
• Java SDK 15
  
• Alchtitry 1.2.4
  

in some tutorial I saw a dff declared:

Hello to all,

I wanted to experiment with the V3 mojo with the sdram shield and realized it takes a little too much money and time to receive it.

So I made the sdram shield manually by modifying the original.
As I could not find the same memory chip inserted on the official shield.
 (I turned the house over to find an old pc133 sdram bank and I'm sure there are but I couldn't find the cards  ).

So I unsoldered one from an old hd (K4S641632K-UC60)
 4 x 1,048,576 words by 16 bit -> 8Mbyte if I'm not mistaken (16 bit words are found everywhere)
Organization Row Address Column Address
4Mx16 A0~A11 A0-A7

It is a little different from the original it has 8 extra bidirectional data pins and
two data mask control pins and has one less addressing bit.
but I think it is compatible and now I'm editing the example file to do some tests.

My questions are these:
- there is a possibility of frying  mojo if I am wrong in setting the doors
 bidirectional data of the sdram?

- is it possible to use it in 8 bit format without modifying the example file?

- I have never used sdram and on some schemes they are inserted
 25 or 33 OHm resistors in series usually to the data pins.
 In fact on the HD card are inserted at least the 16r on these pins.
 I believe it is used to eliminate disturbances (stub resistor).
 Do you think they need a test shield? seen that on the original
 there are not?

I powered the card without the mojo and it seems to work, by measuring the voltages on the pins they are floating or at Hz since the chip is not initialized and it absorbs a few mA.

Fabio

I'm planning to order 25 Au/Io pairs for a lab next quarter and just found out 18 are back ordered. 

Does anyone know what the typical lead time is for back orders.  I don't actually need them until February.  Should I be worried?

Good morning,
It is possible to know the saving path of the Alchitry-Labs configuration files under windows 10.
I couldn't find them anywhere.
Under linux it was very simple.

I try to use DDR3 memory on the Au board for my project and it looks like the first read data get from the FSM I got after about 270nS. It related to about 22 cycles  of  ui_clk. Is it normal behave of DDR3 or have something wrong, please? I need accidently access to memory addresses  for reading and writing by CPU without postponing of reading. Write is no critical because FIFO can be use, but read have to be fast (50ns is enough). Thanks for help.

I have setup Alchitry Labs 1.2.1 on my Windows 10 machine.  I have connected Au to the machine and under UBS Controllers in Device Managers, I do see 2 entries - USB Serial Converter A and USB Serial Converter B.  Both of them show the driver being used as FTDI.

Even after this, both Alchitry Labs and Alchitry Loader do not recognize this and the status is always - 'Could not detect an Au!' when I try flashing on to the device.

I did uninstall the devices from Device Manager with the Option for 'Uninstall Drivers' set to on.  But after I disconnect and connect Au to the PC, the default it took was the same FTDI with no change.

Is there anything else I need to do make Alchitry Labs and Loader recognize the Au?

The example of DDR3 interface works on 325MHz. Why is used this speed, please? By the documentation of AS4C128M16D3LB-12 (chip uses in AU) it looks speed could be 400MHz. Thanks a lot.

Good morning,
Sorry for all these replies to posts I made earlier but didn't have write access before.

Let's get to the problem:
In win10 64bit alchitry labs or alchitry loader fail to detect mojo v3:
- or by reporting "Could not detect a Mojo!"
- or reporting a java error I think related to libusb libraries.

Mojo loader works fine however and loads .bin files correctly.

I tried all libusb drivers using zadig and only once the card was identified correctly and I could load the .bin file. (I was no longer able to recreate this situation)
When the PC was restarted, the card was not found again.
The exact same thing happens to me on the laptop always with win10 64bit but with intel architecture.

Mojo loader works fine however and loads .bin files correctly.

Under Linux Mint 2020 the card is detected perfectly and the .bin file loads smoothly and the serial port works too.

Is there a solution I can use to fix the problem?

Thanks