Hello !
Do I undestand right and FFR API have 96Mhz limitation ?
I try to read AC code from it at Core clock 150Mhz and it freeze at some point in this code :
FLASH_Init(&flashInstance);
FFR_Init(&flashInstance);
/* Read AC. */
memset((void*) activationCode, 0, sizeof(activationCode));
result = FFR_KeystoreGetAC(&flashInstance, (uint8_t*) activationCode);
I can see FLASH_Init have this line :
config->modeConfig.sysFreqInMHz = (uint32_t)kSysToFlashFreq_defaultInMHz; // 96 Mhz
But may be it is common case for Write and Erase as well.
Can flash memory reading via FFR api can be done at 150Mhz if I initialize FLASH_Init
with modified clock 150Mhz ?
Or I can read AC area directly becouse address of it is known. I think I should use FFR API
for have compatibility with next versions.
Regards,
Eugene
1B silicon can work under 150MHz. 96Mhz limit is for writing and erasing. not for read.
if you are sure you have problem when read. please send me your demo project and problem screenshot. I need reproduce the issue first.
Hi ZhangJennie !
Could you give some recommendation for usage of last 32KB flash block 98000-9FFFF of memory.
Test show that is not possible to execute code from it and write/erase some part of it.
Looks like 32KB chunk a real flash memory erasable unit and 512 sectors is just part of it.
FFR area part of it and as usually written via ISP commands by Boot-Rom.
Can I erase/write remain this 32KB block ( 98000- 9DE00)by my SW ( IAP) without any probability to loze FFR context in any scenario ?
Or better do not touch it at all for avoid any problems ?
Does it possible to lock this block somehow ( at secure side start up) that write/erase operations are not possible ?
E.g read only protection like ?
Regards,
Eugene
Is this related with your original question? Is your original question solved?
I made a test based on 1B part. No problem read/write/erase 98000- 9DE00
Have a great day,
Jun Zhang
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------