A method for burning VxWorks operating system under PowerPC architecture embedded platform

Abstract

The application discloses a method for burning a VxWorks operating system under a PowerPC architecture embedded platform, and solves the technical problems of high cost, complicated and complex burning process and inability to save and set burning parameters when burning an operating system by using an existing method. The method uses a USB TAP PowerPC emulator of Freescale, uses CodeWarrior software, and realizes burning of the VxWorks operating system based on different CPU platforms of the PowerPC architecture. Compared with a traditional TRACE emulator burning method, the method effectively improves the burning efficiency of the VxWorks operating system and simplifies the operation process of burning.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of PowerPC architecture embedded technology, and particularly relates to a method for burning a VxWorks operating system under a PowerPC architecture embedded platform. BACKGROUND

[0002] At present, the burning method of the operating system of the traditional PowerPC architecture embedded platform is to use the LA series simulator developed by Lauterbach Company, but the simulator has the following disadvantages: long procurement cycle (3-6 months), high price (about 80,000 yuan in total for the main module and the download line), and the burning must be performed using the TRACE32 software, and the burning script needs to be loaded for 3 times and the breakpoint needs to be set each time, so the burning method is complicated and cannot save the settings. SUMMARY

[0003] The present application aims at solving the technical problems of high cost, complicated burning process and inability to save the burning parameters in the prior art, and provides a method for burning a VxWorks operating system under a PowerPC architecture embedded platform.

[0004] To achieve the above object, the technical solution provided by the present application is as follows:

[0005] A method for burning a VxWorks operating system under a PowerPC architecture embedded platform, which is characterized by comprising the following steps:

[0006] 1) modifying the _init.cfg file provided by the CodeWarrior software according to the burning script file *.cmm file of the operating system to be burned;

[0007] 2) adding the FLASH chip model of the circuit board to be burned in the CodeWarrior software;

[0008] 3) using the USB TAP PowerPC simulator to build a hardware burning environment;

[0009] 4) configuring the CodeWarrior software burning environment;

[0010] 5) configuring the FLASH model and specifications;

[0011] 6) erasing the address space of the FLASH to be burned;

[0012] 7) burning the operating system file into the circuit board to be burned.

[0013] Preferably, the modification of the _init.cfg file in step 1) is specifically as follows:

[0014] The corresponding information in the _init.cfg file of the corresponding CPU chip provided by the CodeWarrior software needs to be modified according to the storage space, starting address and address offset of each memory in the *.cmm file.

[0015] Preferably, the addition of the FLASH chip model in step 2) is specifically as follows:

[0016] The FlashProgrammer.txt template file provided by the CodeWarrior software is modified according to the data manual of the corresponding FLASH chip, saved, and then the device_name.txt file is generated using the perl software, and the content in the device_name.txt file is copied into the FPDeviceConfig.xml file of the CodeWarrior software.

[0017] Preferably, after the configuration of the CodeWarrior software burning environment in step 4), the burning parameters and configuration items can be saved to facilitate direct loading next time, avoiding repeated operations.

[0018] The advantages of the present application are:

[0019] 1. The present application realizes the transplantation of the burning method from TRACE32 to CodeWarrior by modifying the burning script _init.cfg provided by the CodeWarrior software, and once the burning environment in CodeWarrior is configured, the saved parameters can be directly called next time, without the need for repeated operations.

[0020] 2. The present application uses the USB TAP PowerPC emulator, which only needs to build the burning environment and save the relevant settings, and the subsequent burning operation can be completed by simple operation.

[0021] 3. The present application can avoid the complicated and difficult-to-use burning process when burning the operating system, so that the burning process is simple, fast and easy to use. Compared with the traditional TRACE emulator burning method, the present application effectively improves the burning efficiency of the VxWorks operating system and simplifies the operation process. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 is the operation flowchart of the present application;

[0023] Figure 2 is the CodeWarrior burning parameter configuration diagram of the present application;

[0024] Figure 3 is the FLASH model and configuration diagram of the present application;

[0025] Figure 4 is the FLASH erase operation diagram of the present application;

[0026] Figure 5 is the file burning operation diagram of the present application. DETAILED DESCRIPTION

[0027] The present application will be further described in detail below in combination with the drawings and specific embodiments:

[0028] As shown in the figure, the method for burning the VxWorks operating system under the PowerPC architecture embedded platform of the present application comprises the following steps: Figure 1 1) Modify the *_init.cfg file provided by the CodeWarrior software according to the burning script file *.cmm file of the operating system to be burned.

[0029] Among them, the *_init.cfg file corresponding to the CPU model of the circuit board to be burned needs to be found in the installation directory of the CodeWarrior, including the configuration of each chip enable signal, clock configuration, CPU peripheral memory address allocation, etc.

[0030] There are three main items to be configured: LAW, DDR and MMU.

