Update 'src/hw/urukul.md'
This commit is contained in:
parent
1a8c037fe7
commit
0fefa82da7
|
@ -57,7 +57,7 @@ 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
|
||||
|
@ -66,10 +66,12 @@ 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).
|
||||
|
||||
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/<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
|
||||
|
|
Loading…
Reference in New Issue