29 <section id="GUID-566898A8-4655-598F-8430-9E54B440F21E"><title>XIP ROM image</title> <p><b>EKA1</b> </p> <p>In EKA1, an executable file is always uncompressed in |
29 <section id="GUID-566898A8-4655-598F-8430-9E54B440F21E"><title>XIP ROM image</title> <p><b>EKA1</b> </p> <p>In EKA1, an executable file is always uncompressed in |
30 a XIP ROM image. The uncompressed file has had all of its symbols resolved, |
30 a XIP ROM image. The uncompressed file has had all of its symbols resolved, |
31 and can only be executed in its location within the XIP ROM. Files are specified |
31 and can only be executed in its location within the XIP ROM. Files are specified |
32 by using the <codeph>file</codeph> keyword in the <filepath>.oby</filepath> file. |
32 by using the <codeph>file</codeph> keyword in the <filepath>.oby</filepath> file. |
33 The following diagram summarises the situation for EKA1. </p> <fig id="GUID-F781B307-B816-5E86-A92F-81A96D513451"> |
33 The following diagram summarises the situation for EKA1. </p> <fig id="GUID-F781B307-B816-5E86-A92F-81A96D513451"> |
34 <image href="GUID-6E4BA263-5A75-5E8F-9E3A-5517C52DF67E_d0e384771_href.png" placement="inline"/> |
34 <image href="GUID-6E4BA263-5A75-5E8F-9E3A-5517C52DF67E_d0e390624_href.png" placement="inline"/> |
35 </fig> <p><b>EKA2</b> </p> <p>In |
35 </fig> <p><b>EKA2</b> </p> <p>In |
36 EKA2, executables can be placed in the ROM in: </p> <ul> |
36 EKA2, executables can be placed in the ROM in: </p> <ul> |
37 <li id="GUID-6830D039-F67A-5409-9805-ACC34C5AF9C4"><p> <i>uncompressed</i> form |
37 <li id="GUID-6830D039-F67A-5409-9805-ACC34C5AF9C4"><p> <i>uncompressed</i> form |
38 with all of its symbols resolved, and able to be executed in its location |
38 with all of its symbols resolved, and able to be executed in its location |
39 within the XIP ROM. The executable is usually specified by using the <codeph>file</codeph> keyword |
39 within the XIP ROM. The executable is usually specified by using the <codeph>file</codeph> keyword |