TI-RTOS Workshop Setup Guide Rev 3.0

Transcription

1 TI-RTOS Workshop Setup Guide Rev 3.0 Introduction The objective of this guide is to walk you, the student, through all of the necessary steps to download and install all of the tools for Mindshare Advantage s Intro to the TI-RTOS Kernel Workshop as well as the C6000 Embedded Design Workshop. Please RTFM Read the Fine Manual and EVERY step whether you think it pertains to you or not. Having a clean install of all of these tools is CRITICAL for everyone to keep time/pace as the workshop begins. If you don t prepare properly, the instructor must take time to help you install tools which takes time away from other students. SO PLEASE DO YOUR PART. Details about HOW to configure and use the TI-RTOS kernel (SYS/BIOS), as well as Code Composer Studio (CCS) will be taught live and all students will have plenty of opportunities to practice these skills during the lab exercises. Trust the author getting all these tools in the right place and working together to create projects is 80% of the battle and a skill you need to acquire. The getting started hello world out of box experience is crucial and sometimes the most difficult challenge you will face in your application. ;-) So, that s where we start Note: Note: This installation guide covers all installation details for BOTH the TI-RTOS Kernel Workshop (2 days) as well as the C6000 Embedded Design Workshop (2 days). Total download and install time of all tools is 3-4 hours so plan accordingly. For future reference, the main workshop site for the Intro to TI-RTOS Kernel Workshop is here: The 2-Day C6000 Embedded Design Workshop information is here: Disclaimer Mindshare Advantage updates the workshop labs/solutions files at least once per year and verifies that the key lab (lab5 solution) compiles and runs on each of the five targets supported in the workshop. It is possible that a newer version of a library, SDK or compiler will cause an error or warning in your specific setup. Notify us if that is true and we will do our best to help you. However, some users cannot even get their emulator to connect to their board. If you have followed all of the steps in this document faithfully, it may be that your host operating system (or some driver) is faulty. In those cases, it is ok to contact us and we ll try to briefly help you. If there is no quick fix, you will need to ask your specific question on TI s E2E forum: e2e.ti.com. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

2 Workshop Equipment & Requirements Topics TI-RTOS Workshop Setup Guide Rev Topics Workshop Equipment & Requirements You must provide: Provided at the workshop Download Checklist Installation Code Composer Studio Modify Java Memory Used Install Workshop Lab/Solution Files Install TI-RTOS SDK Install xware For Your Target C6000 and C28x Make Sure All MIN Tools are Installed Appendix C6000 Embedded Design Workshop Install C6748 Starterware Final Steps OMAP-L138 LCDK Users Only Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

3 Workshop Equipment & Requirements Workshop Equipment & Requirements You must provide: Windows computer using Windows XP or greater. CCSv6.2+ will run on Windows 7/8/10. You are required to provide your own Windows laptop computer. It should have an available USB port. You will also need at least 1.5 GB of space available on your disk drive to hold the necessary software. If you have a Mac or Linux notebook computer, we have seen students be successful running the development tools in a virtual machine, such as VMware or VM Fusion. That said, we cannot guarantee that our instructors will be able to help you with managing these types of environments. Audio headphones (to watch videos pertaining to YOUR target when waiting for others to finish labs, if time allows) A means of watching.mp4 videos (media player) Pen or pencil and notepad to take notes Before coming to the workshop, you should install ALL the software outlined in this document please be considerate and follow ALL instructions carefully. If not, precious class time will have to be taken to help solve your specific installation problems. If the install is unsuccessful, you will be asked to team up with another student during the labs. Your own development board only these are supported at this time: CC2650 LAUNCH-XL EK-TM4C123GXL LaunchPad (Tiva-C) MSP-EXP430F5529 LaunchPad F28069 Control Stick C6748 (or OMAP-L138) LCDK with XDS100v2 emulator (or other compatible emulators of your choice) Provided at the workshop Printed Lab Manuals For general audience workshops, Mindshare Advantage will print copies of the lab manuals one per student. If this workshop is being held on-site at your company s location, you must provide your own copies of the lab manual. You can also simply follow the PDF on your laptop, but Alt-Tabbing between lab instructions and Code Composer will drive you nuts. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

