Add two common fails on Urukul, and one hint to Fastino
Signed-off-by: Egor Savkin <es@m-labs.hk>
This commit is contained in:
parent
bc20eb0de7
commit
767471689e
|
@ -49,4 +49,38 @@ Press ENTER when done.
|
||||||
1. Setup oscilloscope's impedance at 50 ohm
|
1. Setup oscilloscope's impedance at 50 ohm
|
||||||
2. Touch each connector with oscilloscope, setup time- and voltage- scale and trigger, so that you can see sine waves
|
2. Touch each connector with oscilloscope, setup time- and voltage- scale and trigger, so that you can see sine waves
|
||||||
3. Measure frequencies and amplitudes on each connector, check with `artiq_sinara_test`'s respective values
|
3. Measure frequencies and amplitudes on each connector, check with `artiq_sinara_test`'s respective values
|
||||||
4. When done, proceed with `artiq_sinara_test` and check LEDs are lighting up one after another
|
4. When done, proceed with `artiq_sinara_test` and check LEDs are lighting up one after another
|
||||||
|
|
||||||
|
|
||||||
|
## Common problems
|
||||||
|
|
||||||
|
### Urukul AD9912 product id mismatch
|
||||||
|
|
||||||
|
```pycon
|
||||||
|
ValueError: Urukul AD9912 product id mismatch
|
||||||
|
```
|
||||||
|
|
||||||
|
Some Urukuls may fail with this error during testing, usually meaning that the Urukul has not been flashed with the
|
||||||
|
firmware, especially if the ID is `65535` (you will need to edit the code to check this).
|
||||||
|
|
||||||
|
You can flash the firmware yourself with a JTAG adapter:
|
||||||
|
|
||||||
|
1. Download the latest binary release from [quartiq/urukul](https://github.com/quartiq/urukul) and extract the `urukul.jed` file.
|
||||||
|
2. Connect the Urukul with the JTAG adapter to the PC and connect its EEM0 to any available Kasli/Kasli-SoC (do not hot-plug), then turn on the Kasli/Kasli-SoC.
|
||||||
|
3. Run `nix-shell -p xc3sprog`.
|
||||||
|
4. Run `xc3sprog -c jtaghs2 urukul.jed -m /opt/Xilinx/Vivado/<available version>/data/xicom/cable_data/digilent/lnx64/xbr/`.
|
||||||
|
5. If the last command outputs Verify: Success, then your Urukul is ready. It can also output the message
|
||||||
|
```shell
|
||||||
|
*** buffer overflow detected ***: terminated
|
||||||
|
Aborted (core dumped)
|
||||||
|
```
|
||||||
|
, which is okay if `Verify: Success` was also emitted.
|
||||||
|
|
||||||
|
### no valid window/delay
|
||||||
|
|
||||||
|
```pycon
|
||||||
|
ValueError: no valid window/delay
|
||||||
|
```
|
||||||
|
|
||||||
|
Check with the customer to see if synchronization is necessary, and disable it if it is not.
|
||||||
|
In any case, simply restart the test.
|
|
@ -20,6 +20,9 @@
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Fastino uses two physical EEM channels, but in the JSON file there should be only one channel specified,
|
||||||
|
and it should be the one connected to Fastino's EEM0.
|
||||||
|
|
||||||
## Setup
|
## Setup
|
||||||
|
|
||||||
Connect the BNC/SMA-IDC adapters to the Zotino/Fastino with 26-pin cable if needed by customer. Be aware of the ports order -
|
Connect the BNC/SMA-IDC adapters to the Zotino/Fastino with 26-pin cable if needed by customer. Be aware of the ports order -
|
||||||
|
|
Loading…
Reference in New Issue