Specifications:
Vivado 2022.1
KV260 with petalinux Ubunutu 22.04 image on SD card from here: Step 1: Set up the SD Card Image — Kria™ KV260: Linux Boot Ubuntu 22.04 documentation
PYNQ version: 3.0
Behaviour:
I am using the Kria-PYNQ repo ( GitHub - Xilinx/Kria-PYNQ: PYNQ support and examples for Kria SOMs ) on the KV260 and running a notebook where i can execute lines like:
from pynq import Overlay
from pynq.lib import AxiGPIO
import numpy as np
overlay = Overlay(“./bitstream/design_1.bit”)
to load the bitstream onto the board.
I am then also able to send data to the board so as to do inference.
However, when i open Vivado and connect to the board the board will start to soft lock and/or completely freeze.
Sometimes it will work for a bit and i will even be able to inspect some signals in the ILA debug waveform window, but invariably it will crash.
I’ve had error messages ranging from:
[ 5218.787819] mmc1: Timeout waiting for hardware interrupt.
[ 5218.793222] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 5218.799652] mmc1: sdhci: Sys addr: 0x00000008 | Version: 0x00001002
[ 5218.806083] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
[ 5218.812506] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000023
[ 5218.818929] mmc1: sdhci: Present: 0x01f70000 | Host ctl: 0x0000001f
[ 5218.825353] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 5218.831776] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 5218.838199] mmc1: sdhci: Timeout: 0x00000009 | Int stat: 0x00018002
[ 5218.844623] mmc1: sdhci: Int enab: 0x03ff008b | Sig enab: 0x03ff008b
[ 5218.851046] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000001
[ 5218.857469] mmc1: sdhci: Caps: 0x35ecc881 | Caps_1: 0x00002007
[ 5218.863892] mmc1: sdhci: Cmd: 0x00000c1b | Max curr: 0x00000000
[ 5218.870316] mmc1: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0x00edc87f
[ 5218.876739] mmc1: sdhci: Resp[2]: 0x32db7900 | Resp[3]: 0x00000900
[ 5218.883162] mmc1: sdhci: Host ctl2: 0x00000000
[ 5218.887589] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000080ce1120c
[ 5218.894707] mmc1: sdhci: ============================================
to
[ 775.446902] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 775.453758] SMP: stopping secondary CPUs
[ 776.523016] SMP: failed to stop secondary CPUs 0,2-3
[ 776.527973] Kernel Offset: disabled
[ 776.531442] CPU features: 0x0,00002001,00000846
[ 776.535956] Memory Limit: none
[ 776.538997] —[ end Kernel panic - not syncing: Oops: Fatal exception in int errupt ]—
The exact way the board crashes or locks up is not always according to a consistent pattern, but it does always include connecting to the board in vivado’s hardware manager.
What i’ve tried:
I am currently trying to make a petalinux image myself for the board since i suspect it might be because of a mismatch in dependencies that the standard image has on the FPGA hardware that are different than the hardware in vivado. This is quite a time consuming process though so before I spent too much time on this I thought I’d ask if anyone knows what the issue could be.
Let me know as well if any more info is missing from here that might be useful!