??? 09/07/09 13:59 Modified: 09/07/09 14:01 Read: times |
#168774 - Don't forget about the Maxim/Dallas parts! Responding to: ???'s previous message |
Erik Malund said:
Using the one-clocker's auto-increment
I recall no one-clockers with auto-increment Erik Jan mentioned one family ... the Maxim/Dallas DS89C4x0 series. They all have auto-increment/decrement of their two data pointers, though they're separately enabled, and there's a toggle feature, too, so you can, if you like, use the two data pointers alternately with both or either one, on auto-increment or auto-decrement, in case you're moving data around, or something like that. They also allow you to adjust the external bus cycle length, as do some of the SiLabs MCUs, among others, and they can do a few other things too. I've used that feature in cases where the DS89C450 was simply behaving as a DMAC, generating addresses but not even dealing with the data. That would be perfect for rapid memory-mapped screen updates, etc, too, as you could build the next screen at your leisure, then update in one quick operation using the two data pointers in auto increment or decrement mode with an unrolled loop. It wouldn't be pretty, nor would it be code-space-thrifty, but it would be really fast! RE |
Topic | Author | Date |
Fastest way to fill buffer | 01/01/70 00:00 | |
something like this | 01/01/70 00:00 | |
when software hits limits... | 01/01/70 00:00 | |
auto-increment | 01/01/70 00:00 | |
Two questions .. | 01/01/70 00:00 | |
But Gonzallo unrolled it already isn't it? | 01/01/70 00:00 | |
Yes, but not with the hardware increment | 01/01/70 00:00 | |
be specific | 01/01/70 00:00 | |
Don't forget about the Maxim/Dallas parts! | 01/01/70 00:00 | |
what to unroll | 01/01/70 00:00 | |
Well, what you CAN do ...![]() | 01/01/70 00:00 |