2 ms·
Even 133MHz is overkill for most applications. It only has 264k of RAM anyways, and all application code needs to be loaded from external flash. Pretty much all
by crote 4y ago
Even 133MHz is overkill for most applications. It only has 264k of RAM anyways, and all application code needs to be loaded from external flash. Pretty much all peripherals are offloaded to dedicated hardware, and it even has two cores and pretty exhaustive DMA capabilities.
There are very few embedded applications where you need more computation power than a RP2040 can offer without being limited by RAM or flash. Sure, they could have tried pushing it even harder, but why bother when it is already enough?
- londons_explore 4y agoWell In which case, doing more per clock cycle means fewer latches and d-flops, more efficient combinatorial logic, and ultimately they could have used less silicon area and made a cheaper chip with the same functionality. To be fair to them, I think it was a fairly inexperienced design team making their first silicon, in relatively low volumes (10's of millions). They weren't an established player trying to make a 1 billion+ production run super competitive product where fractions of a cent matter.