conflicting types for 'task_handler_t'

[Anonymous]

I have built a test project using ConfigTools for LPC54606J512BD100 with MCUXpresso IDE v11.6.1 [Build 8255].

When I try to compile, I get the error "conflicting types for 'task_handler_t'" in file fsl_os_abstraction_bm.c

This project has no code added or modified by me and ConfigTools shows 0 errors and 0 warnings.

I'm not sure what file I need upload to this forum entry for someone to try to reproduce.

[Anonymous]

Six files in the osa/ directory.

Yes, I added FreeRTOS

I did not add osa/ before using the ConfigTools. Everything was done through
that interface.

I added:
Operating Systems:
FreeRTOS kernel

Drivers:
adc
clock
common
ctimer
dma
dmic
dmic_dma
flexcomm
flexcomm_i2s
flexcomm_i2s_dma
gpio
i2c
i2c_dma
i2c_freertos
iocon
power
reset
sdif
spi
spi_dma
spi_freertos
usart
usart_dma
usart_freertos

CMS Include:
CMSIS_Include_CM
LPC54606_CMSIS
LPC54606_system

Utilities:
assert
debug_console
serial_manager
usart_adapter

Middleware:
File System
FAT File System
fatfs
mmc
ram
sd
usb

Memories
SDMMC Stack
mmc
sd
sdmmc_host_sdif_interrupt
sdmmc_osa_bm

[RaRo]

Hello @Anonymous,

It seems there is a situation with the FATFS Middleware and the MMC disk.

Configuring the MMC disk, ConfigTools adds files from baremetal operating system: fsl_os_abstraction_bm.c and fsl_os_abstraction_bm.h; for make the MSDK adaptation configuration to work.

The problem with these files being added at OSA folder, is that you have the variable "task_handler_t" declared in two files: fsl_os_abstraction_bm.c and fsl_os_abstraction_free_rtos.c; making the build to fail.

Regards, Raul.

[Anonymous]

Thank you for the explanation.

Do you think this will be corrected in an update?

[RaRo · Accepted solution]

Hello @Anonymous,

Thank you for the feedback, we will let the team in charge know about this issue.

Best regards, Raul.

[stefanct]

This is still a problem, at least for i.MX RT MCUs. One has to exclude fsl_os_abstraction_bm.c from the build after adding the freertos component to an existing project via the sdk components manager with that family. I guess it's the same underlying issue.

[Anonymous]

Thanks a lot for looking into this.

[RaRo]

Hello @Anonymous,

Trying to replicate your error, there is a possible redefinition of "task_handler_t" in files inside folder OSA. This redefinition is making your program to fail in building.

Could you please help us checking the OSA folder? How many files do you have? Did you add the OSA component before the ConfigTools configuration?

Also, are you using FreeRTOS or baremetal for your aplication? What modules/peripherals are you using or editing trough ConfigTools?

Best regards, Raul.

[Anonymous]

Somewhat disappointing no one from NXP seems concerned ConfigTools is creating code with errors.