![]() It’s worth attempting to run the workspace setup now to see how far things go. Make sure to do this in a new, empty directory. Searching, I found it can be installed and checked using: This will download the workspace_1701.py script.īefore I even got started, I found python3 is missing. $ git config -global user.email the workspace setup script from the HOWTO link or paste the following into a browser address bar, or better yet use wget to retrieve it: $ git config -global user.name "John Doe" It doesn’t really matter since it will not be used to commit any changes to any of the repositories. ![]() ![]() To get started, perform the git setup, and change your info as needed. This will get most of what is needed, but some extra packages are always required. On RHEL 7 or CentOS 7, the ‘yum’ command can be used to install missing packages.įor my trial, I setup a machine with CentOS 7 and selected a starting configuration with Gnome desktop and all software developer tools. On a network of Linux machines, this may require a system admin to get involved since individual users may not have the ability to install missing packages. One of the challenges with any Linux distribution is how to make sure all the required tools are available, and if not, to get them installed. Make sure to install git and python3 on the machine before getting started. No information about Android is provided, which is also supported by the Linaro software stack and Fast Models. ![]() The target for this article is 64-bit Linux. For this reason, only the build from source path is covered here. There is an option to run pre-existing binaries, but to do any software development all the software should be compiled from source so it can be changed and debugged. There is a short HOW TO article on the Arm community which gives an overview of the build and run process. Another assumption is that most embedded projects will need to change the hardware configuration in some way and will want to learn how to do this with Arm Fast Models and create a virtual prototype that best represents the new system being designed. The current version of Arm Fast Models will be used, this is version 11.2. Hopefully this example will provide enough background to enable readers to adjust as needed for other combinations. With the host operating system and the target CPU configuration set, let’s see how to use the Linaro deliverables under these slightly different conditions. For the purposes of this example, let’s say everybody is using Red Hat Enterprise Linux 7 (or the CentOS 7 equivalent). After all, this is a big benefit of using virtual prototyping improved communication among the various teams in a project. Although every company is unique, a reasonable assumption is that the software team and hardware team should work on the same network with the same host operating system if they want to share information during the early software development and hardware validation phases of the project. This poses a challenge for a project with embedded Linux development and EDA tools for chip and system development. Each EDA company publishes operating system roadmaps, and I checked one from Cadence and one from Synopsys to confirm that Red Hat Enterprise Linux 7 is still a primary platform in 2018. This is primarily due to the cost of software testing and the impact to retest when a new operating system is introduced. In contrast, the EDA community continues to focus on Red Hat Enterprise Linux (or the CentOS flavor). In addition to changing the CPU configuration, another challenge is Ubuntu seems to be the most popular host operating system in the software development community. For this exercise, let’s imagine a new embedded Linux project is starting and it uses a different CPU configuration, a Cortex-A53 single cluster, quad core configuration. The default configuration is to run on the Arm AEM (architectural envelope model) with a dual-cluster system and one core in each cluster. It also provides some insight into what is really happening and how to debug the flow when just following the instructions doesn’t work. This article provides some confidence that the Linaro deliverables can be adapted when a project is a little different from the default assumptions. Although there is some existing information on this topic, there are two assumptions that often create challenges when trying to apply the Linaro deliverables to an actual project. This article explains how to build and run this software on Arm Fast Models. Linaro provides a complete software stack for secure boot, u-boot, and Linux.
0 Comments
Leave a Reply. |