Recently I have a chance to debug U-Boot on a LS1021ATWR board. Here is recording what I did, and also some notes and hints for other beginners.

CodeWarrior for QorIQ related documents are located under CW installation path, like: D:\Freescale\CW_PA_v10.5.1\PA\Help\PDF   And some docs in the official website:CodeWarrior Dev Tools for Networked Apps|NXP Knowledge center:  Submit Form   See below list in this place:   QCVS: PBL Configuration using QCVS   Debug with CodeWarrior: Debugging Linux Kernel with CodeWarrior for PA Use CodeWarrior for ARMv8 to Debug U-boot and Linux Kernel and Bring up Bare Boards Secure Boot/Debug Configuration for LS1 U-Boot debug on LS1021ATWR Debugging ARMv7 Applications running in an Environment initialized by U-Boot / ROM target debug U-Boot Debug using CodeWarrior for QorIQ LS series – ARM V7 ISA Aurora Trace for CodeWarrior Power Architecture T1040 debug with Codewarrior PA10.3.3 CodeWarrior U-Boot Debugging U-Boot Debug using CodeWarrior for ARMv7 Linux kernel and modules debug using CodeWarrior for ARMv7 Linux application debug using CodeWarrior for ARMv7 and AppTRK Secure Boot/Debug Configuration for LS1   CWTAP/USBTAP: How to use CodeWarrior TAP on LS1024ARDB Connecting Multicore with one TAP How to deal with connection error with CWTAP or USBTAP Using IDcode.tcl and Scanboard   Tools: Adding nand flash(MT29F2G08ABBDA) support in CW 10.3 Flash Programmer for CodeWarrior Power Architecture How to install and use eGit plug-in in CodeWarrior.pdf Programing eMMC/SD card using CW for ARMv7   Release and packs: CodeWarrior 10.3 ready now for Power Architecture! CodeWarrior 10.2.1 for Power Architecture...don't miss this! VortiQa, the new magical AIS New Service Pack arrival for Power Architecture! (Windows)~ New Service Pack arrival for Power Architecture! (Linux)~ You'll need this Tips for your brand new CodeWarrior TAP! (Power Architecture) Other: Const_print_prob.zip

Live Board Configuration for QorIQ device       Live QorIQ DDR Triage Center Bring your board, triage the DDR interface quickly QorIQ configuration and validation with QCVS tool

This document uses LS1043ARDB as an example to introduce how to use CodeWarrior for ARMv8 to connect to the bare board to do flash programming, how to use attaching method to debug u-boot and Linux Kernel on QorIQ LS ARM 64 bit target boards. In the document some new features of CodeWarrior for ARMv8 are used, so it is needed to download the latest CodeWarrior Networked Application Suite v2016.01 and install CodeWarrior for ARMv8.   1. CodeWarrior Connects to the Bare Board to do Flash Programing   2. Debug u-boot with CodeWarrior for ARMv8   3. Debug Linux Kernel by Attaching Running U-boot

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!

This document discusses how to use CodeWarrior for PA to debug Linux Kernel on QorIQ PowerPC platforms. It describes how to configure and build Linux Kernel to support CodeWarrior debugging, how to configure CodeWarrior IDE settings to prepare for Linux Kernel debugging, how to debug Linux Kernel in different booting up stages starting from attaching to the running u-boot.   1. Build Linux Kernel for Debugging   2. Create CodeWarrior Project and Set Attach Launch Configuration for debugging 2.1 Import Vmlinux to Create a CodeWarrior project 2.2 Configure the Attach Launch Configuration   3. Debugging Linux Kernel by Attaching to a Running U-Boot 3.1 Debugging Linux Kernel at the entry point 3.2 Debugging the Kernel before the MMU is Enabled 3.3 Debugging the Kernel after the MMU is Enabled

