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

Correct description of feedback #102

Merged
merged 2 commits into from
Dec 29, 2020
Merged

Correct description of feedback #102

merged 2 commits into from
Dec 29, 2020

Conversation

SpenceKonde
Copy link
Contributor

feedback input takes the "output" of the even LUT (which is taken as the output of the sequencer if that is used, otherwise the output of the LUT itself. Unclear if intended and the documentation is poorly written.

Also - were you going to cut the tinyAVR and Dx-stuff from the readme for MegaCoreX? (do note that I've cut the mega/Dx-stuff from megaTinyCore readme, and am cutting tiny stuff from DxCore version.

feedback input takes the "output" of the *even* LUT (which is taken as the output of the sequencer if that is used, otherwise the output of the LUT itself. Unclear if intended and the documentation is poorly written. 

Also - were you going to cut the tinyAVR and Dx-stuff from the readme for MegaCoreX? (do note that I've cut the mega/Dx-stuff from megaTinyCore readme, and am cutting tiny stuff from DxCore version.
@SpenceKonde
Copy link
Contributor Author

SpenceKonde commented Dec 24, 2020

Oh - an as a wacky aside - as you surely know, there are multiple ways to make a LUT oscillate (the simplest, truth=0x01, input0 feedback and the others masked (on an even LUT, of course!) runs at nearly 100 MHz on Dx parts, routing it through the event system gives ~53 on same chip, two LUTs bouncing off eachother is like 35, and so on). Anyway, if you set up one of those to output on the pin, then jump that to PA0, and set the clock to external, you can clock the chip off it's oscillating LUT :-P Why you would want to is another matter (in fact, I'm almost positive only a madman would) - but its good for a laugh, no? (obviously you do need to prescale it to get the clock speed in spec, depending on the part and how you've got the LUTs oscillating)

It *only* controls filter/sync, and sequential logic. without those, these logic blocks react as fast as the transistors can switch. Which can be..... surprisingly fast!
@MCUdude
Copy link
Owner

MCUdude commented Dec 25, 2020

Thanks for the PR! And merry Christmas!

Unclear if intended and the documentation is poorly written.

It's just poorly written, sorry.

Also - were you going to cut the tinyAVR and Dx-stuff from the readme for MegaCoreX? (do note that I've cut the mega/Dx-stuff from megaTinyCore readme, and am cutting tiny stuff from DxCore version.

I've totally forgotten to remove the tinyAVR references in the readme. Would you like to do this in this PR too? 😇

Oh - an as a wacky aside - as you surely know, there are multiple ways to make a LUT oscillate (the simplest, truth=0x01, input0 feedback and the others masked (on an even LUT, of course!) runs at nearly 100 MHz on Dx parts, routing it through the event system gives ~53 on same chip, two LUTs bouncing off eachother is like 35, and so on). Anyway, if you set up one of those to output on the pin, then jump that to PA0, and set the clock to external, you can clock the chip off it's oscillating LUT :-P Why you would want to is another matter (in fact, I'm almost positive only a madman would) - but its good for a laugh, no?

Cool, I didn't know this. I'll for sure give it a try to see what frequencies I can achieve.

@MCUdude MCUdude merged commit a3f0498 into MCUdude:master Dec 29, 2020
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.

2 participants