Region `flash' overflowed by 18972 bytes (make px4_fmu_v6x)

Pixhawk
1

Hello,

FAQ shows to comment out modules that I don’t need.

Furthermore, It tells to run the followinf command to determine large memory consumers.

arm-none-eabi-nm --size-sort --print-size --radix=dec px4_fmu-v6x_default.elf | grep " [bBdD] "

The .elf file does not exist in my directory.

How do I know which module is which? Is there a document that explains what each module does?

CONFIG_BOARD_TOOLCHAIN="arm-none-eabi"
CONFIG_BOARD_ARCHITECTURE="cortex-m7"
CONFIG_BOARD_ETHERNET=y
CONFIG_BOARD_SERIAL_GPS1="/dev/ttyS0"
CONFIG_BOARD_SERIAL_GPS2="/dev/ttyS7"
CONFIG_BOARD_SERIAL_TEL1="/dev/ttyS6"
CONFIG_BOARD_SERIAL_TEL2="/dev/ttyS4"
CONFIG_BOARD_SERIAL_TEL3="/dev/ttyS1"
CONFIG_BOARD_SERIAL_EXT2="/dev/ttyS3"
CONFIG_BOARD_SERIAL_RC="/dev/ttyS5"
CONFIG_DRIVERS_ADC_ADS1115=y
CONFIG_DRIVERS_ADC_BOARD_ADC=y
CONFIG_DRIVERS_BAROMETER_BMP388=y
CONFIG_DRIVERS_BAROMETER_INVENSENSE_ICP201XX=y
CONFIG_DRIVERS_CAMERA_CAPTURE=y
CONFIG_DRIVERS_CAMERA_TRIGGER=y
CONFIG_DRIVERS_CDCACM_AUTOSTART=y
CONFIG_COMMON_DIFFERENTIAL_PRESSURE=y
CONFIG_DRIVERS_DIFFERENTIAL_PRESSURE_AUAV=y
CONFIG_COMMON_DISTANCE_SENSOR=y
CONFIG_DRIVERS_DSHOT=y
CONFIG_DRIVERS_GNSS_SEPTENTRIO=y
CONFIG_DRIVERS_GPS=y
...

Thanks for your help.

Mustafa

2

Hello,

I took the initial guess to comment out several entries from the list and was able to make the px4_fmu_v6x. As soon as the make is done, I was expecting Gazebo Harmonic simulator starts up but it did not happen. What am I missing?

Mustafa

3

Hi! To run the simulation you need a different make command, see here.
And btw if you didn’t locally change anything in the PX4 source code the “flash overflow” likely is due to an outdated compiler. You can check the version you have with gcc -v.

4

Hi @sfuhrer Thank you for your reply. I was following this document on building PX4 Software. What is the purpose of that document? Since I am using PixHawk 6x flight controller, I figured that would be the closest to resemble my drone, therefore I followed the above link. As I am new to PX4, I am sometimes confused the order and the context of certain information.

I have the following gcc on my Ubuntu environment.
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04.2)

Mustafa

5

@mcayci Sorry for the confusion. I think you did everything right, but the install script lets your Ubuntu version install whatever compiler version it defaults to. On Ubuntu 22.04 this is probably ARM GCC 9 or 10 compared to 13 on 24.04. You can check with:
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009

JFYI The version you pasted is the native GCC to compile software for your computer e.g. simulation not autopilot hardware. But it shows us what Ubuntu version you’re running.

In principle you can also compile PX4 with ARM GCC 9 (was the default until a certain release) but newer versions will directly run out of flash and you’d need to trim things down which is a hassle.

What I would do in your case is to either switch to an Ubuntu 24.04 setup if that’s easy for you or if you want to stick to 22.04:

6

I understand that the compiler and system versions need to be upgraded, but why do the checks also fail after submitting a PR on GitHub?