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

[feature] Caching and diffing bin/hex #1366

Open
lefebvresam opened this issue Feb 5, 2024 · 1 comment
Open

[feature] Caching and diffing bin/hex #1366

lefebvresam opened this issue Feb 5, 2024 · 1 comment

Comments

@lefebvresam
Copy link

In most of the cases when you are programming you only change small pieces of code. It means that the bin/hex is changed only slightly based on the previous one. When you program the device, all blocks are programmed again. It means that even when you change a small string value, all 40 or 50 memory blocks are re-programmed again and you have to wait all the times for 40sec because the max programming speed is 4Mbps. Should it be possible to check which blocks have been changed based on the previous bin/hex and only program those which are different? It could speedup the development cycle a lot. It could be an option to provide --non-caching or something like that to reprogram the whole flash.

@Nightwalker-87
Copy link
Member

Likely a duplicate of #1238.

@Nightwalker-87 Nightwalker-87 pinned this issue Feb 5, 2024
@Nightwalker-87 Nightwalker-87 changed the title [feature] Chaching and diffing bin/hex [feature] Caching and diffing bin/hex Feb 10, 2024
@Nightwalker-87 Nightwalker-87 removed their assignment Feb 20, 2024
@Nightwalker-87 Nightwalker-87 unpinned this issue Mar 10, 2024
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