Maybe not, unless there is a way to make it stop after it has done any whole number of full transfers (the full transfer count being transferred).
The goal is just to start it and have it loop indefinitely sending the same data block. Then the CPU stops it and it should always stop at the end of the data block and not somewhere else, at random, as from CHAN_ABORT.
Another option seems to be to pause the transfer and unpause it a few times, checking for a moment when a whole buffer has been transferred.
Writing to TRANS_COUNT, while it is running has no effect it seems, as expected.
The goal is just to start it and have it loop indefinitely sending the same data block. Then the CPU stops it and it should always stop at the end of the data block and not somewhere else, at random, as from CHAN_ABORT.
Another option seems to be to pause the transfer and unpause it a few times, checking for a moment when a whole buffer has been transferred.
Writing to TRANS_COUNT, while it is running has no effect it seems, as expected.
Statistics: Posted by wisi — Mon Jun 09, 2025 12:41 am