There is a very simple firmware also in. So I can’t remove the whole system except AHB to APB bridge and GPIO DUT Slave. I should verify the GPIO dut slave with CPU.
I thought that I would need to make a Slave port in the BUS Matrix(cmsdk_ahb_busmatrix) for verification only? but I’m not sure about this. Could you please guide me how to verify the GPIO DUT Slave such as this architecture?
If you have to keep the CPU in, there’s not much chance of using the AHB VIP here for anything GPIO related. Sounds like you have to write all your tests in C/assembly.
Maybe I think I have to remove the CPU then replace it with agent acting as CPU.
Could you give some Idea if I remove the CPU then what the best general solution do?
Why don’t you just make a TB around the GPIO block, if this is what you’re testing? Alternatively you can force the outputs of the CPU to be driven by an AHB agent. This is what I’d do if the focus is more on the connections between the blocks.