A Simple Migration Checklist for HiSilicon

This practical migration checklist guides your move from a generic ARM platform to a HiSilicon SoC. You are likely familiar with the ARM Cortex-A7 processor, a staple in mobile smartphones for its excellent power efficiency. Your goal is to achieve superior performance and power management.

The ARM Cortex-A7 often uses a big.LITTLE architecture. Understanding this big.LITTLE power model is key. The big.LITTLE power design offers great power savings. Your new processor must improve on this power. The big.LITTLE power concept is vital. This big.LITTLE power is for mobile smartphones. The big.LITTLE power is for mobile smartphones. The big.LITTLE power is for mobile smartphones. The big.LITTLE power is for mobile smartphones.

This migration checklist simplifies the process into four core phases:

Pre-Migration Analysis
Low-Level System Porting
Driver and Middleware Adaptation
Application Validation

Key Takeaways

Plan your migration carefully. Compare your old ARM platform with the new HiSilicon hardware. This helps you understand the changes.
Set up your development tools. Use the HiSilicon SDK and toolchain. This prepares your system for the new processor.
Port the bootloader and Linux kernel. Use HiSilicon's specific code. This makes the core software run on the new hardware.
Adapt drivers and middleware. Replace old drivers with HiSilicon's optimized versions. This unlocks the hardware's full power.
Validate your applications. Recompile your apps and test the system. This ensures good performance and power use.

PRE-MIGRATION ANALYSIS

A successful migration begins with careful planning. You must first analyze the differences between your current ARM platform and the new HiSilicon hardware. This phase ensures you have the right tools and a clear understanding of the hardware changes.

HARDWARE FEATURE MAPPING

You need to create a detailed map of hardware features. Your previous platform likely used an ARM Cortex-A7 processor, known for its big.LITTLE power model in mobile smartphones. The goal is to leverage the superior performance and power efficiency of a HiSilicon octa-core processor. An octa-core design often enhances the big.LITTLE processing concept for better task management.

Compare every component. Document the specifics of your old ARM processor and contrast them with the new octa-core chip. This comparison highlights the advancements in power and performance. The big.LITTLE architecture in older Cortex-A7 processors was a leap in power efficiency for mobile smartphones. Your new octa-core processor builds on this big.LITTLE foundation. The ARM Cortex-A7 is a capable processor, but the move to an octa-core ARM platform unlocks new levels of performance. This is especially true for demanding mobile applications in modern smartphones. The big.LITTLE power design is central to the power efficiency of many ARM Cortex-A7 processors used in smartphones. Your migration should capitalize on the evolution of this big.LITTLE power model.

Note: A feature-by-feature comparison table is your best tool here. List peripherals like GPIO, I2C, SPI, and multimedia engines. This map will become your guide during driver adaptation. The big.LITTLE power concept is key to the power efficiency of the ARM Cortex-A7.

Feature	Generic ARM Cortex-A7	HiSilicon Octa-Core
CPU Core	Dual/Quad-core big.LITTLE	Advanced octa-core big.LITTLE
GPU	Generic Mali series	HiSilicon-specific GPU
Video Engine	Standard VPU	Media Process Platform (MPP)
Power Mgmt	Standard PMIC	Enhanced power management

TOOLCHAIN AND SDK SETUP

Next, you must set up the correct development environment. You will replace the generic ARM toolchain with the specialized HiSilicon SDK. This SDK contains the necessary compilers, libraries, and headers optimized for the new processor.

To configure your project, you will use a specific toolchain file provided by HiSilicon.

Download and place the HiSilicon SDK in a directory like /opt/hisi-linux/x86-arm.
Navigate to your project and create a build directory.
Invoke CMake with the -DCMAKE_TOOLCHAIN_FILE flag, pointing to the correct HiSilicon toolchain file (e.g., hisiv500.toolchain.cmake).
Build your project using make.

For efficient development, you should also configure a network boot environment. This involves setting up TFTP and NFS servers on your development PC. This setup allows you to quickly deploy and test new kernel images and root filesystems on the target board without flashing storage media each time.

TFTP Server Setup: Install a TFTP server (like atftpd or tftp-server) and configure its root directory (e.g., /tftpboot). You will place your kernel image (uImage) here.
NFS Server Setup: Install the nfs-kernel-server package. You will then export your root filesystem directory by adding an entry to the /etc/exports file and restarting the service.

This preparation streamlines the entire porting process that follows.

LOW-LEVEL SYSTEM PORTING