[0031] Open the file using Notepad, find the corresponding area in *.cmm and *_init.cfg respectively, and modify the corresponding address in *_init.cfg to be consistent with the address in *.cmm.

[0032] Among them, the LAW item is to configure the start address and end address of the correct FLASH, DDR, NVRAM and DPRAM for the CPU; the DDR item is to configure the correct mode, clock, enable, address, etc. for the SDRAM; and the last MMU item is to configure the address space for the CPU to burn the operating system.

[0033] 2) Add the FLASH chip model of the circuit board to be burned in the CodeWarrior software.

[0034] CodeWarrior comes with a part of FLASH models, but it cannot cover all FLASH chip models, so if the FLASH chip of the circuit board to be burned is not among them, the used FLASH chip needs to be added manually.

[0035]

[0036] ​Firstly, the template file FlashProgrammer.txt in CodeWarrior software needs to be modified according to the data manual of the corresponding FLASH chip, and then saved to generate the device_name.txt file by using perl software. The content in the device_name.txt file is copied to the FPDeviceConfig.xml file in CodeWarrior software.

[0037] 3) Build the hardware burning environment by using the USB TAP PowerPC emulator.

[0038] Connect the USB end of the USB TAP PowerPC emulator with the PC, and connect the JTAG connector end with the JTAG socket of the CPU chip of the circuit board to be burned. In this embodiment, the USB TAP PowerPC emulator of Freescale is used.

[0039] 4) Configure the burning environment of CodeWarrior software.

[0040] Open the Flash Programmer menu in CodeWarrior, select the CPU series, the CPU specific model, the emulator model and the modified _init.cfg file in Target Configuration according to the actual situation, and fill in the storage cache address and the storage cache capacity according to the burning script requirements, as shown in Figure 2

[0041] 5) Configure the FLASH model and specifications.

[0042] Fill in the base address of the FLASH chip, select the chip model and the chip specifications in Flash Configuration under the Flash Programmer menu, as shown in Figure 3

[0043] 6) Erase the address space of the FLASH to be burned.

[0044] Check All Sectors in Erase / Blank Check under the Flash Programmer menu, and click Erase to erase, as shown in Figure 4

[0045] 7) Burn the operating system *.bin file into the circuit board to be burned.

[0046] ​​​Select the operating system file and its type to be burned under Program / Verify in the Flash Programmer menu, fill in the compensation address, and click Program to burn, as shown in Figure 5

[0047] When the normal burning of the operating system is completed according to the above steps, the configuration parameters from step 3) to step 7) can be saved by clicking Save Setting in the Flash Programmer interface, and the saved parameters can be loaded in Load Setting next time when burning.

[0048] Thus, the burning of the VxWorks operating system under the PowerPC architecture embedded platform can be simply, effectively and quickly completed.

[0049] The above is merely a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed by the present application, and these modifications or replacements shall be encompassed within the protection scope of the present application.​

Claims

1. A method for burning VxWorks operating system under PowerPC architecture embedded platform, characterized in that, The steps include: 1) Modify the _init.cfg file provided by CodeWarrior software according to the burning script file *.cmm file of the operating system to be burned; There are three projects to be configured, namely LAW item, DDR item and MMU item. The LAW item is to configure the starting address and ending address of the CPU for the correct FLASH, DDR, NVRAM and DPRAM. The DDR item is to configure the correct mode, clock, enable and address for SDRAM. The last MMU item is to configure the address space of the CPU for burning the operating system; 2) Add the FLASH chip model of the circuit board to be burned in CodeWarrior software; According to the data manual of the corresponding FLASH chip, modify the FlashProgrammer.txt template file provided by CodeWarrior software, save it, use perl software to generate device_name.txt file, and then copy the content in device_name.txt file to FPDeviceConfig.xml file in CodeWarrior software; 3) Use USB TAP PowerPC emulator to build a hardware burning environment; 4) Configure the CodeWarrior software burning environment; Open the Flash Programmer menu in CodeWarrior, select the CPU series, CPU specific model, emulator model and modified _init.cfg file in Target Configuration according to the actual situation, and fill in the storage cache address and storage cache capacity according to the burning script requirements; 5) Configure the FLASH chip model and specification; 6) Erase the address space of the FLASH to be burned; 7) Burn the operating system *.bin file into the circuit board to be burned; After completing the normal burning of the operating system, click Save Setting in the Flash Programmer interface to save the configuration parameters of steps 3) to 7). Next time, load the saved parameters in Load Setting when burning.

2. The method of claim 1, wherein the PowerPC architecture embedded platform is a Freescale QorIQ P2020 platform. Step 1) Modify the _init.cfg file specifically: According to the storage space, starting address and address offset of each memory in the *.cmm file, modify the corresponding information in the _init.cfg file of the corresponding CPU chip provided by CodeWarrior software.

Images