{"id":981,"date":"2013-09-14T10:49:58","date_gmt":"2013-09-14T05:19:58","guid":{"rendered":"http:\/\/www.e-consystems.com\/blog\/windowsce\/?p=981"},"modified":"2023-08-15T12:31:28","modified_gmt":"2023-08-15T07:01:28","slug":"wec2013-understanding-startuptext-macro","status":"publish","type":"post","link":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wec2013-understanding-startuptext-macro\/","title":{"rendered":"WinCE2013-Understanding STARTUPTEXT macro-Part1"},"content":{"rendered":"

On continuation of Windows Embedded Compact 2013 porting blog series, I would like to share about the change in STARTUPTEXT macro and its effect on WinCE2013. Before that we have to understand the purpose of this macro.<\/p>\n

STARTUPTEXT is used in assembly file (.s) before the first assembly routine to indicate the linker in order to place the code very first location in the CODE section.<\/p>\n

\"startup\"<\/p>\n

Figure 1) sample startup.s file<\/p>\n

This is mapped to .astart segment as shown below in earlier versions of Windows CE. You can find the below macro definition in \\<_WINCEROOT>\\PUBLIC\\COMMON\\SDK\\INC\\kxarm.h<\/p>\n

\"startuptext\"<\/p>\n

Figure 2) STARTUPTEXT Macro in earlier version of Windows CE.<\/p>\n

You can see the below map file of the sample executable where the StartUp routine is placed very first in the code section.<\/p>\n

\"MAP-WEC7\"
map file WEC7<\/figcaption><\/figure>\n

Figure 3) .MAP file for an executable in WEC7<\/p>\n

Now come back to WinCE2013. Here this macro is mapped to TEXTAREA which is .text segment as shown below.<\/p>\n

\"startuptext-wec2013\"<\/p>\n

Figure 4) STARTUPTEXT macro in WinCE2013<\/p>\n

Because of this change, the StartUp code is linked in .text segment, which is the 3rd segment of code section as shown below.<\/p>\n

\"map-wec2013-1\"<\/p>\n

\"map-wec2013-2\"<\/p>\n

Figure 5) .Map file for an executable in WinCE2013<\/p>\n

Even changing the STARTUPTEXT Macro to .astart segment won\u2019t work out here, since the linker is ignoring the .astart segment when we simply replace the .text<\/strong> to .astart<\/strong>. Due to this reason, you can\u2019t expect the entry point of the executable at 0th location. Which means in an .nb0 file, you can\u2019t expect the entry point routine (StartUp) immediately after the 4KB jump page introduced by ROMIMAGE tool. This is vary based on the location where the .text segment is started in the executable. In our example, it is 0x000040e0 (0x1000 + 0x000030e0) as shown below.\"startup_lst\"<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

Figure 6) Startup.lst file<\/p>\n

\"nbo_file\"<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

Figure 7).nb0 file<\/p>\n

As I already mentioned in the previous article<\/a><\/strong>, ROMIMAGE tool generate jump instruction((BLX BaseAddress+000040e1) at the beginning of the 4K page (jump page) for .nb0 and generate the start address (BaseAddress+000040e1) for nk.bin.<\/p>\n

Considerations<\/strong><\/p>\n

There are some size constrained binaries specifically pre bootloaders such as XLDR\/IPL are loaded by processor boot ROM from NAND\/SD card to a small size SRAM and this will load the Eboot to DDR and jump to Eboot. Mostly this is an .nb0 file since the processor boot ROM doesn\u2019t have intelligence to read the .bin format. Due to the size constraints for the XLDR, the jump page is removed to reduce the binary size in few processor BSPs. This works in earlier versions of Windows CE since the StartUp entry point is always start after the jump page when STARTUPTEXT is used. But for Windows Embedded Compact 2013, you can\u2019t cut the jump page. Since the Startup entry point is not fixed and it is based on the .text segment starting location. This entry point is known only to the jump instruction in the jump page.<\/p>\n

Cutting the jump page is not the right way to reduce the binary size for XLDR\/IPL until you did some tweaks (which I will explain in the next part<\/a> ) to fix the entry point at the beginning, instead you can find some other ways such as removing unnecessary debug messages and code from the source files and its included libraries.<\/p>\n

 <\/p>\n

<\/p>\n

\n

<\/p>\n

Figure 1) sample startup.s file<\/p>\n

Figure 1) sample startup.s file <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

On continuation of Windows Embedded Compact 2013 porting blog series, I would like to share…<\/p>\n","protected":false},"author":12,"featured_media":1271,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[190,72],"tags":[166,164,165,145],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/posts\/981"}],"collection":[{"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/comments?post=981"}],"version-history":[{"count":26,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/posts\/981\/revisions"}],"predecessor-version":[{"id":1929,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/posts\/981\/revisions\/1929"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/media\/1271"}],"wp:attachment":[{"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/media?parent=981"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/categories?post=981"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.e-consystems.com\/blog\/windowsce\/wp-json\/wp\/v2\/tags?post=981"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}