Skip to content
This repository was archived by the owner on Jun 5, 2019. It is now read-only.
This repository was archived by the owner on Jun 5, 2019. It is now read-only.

Extended Weak Reference Not Recovered - Data not on 16bit boundary #547

@rrideAMT

Description

@rrideAMT

I found an issue with the Extended Weak Reference implementation that I would like to have some input on from others here that have more in depth knowledge of NET MF implementation.
The issue occurs if the Class created for the EWR results in an even or odd number of bytes in the data array.
When the resulting data array was an even number of bytes (on 16 bit boundary, same as Flash data access) the EWR could be recovered. An odd number of bytes resulted in a CRC check failure on the data as the last byte was not written to the Flash storage area.
I am not sure if the fix should be to the Flash_Driver or should the fix be in the EWR somewhere to pad the data to the 16bit boundary. Right now I made a fix to the Flash_Driver to write/read the additional word to include the remaining byte outside the word boundary. I am concerned this fix may not be best as the Flash Driver is reading and writing an extra byte.
Thanks for any help with this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions