[AUDIO LOGO]

Hi, and welcome to this video overview of the new Multi-Core SysConfig tool for C2000. I'm Ben Collier. In this video, I will be giving a quick overview of the new SysConfig features that will be simplifying development for Multi-Core C2000 devices.

Before the Multi-Core SysConfig tool, users would develop completely separate projects for each core. Developers would build a data out file with each project without knowing if there were conflicts between the different project settings. Only after loading the code onto the device would devs be able to determine if something was wrong with their Multi-Core projects.

With many issues, like in the case of a CPU trying to access a peripheral for which it does not have permissions, developers will not see an error message when they encounter a problem. Instead, users would need to spend time investigating why they see unexpected results.

The new Multi-Core SysConfig tool will be improving development for Multi-Core C2000 devices in many ways. A lot has been added to the SysConfig tool, giving developers new ways to generate code for all cores with one easy-to-use GUI. Users can switch between the views for CPU1 and CPU2 by using the tabs at the top of the screen.

One of the important new features is the ability to assign ownership of shared resources with the simple dropdown menus. This can be especially useful when configuring global device memories. Multi-Core SysConfig also allows code to be generated on both CPUs from settings made on one CPU. This can be helpful when defining important macros that will be used on both CPUs, which is common for peripherals like Inter-Processor Communication.

Importantly, SysConfig will immediately alert users when there is a problem with their settings, which allows users to quickly diagnose problems in their projects. I will now walk through some of these features in greater detail.

One of the ways that Multi-Core SysConfig will connect user development across cores is that some of the code will be generated on both CPUs from a setting made only in one CPU. Here we see GPIO definitions in the code for CPU2 that come from settings made for CPU1. You can also see here that there is a warning on CPU2 for a setting that the GUI thinks should be implemented on CPU1. There will also be a warning on CPU1 ensuring that users will not miss this message.

For many shared peripherals, developers must use SYSCTL functions on CPU1 to assign ownership of shared resources to CPU2 before CPU2 is able to use that peripheral. Multi-Core SysConfig allows users to accomplish this by simply selecting which CPU should own each peripheral in a dropdown menu instead of using DriverLib functions. By default, SysConfig assigns all shared resources to CPU1.

Now I will discuss how Multi-Core SysConfig can help developers with Inter-Processor Communication, also called IPC. SysConfig's IPC module shows the interrupts that can be triggered by an IPC flag. These interrupts are enabled by selecting them from a dropdown menu and clicking the Enable button. SysConfig will then indicate which flag is needed on the other CPU to trigger the ISR. This helps users keep track of which direction the information is flowing with each flag.

SysConfig also lets users define their flags from a dropdown menu, ensuring that no flags are defined twice or different flags are given the same name.

Thank you for watching this brief video overview of the new Multi-Core SysConfig tool for C2000 devices. The most important takeaways are that the SysConfig tool now allows developers to generate code for all cores of their Multi-Core C2000 device with one GUI. The tool also allows important code to be generated on both CPUs from changes made in a single place.

The tool will also catch errors from settings made for one core that are incompatible with settings made on another core, which saves wasted debug time. Here are some additional resources for C2000 development. To use Multi-Core SysConfig, you will need C2000 4.03 or later. These links can also be found in the video description. Thanks for watching.