From 0fefa82da765c69a3167de1ce88a62e28c7791d9 Mon Sep 17 00:00:00 2001 From: mwojcik Date: Thu, 25 May 2023 15:56:03 +0800 Subject: [PATCH] Update 'src/hw/urukul.md' --- src/hw/urukul.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/hw/urukul.md b/src/hw/urukul.md index 6680a69..c77ed4b 100644 --- a/src/hw/urukul.md +++ b/src/hw/urukul.md @@ -57,19 +57,21 @@ Press ENTER when done. ## Common problems -### Urukul AD9912 product id mismatch +### Urukul AD9912 product id mismatch or missing LEDs ```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). +firmware, especially if the ID is `65535` (you will need to edit the code to check this). + +Another common symptom of no firmware is that no LEDs are lit up, besides Power Good - whereas if the firmware has been flashed, the RF channels will be lit red. 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. +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 power on the Kasli/Kasli-SoC. 3. Run `nix-shell -p xc3sprog`. 4. Run `xc3sprog -c jtaghs2 urukul.jed -m /opt/Xilinx/Vivado//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