4 Download Checklist Download Checklist Integrated Development Environments (IDE) Code Composer Studio v You can download either the web installer or offline installer. The web installer is smaller, but the off-line installer is more flexible. If you have a fast internet access, we suggest the off-line installer. Clicking the link for either installer, you will be directed to log in (or create a free) my.ti account. Note: If you already have CCSv7.2+ or newer on your laptop, there is no need to download or install CCS unless you want to add new components, or if you want the absolute latest version which is fine as well. The labs and solution files are NOT guaranteed to work with CCSv6.2 or older. Then, once you agree to the export conditions you will either be ed a link or be directed to a web page with the link. Workshop Course Materials (links provided after registration or payment) TI-RTOS Workshop Manual (PDF) Workshop Lab Files (.123 rename to.zip after downloading) Installation Document (PDF) (the document you are reading now) For 4-day C6000 students only: C6000 Workshop Manual (PDF) 00-4 Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

5 Download Checklist Download Latest TI-RTOS SDK and BIOS tools As of the CCSv6.0 release, no RTOS tools are installed other than XDC. So, after installing CCS later in this document, you will also need to install the tools listed below. This workshop now takes advantage of all of the new TI-RTOS SDK releases available as of April 2014 along with CCSv6. So, make sure you download the following tools carefully and then install them when told to later in this document. Download latest TI-RTOS for YOUR architecture (Windows Version): First, you must download the TI-RTOS SDK for YOUR architecture provided at this link: Click the Get Software button and this will take you to the download page (snapshot as of 9/01/17): MSP430 USERS MUST use TI-RTOS ver or later or the labs WILL NOT WORK (API change). Click on the Windows link of the latest release for YOUR architecture as shown in the table above. For your information, all of the TI-RTOS related tools can be found on this page: You can see the huge, long list of tools. Keep in mind that tools are MATCHED together. You can t use an old BIOS release with a new UIA or new XDC, etc. This is actually one of the most common errors new users make. C6000 users have the same tools the TI-RTOS SDK will not be updated past where it is today. The point here is that the tools matching is handled FOR YOU by creating these SDKs with matched tools. When you install the TI-RTOS SDK package, the installer will attempt to ALSO install the proper version of XDC if you don t already have it. In effect, the TI-RTOS SDK package installer is forcing this MATCHING of all the tools which is fantastic (in the author s opinion) because it helps all users make fewer mistakes in this critical area of getting the right SET of tools. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

6 Download Checklist Download Latest Driver Libraries for Your Target Once again, MSP430 and Tiva-C users are in luck you get the driver libraries WITH the TI-RTOS SDK download. However, C28x and C6000 users will need to download driver libraries and install them. We plan to simply blink an LED in this workshop (sounds simple, but we decided to keep the application simple so we could focus on the TI-RTOS kernel concepts). A driver library, specific to your target, is necessary to enable us to write code to blink the LED, set up hardware timers and perform delay functions. MSP430, CC2650 and Tiva-C USERS ONLY SKIP THIS SECTION (no need to download driver libraries) C28x and C6000 USERS ONLY follow the steps in this section to download your driver libraries C6000 or C28x USERS download the latest driver library Only download the libraries (xware) for YOUR specific target: C28x Users Control Suite C6000 Users MCSDK OMAPL-138-MCSDK C6000 Users once you get to the MCSDK download page, download the following: C6000 Users Yes, it says OMAP-L138 MCSDK (Multi-core SDK). Even though we use the C6748 LCDK in the workshop, this SDK covers the C6748 (single core DSP) as well as the OMAP-L138 (ARM9 + C674x CPU). So this IS the correct SDK for C6000 users in the TI-RTOS workshop Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

