For use of CWTAP/USBTAP with CodeWarrior to connect target board, connection error is the type of issues that happened commonly. How to deal with it? Attached are tips for some general things to check, here assuming target device is Power Architecture, and the tap is USBTAP or CWTAP/USB. For other targets it may be similar in some tips. There might be variable reasons for the connection error, if the common tips in the attachment could not solve the problem, please enable CCS log and post on Freescale community or contact Freescale technical support for help. See attachment for steps to enable logging. Also there are two useful documents in C:\Freescale\CW_PA_v10.4.0\PA\Help\PDF: CodeWarrior TAP User Guide.pdf and USB TAP User Guide.pdf. Welcome any correction and supplement for the tips. Make CodeWarrior connection easier!
Sometimes you will need to connecting multi-cores for debug or trace purpose. Here is a step by step instruction of connecting Multicore with CodeWarrior for PA through one USBTAP. If you manually creating two projects, one for each core, with same connection configuration, and trying to connect to the same target board, there is no problem when connecting the first core, problem occurs when connecting the second one, you’ll get below error: It complains the connection is already in use, connecting the second core requires closing the previous one. If closing the first core session, the second core could be connected successful. But the purpose is to connecting both cores through same TAP simultaneously. The way for connecting Multicore with one TAP is using the CodeWarrior AMP option: • AMP (one project per core) - Select this option to generate a separate project for each selected core. The option will also set the core index for each project based on the core selection. • AMP (one build configuration per core) - Select this option to generate one project with multiple targets, each containing an lcf file for the specified core. Below are the steps of creating Bareboard project: Select File > New > CodeWarrior Bareboard Project Wizard from the CodeWarrior IDE menu bar. Specify a name for the new project in the Project name text box. Click Next. Select the target processor for the new project from the Processor list. Select Application from the Project Output group. Click Next. Select a supported connection type (hardware, simulator, or emulator), from the Debugger Connection Types group. Select the board you are targeting, from the Board drop-down list. Select the launch configurations, you want to include in your project, and the corresponding connection, from the Launch group. Select the interface to communicate with the hardware, from the Connection Type drop-down list. Click Next. Select the programming language, you want to use, from the Language group. Select a toolchain from the Toolchain group. Select an option from the Floating Point drop-down list, to prompt the compiler to handle the floating-point operations by generating instructions for the selected floating-point unit. Click Next. The Configurations page appears. 12. Select a processing model option from the Processing Model group. See below picture. 13. Select the processor core that executes the project, from the Core index list. Click Next. See below picture. Remember to choose ALL the cores you would like to connect. 14. Click Finish. If choosing the first option, it will create project for each core selecting in “Core index”. Even though the two projects use the same connection configuration, this way allows debugger to connect two projects without problem, see below capture: If choosing the second option, it will create one project only but with configurations for for each core selecting in “Core index”. Even though the two configuration use the same connection configuration, this way allows debugger to connect two sessions without problem, see below capture:
Get to meet the new release everyone! VortiQa application identification software (AIS) identifies a wide variety of applications traversing your network, including various voice, streaming audio-video, web-based applications and client-server applications. This software package forms a fundamental building block of any state-of-the-art traffic policy enforcement device such as WAF, NAC, next-generation firewall and enterprise WLAN AP. VortiQa AIS is built on top of the VortiQa platform services package (PSP)—the middleware framework—which facilitates the migration of networking applications from kernel space to user space without drastically affecting the performance. VortiQa AIS primarily performs its operation by searching for application-specific signatures in the packet data stream, also known as deep packet inspection (DPI). The signatures are loaded on the device at the boot time and get updated periodically. The DPI capabilities of VortiQa AIS allow detection of the supported applications even if they run on non-standard transport ports. This signature-based detection approach is supplemented by protocol analytics, wherever necessary, in order to maximize the accuracy of the results. So this is basically how it functions: The key features: Reliable application detection with 1100+ signatures, e.g. iTunes®, Netflix®, Facebook® and YouTube® Port-agnostic application detection with universal signatures such as Yahoo® and MSN® IM. Nested detection for select applications, such as Facebook photo sharing and Facebook games Encoded and obfuscated URL support Hardware acceleration support Notification methods Event logging Plus, supported devices: QorIQ Communications Processors Value-Performance Tier QorIQ Communications Processors Mid-Performance Tier QorIQ Communications Processors High-Performance Tier QorIQ Qonverge B Series QorIQ Qonverge BSC Series Where do I get it? If you can't wait to get this great new software, please contact you Freescale's sales representative. Visit freescale.com/VortiQa or get more info in here !
Mentor Graphics makes available to the public (licensed, but free of charge) their Embedded Performance Library (MEPL) that adds Altivec support to projects built using e6500 gcc tools (version 4.7.2 or later.) This file explains how to add that support to a CodeWarrior PA10.3.3 project for T4240QDS.