There is an error when compiling the microcontroller, and there is an error in the compilation of th

The meaning of this phrase is:

unknown control or wrong parameter (independent variable)".

You have to look at the context of the program manifest to know "what to do".

Before looking at the context of the program list, you must know what language you use, which version of the compilation, which microcontroller you use, and so on, and so on.

Regarding the supplement] began to appear, there are several possibilities:

1) Is there include in the file header, and the included file is not appropriate?

2) Is there a mistake in the operation of the development interface (I am not familiar with A51 and related development tools, and some operations in other systems are conditional)?

In some systems, compilation and linking are done step-by-step, when did you get this hint?

There is an error in the compilation of the stm32 program, which is caused by a setting error, and the solution is as follows:

1. Open the STM32 ST-Link Utility and select File ->Open File....Or press the shortcut key "Ctrl + O" to open a burning file.

2. Find the HEX file you want to burn and select "Open".

3. The software will load the hex file into the window, and at the same time, the check code of the file will be displayed in the message box below.

4. Then click "target ->connect" in the menu bar to start connecting to the target.

5. Start to connect to the target, after success, the target chip information will be displayed on the left side of the software toolbar, and relevant prompts will be made in the message box below.

Declarations for variables cannot be placed after an executable statement, and variables must be declared at the beginning.

That is, move the gpio inittypedef gpio initstructure before systeminit().

This error means that the declaration of the variable cannot appear after the block of executable statements, that is, your GPIO initialization struct declaration should be placed before the PD port clock is enabled, and the gpio inittypedef gpio initstructure should be placed; put in rcc apb2periphclockcmd(rcc apb2periph gpiod,enable); The front is fine.

Hello, there may be a variety of reasons for the failure of the MCU to create in the compilation, and here are some possible solutions to the failure:1Check**:

Compilation failures may be due to syntax errors or logic errors in **. Please double-check to make sure that it is correct. 2.

Check the compiler: There may be a problem with the compiler, you can try reinstalling or updating the compiler. 3.

Check the library file: If the library file is used in the code of the generation state, it may be that the library file has a problem causing the compilation to fail. Please check that the library files are installed or updated correctly.

4.Check the MCU connection: If the MCU connection is incorrect, the compilation will also fail to detect Peichan.

Please make sure that the microcontroller is properly connected to the computer and that there is no problem with the cable. 5.Check the compilation options:

The compilation options may not be set correctly, causing the compilation to fail. Please check that the compilation options are set correctly. 6.

Check the computer environment: There may be a problem with the computer environment that is causing the compilation to fail. Please check that your computer environment is set up correctly.

In short, solving the problem of MCU compilation failure requires careful examination of multiple aspects such as **, compiler, library files, MCU connection, compilation options, and computer environment. If the above methods do not solve the problem, you can try to ask for help in the relevant forums or communities, or contact the technical support of the microcontroller manufacturer. <>

Summary. Hello dear, happy to answer your <>

There may be several reasons why the MCU fails to create in compilation:1Syntax error written:

There may be grammatical errors, such as misspellings, unenclosed statements, etc., that cause compilation failures. At this point, you need to check ** and fix the error. 2.

3.Compiler settings: If the compiler is set up incorrectly, it can cause compilation errors.

At this point, you need to check that the compiler configuration is correct and fix error 4Hardware connection issues: If there is a problem with the hardware connection, it may cause compilation failures.

At this point, you need to check whether the hardware connection is correct.

What should I do if the MCU fails to be created in compilation?

Hello dear, it is my pleasure to answer the <> of Bu Xi for you

There may be several reasons why the MCU fails to create in compilation:1Syntax error written:

There may be grammatical errors, such as misspellings, unenclosed statements, etc., that cause compilation failures. At this point, you need to check ** and fix the error. 2.

Lack of related library files: If the use of other library files in ** is missing, it will also cause compilation failure. At this point, you need to add the appropriate library files to the build environment.

3.Compiler settings: If the compiler is set up incorrectly, it can cause compilation errors.

At this point, you need to check that the compiler configuration is correct and fix error 4Hardware connection issues: If there is a problem with the hardware connection, it may cause compilation failures.

At this point, you need to check whether the hardware connection is correct.

Pro-noisy skin, solution: 1Check ** and fix grammatical errors.

2.Add the appropriate library files to the compilation environment. Liquid mold 3

Check that the compiler configuration is correct and fix errors. 4.Check that the hardware is connected correctly.

Dear, if the above methods can't solve the problem, you can try to reinstall the compiler or change the version. If Li Hongguo still can't solve the problem, it is recommended to seek help from relevant technical support or limb book forums. <>