7 Installation Installation Code Composer Studio Note: If you already have CCSv7.2 or higher installed on your machine, you can skip the CCS installation procedure. If you want to ADD a target or two to your CURRENT installation, simply re-run the installation again and install these new components. Install Code Composer Studio 7.2 or newer 1. If you haven t already done so, download CCS. (Refer to the Download Checklist for details.) 2. Disable anti-virus (e.g. McAfee) and spyware protection, firewall, etc. if possible. We have seen NUMEROUS problems later on when using CCS if your anti-virus protection was NOT disabled during installation. You have been warned. 3. If you downloaded the full, all-in-one installer you must unzip it first. Windows makes zip files look like folders, but trying to run an installer from a zipped file does not work well. PLEASE UNZIP THE INSTALLER BEFORE INSTALLATION. 4. Run the CCS Installer AFTER you have UNZIPPED IT. ccs_setup_ exe (version available when this document was printed) 5. When the installation program runs, accept the license agreement and click Next. 6. Note about CCS installations: When the Choose Installation Location dialog appears, we suggest that you install Code Composer in the default C:/TI folder. If the install program ever asks you if you want to install CCS as a plugin to Eclipse, do NOT say yes. Click Next. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

8 Installation 7. Choose the devices you plan to use in the Processor Support dialogue. Choose the following for your target: C28x users choose C2000 real-time MCUs C6000 users choose C6000 Power-Optimized DSP (however, if you want OMAP-L138 support which is NOT required for the workshop, choose OMAP-L1x DSP + ARM9 Processor) OMAPL138 LCDK USERS ONLY: We will say it again here in order to load the proper target device for the OMAP-L138 LCDK, you MUST choose OMAP-L1x DSP + ARM9 Processor. MSP430 users choose MSP430 ultra-low power MCUs MSP432 users, select SimpleLink MSP432 low power + performance MCUs (no labs or solutions are written for this architecture yet in this workshop, FYI) Tiva-C users choose 32-bit ARM MCUs CC26xx users, choose SimpleLink CC13xx and CC26xx Wirleless MCUs The more devices you choose means a longer installation time. If you have a slower computer, we recommend choosing as few as possible. (It s not really about CPU performance; installations are all about copying a lot of files.) And, if for some reason, you didn t add the proper device, you can always re-run the CCS installer and choose a different or more choices and CCS will only install the DIFFERENCE between what you have on your computer vs what you newly selected. When done selecting processors, click Next Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

9 Installation 8. Choose the emulation drivers (C6000 USERS PAY CLOSE ATTENTION HERE). The next screen checks the boxes for the emulator drivers based on your target selections in previous dialogues. They are probably already correct. However, C6000 users must check the box for your chosen emulator Blackhawk, Spectrum Digital, XDS100 or XDS200. If you don t check the right box, your emulator won t work. If in doubt, just check the all. ;-) Make sure the selections are correct and then click Next 9. AFTER INSTALLATION Install updates, manage license. After installation of CCSv7.2 (or higher), open CCS (note license info below to choose the right one that being the EVALUATION LICENSE) and allow it to install any new tools and then select Help Check for Updates. Update all of the tools related to your architecture or emulator and the TI Emulators. Check each one that applies and then click Next and follow the instructions. After the updates have been completed, close CCS and re-open it to allow the changes to take effect. Also, click Help Code Composer Studio Licensing Info and select the proper license. Most users should choose the 90-day evaluation license unless you have already purchased a license. C6000 USERS do NOT select the FREE License option. This will NOT support the better emulators like XDS200, 510, 560. Please make sure you select the EVAL license which gives you 90 days use of CCS with ANY emulator you choose. Just safer that way. MSP430 USERS please select the EVALUATION License. The Free license is limited to 16K and some labs could compile larger than that. IN GENERAL Choose the EVALUATION LICENSE instead of the Free License due to some restrictions on compiled code size (MSP430) and emulator use (C6000). Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

