Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ex_2 use DMA prime cache (ex_1 merge) #23

Merged
merged 3 commits into from Apr 27, 2021
Merged

Conversation

Defragster
Copy link
Contributor

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

Opps : just saw I did not add DMAMEM to that - running from RAM1 or DMAMEM shows same behavior, will edit that in as comment option after creating PR

Add DMAMEM specifier to prime cache
Calc _isr freq as float to be right on bigger numbers
Add "dsb" for fun.
@mjs513 mjs513 merged commit 536df7e into mjs513:main Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants