Message Edited by rocco on 2006-08-12 01:14 PM
Tank you for you aid. I'm using 908LJ12, also I'm using CW 3.1. Desire that the CODE section this a continuation of PARAMETERS section at the time of compiling it, but it seems to me that the compiler does not accept another section to me although I have defined it in the .PRM file.
When I say to "complier" I refer to the united compiler and linker. Desire that the PARAMETERS SECTION and the CODE SECTION are located in the segment ROM, one to continuation of the other respectively. In the .PRM file, I generate this sections, but in the .MAP file they do no appear. When I enter to debug, the PARAMETER SECTION is not present.
Before nothing tanks.
Correct Rocco, it is exactly what I want to do, but the CW this not taking it. I am going to return to prove and I say to them that is happened.
Tanks to you two. (Gracias a los dos)
/* This is a linker parameter file for the LJ12 */NAMES END /* CodeWarrior will pass all the needed files to the linker by command line. But here you may add your own files too. */
SEGMENTS /* here all RAM/ROM areas of the device are listed. Used in PLACEMENT below. */ Z_RAM = READ_WRITE 0x0060 TO 0x00FF; RAM = READ_WRITE 0x0100 TO 0x025F; EEPROM = READ_ONLY 0xC000 TO 0xC1FF; ROM = READ_ONLY 0xC200 TO 0xEFFF;END
PLACEMENT /* here all predefined and user segments are placed into the SEGMENTS defined above. */ PARAMETERS INTO EEPROM; DEFAULT_ROM INTO ROM; DEFAULT_RAM INTO RAM; ZEROPAGE INTO Z_RAM;END
VECTOR 18 RTIIsrVECTOR 1 TickIsrVECTOR 0 Entry /* reset vector: this is the default entry point for a Assembly application. */INIT Entry /* for assembly applications: that this is as well the initialization entry point */
Or alternatively write
PARAMETERS, CODE INTO EEPROM;
This will also place CODE right after PARAMETERS into EEPROM.
Retrieving data ...