10 Installation Modify Java Memory Used If you don t follow these steps, you may encounter a JVM heap low error. This is common because the TI-RTOS Kernel and CCS assume a very minimal memory footprint on the host PC. The author has experienced this more times than not, so that s why the following step is here. However, with the latest CCSv7.2.0, the original numbers have increased significantly. Huh, maybe they finally listened to me for once. ;-) 10. Modify ccstudio.ini to increase java memory footprint. The INI file for TI s version of Eclipse is named ccstudio.ini. It is located here (assuming you installed CCS at the default location of C:\TI): C:\TI\ccsv7\eclipse\ccstudio.ini Open this file (via WordPad not Notepad due to the line returns) and you ll see two settings that need to be modified. Near the bottom of the file, you will see these settings and modify them to reflect the new settings shown: Xms128m Xms256m Xmx768m Xmx768m (keep the same) Xms is the minimum heap size used. This hardly ever causes problems. It is Xmx (max heap) that needs to be correct and TI has made this change recently to avoid JVM heap low errors. Keep in mind that if you go over 768m for Xmx, you could get an error Cannot create Java Virtual Machine. The author experienced this when Xmx was set to 1024m, so beware. Save your ccstudio.ini file. Note this setting will only apply to the CURRENT install of CCS. If you install a later version, you ll need to modify the new ccstudio.ini file just as above. If you do NOT make these changes, CCS still works fine, the labs will work fine but you may get annoyed at the constant reminder when working in CCS with TI-RTOS that the JVM heap is low Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

11 Installation Install Workshop Lab/Solution Files 11. Unzip the labs_sols.zip file and place at your root folder. You should have downloaded a file named (version might be same or higher): MA_TIRTOS_Workshop_Lab_Files_Rev The.123 extension is used to help bypass some of your company s IT filters. Simply rename the file with.zip extension after downloading. Unzip the contents of this folder and you will see the following list of files and folders: Create a new folder named C:\TI_RTOS (or choose your default root drive) and copy ALL of these files and folders to this new folder:: C:\TI_RTOS This folder now contains all of the labs and solution files for all architectures supported by this workshop. This is NOT the TI-RTOS SDK that you downloaded earlier. This is the author s set of lab/solution files and all supporting documentation needed for the workshop. Once unzipped and located at your root directory, expand the list of files/folders and doublecheck you see this at C:\TI_RTOS: Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

12 Installation 12. Download the latest student guides. After registration for the workshop or payment for the self-paced materials, you will receive a link to download latest lab/solution files. The user/lab guides and installation guide are available on our website for free. Verify you have downloaded the latest Workshop PDF file (it was on the list of required downloads earlier), as you will be referring to this throughout the workshop. If you are a 4-day C6000 student, the first two days are covered by the TI-RTOS Workshop Student Guide PDF. However, days 3 and 4 are located in a separate PDF document here C6000 Embedded Design Workshop. The labs/solutions files that you purchased or downloaded apply to both 2-day workshops. Install TI-RTOS SDK 13. Install your new TI-RTOS SDK. In a previous step, you downloaded the TI-RTOS SDK for your architecture. It is now time to install this package. Double-click on the.exe file and install the TI-RTOS SDK to: C:\TI The SDK installer will attempt to also install XDC tools if you don t already have the proper version. If it wants to install it, let it. If it says you already have the latest, then say ok. Again, these package installs are doing their best to MATCH the proper tools sets together which is a huge benefit. Warning some users decide to place these tools in another folder besides C:\TI. Yes, you can make CCS discover the right path, but it doesn t often find it correctly which causes all sorts of problems in the labs. They are fixable just a waste of precious in-class time. So, PLEASE do yourself and others a favor and install these tools in C:\TI. After installation, use Windows Explorer to make sure it installed properly Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

13 Installation Install xware For Your Target C6000 and C28x MSP430, CC2650 and Tiva-C users can skip the next step This class requires driver libraries to set up clocks, interrupts, timers and peripherals like GPIO to blink LEDs on the board. You were asked previously to download your specific target s driver library it is now time to install it. 14. C6000 and C28x USERS ONLY install your driver library now. MSP430 and Tiva-C users have their driver libraries contained inside the TI-RTOS SDK download. However, C6000 and C28x users need to install their driver libraries because they are NOT contained (yet) in the TI-RTOS SDK download. In a previous step, you downloaded the installer for your xware: C28x users downloaded the latest ControlSuite C6000 users downloaded the latest MCSDK Please install this library at C:\TI if you haven t already done so. If you already have this library on your laptop and it is the LATEST version, just leave it alone. Make Sure All MIN Tools are Installed 15. Comment regarding CCSv6.2+ vs. CCSv5.5 (or older). As stated earlier, CCSv6.0 or newer is a REQUIREMENT for this workshop. All labs have been tested against CCSv6.2.0 and the stock tools they use plus the TI-RTOS SDK tools for each architecture along with the other mentioned tools as of Dec First, XDC is installed along with CCSv6.0+. All TI-RTOS SDKs include BIOS and UIA as sub products in the packages. The later TI-RTOS packages (ver and later) include newer versions of BIOS and UIA that s fine. Just let the SDK install along with possibly XDC and you ll be ready for the labs. As of Oct 2017, the workshop was upgraded to use the following versions of tools: CCSv MSP430 TI-RTOS ver TM4C (Tiva-C) TI-RTOS ver C2000 TI-RTOS ver CC2650 TI-RTOS ver C6000 TI-RTOS ver xdctools ver _core (for all targets except for CC2650) xdctools ver _core (for all targets except for CC2650) all of the latest compilers/linkers as of Sep 2017 for every architecture Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