Good news everyone!   CodeWarrior for Power Architecture has now been updated! This wonderful combination is designed to bring out the full potential of your communication and networking applications. The CodeWarrior IDE integrated within the Eclipse development framework, combines Linux® build tools and highly advanced multiprocessor, along with multicore debugging with software analysis capabilities, allowing you to build, debug and optimize the performance of Freescale Power Architecture-based multicore applications.   What's NEW in it? Updated Documentation New IDE features (based on Eclipse Indigo 3.7.1, click here to know more!) New Debugger Features (specific to Power Architecture devices) New processor support Regular FEATURES Eclipse IDE Flash programmer Hardware diagnostics Linux application debug Bare-Board multicore debug (restrictions based on suite) Integrated GCC Build Tools/Project Management Linux Trace (Linux Based Software) Linux Kernel Debug (restrictions based on suite) CodeWarrior Build Tools (restrictions based on suite) Trace (bare metal; selected cores only) (restrictions based on suite) Performance analysis (selected cores only) (restrictions based on suite) Works with CodeWarrior TAP, Gigabit TAP and USB TAP control probes   If you wanna know more about it, take a look at the Release Note or go to the Freescale web page. If you want to star with the download at once, click here!  

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:

1. You should have CodeWarrior TAP(CWH-CTP-BASE-HE)and Probe Tips for LS1024A(CWH-CTP-VSPA-YE)   2. Install CodeWarrior for QorIQ LS Series ARMv7 ISA Windows v10.0.4   3. Install CodeWarrior patch (LS1024A-2MA_Windows_SP.zip)forLS1024/MA 4. Connect this tool to LS1024A RDB board and run CodeWarrior environment.   5.Start the bootloader and stop it at Barebox command line   6. In CodeWarrior environment File->New->Codewarrior Bareboard project wizard to add a LS1024A project.     Run->Debug configuration->Debug   7. Window->Show View->Registers. Only ARM architecture registers you read here.   8. If you want to read peripheral device controller register, please use shell mode    Window->Show->Debugger Shell   CodeWarrior Debugger Shell v1.0 %> cmdwin::mem <device based address>+offset -s (use command “help cmdwin::mem” to get the detail )

The advantages we can get out of QorIQ processing platforms are merged into so many applications!  Just to mention some, we can find it within networks, mobile wireless infrastructure, automated functions, medical use, and many many more! This way you can get high-performance communications, base stations and computing systems to market easier with its advanced tools, multiple cores, accelerators, security and more. Some service packs have been released to empower your design in this handful technology. The forth of them is being presented here with the Power Architecture Processors v10.1.2 Service. This time, the improvements have been applied in the following devices: P4040 DS       Bare-metal support      U-boot debug P4080 DS       Bare-metal support      U-boot debug P3041 DS Hydra       Linux Kernel and Application Debug P3041 DS SuperHydra       Linux Kernel and Application Debug     There are many more new features added and improved for Power Architecture Processors v10.1.2 Get to meet them in the Release Note! And download now the Service Pack 4 for Windows !   You rather Linux version?

There's a ton of devices that can be debugged out with the new TAP kit for CodeWarrior. If you already met this TAP, today I'd like to introduce the CWH-CTP-COP-YE which is a removable probe tip targeted for Power Architecture processors, meant to connect the Power Architecture microprocessor target system’s JTAG port to the CodeWarrior TAP base unit’s 30-pin target connector.   This tip is totally compatible with the CodeWarrior TAP that I've been talking about (CWH-CTP-BASE-HE) base unit, and if you are intending to use it on Power Architecture-supported devices, you'll need to get one of these Tips specially built for the occasion. Check out some of its features up next!   Features Removable probe tip Low cost and economical to order several spares Allows base unit to work with several different target types   System Requirements Power Architecture -based target system with JTAG header CodeWarrior TAP  

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!

As you might be well aware now, Power Architecture technology spans applications from satellites to automotive control to servers, for which it has become the preferred platform for many mission critical applications and markets.   Power Architecture technology is present in many single–, dual– and multicore Freescale processors, and the great news is CodeWarrior 10.3 (latest release) is now supporting it, enabling all those great projects out there with the most advanced features in the following categories:   Licensing Build Tools IDE Power Architecture Debugger Trace, Profiling and Performance Analysis And many other ones that you will learn of in the Release Note     There are also a few new System Requirements, so check them up before installing!     WINDOWS LINUX Windows 7 SP1 32/64-bit Windows Vista SP2 32/64-bit Windows XP SP3 32/64-bit Red Hat® Enterprise Linux 5.4, 32/64-bit Ubuntu 8.0.4 32-bit Ubuntu 9.10 32-bit Ubuntu 10.4 64-bit Ubuntu 11.04 64-bit Ubuntu 12.04 32-bit and 64-bit SuSE 11 32-bit Fedora 18 64-bit   For other OS requirements, check further references in Release Note     If you are now ready to download CW10.3 for Power Architecture, click here!