Construction of BREW ™ applications can be downloaded to a method September 12, 2003 Author: Qualcomm mobile front line
Once the application is created and tested on the Brew Simulator, you will need to compile its ARM applications. It is recommended to use the RealViewTM Brew Compilation Tool with BREW. You can also use the ARM Developer Suite (ADS). The RealViewTM Brew Compilation Tool is part of the ADS. Step 1: Source code guidelines
There should be no static or global data in the application. Static data can be simulated using a small program data structure. A small program should be built with static or global data and generate location independent code. Since you can introduce your global data, you should check the mapping file after compiling the application, make sure there is no data segment being marked as read or written. Do not include and link "standard C library". Use the AEE memory service (in aeeheap.h) and standard library macros (in aeestdlib.h). For example, using malloc () allocate memory, use WSTRCPY () to copy the Unicode string. In addition to the file name is Isolatin1 / ANSI, BREW is only compatible with Unicode (non-ISOLATIN1 / ANSI). Always use AECHAR instead of "char". Use the string services provided in AeestDlib.h to manipulate strings. Step 2: Installing RealViewTM Brew Compilation Tools / ADS to install the RealViewTM Brew Compilation Tool / ADS in a path that does not contain spaces. It is recommended to install the ARM compiler in the C: / ADS directory. Step 3: Compile ARM
Use the generated file replica in the BREW SDKTM example. Change all references to generate file names and all references to the application name in the file. This generated file is suitable for ADS 1.0.1. To make it apply to the ADS1.1 and RealViewTM Brew Compilation Tools (part of ADS1.1), search for ZA1 in the file and change it to ZO. For ADS 1.0.1: ZA = -ZA1 For ADS 1.1: ZA = -ZO You can check the ADS version by opening the MS-DOS command prompt and type the following command: armcc -vsn If the ARM compiler is in a non-C: / ADS The location is installed, and the generated file and environment variables are required accordingly. Open the MS-DOS command prompt and type the following command: nmake / f myapp.mak all This command will create an ARM executable myApp.mod. Compilation error: ARM compiler WARNING Some warnings are issued during the compilation process. They can be completely ignored:
"Warning: C2067i: The future version of the compiler does not support -zas option" WARNING: C2071W: The future version of the compiler does not support -za option "WARNING: L6305W: The image does not have an entry point. (Due to a variety of options or not specified or Not set). Step 4: Creating a signature file To get a test signature for your application, you need to have permission to access the developer's outslon (access to the developer's outning network, please visit the link: http: // www .qualcomm.com / Brew / Sch / Developer / Become / Authentication.html). Once you log in to the developer's outning network, start the test signature generator (you can from https://brew.qualcomm.com/developer/extranet/support /devtools.jsp is obtained). Enter a valid ESN and (optional) application name.en can find the phone by removing the battery. Replacing the battery. SESIN is used in h: 0xAabbccdd format, located under the first barcode. Format Enter - 0xAabbcdd. Press "Generate" to generate a test signature file, then press Download "to transfer to your computer. Step 5: Transfer your file to the phone to connect your phone to the PC Make sure the phone is powered on. Using BREW Apploader (you can get from https://brew.qualcomm.com/devtool/extranet/support/devtools.jsp Developer's outslonnet). Note: Make sure all files and folders are Under the file system that is transferred to the phone, you will use your lowercase.
Create a new folder "MyApp" under "/". Among them, myApp is your application name. Copy myApp.mod (compiled in step 3) to the "MyApp" folder on the phone. Copy myApp.sig (get the test signature generator in step 4) to the MyApp folder on the phone. If you are using, copy the BAR file "MyApp.bar" to the MyApp folder on the phone. Copy the MIF file "MyApp.mif" into the "/" directory on the phone. You can also copy any other file specific files to the subdirectory of the application directory or application directory. The directory structure on the phone should be as follows:
/myapp.mif- Generate /MYAPP/myapp.mod- Brew MIF Editor with ARM Developer Suite Compile and Link /myApp/myApp.sig- By Test Signature Builder Generate /myApp/myapp.bar (if used) - Generate step 6 by the BREW resource editor: Reset the phone to turn it off again. Your new download BREW application will be under the BREW Apps menu. Keywords: ARM, compile, sign, download, .mif, .sig, .mod,. Bar