14 Installation 16. Open CCS and allow auto-discovery of all new tools installs. After installing all of the new tools, you need to open CCS (again) and allow the auto discovery tool to FIND these new tools and install them into CCS. CCS auto discovery paths are typically set for CCS_INSTALL_PATH plus C:\TI. The author has witnessed CCS NOT auto discover every new tool the FIRST time CCS is invoked. Simply run CCS, allow auto discovery to run, then close CCS and re-open it again to see if it discovers any new tools the second time. Warning: If you put tools in folders other than C:\TI, your mileage may vary. At this time, you can also check to make sure your license is working properly via Help Code Composer Studio Licensing Info. Thankfully, as of CCSv7, it s all free. Yeah TI. FYI at the beginning of the workshop, you will be given a USB key that has some videos on it related to your architecture. If you get done with a lab and the optional lab before others (you re one of those fast people), you can take some time to watch some selected architecture videos. If you think you re one of those people, double make sure you bring headphones with you to class. Having optional labs and videos available helps the faster users get more out of the lab time vs. twiddling their thumbs waiting for others of course, you could also just check or call your boss to tell him/her how wonderful and valuable this workshop has been! C day workshop students.move on to the appendix for more instructions. That s it. You re done Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

15 Appendix C6000 Embedded Design Workshop Appendix C6000 Embedded Design Workshop If you are attending the C day workshop after the TI-RTOS workshop is finished, you have some additional installation work to do. It is not a lot, but the labs for this workshop won t work unless you have these additional tools installed. Install C6748 Starterware BEFORE you install the software 1. Create a new folder in C:\TI - something like C6748_StarterWare_1_20_04_01. Why? Because when it installs, it will create ~15 subfolders. Noted on some forums, the default folder C:\Program Files should be AVOIDED due to build problems folks had (due to the SPACE in Program Files ). The author had the same problem and it worked flawlessly when he installed it in the new folder under C:\TI. You have been warned. 2. Install Starterware from this location: The workshop is based on version v Use the typical install. Final Steps 3. Make sure vars.ini is imported into CCS. The audio labs in the C6000 Embedded Design Workshop require the variable C6748_STARTERWARE_INSTALL to be set in CCS to your StarterWare install folder (like the one mentioned above C6748_StarterWare_1_20_04_01 ). This is the same vars.ini file used in the TI-RTOS workshop. Simply import that file into your workspace so that the build files (include files) can be properly located. If you are unfamiliar with this process, review the steps of Lab 4 in the TI-RTOS workshop. 4. Note about GEL files It is CRUCIAL that you use the GEL files located in the C6000 Labs folder: C:\TI-RTOS\C6000\Labs\MA_gel Two of the GEL files in this folder are for users of the C6748 and OMAP-L138 LCDKs. These GEL files are specifically designed to work with the audio files used in the workshop. These GEL files are attached via the target config files below. If you create your own target configuration files later, make sure you point the initialization script to these GEL files for best operation. These EVMs ship with their own GEL files and they work ok, but the author modified those with some special reset/clear commands when a new file is loaded to avoid common CCS problems. If, for example, you are using the C6748 LCDK in the workshop, you will need to import the target configuration file: XDS510_USB_LCDK_6748_MA.ccxml. This file uses the GEL file: C6748_LCDK_MA.gel. If you are using the OMAP-L138 LCDK, use that version of that target configuration file which will automatically use the GEL file associated with that target. As stated in the next step, if you are using a different emulator, you can simply import the correct target configuration file for your target and then change the emulator choice and point to the previously written GEL files for this workshop. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

