Skip to content
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

Config writer needs flash ID verification #10

Open
cr opened this issue Apr 11, 2019 · 3 comments
Open

Config writer needs flash ID verification #10

cr opened this issue Apr 11, 2019 · 3 comments

Comments

@cr
Copy link
Owner

cr commented Apr 11, 2019

The config writer currently happily rewrites the flash ID at offset 0x100 with a mismatching value, but it should warn the user if they try and ask if they are --really sure.

@johannessen
Copy link
Contributor

johannessen commented Apr 11, 2019

At first glance, I misread this and thought you would like a warning before overwriting the MMSI – something that has been discussed on the HX870 mailing list as a possible enhancement of the YCE15 software. My bad.

But is overwriting the data at 0x100 really an issue? I've been doing it the entire time since I started using pyhx870 and there was never a problem. The device seems to simply ignore that. It gives back the updated data on 0x100 next time you read it.

BTW, I highly doubt this is a flash ID. The values are changing every time I dump the device's memory. They appear to be some sort of time stamp, plus other data that I haven't figured out.

@johannessen
Copy link
Contributor

Oh, actually the time stamp thing is at 0x110. I apologise – I really shouldn’t have commented without checking the memory layout table first.

Please disregard my earlier comment!

@cr
Copy link
Owner Author

cr commented Apr 11, 2019

By the way, that location at 0x110 contains the date (YYMMDD), time (HHMM), and GPS coordinates (internal coordinate format) where the radio was last turned off.

johannessen added a commit to johannessen/hx870 that referenced this issue Nov 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants