Ex_2 use DMA prime cache (ex_1 merge) #23
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merged Ex_1 edits dropping DMA into Ex_2
Updated 't' _isr Busy loop to use DMA array - running faster using ref table allows more _isr's sec and also using DMA buffer - some part of 32KB with each _isr to confirm it doesn't conflict/confuse and camera driver code using that memory.
No reason this Ex_2 can't replace Ex_1 as it does nothing ( except idle code ) unless the 't' is activated for timing. Generating _isr() busy work and a flurry of interrupts to do it. loading the CPU rather than just an empty loop().
Adjusting priRestart to smaller or larger PRIME # ( several listed in //comment ) will vary the completion time of the _isr allowing more or less to complete before the next timer tick.
Adjusting PrPS is the freq of the _isr()'s desired
Adjusting tableSize to 1 eliminates the DMA usage for cache of lower prime factors to test