Overview: This webinar shows you how to set up a Linux-based cross-development environment for doing development work on a typical ARM target board. Live demonstrations com-plement the lecture material to show you exactly how the process works. While the examples presented utilize an ARM processor, the basic concepts are applicable to any architecture.
We'll begin by reviewing the basic cross-development paradigm and describing a typical toolchain. We'll configure the workstation's network interface to support the Network File System (NFS). We'll also need a simple serial terminal emulator for talking to the target board's boot loader. A typical ARM-based target single board computer (SBC), the Mini2440, will be intro-duced. We'll configure the board's network interface to connect with the workstation when it boots up.
Then, after reviewing the Linux notion of "mounting" file systems, we'll use NFS to mount the target board's root file system. Eclipse will be introduced to illustrate the value of an Integrated Development Envi-ronment (IDE). Eclipse is a popular Open Source project that has been adapted by several commercial tool vendors as the basis for their own IDEs. We'll demonstrate how a network-based target file system, together with Eclipse, speeds up the ed-it/compile/debug cycle.
Having built and tested a simple application program, we'll move on to review several Open Source build systems that aim to simplify the process of setting up a development environment. These packages encompass all of the elements of the environment in-cluding: tool chain, libraries, utilities in the form of BusyBox, Linux kernel, and boot loader.
Want to use Windows? Well, if you must. While it's a little more involved, it is possible to set up a usable Linux development environment in Windows. One of the problems is that Windows doesn't ship with an NFS server. We'll wrap things up then, by taking a look at a Windows-based cross-development platform.
Why should you attend: Any task is accomplished faster, easier and more efficiently with the right set of tools. Thus, when developing embedded devices with Linux, good practice requires that you have a well-structured development environment. While it may be possible to do develop-ment on the target device itself, it's usually not the most efficient or productive environment. The preferred alternative is a cross-development environment on a workstation class PC.
How or where do you get a cross-development environment? You can go to a commercial tool vendor and pay a lot of money. Or you can set one up yourself. The goal of this presentation is to show you that it's not that difficult, especially if you use one of the popular Open Source build systems. Even if your target does not use Linux, a proper Linux-based cross-development envi-ronment is still a good investment in productivity. You can just as easily use other target operating systems or program to the bare metal.
Especially if you're new to embedded development, this webinar will get you started on the right track toward greater productivity and quicker time to market.
Areas Covered in the Session:
Who Will Benefit:
We'll begin by reviewing the basic cross-development paradigm and describing a typical toolchain. We'll configure the workstation's network interface to support the Network File System (NFS). We'll also need a simple serial terminal emulator for talking to the target board's boot loader. A typical ARM-based target single board computer (SBC), the Mini2440, will be intro-duced. We'll configure the board's network interface to connect with the workstation when it boots up.
Then, after reviewing the Linux notion of "mounting" file systems, we'll use NFS to mount the target board's root file system. Eclipse will be introduced to illustrate the value of an Integrated Development Envi-ronment (IDE). Eclipse is a popular Open Source project that has been adapted by several commercial tool vendors as the basis for their own IDEs. We'll demonstrate how a network-based target file system, together with Eclipse, speeds up the ed-it/compile/debug cycle.
Having built and tested a simple application program, we'll move on to review several Open Source build systems that aim to simplify the process of setting up a development environment. These packages encompass all of the elements of the environment in-cluding: tool chain, libraries, utilities in the form of BusyBox, Linux kernel, and boot loader.
Want to use Windows? Well, if you must. While it's a little more involved, it is possible to set up a usable Linux development environment in Windows. One of the problems is that Windows doesn't ship with an NFS server. We'll wrap things up then, by taking a look at a Windows-based cross-development platform.
Why should you attend: Any task is accomplished faster, easier and more efficiently with the right set of tools. Thus, when developing embedded devices with Linux, good practice requires that you have a well-structured development environment. While it may be possible to do develop-ment on the target device itself, it's usually not the most efficient or productive environment. The preferred alternative is a cross-development environment on a workstation class PC.
How or where do you get a cross-development environment? You can go to a commercial tool vendor and pay a lot of money. Or you can set one up yourself. The goal of this presentation is to show you that it's not that difficult, especially if you use one of the popular Open Source build systems. Even if your target does not use Linux, a proper Linux-based cross-development envi-ronment is still a good investment in productivity. You can just as easily use other target operating systems or program to the bare metal.
Especially if you're new to embedded development, this webinar will get you started on the right track toward greater productivity and quicker time to market.
Areas Covered in the Session:
- Cross-development tool chains
- Configuring the workstation for NFS
- The target board
- Mounting the target's root file system over the network
- Eclipse
- Open Source build systems
- Yocto
- OpenEmbedded
- Buildroot
- Linaro
- What about using Windows?
Who Will Benefit:
- Embedded engineer
- Software engineer
- Firmware engineer
- System architect
- Engineering Manager
No comments:
Post a Comment