Has the use of BSPCFG_FLASHX_SIZE been deprecated?

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

Has the use of BSPCFG_FLASHX_SIZE been deprecated?

Jump to solution
479 Views
edwarddarosa
Contributor II

I'm using MQX 4.0.

I am assuming the block size and location is based solely on the _bsp_flashx_file_blocks array in init_flashx.c.

Tags (2)
0 Kudos
1 Solution
371 Views
DavidS
NXP Employee
NXP Employee

Hi Ed,

Short answer: Yes you are correct.

Longer answer:  The BSPCFG_FLASHX_SIZE really seems to be a simple hardcoding/manual macro to define the total size of flash that will be accessible to the FLASHX driver.  The linker file and init_flashx.c structure seem to be the more dynamic and program friendly way to define the flash space and what portion of that flash space will be used for FLASHX driver.

Hope this helps.

Regards,

David

View solution in original post

0 Kudos
2 Replies
372 Views
DavidS
NXP Employee
NXP Employee

Hi Ed,

Short answer: Yes you are correct.

Longer answer:  The BSPCFG_FLASHX_SIZE really seems to be a simple hardcoding/manual macro to define the total size of flash that will be accessible to the FLASHX driver.  The linker file and init_flashx.c structure seem to be the more dynamic and program friendly way to define the flash space and what portion of that flash space will be used for FLASHX driver.

Hope this helps.

Regards,

David

0 Kudos
371 Views
edwarddarosa
Contributor II

Yes, definitly helpful. I will consider flashx related info that include the setting of BSPCFG_FLASHX_SIZE as most likely outdated.

Thanks,

Ed

0 Kudos