Don't be fooled by megaherz

mikrobitti.fi/uutiset/mb/acac445c-5ec8-44fe-b979-91aedf78bc3f

Different microcontrollers range from 16mhz to 160mhz. But dont be fooled by thinking that highest mhz is always the best device.

Also remember that microcontrollers have REALLY low mhz ranges compared to actual proper CPUs like ones in Raspberry Pi which is in Ghz range. Raspberry and a microcontroller arent the same thing.

The list from fastest to slowest:
Arduino Due R3-E
Open Smart Due R3
Wemos D1
Keyes Tudio Uno R3
Open-Smart Uno
Arduino Uno
Open-Smart Nano
Arduino Micro
Robotale Mega 2560

Attached: d6e17aa6-cbe3-5bb7-9d77-8ffcc8647a53.jpg (650x433, 90K)

ok

THIS CODE is used to determine the speed of devices:

"
void setup() {
Serial.begin(9600);
Serial.println("Aloitetaan!");
}

void loop() {
long alku, loppu, aika, laskutoimituksia, kokonaislukulaskentanopeus, liukulukulaskentanopeus;
laskutoimituksia=1000000;

// Kokonaislukulaskentanopeuden mittaus
alku=millis();
for (long i=0; i

You really don't need more than 32 MHz on MCU.

>kokonaislukulaskentanopeus

Attached: e.jpg (258x258, 51K)

fastest is picrelated

Attached: ESP8266-OLED-preflashed-development-board-Screen-0-96-inch-OLED-version-ESP8266-18650-0-96-inch.jpg (1000x1000, 121K)

>But dont be fooled by thinking that highest mhz is always the best device.
Who would even think that? Even decades ago, the 1MHz 6510 was better than the 4.77MHz 8088, clock cycles mean nothing in the real world.

Attached: 1540777676729.gif (291x300, 2.92M)

attiny85 > your entire list

>not a sop23 attiny10
pleb

I would think the esp32 would beat them all. And you not need to write ardrino code, use esp-idf instead

True, but better still is stuff like STM32F7 and freescale shit

>4gpio
good luck with that

Attached: 84466237.jpg (1000x839, 85K)

attiny is literally the same core in a smaller package

and?

Of course kokonaislukulaskentanopeuskoe needs a kokonaislukulaskentanopeusfunktion, how else can you find out the kokonaislukulaskentanopeus of your kokonaislukuladkentakykyisen processor?

Also remember to wear pants in public areas. Pants are important.

Attached: ithink.jpg (676x399, 69K)

for (float i=0; i

plenty to kick ur ass

Who said it was faster than the entire list?

>The list from fastest to slowest:
>attiny85 > your entire list

and?

It's greater than all of those garbage micro controllers, m8

>It's greater than all of those garbage micro controllers

Pretty sure it's smaller
And also the same microcontroller

nobody said anything about it's size. dummy

>It's greater than all of those garbage micro controllers

yep, it is greater than they are. Similarly I am greater than you are. Certainly not bigger though, since you're a fat piece of shit. What about it?

>8 pin package greater than 48 pin package

Do you even electronics

>no MSP430
I am disappointed

yeh

>don't be fooled by megaherz

Attached: unnamed.jpg (900x900, 71K)

Kinda does for short pipelines like ARM has, but memory speed is alway a bottleneck.

You don't need such a fast clock for your blinking LED arduino example user.

>Different microcontrollers range from 16mhz to 160mhz.
Not sure who would want to work in the milli Hertz range. Anyways, the 6502 at 1 MHz was often faster than Z80 at 4 MHz. Also 6502 was a delight to program, while Z80 was a mess that made you want to take a shower after programming it.

I wanted a 16 code 6502 at 1 GHz on a chip. With 64 KB RAM per core it could really be all in one chip, easily. the 6502 is still very efficient in interrupt responses.

>tests in OP clearly show ESP8266 being slower

>this dumb nigger posts his crap regardless

I read your message.

This is horrible looking code. Do you usually program like this? Wtf is up with your variable names????

Yes, it is

Attached: LOW_POWER_CPU_BLENDEE.gif (400x296, 353K)

is there something as good as 6502 but more modern?

fun fact: arm can trace its ancestry back to 6502

>Using the overpriced atmel family

>implying I'm not a brainlet and can use anything else

In real time systems it's not the frequency that's important, but the delay.

Attached: 1423320709030.png (803x688, 231K)

*core, not code.
BTW the BBC had the Tube interface for using two processors in a machine. Pretty impressive for a 35 year old design.
>is there something as good as 6502 but more modern?
Not that I know of. The 6809 (and 6309) had more features but is almost as old. It was the tail end of the 8-bit era.
>fun fact: arm can trace its ancestry back to 6502
Quite correct.

What I never understood is why WDC or Apple never implemented SWEET-16 in silicon, that would have kickstarted the 16-bit era a lot earlier and with a cleaner design than what we got.

>BTW the BBC had the Tube interface for using two processors in a machine. Pretty impressive for a 35 year old design.
Not really, proper multi-processing was implemented on real computers for over two decades by that time, and even in microcomputers dedicated I/O and application processors weren't an alien concept and quite common in higher-end systems.

But what about difference in optimizations, executables, serial processing speed, etc. for the target architectures?
It looks like you're mainly just testing serial throughput.