Title: Added support for segment addresing in output hex files by mmajchrzycki · Pull Request #5 · python-intelhex/intelhex · GitHub
Open Graph Title: Added support for segment addresing in output hex files by mmajchrzycki · Pull Request #5 · python-intelhex/intelhex
X Title: Added support for segment addresing in output hex files by mmajchrzycki · Pull Request #5 · python-intelhex/intelhex
Description: I recently met a problem with application which requires Intel HEX files but with segment addressing instead of linear. So I added another (shex - segment hex) output format for hex files.
Open Graph Description: I recently met a problem with application which requires Intel HEX files but with segment addressing instead of linear. So I added another (shex - segment hex) output format for hex files.
X Description: I recently met a problem with application which requires Intel HEX files but with segment addressing instead of linear. So I added another (shex - segment hex) output format for hex files.
Opengraph URL: https://github.com/python-intelhex/intelhex/pull/5
X: @github
Domain: patch-diff.githubusercontent.com
| route-pattern | /:user_id/:repository/pull/:id/files(.:format) |
| route-controller | pull_requests |
| route-action | files |
| fetch-nonce | v2:45f42665-0285-8991-759d-7a08bd6f4084 |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | A9CE:CFD44:3B965:4DBB6:698DEEA7 |
| html-safe-nonce | 3a49d07b764154fc088e9803fda6c65837bf7067ed9c1f84b09a2b1df6bbc0f8 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBOUNFOkNGRDQ0OjNCOTY1OjREQkI2OjY5OERFRUE3IiwidmlzaXRvcl9pZCI6IjQyODc4NzQxNjM1NzY1MzI2NDciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | efcf63fe65b37bc03f348ef282fdd5d9af0f62e5d81251e6f7ad153a6296de37 |
| hovercard-subject-tag | pull_request:67184349 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/python-intelhex/intelhex/pull/5/files |
| twitter:image | https://avatars.githubusercontent.com/u/6490687?s=400&v=4 |
| twitter:card | summary_large_image |
| og:image | https://avatars.githubusercontent.com/u/6490687?s=400&v=4 |
| og:image:alt | I recently met a problem with application which requires Intel HEX files but with segment addressing instead of linear. So I added another (shex - segment hex) output format for hex files. |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 929d0ce8b653d60df0698366d7e9012f9423ea1bace40816e16e5b007242aae4 |
| turbo-cache-control | no-preview |
| diff-view | unified |
| go-import | github.com/python-intelhex/intelhex git https://github.com/python-intelhex/intelhex.git |
| octolytics-dimension-user_id | 55888006 |
| octolytics-dimension-user_login | python-intelhex |
| octolytics-dimension-repository_id | 33128473 |
| octolytics-dimension-repository_nwo | python-intelhex/intelhex |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 33128473 |
| octolytics-dimension-repository_network_root_nwo | python-intelhex/intelhex |
| turbo-body-classes | logged-out env-production page-responsive full-width |
| disable-turbo | true |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 143e58641f5eb460a02eda3a18cc1ef28e8c5188 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width