LPC55S69: FLASH_Read API in SDK v2.8

[EugeneHiihtaja]

Hi !

Do I understand and in new SDK correct version of FLASH_Rread API is exposes from BootRoom ?

Is this Read function handle nonflashed Flash memory areas what is not written before ?

As usually we have HardFault if erased but now written area was read directly.

Regards,

Eugene

[Sabina_Bruce]

Hello Eugene,

Hope you are doing well.

I am not understanding your questions very well. Could you please clarify what you mean by exposing the bootrom. 

Is this Read function handle nonflashed Flash memory areas what is not written before ?

As usually we have HardFault if erased but now written area was read directly.

Do you mean areas that have never been written we should not see information, but not a hardfault. Could you please provide an example of what you mean so I may understand better.

Best Regards,

Sabina

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

----------------------------------------------------------------------------------------------------------------------- 

[EugeneHiihtaja]

Hi Sabina !

In previos version it was no any FLASH_Read API at all.

And if you read nonwritten flash by directly it cause HardFault.

Now FLASH_Read is exposed and might work well on top of all areas.

But NXP confirmation is always required.

Regards,

Eugene

[Sabina_Bruce]

Hi Eugene,

I tried the Flash_Read as you mention for the section that is erased and I do not get a hardfault.

Please provide the example as you are working with to replicate this.

Best Regards,

sabina

[EugeneHiihtaja]

Hi Sabina !

 I have taken in use FLASH_Read and haven't seen hardfault any more.

But I should know if this happens randomly or NXP expose new API for cover this problem.

It is not so clear from existing documentation ( if any ).

Regards,

Eugene

[Sabina_Bruce]

Hope you are well.

If you are able to produce the hardfault again, please share the steps so I can analyze if this behavior is expected or not. If it occurs randomly it will be difficult to pinpoint if the cause is from the API or a different point in the application.

Best regards,

Sabina

[janpieterderuit]

Reading with FLASH_Read API does not cause hardfault, but reading from an erased page will return an error (I think it was kStatus_FLASH_EccError).

So first page should be checked with FLASH_VerifyErase.