Running the test eth_fw_data_check causes luwen to think that DMA keeps going so the chip hangs with the following error - It is not currently safe to communicate with ARC because, there is an outstanding PCIE DMA request
Did some digging and looks like the register ARC_CSM.ARC_PCIE_DMA_REQUEST.trigger has a non 0 value, while if that same register is read using the old backend I see its value being 0
Reading from spi or running test-pcie-dma produces the same error. This was observed on 2 different WH systems, in both cases the chip was still accessible afterwards and passes test-pcie-dma.
Running the test
eth_fw_data_check
causes luwen to think that DMA keeps going so the chip hangs with the following error -It is not currently safe to communicate with ARC because, there is an outstanding PCIE DMA request
Did some digging and looks like the registerARC_CSM.ARC_PCIE_DMA_REQUEST.trigger
has a non 0 value, while if that same register is read using the old backend I see its value being 0