You are now entering the most technical phase of the migration. This stage focuses on making the core software—the bootloader and the Linux kernel—run on your new HiSilicon hardware. Your starting point must be the HiSilicon-specific source code from their SDK. Generic code will not work for the unique architecture of the new octa-core ARM processor. This work is vital to leverage the advanced big.LITTLE power model, a significant upgrade from your previous ARM Cortex-A7 processor.

BOOTLOADER CONFIGURATION

First, you will configure U-Boot, the bootloader. You must compile a U-Boot image specifically for your HiSilicon octa-core platform. Once compiled, you need to flash this image onto the board's storage, like SPI flash or eMMC.

A common method involves using a network connection:

Set your board's U-Boot environment to connect to your development PC's IP address.
Transfer the bootloader image to the board's RAM using TFTP.
Write the image from RAM 경쟁 to the flash memory using the mmc write or an equivalent command.

After flashing, you must configure U-Boot environment variables. These variables tell the bootloader where to find the kernel and what parameters to pass to it. You will set bootargs to define kernel command-line options. This step is crucial for the new ARM processor to boot correctly, managing its big.LITTLE power configuration for mobile applications. The old ARM Cortex-A7 processor in mobile smartphones also relied on this, but the new octa-core ARM chip offers superior efficiency.

Image	File Name	RAM Address
Linux kernel	`bootfile`	`kernel_addr_r`
Device tree blob	`fdtfile`	`fdt_addr_r`
Ramdisk	`ramdiskfile`	`ramdisk_addr_r`

KERNEL PORTING

Next, you will port the Linux kernel. You must use the kernel source provided in the HiSilicon SDK. This source contains the necessary drivers and configurations for the octa-core ARM processor. The goal is to unlock the performance and power efficiency of the new big.LITTLE architecture, far surpassing the old ARM Cortex-A7.

The most critical task here is updating the Device Tree Source (DTS) file.

The DTS is the blueprint for your hardware. It tells the Linux kernel how peripherals are connected to the ARM processor. You must modify the DTS to match your board's specific layout, ensuring every component is correctly recognized by the system.

Your modifications will enable the kernel to properly initialize the advanced big.LITTLE processing of the octa-core chip. This ensures optimal power management, a key feature for modern mobile smartphones. A correct DTS is essential for the stability and performance of your new system, harnessing the full power of the ARM Cortex architecture. This big.LITTLE power design is a leap forward from the ARM Cortex-A7 processor used in older smartphones. The big.LITTLE power model is central to the efficiency of your new mobile device.

DRIVER AND MIDDLEWARE ADAPTATION

With the low-level system booting, you will now adapt the software that sits between the kernel and your applications. You must replace generic drivers with HiSilicon's optimized versions. This step is essential to unlock the full hardware potential of the new octa-core arm processor and its advanced big.little power architecture. Your goal is to maximize performance and power efficiency.

PERIPHERAL DRIVER MIGRATION

You need to migrate your peripheral drivers. This involves replacing standard Linux drivers for components like I2C, SPI, and GPIO with the specific drivers found in the HiSilicon SDK. The most significant challenge is often the multimedia framework. The new octa-core arm processor offers superior media capabilities.

Your biggest task is migrating from standard frameworks like V4L2 (for video) and ALSA (for audio) to HiSilicon's proprietary Media Process Platform (MPP). This platform is highly optimized for the arm cortex processor. It directly controls the hardware video encoders and decoders, delivering performance that generic APIs cannot match. This is critical for modern mobile smartphones that rely on efficient video processing. The big.little power model of the arm cortex processor helps manage this workload.

Adapting your application to use the MPP APIs is non-trivial but necessary. It is the key to leveraging the hardware acceleration of the arm cortex processor, ensuring smooth media playback and recording on mobile smartphones. The big.little power design ensures this performance does not drain the battery. This is a major benefit over older arm cortex platforms.

FILESYSTEM AND STORAGE

Next, you must configure the filesystem and storage drivers. Your board may use raw NAND flash, which requires a specialized filesystem like the Unsorted Block Image File System (UBIFS). You need to enable the correct options in the kernel to support it. This ensures data integrity and manages flash wear, which is vital for the longevity of mobile smartphones. The big.little power model of the arm processor contributes to overall system stability and power efficiency.

Enable CONFIG_MTD_UBI=y in your kernel configuration.
Enable CONFIG_UBIFS_FS=y to add filesystem support.

You then instruct the kernel to use this filesystem by modifying the boot arguments. The bootargs variable in U-Boot tells the kernel where to find the root filesystem. For a UBIFS setup, your boot arguments will look similar to this:

ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs

