Title: Option to insert 'Extended Segment Address' record type instead of 'Extended Linear Address' · Issue #40 · python-intelhex/intelhex · GitHub
Open Graph Title: Option to insert 'Extended Segment Address' record type instead of 'Extended Linear Address' · Issue #40 · python-intelhex/intelhex
X Title: Option to insert 'Extended Segment Address' record type instead of 'Extended Linear Address' · Issue #40 · python-intelhex/intelhex
Description: Hello, my issue might be considered more as improvement. So I don't know if this is the right place. I've observed that when You want to use write_hex_file, then You cannot decide which type of Extend Address record type will be used in ...
Open Graph Description: Hello, my issue might be considered more as improvement. So I don't know if this is the right place. I've observed that when You want to use write_hex_file, then You cannot decide which type of Ext...
X Description: Hello, my issue might be considered more as improvement. So I don't know if this is the right place. I've observed that when You want to use write_hex_file, then You cannot decide which typ...
Opengraph URL: https://github.com/python-intelhex/intelhex/issues/40
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Option to insert 'Extended Segment Address' record type instead of 'Extended Linear Address'","articleBody":"Hello,\r\nmy issue might be considered more as improvement. So I don't know if this is the right place.\r\nI've observed that when You want to use [write_hex_file](https://github.com/python-intelhex/intelhex/blob/5c15003d08bf53512d5eaa54c7d2825a8b5c37cc/intelhex/__init__.py#L547), then You cannot decide which type of Extend Address record type will be used in hex file:\r\n- Extended Segment Address: record type 0x02\r\nor\r\n- Extended Linear Address: record type 0x04\r\n\r\nAlways second one will be used (0x04) and it cannot be changed as far I can see.\r\nThe code responsible\r\n`while cur_addr \u003c= maxaddr:`\r\n` if need_offset_record:`\r\n` bin = array('B', asbytes('\\0'*7))`\r\n` bin[0] = 2 # reclen`\r\n` bin[1] = 0 # offset msb`\r\n` bin[2] = 0 # offset lsb`\r\n` bin[3] = 4 # rectyp`\r\nI know that having that record type (0x04) shouldn't be a problem for most cases, but I have to deal with some legacy software. I run into problems when this record is not 0x02.\r\nIs there any chance to add an option for 'write_to_hex' to have possibility to have functionality tp force using Extended Segment Address record types in output file.\r\nIn particular scenario when You initialize IntelHex with file that contains this kind of records, writing this with 'write_hex_file' (without changing any byte of payload) will result with differences comparing to original.\r\n\r\nI can try to create a pull request with changes by myself, but I'm not very experienced Python programmer. I do Embedded (mostly C), but I starting to use Python more and more, especially for tooling.","author":{"url":"https://github.com/fernandez85","@type":"Person","name":"fernandez85"},"datePublished":"2020-05-24T12:10:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/40/intelhex/issues/40"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:404f8e90-4718-9517-7515-8fb6f009a821 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E3DE:29F76B:52C1C6:7149FC:698D8B99 |
| html-safe-nonce | 343601cf98f6156796746546a73cebc90daf10abe8bbda4beba18551a1487ee0 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFM0RFOjI5Rjc2Qjo1MkMxQzY6NzE0OUZDOjY5OEQ4Qjk5IiwidmlzaXRvcl9pZCI6IjE4NjkxODIwMzU0MTY2ODEzNzAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 436fa0a00ef8f8877cde5b5d132fc5a3e4ec58c62ec5f5b20adb7bfebf1c09dc |
| hovercard-subject-tag | issue:623852000 |
| github-keyboard-shortcuts | repository,issues,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/_view_fragments/issues/show/python-intelhex/intelhex/40/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d01a67fb6c646eb28428c85548583e71cb3059af61d9bfdc63f6a6f668ca04e6/python-intelhex/intelhex/issues/40 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d01a67fb6c646eb28428c85548583e71cb3059af61d9bfdc63f6a6f668ca04e6/python-intelhex/intelhex/issues/40 |
| og:image:alt | Hello, my issue might be considered more as improvement. So I don't know if this is the right place. I've observed that when You want to use write_hex_file, then You cannot decide which type of Ext... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | fernandez85 |
| hostname | github.com |
| expected-hostname | github.com |
| None | c0818105fa276287e9369cfdefa0a0fa7953719791ceff9b94d69623c0a4fe8a |
| turbo-cache-control | no-preview |
| 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 |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | bd964b0594af16531b06ac03e14711206a3079aa |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width