Bug in SDMMC_BLOCK

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User16740
Level 1
Level 1
5 replies posted 5 questions asked First reply posted
Hello All,

SDMMC_BLOCK V4.0.32 can be erroneously configured to same name (SDMMC_BLOCK_SD) for a a macro and a symbol.

sdmmc_block_conf.h:

#define SDMMC_BLOCK_MAJOR_VERSION (4U) /**< Major version */
#define SDMMC_BLOCK_MINOR_VERSION (0U) /**< Minor version */
#define SDMMC_BLOCK_PATCH_VERSION (32U) /**< Patch version */

#define SDMMC_BLOCK_SD
#define SDMMC_BLOCK_SD_NUM_DELAY_ELEMENTS (8U)
#define SDMMC_BLOCK_SD_SUPPORT_4_BUS_WIDTH (1U)
#define SDMMC_BLOCK_RTOS_MODE_SELECT (1U)


sdmmc_block_conf.c:


/* SDMMC SD mode instance */
SDMMC_BLOCK_SD_t SDMMC_BLOCK_SD =
{
.sdmmc = XMC_SDMMC, /* SDMMC instance */
.int_priority = 63U, /* Node interrupt priority */
.int_sub_priority = 0U, /* Node interrupt sub-priority */
.mode_init_flag = false, /* Mode initialization false by default */
.rtos = &SDMMC_BLOCK_CMSIS_RTOS, /* RTOS resources */
};


Which does not compile, as there is no validity check for the application instance label:

5157.attach

Regards,

Mark.
0 Likes
1 Solution
Vasanth
Moderator
Moderator
Moderator
250 sign-ins 500 solutions authored First question asked
Hi Mark,

Thanks for sharing the info to other community users. The validity check for instance label should be taken care in the future versions of the software support for the device.

Best Regards,
Vasanth

View solution in original post

0 Likes
1 Reply
Vasanth
Moderator
Moderator
Moderator
250 sign-ins 500 solutions authored First question asked
Hi Mark,

Thanks for sharing the info to other community users. The validity check for instance label should be taken care in the future versions of the software support for the device.

Best Regards,
Vasanth
0 Likes