This command attaches the first MTD device to UBI and mounts the "rootfs" volume. A correctly configured filesystem is fundamental for a stable system on your new octa-core arm processor. It ensures the big.little power architecture of the arm cortex processor operates with maximum efficiency for demanding mobile applications on smartphones. The big.little power design is central to the processor's low power consumption.

APPLICATION VALIDATION: THE FINAL MIGRATION CHECKLIST

You have reached the final stage of your migration checklist. This phase validates all your porting efforts. You will now recompile your applications and conduct rigorous system testing. This ensures your product meets its performance and power targets.

APPLICATION RECOMPILATION

First, you must recompile your application source code. You will use the HiSilicon toolchain you configured earlier. This step links your software with the new, optimized system libraries. Your application can now access the hardware's full potential.

Tip: Pay close attention to linking against HiSilicon's proprietary libraries, like the Media Process Platform (MPP). This is essential for achieving high performance in multimedia applications for mobile smartphones. Proper linking unlocks significant power savings.

Your build process will now use the new cross-compiler. A typical command might look like this:

cmake .. -DCMAKE_TOOLCHAIN_FILE=hisiv500.toolchain.cmake
make

This process ensures your application is ready for the new hardware. It is a critical step for the power and efficiency of mobile devices.

SYSTEM TESTING AND DEBUGGING

Next, you will perform comprehensive system testing. Your goal is to verify stability, performance, and power consumption. You should create a detailed test plan covering all critical functions for mobile smartphones.

Your testing should include several key areas:

Functionality Tests: Confirm that all peripherals and application features work as expected.
Performance Benchmarks: Measure CPU, memory, and graphics performance to validate improvements.
Stress Tests: Run the system under heavy load to check for thermal issues and stability. This tests the system's power management.

Measuring power is the most important part of this final migration checklist. You must verify the system's power usage in different states, such as idle, full load, and standby. This validation confirms the power efficiency of your new platform. Excellent power management is vital for the battery life of mobile smartphones. Your tests must prove the system's low power draw. This ensures the final product delivers on its promise of superior performance and low power for mobile smartphones.

Your migration checklist journey ends here. You successfully navigated the main challenges of adapting to HiSilicon's specific hardware and arm software stack. The most critical adaptations for your arm cortex system involved the bootloader, the kernel Device Tree (DTS), and the proprietary Media Process Platform (MPP) APIs. These changes unlock superior power management for mobile smartphones. Your new arm platform now has the foundation for excellent power efficiency, a key goal for all mobile smartphones.

A thorough final validation is the last step. This testing confirms your system's stability and performance. You must verify the low power draw of the arm cortex chip. This ensures the great battery power modern mobile smartphones require. The arm architecture's low power design is vital for the success of mobile smartphones. Your arm system's power efficiency is crucial for mobile smartphones. The arm cortex processor's low power is a win for smartphones.

Written by Wyatt Yan from ic-online.com

ic-online.com is a fast-growing global electronic components distributor and a trusted ERAI member, delivering authentic parts and secure supply chain solutions to customers worldwide.

We provide millions of in-stock ICs and semiconductors with same-day shipping, while offering complete one-stop BOM sourcing and turnkey PCBA services, including PCB fabrication, SMT assembly, and full production support.

From prototype to mass production, we help engineers and buyers reduce costs, shorten lead times, and simplify procurement.

One BOM. One Partner. One Complete PCBA Solution.

Visit ic-online.com and submit your RFQ today.

FAQ

How does the new big.little design improve power?

Your new arm platform enhances the big.little architecture. It manages tasks more efficiently than the old arm cortex a7. This results in better power savings for mobile devices. Your smartphone gains longer battery life and improved thermal performance, a key goal for modern smartphones.

What security benefits does this migration offer?

You gain enhanced system security. The new arm cortex platform provides robust hardware security features. These features protect user data on the smartphone. This focus on security is vital for data security and privacy, giving you a more secure foundation for your applications on smartphones.

Can this platform handle data mining on smartphones?

Yes, it excels at tasks like human activity recognition. The improved performance and security are ideal for data mining on smartphones. Your applications get strong privacy protections. The platform's security architecture is crucial for smartphone-based data mining and protecting user privacy on all smartphones.

This robust security is essential for any application involving human activity recognition. Your smartphone must ensure user privacy.

Why is this migration good for high-performance mobile apps?

This migration unlocks superior smartphone performance. The advanced arm cortex processor surpasses the older a7. Its big.little design optimizes power for demanding tasks like human activity recognition. This platform provides the security and performance needed for high-performance mobile applications and data mining on smartphones.