| [<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Subject:
__CONFIG in gpasm
From: Scott Dattalo ####@####.#### Date: 24 Jan 2000 18:55:33 -0000 Message-Id: <Pine.LNX.4.05.10001241236250.26513-100000@tempest.blackhat.net> I had to make significant modifications to the __CONFIG directive logic (do_config()) in gpasm to accomodate the 18cxxx configuration words. The code works except for one caveat - the hex files are limited to 64k (and the 18cxxx configuration words are at address with a 0x300000 base). - How does mpasm get around this problem? (I think I know...) - Would anyone object if for now that the 18cxxx configure words are placed at addresses based 0xf000? (Because I don't have the time right now to do it correctly.) Scott | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| [<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||