ATF Build Fails when Log Level is Verbose

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ATF Build Fails when Log Level is Verbose

770 Views
smiller2
Contributor III

In order to debug what is going wrong with the bootloader,   I changed the LOG_LEVEL in the MAKEFILE to "50".   Using flex-builder, if I attempt to compile for the qspi, then the build fails in xlat_tables_arch.c   Below is the console dump for the first error.   There are several other similar errors after that.   

****************************************

CC lib/xlat_tables_v2/xlat_tables_internal.c
lib/xlat_tables_v2/xlat_tables_internal.c: In function ‘xlat_desc_print’:
lib/xlat_tables_v2/xlat_tables_internal.c:1051:3: error: format not a string literal and no format arguments [-Werror=format-security]
tf_printf((desc & LOWER_ATTRS(AP_RO)) ? ro_str : rw_str);

0 Kudos
1 Reply

767 Views
yipingwang
NXP TechSupport
NXP TechSupport

I also reproduced your problem in my build environment, I have reported this issue to the Application team.

So far, please use LOG_LEVEL="40" in atf Makefile, please refer to the following modification in Makefile.

# Process Debug flag
$(eval $(call add_define,DEBUG))
DEBUG := 1
ifneq (${DEBUG}, 0)
BUILD_TYPE := release
TF_CFLAGS += -g
ASFLAGS += -g -Wa,--gdwarf-2
# Use LOG_LEVEL_INFO by default for debug builds
LOG_LEVEL := 40
else
BUILD_TYPE := release
$(eval $(call add_define,NDEBUG))
# Use LOG_LEVEL_NOTICE by default for release builds
LOG_LEVEL := 20
endif

 

0 Kudos