STM32H7S78-DK development kit first week review: initial lighting test, many problems

ccccccc@

STM32H7S78-DK development kit first week review: initial lighting test, many problems [Copy link]

It’s been a long time since my last unboxing, and I finally found some time to continue writing.

Looking at other posts, the touch screen process can be performed after powering on, but mine did not respond after powering on. Checking the activity notification, it may be that the previous user has cleared the process, which is not a big problem.

I went to the official support and downloaded two routine files, namely:

The one above is a hex file, and the one below is a project file. I need help here. When the hex file is burned, it will show that the burning failed.

The following project will report a bunch of missing libraries when compiled using MDK-arm

When I checked the path, I found that some files could not be found in the path:

Feeling that I was hitting a wall everywhere, I simply started to try to light a lamp

Use cubemax to initialize the corresponding four pins directly:

Then configure the project. I use mdk for development:

After generating the code, open the mdk file:

There are two files in it, namely boot and appli. There is also an error when compiling boot, but we only need to burn appli at present.

Right click and set appli as active item, compile, but when using mdk to burn directly, the development board does not respond. I wonder if it is a broken one. Then use programe to burn, and it succeeds.

At present, the reasons for several problems are still unknown. We have only verified that there are no problems with the development environment and steps. Next, we will start the development of ADC. . .

Jacktang

Right click and set appli as the active item to compile. However, when using mdk to burn directly, the development board does not respond. Is there a problem with the compilation environment?

ccccccc@

Jacktang posted on 2024-10-10 07:26 Right-click and set appli as the active item to compile, but when using mdk to burn directly, the development board does not respond. Is this the compilation environment...

The compiled file can be burned directly without any problem and can run normally. And when mdk clicks to burn, it shows that the burning is successful.

秦天qintian0303

It is troublesome if the board is too advanced, and there are too many things to pay attention to.