English is currently available.
Getting Started with TEP DISCUSSION
How can a beginner turn 'Which board is best?' into a question that has a useful engineering answer? Recent dual-processor boards offer more options, but a larger feature list does not automatically fit a small sensor project.
Suppose the design needs two analog inputs, an I2C display, wireless logging and a motor-control output. Which requirements should be quantified before comparing boards?
Make a pin and peripheral budget first. Two analog inputs require suitable ADC channels, voltage ranges and sampling behavior; merely counting GPIO pins is insufficient. Check whether pins are shared with boot configuration, onboard hardware or other peripherals. For the motor, identify the external driver and control interface. A development-board pin should not be assumed capable of powering the motor directly.
Define timing and storage requirements. Specify the motor-loop period, acceptable jitter, sensor sample rates and the amount of data that must survive a network outage. At 16 bytes per record and 100 records per second, one hour requires about 5.76 MB before filesystem or protocol overhead. That calculation can change the choice of storage more than CPU clock speed does.
Then compare software support, debug access, logic voltage, power consumption and availability. If networking or a user interface occasionally stalls, decide whether the motor control may stall with it. That is where an MCU plus a higher-level processor can help, but it also adds complexity. A clear list of mandatory requirements lets people explain tradeoffs instead of recommending their favorite board.
