-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Method to restore EEPROM values #85
Comments
Same request here! |
For reference, this is the EEPROM data of one of my sensors in a way it can be loaded in a C program: Warning!
|
Here is mine dump, maybe will be useful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like a number of other people here, I've got lots of 65535 / 0xFF / FFFF in my EEPROM data resulting in an unusable $50 sensor. My sensor seemed to be all fine until I used the mlx90640 on a jetson nano. So if the EEPROM can be corrupted by the user - surely it must be possible to restore values to it. At this point, I don't mind if its not factory calibrated EEPROM data - I just don't was a $50 very light paperweight.
Using the C API, I get I2C Read Error! whenever it calls MLX90640_I2CRead() - and zeros are returned from MLX90640_DumpEE(MLX_I2C_ADDR, eeMLX90640).
Using the python bindings it does manage to get to a state where I can dump the EEPROM data, so I can see the values have been corrupted.
Reading through the MLX90640 docs it seems there is a way to upload EEPROM data using the windows-based melexis mlx90640 viewer/controller .exe but could this functionality be included in this library? It would be very helpful to a lot of people here!
Thanks,
The text was updated successfully, but these errors were encountered: