firmware build

joke

@JoergS5 Thank you, I re-decompressed arm, and after recompiling, there was a new problem, is this set wrong

dc42

@joke 'make' is not part of the ARM compiler bundle. It is an optional component of msys2 that has to be installed separately.

joke

@dc42 I have installed msys2.Follow the steps you gave.Do I still need to add it to Eclipse?

dc42

@joke add C:\msys64\usr\bin to your PATH in windows. Then exit and reload Eclipse (otherwise it won't pick up changes to the Windows path).

joke

@dc42 I made these changes, but I still have this error.

joke

@dc42 I tried to do this and could find make, but these new errors appear.

JoergS5

This post is deleted!

JoergS5

@joke said in firmware build:

re-decompressed arm, and after recompiling

I didn't recompile it, but used the ready compiled files. Did you check that there are include subdirectories parallel to your bin directory?

The include files are necessary for the compiler to find uint32_t, which is included in stdlib.h

joke

@JoergS5 D:\arm-gnu-toolchain-12.2.mpacbti-rel1-mingw-w64-i686-arm-none-eabi\arm-none-eabi\include\c++\12.2.1\stdlib.h I can find it, so the compiler path I set is D:\arm-gnu-toolchain-12.2.mpacbti-rel1-mingw-w64-i686-arm-none-eabi\arm-none-eabi\bin. These errors still occur after compiling.Thank you.

JoergS5

@joke if you have still the msys2 part in ArmGccPath setting, this may confuse the compiler. You should remove it.

JoergS5

@joke an my path is different from your:

C:\Program Files (x86)\Arm GNU Toolchain arm-none-eabi\12.2 mpacbti-rel1\bin\

don't know why they are different, we both use 12.2 (independent from the beginning of course).

dc42

@joke which version of each project have you loaded into your Eclipse workspace?

dc42

@joke I think the issue may be that you are building an older version of the firmware with a compiler and library version more recent than we used with that version. In this case I think you can work around the issue by adding the line #include <stdint.c> before the line extern void vAssertCalled(uint32_t line, const char *file) noexcept; near the start of file nano-mallocr.c.

joke

@dc42 I downloaded the 3.5 version in the picture above on the website, but after downloading the suffix of the software is 3.4, I don't know how many versions I own, is there no update 3.5 series in github now?

joke

@dc42 I added some code to it, but I still get new errors.

joke

@JoergS5 I have deleted them in ArmGccPath.But I still get the error.

JoergS5

@joke I have no new idea, only to create everything new.

My approach building firmware is to use a stable tagged version and build it from this version. I currently use 3.5.0beta3, this compiles ok. A part of the projects don't exist with this tag, then I use the older tagged version.

My other guideline is to not use any unusual subdirectory names (no spaces, foreign characters, on different drive letters) and to use short ones.

With an error like yours, an error with Eclipse is also a possibility, so I search the newest stable Eclipse and install it new. You can install parallel to the exisiting one (you can even run both Eclipses at the same time, if you have enough RAM, but use two workspaces in this case).

joke

@JoergS5 Thank you very much, I also tried to do it but there are still errors, let me ask the administrator.

joke

@dc42 said in firmware build:

#include <stdint.c>

It seems as if open is 3.4. No 3.5.

joke

@dc42 said in firmware build:

#include <stdint.c>

I found the latest version, but I tried to build, still get an error, can you help me take a look? I don't quite understand .