Technical Analysis of ARM7&ARM9 Dual-core Platform

Publisher:SereneHarmonyLatest update time:2014-08-21 Source: eefocusKeywords:WinCE  Linux  uClinux Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

       At present, the leading products in the embedded system teaching platform market are based on ARM7 or ARM9 architecture. It is generally believed that ARM7 is a low-end product and ARM9 is a high-end product. There is also a so-called "ARM7 & ARM9 covering high-end & low-end teaching platform". It is advertised that "both sets of CPU sub-boards can be freely plugged and unplugged, and one set of experimental system can be changed into two sets. The ARM7 experimental system can realize basic ARM embedded teaching, mainly including instruction experiments, basic interface experiments, UCOS-II operating system experiments and uCLinux operating system experiments; the ARM9 experimental system can realize high-end ARM embedded teaching, mainly including extended interface experiments, Linux operating system experiments and WinCE operating system experiments." 

       This view is suspected of misleading users. Because ARM9 and ARM7 belong to ARMv41, they are low-end series of ARM microprocessors. At present, the real high-end ARM architecture processors on the market are Intel XScale compatible with the ARMV5TE system, such as PXA255 and PXA270. 

       From the perspective of the development of embedded system teaching platforms, there will be two development directions in the future. That is, on the one hand, it develops towards the high-end XScale series, which is mainly aimed at computer, software and other majors. This type of high-end platform has powerful computing power and multimedia functions. The teaching content focuses on operating systems, drivers and software applications, and cultivates embedded software talents in the fields of consumer electronics, handheld devices, wireless networks, mobile games, etc.; on the other hand, it is the mid- and low-end teaching platform of the ARM7/ARM9 series, which is mainly aimed at electronic engineering, automation, instrumentation and other majors. This type of platform has rich interfaces and functions, and the teaching content focuses on microprocessor interface design, driver development and system applications, and cultivates embedded technical talents in application fields such as industrial automation, measurement and control, and intelligent instruments.

       It is completely unnecessary to claim that two CPU daughter boards are used to realize the functions of ARM7 & ARM9, and it increases the cost and complexity of maintenance for users. The reasons are as follows: 

       1. From the teaching content of ARM architecture, the instruction set of ARM9 is fully compatible with ARM7, and there is no difference in teaching. Therefore, ARM instruction experiments and basic interface experiments are not the patents of ARM7. People who have done ARM system development know that these teaching experiments of ARM7 can also be completed with ARM9; 

       2. From the teaching content of operating system, most of the current teaching uses µCOS-II or Linux. µCOS-II has simple code and is easy to teach and learn. Linux has powerful functions, but it has high basic requirements for students. At present, most ARM7 teaching platforms on the market support µCOS-II or uCLinux, and ARM9 basically supports Linux and WinCE. But µCOS-II is not the patent of ARM7 and can run on ARM9. And uClinux is a subset of Linux. Whether from the perspective of developers or from the perspective of teaching, the Linux system can be fully compatible with uCLinux applications. 

       The main reason for claiming to support the dual cores of ARM7 and ARM9 is that their technical capabilities are weak and they cannot complete the porting and expansion of µCOS-II on ARM9, so they use ARM7 to make up for the teaching content of µCOS-II. Imagine, if there is an ARM9 platform that can run operating systems such as µCOS-II, Linux, WinCE, etc., why do we need ARM7 to make up for it? In fact, such a platform already exists. Some companies with strong technical strength have ported µCOS-II to ARM9, such as UP-NETARM2410 and UP-NETARM2410S. 

       3. From the perspective of the teaching content of hardware design, the dual core platform that supports ARM7 and ARM9 has caused a waste of hardware resources and it is difficult to give full play to the respective advantages of ARM7 and ARM9. For example: using s3c44b0 and s3c2410 processors as the cores of ARM7 and ARM9, the s3c2410 platform supports USB host and USB client, and supports true color TFT LCD. In order to be compatible with s3c44b0, the main platform has to use a 256-color STN LCD; if it wants to have a USB host or client interface, it has to use other chips for expansion. This will limit the functions of the ARM9 processor and cannot give full play to the performance of the ARM9 processor. 

       4. From the perspective of product cost service maintenance, the use of a dual-core platform that supports ARM7 and ARM9 will undoubtedly increase the cost of the product, because the most expensive chips in the teaching platform are the microprocessor and memory, and from a teaching perspective, this part of the increased cost is meaningless. From a scientific perspective, this approach wastes resources, and its cost-effectiveness is no better than a development board. In addition, the use of a dual-core platform that supports ARM7 and ARM9 reduces the reliability of the system. Students will often switch between the two cores during the experiment, and the probability of damage will greatly increase, increasing the subsequent maintenance cost. It 

       can be seen that only one ARM9 platform can meet the needs of mid- and low-end teaching at the same time. Adding an additional ARM7 to meet low-end teaching tasks can only be considered superfluous. It simply increases the hardware cost and limits the expansion of the hardware platform. 

       The purpose of embedded system teaching should be to let students learn a method of embedded platform development and design. The changes are mainly reflected in running different operating systems, rather than whether the hardware uses ARM7 or ARM9. The teaching idea should be "teaching people how to fish". What students learn is the design method. In the future, whether it is ARM7, ARM9, or XScale, or even MIPS, alpha, 68k, powerpc and other microprocessors of other architectures, they are all the same for an excellent embedded system engineer.

