| ??? 01/14/03 18:23 Read: times |
#36441 - RE: intel format addr translator/editor |
Dan Henry wrote:
------------------------------- If it is truly limited to data, for text files having a constrained format like Intel HEX, I would be inclined to write a utility in C. For text files having a more varied format, text processing languages (with pattern matching) like Awk, Perl, etc. are quite useful and quite handy to have in one's Bag-O-Tricks. Dan, Thanks for the suggestions. As per the reply I just made to Erik, even though what I'm trying to move isn't truly just a block of data (it includes "code"), I am trying to treat it as such as the problem is that the linker is creating the desired "logical" addresses (bank number + 16 bit address) but is not giving it the "physical" address that the hardware (& a Philips utility) are requiring. If I can't verify (in short order) that the compiler upgrade will solve this problem, I'll probably give it a try in Perl (which will be a learning experience for me). Jeff |
| Topic | Author | Date |
| intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
| RE: intel format addr translator/editor | 01/01/70 00:00 | |
RE: intel format addr translator/editor | 01/01/70 00:00 |



