[gem5-users] Accelerator as PIO device writing back to main memory

2021-09-13 Thread diavastos--- via gem5-users
Hi all, I implemented an accelerator as a PIO device in the latest version of gem5 and I am having issues with accessing the main memory for write operations. Reading from main memory works correctly. I used as an example an old entry "gem5-accel" that implements a Daxpy accelerator (as far as

[gem5-users] Re: Accelerator as PIO device writing back to main memory

2021-09-15 Thread diavastos--- via gem5-users
Giacomo, Answering your questions: 1. No, I build my own config file using the configs/example/apu_se.py as a baseline 2. I have several simple memory objects on the accelerator that connect directly on the membus that then connects to the memory controller. But I have no iobridge between those

[gem5-users] BasicPioDevice read() / write() not responding

2021-10-23 Thread diavastos--- via gem5-users
Hi all, I implemented a device using the BasicPioDevice class but I can't seem to get the read() & write() calls to work. I assigned a pioAddr=0x2 and a pioSize=4096 and I try to write to the device directly using these two methods: Method 1: --- uint32_t inp_params2 = 14; uin

[gem5-users] Re: BasicPioDevice read() / write() not responding

2021-10-24 Thread diavastos--- via gem5-users
Hi, Thank you for the replies! I mapped the physical address of the device to a virtual address and marked it as uncacheable and did the trick for X86. So now using memcpy() I read/write from and to the device using it's mapped virtual address. However, for ARM it only works for read. Even if