Mantis Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000660LoaderFile Loading/Savingpublic2012-08-27 14:262012-09-04 18:56
ReporterFred 
Assigned Tosean94z 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusassignedResolutionopen 
PlatformAllOSAllOS VersionAll
Product Version0.1.0-SNAPSHOT 
Target Version0.1.0Fixed in Version 
Summary0000660: Add option to rip/save as S1 records instead of S2
DescriptionAgain, for diff compatibility.
TagsNo tags attached.
Issue TypeNew Feature
Risk of Breakagemedium
Attached Files

- Relationships

-  Notes
User avatar (0001926)
sean94z (reporter)
2012-08-27 21:17

What should be the default also should this option be in the advanced tab?
User avatar (0001932)
Fred (administrator)
2012-08-27 21:48

Current way is fine for default, yes to "in advanced tab".
User avatar (0002006)
sean94z (reporter)
2012-09-03 20:32

I can add this, but it seems to go against SREC specifications...

http://en.wikipedia.org/wiki/SREC_%28file_format%29 [^]
S1, S2, S3

Data sequence, depending on size of address needed. A 16-bit/64K system uses S1, 24-bit address uses S2 and full 32-bit uses S3.

thoughts ?
User avatar (0002023)
Fred (administrator)
2012-09-04 17:44

Our addresses can be 24 or 16 depending on the size of the image and what it contains. So yes, add it, please. Obviously it won't be possible to use it on anything with paged data. Handle that properly.
User avatar (0002024)
sean94z (reporter)
2012-09-04 18:28

Right. So you will get a dump of flash that lies within the 16-bit address space.
User avatar (0002025)
Fred (administrator)
2012-09-04 18:56

No, you'll disallow the option to use 16 bit if the addresses fall outside of the base range. To do this right you need to know the meaning of the PPAGE values, which you can, because you know the CPU type from asking the SM...


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker