Hi @thierry, thanks a lot for your reply.
I was experimenting a lot with setups and configurations to debug this issue - with no luck.
So, the aforementioned problem still persists in my setup and I believe it is reproducible, since I am using the default configuration. So quickly replying to the notes above:
- My tracker is able to track the two PYNQ boards, no problem on connection.
- It fail regardless of which PYNQ board is connected to the tracker. What I’ve discovered after running several times is the follow:
- PYNQ#1 is assigned the first workload and it gets frozen (if I leave it running it will expire with a timeout as listed above). PYNQ#2 is assigned workloads and completes the autotuning successfully.
- After the previous successful execution (only using 1 PYNQ board), if I re-execute the same script the opposite it happening, i.e. PYNQ2 is frozen and PYNQ1 does the work.
- So if I register only one device to the tracker, I cannot autotune, since 1 PYNQ is frozen and the atotuning script cannot find any available PYNQ to do the work. (When a PYNQ is frozen, the status on tracker is
total:1 free:0 pending:1 - If I register two PYNQs, my job is done since the status on tracker is
total:2 free:1 pending:1, but obviously, autuning does not scale on the number of PYNQs, so I cannot speedup.
- Indeed, I just have the default configuration with installation instructions and tutorial so I believe the above is reproducible with just one PYNQ.
I would be grateful if you could guide me how to debug this issue.
Regards,
Dionysios