cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE levelX Code Generation bugs

Jackle
Associate III

 

Try to use LevelX customized Nor driver for STM32G0 in 

lastest release STM32CubeIDE 1.14.1

When I regenerate code, whatever user code in lx_nor_driver_write() function will be copied to lx_nor_driver_block_erase() and lx_nor_driver_block_erased_verify().

static UINT lx_nor_driver_write(ULONG *flash_address, ULONG *source, ULONG words)

{

UINT ret = LX_SUCCESS;

 

/* USER CODE BEGIN NOR_WRITE */

=====> Whatever is here will go to lx_nor_driver_block_erase() and lx_nor_driver_block_erased_verify()

/* USER CODE END NOR_WRITE */

 

return ret;

}

static UINT lx_nor_driver_block_erase(ULONG block, ULONG erase_count)

{

 

UINT ret = LX_SUCCESS;

 

/* USER CODE BEGIN NOR_WRITE */

=====>Whatever is here will go to lx_nor_driver_block_erase() and lx_nor_driver_block_erased_verify()

/* USER CODE END NOR_WRITE */

 

return ret;

}

 

static UINT lx_nor_driver_block_erased_verify(ULONG block)

{

UINT ret = LX_SUCCESS;

 

/* USER CODE BEGIN NOR_WRITE */

=====>Whatever is here will go to lx_nor_driver_block_erase() and lx_nor_driver_block_erased_verify()

/* USER CODE END NOR_WRITE */

 

return ret;

}

 

============= even when you delete user code section in lx_nor_driver_block_erase() and lx_nor_driver_block_erased_verify()

Regeneration will copythe user code in lx_nor_driver_write() to those two functions.

 

This is a serious bug and a stopper for user to use the software. Please have it fixed ASAP.

1 REPLY 1
Ghofrane GSOURI
ST Employee

Hello @Jackle 

First let me thank you for reporting.

I will check this issue internally and get back to you asap.

Thx

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.