MCUXpresso generates the wrong function signature

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

MCUXpresso generates the wrong function signature

Contributor III

The Peripherals tool of MCUXpresso 10.2.1 generates the wrong function signature from the eDMA mode of the SPI peripheral using KSDK 2.4.2 for the FRDM K64F.

If you enable 'Initialization of eDMA callback' and provide a 'Transfer callback function name', the generated function signature in the peripherals.h header file is:

/* DSPI eDMA callback function for the SPI component (init. function BOARD_InitPeripherals)*/
extern void DSPI_Callback(DSPI_Type *, dspi_master_edma_handle_t *, status_t, void *);

There is no such type as 'DSPI_Type' and so including this file generates compile errors. The correct type (according to MK64F12.h) is 'SPI_Type' without the leading 'D'. The rest of the DSPI API correctly uses the SPI_Type name.

0 Kudos
1 Reply

NXP Employee
NXP Employee

Hi Simon,

thank you for reporting this bug. It will be fixed in next release of the Peripherals tool components.

Meanwhile, please use attached patch for MCUXpresso Config Tools v4.1 / MCUXpresso SDK v2.4.2:

1. Copy content of the archive to your local MCUXpresso Config Tools v4.1 data repository (it is shared with MCUXpresso IDE 10.2.x). Here is location of the local repository per operating system:

  • Windows: C:\ProgramData\NXP\mcu_data_v4.1\
  • Linux and Mac: /home/<user>/.nxp/mcu_data_v4.1/

2. Open your project in Peripherals tool and click the Update Project button. Content of peripherals.h will be updated with the fix.



0 Kudos