ARM processors are widely used around the world, and 32-bit RISC-based embedded processors have become the standard in embedded design and application. Compared to the popular 8-bit microcontrollers commonly used in China, 32-bit embedded CPUs offer significant advantages. They bring advanced hardware capabilities and enhanced performance, allowing entire systems to be upgraded through software alone. Unlike 8-bit processors, which typically face a 64KB software limit, 32-bit systems allow for more complex and large-scale applications. This makes it possible to implement the concept of "hardware-software integration" effectively.
What has changed?
In China, many engineers are well-versed in 8-bit processor development, with a wealth of tools and low costs. However, developing 32-bit processors is quite different from working with 8-bit devices.
First, real-time multitasking operating systems (RTOS) are now essential in 32-bit embedded systems.
With more powerful CPUs, the instruction set becomes larger, and system software becomes more complex. Therefore, an RTOS is often chosen to manage tasks efficiently. Software engineers must learn new RTOS technologies and understand how to design and debug both low-level and application software. This presents a new challenge but also offers benefits like modular and portable software, making future software management easier.
Second, the debugging interface has evolved.
For 8-bit processors, in-circuit emulators (ICE) were commonly used. However, for 32-bit systems, high clock speeds and complex packages like BGA make ICE less practical. Instead, JTAG interfaces are used for debugging. These are usually 14-pin or 20-pin sockets, and JTAG debuggers provide cost-effective solutions by accessing CPU information directly. This reduces the need for expensive ICE setups.
Third, the development process has changed.
In 8-bit systems, developers focused on hardware and software separately, often finishing hardware before writing application code. For 32-bit systems, hardware and software development happen simultaneously. A real-time OS environment is required, and application software can be developed and debugged alongside the hardware. Once the BSP (Board Support Package) is ready, the system and application software can be integrated. This allows for more flexible and reusable software across different platforms.
So, what tools and environments are needed for 32-bit embedded development?
First, choose a suitable multitasking OS.
There are many commercial RTOS options like Linux, Nucleus, WinCE, and VxWorks. Developers can pick based on technical and commercial needs.
Next, select the right build and debugging tools.
Based on the OS and programming language (C or C++), a compiler, linker, and simulator should be chosen. For ARM processors, common choices include ARM's SDT, ADS, and free GNU tools. Many vendors provide complete IDEs that include compilers, linkers, simulators, and debuggers, making development more efficient.
Also, choose the right JTAG emulator.
JTAG emulators connect to the target board via cables and communicate with the host through parallel, USB, or network ports. Each method has its pros and cons in terms of speed, convenience, and resource sharing. The JTAG frequency also affects performance. A good JTAG tool should support task-level debugging and recognize various RTOS environments to simplify software testing.
Developing 32-bit systems brings unique challenges. Engineers must be well-prepared, especially during BSP (Board Support Package) development. After hardware is debugged, the RTOS must be ported, and the BSP plays a key role in connecting the OS to the hardware. Without a properly functioning BSP, system debugging is nearly impossible. This phase can take weeks or even months, requiring deep knowledge of the CPU, hardware, and OS.
Parallel development of application software is also important. With shorter development cycles, software and hardware must be developed together. Developers can use evaluation boards or virtual environments provided by RTOS vendors to write and test code before deploying it on the actual hardware. This approach saves time and improves efficiency.
Overall, 32-bit embedded systems require a shift in mindset and skillset. Engineers must adapt to new tools, methods, and challenges, but the rewards in performance and flexibility are well worth the effort.
Cable Box,Junction Boxes,Cable Connection Box,Waterproof Cable Box,Electrical Junction Boxes
Jiangmen Krealux Electrical Appliances Co.,Ltd. , https://www.krealux-online.com