Keywords:WinCE  Linux  uClinux Reference address:Technical Analysis of ARM7&ARM9 Dual-core Platform

Previous article:Design and implementation of tax control cash register system based on ARM controller LPC2214
Next article:Design of wireless communication terminal system based on STM32

Recommended ReadingLatest update time:2024-11-16 18:05

Compile the Makefile of the driver module based on ARM LINUX
KERNELDIR = /home/wenhao/platform/linux-2.6.34 PWD := $(shell pwd) CROSS_COMPILE = /usr/local/arm/4.3.2/bin/arm-linux- CC    = $(CROSS_COMPILE)gcc obj-m := key.o  modules:     $(MAKE) -C $(KERNELDIR) M=$(PWD) modules clean:     rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions .PHONY: modules clean
[Microcontroller]
File descriptors in the Linux kernel (V) -- allocation of fd -- locate_fd
Kernel version: 2.6.14 CPU architecture: ARM920T Author: ce123(http://blog.csdn.net/ce123) Continuing from the previous blog, we will analyze the allocation function locate_fd of another file descriptor fd. The dup system call is used to copy the file corresponding to a file descriptor, and the return value is a f
[Microcontroller]
Linux 2.6.32 ported to MINI 2440 (3) supports yaffs2 file system
Development Environment:     Host: fedora 14     Virtual machine: vmware workstation 10     Cross-compilation tool: arm-linux-gcc 4.3.2     Development board: mini2440 (2m nor, 64m sdram, 256m nand) 1. Get the yaffs2 source code    I have a compressed package from the Friendly Arm CD, but it is in zip form
[Microcontroller]
Linux 2.6.32 ported to MINI 2440 (3) supports yaffs2 file system
Linux kernel transplantation s3c2410, preparation work
1. The first is to obtain the Linux kernel source code, which seems to be nonsense. The download address is as follows: ftp://ftp.kernel.org/pub/linux/kernel/v2.6/Download: linux-2.6.16.22.tar.bz2  patch-2.6.22.6.bz2 What needs to be explained in the above step is that generally speaking, each patch file of the Linux
[Microcontroller]
mini2440 downloads the Linux virtual machine program through dnw
First, let the Linux virtual machine support dnw transmission Download the compiled dnw in the link and put it in /usr/bin of Linux and you can use it How to use dnw dnw is a USB tool that sends files via USB to a bootloader with USB download capability. The command itself is used as follows (to be sent successfully
[Microcontroller]
OK6410A Development Board (VIII) 61 linux-5.11 OK6410A Process Communication Mechanism 1 Signal
Signal Asynchronous communication mechanism Unreliable/Reliable Signal processing method Ignore // SIGILL and SIGSTOP cannot be ignored Catch // SIGILL and SIGSTOP are not catchable default // Signal processing has a default (not the default above) processing method for each signal // Users can mod
[Microcontroller]
Brief Analysis of Linux Exception Handling Code on ARM Platform
Linux version 3.10.40 ARM processors support multiple exception modes, such as reset, irq, fiq, etc. After an exception occurs, the processor jumps to the specified address according to the configuration. It can be configured to start from address 0 or address 0xFFFF0000. We analyze the implementation on Linux from
[Microcontroller]
Linux-2.6.38 to tiny6410 porting manual (Part 2) __Network Card & NFS
Last time, the NAND flash was ported from Linux-2.6.38 to Tiny6410. The porting manual (Part 1) can be found at http://www.arm9home.net/read.php?tid-14196.html . Today, we are porting the DM9000 network card and setting up the NFS file system. 1. vi include/linux/dm9000.h. Add unsigned char param_addr in line 28;
[Microcontroller]
Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号