16 Appendix C6000 Embedded Design Workshop 5. Note about target config files Also, make sure you are using the target config files in the following folder: C:\TI_RTOS\Workshop_Admin\Target_Config_Files You can always create your own target config files, but these files use the GEL files specified in the previous step and are designed to work with the Starterware audio application. These GEL files are set up to use the Spectrum Digital XDS510 USB Emulator. You may be using a different emulator. If so, simply make a COPY of the target configuration file for your target (either C6748 or OMAPL138 LCDK) and name the copy appropriately something that describes your emulator connection. Note that each of these target config files selects the appropriate TARGET in the file i.e. the LCDK6748 or LCDKOMAPL138. Let s assume you are using the BlackHawk XDS560v2 emulator one of the best in the industry the author believes. After you make a copy of the current.ccxml file, you may want to name the new one BH_XDS560v2_USB_LCDK_C6748.ccxml. Then, in CCS, you will need to import this target configuration file (see the first steps of Lab 1 from the TI-RTOS workshop), MODIFY the connection and make sure the board or device is set to either LCDK6748 or LCDKOMAPL138 and that the GEL files associated with these target config files are correct. Then save your new target configuration file for use in all of the labs. 6. Make sure the BOOT SWITCHES on your LCDK are set properly. First, pull out the SD card located on the bottom of the LCDK. We are not using Linux or U- boot, so this is unnecessary. The following applies to BOTH the C6748 and the OMAPL138 LCDK boards The first FOUR switches on SW1 (near the middle of the board, look like 8 small DIP switches) set the boot mode for the processor (1-4) and the second four (5-8) are connected to GPIO pins on the processor. Regardless of HOW the switches were set by default, make sure ALL swtiches are in the OFF position or DOWN or closer to the numbers as shown: This turns OFF all boot modes so you can easily hook up CCS in debug mode and not worry about any boot modes automatically running. If you are concerned about putting them back in the right place, you can access this document later on to understand how the switches affect booting: urces 7. Helpful StarterWare documents include: Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0

17 Appendix C6000 Embedded Design Workshop OMAP-L138 LCDK Users Only 8. OMAP-L138 LCDK Users ONLY Pay Attention to THESE STEPS: Open your target config file for editing. Under Advanced Setup, click Target Configuration : This will open the following dialogue box: There are four processors. Ignore the PRUs and highlight ARM9_0 as shown above. Under initialization script on the right, you must use the GEL file written for the workshop with the path as shown. Then click Save. Once done, click Test Connection. You should be able to connect at this point. Now, you can follow the lab one steps through Launch Configuration which should now work just fine. Once you do, you will see the GEL file running in the Console window. It looks like this: When the gel file runs, it connects to the ARM9, puts the ARM9 in reset and wakes up the DSP. The GEL file also initializes all memory contents and DDR memory and PLLs. The standard default GEL file also performs these operations, but there are a few modifications I made to make the GEL file more stable. Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev

18 Appendix C6000 Embedded Design Workshop Ok, you have now launched the target configuration and you see the following CPUs: Your GUI will look slightly different because the author loaded the C6000.out file already and ran it. So follow these next steps to load ANY.out file for ANY lab to the C674x CPU on the OMAP-L138 LCDK: Highlight the ARM9_0 CPU by clicking on it. Select Run->Connect (GEL file runs which halts the ARM9 and brings the DSP out of reset) Then click on the C674x_0 CPU and Run->Connect this CPU Then, with the C674x_0 still highlighted, Run->Load the C6000.out file from Lab 1 (or any.out file from any lab). Then click play/resume. We do NOT use the ARM9 in the workshop at all. The.out file only runs on the C6748. However, when you have two processors on board, you must first connect to the ARM9 (and run the GEL file to wake up the DSP) and then connect to the DSP and load the.out file on the DSP. If we were running code on the ARM processor, it would be a.bin file. That s it. You re done Intro to the TI-RTOS Kernel Workshop - TI-RTOS Workshop Setup Guide Rev 3.0