-
Notifications
You must be signed in to change notification settings - Fork 104
Best practices for adding more config keys #59
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
Comments
IIRC, I used the full version of Adobe Acrobat to export the PDF as an xlsx spreadsheet. It was then a couple of hours work to extract and format just the keys and their descriptions from the relevant cells. IIRC having the data in xlsx format made it much easier to discard the surrounding text, like headers and footers etc.. But, for new keys, there must be a simpler way to do this. I suspect the various pdf diff tools that are out there will fail as the differences between say the F9P and the F9T interface descriptions will be huge. However, there may be a 'quick' way to extract just the hex keys making it easier to spot any new ones with a simple diff. I shall think on this... |
Here's a method which works. It's not particularly quick or elegant, but it works...
Use KDiff3 or another diff package to see the new additions. |
“strings <file.pdf>“ should get you the relevant text. strings file.doc | more is the way we used to read Microsoft word documents on Sun workstations in the mid-90’s 😀 I suppose Perl Regex after that for extraction… |
Amazing. Thanks Paul! And this should serve as a 'how to' to our future selves. |
The ZED-F9R introduces some additional config keys, namely the ESF range of keys (ex: CFG-MSGOUT-UBX_ESF_ALG_I2C). I suspect the ZED-F9T adds a few as well and more modules are always looming on the horizon.
The text was updated successfully, but these errors were encountered: