DOCSLIB.ORG

Winidea 2017 / 9.17

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Winidea 2017 / 9.17 _ RELEASE NOTES winIDEA 2017 / 9.17 9.17.0.0.69386 (14.06.2017) 5 Deprecates 5 9.17.17.0.73896 (13.11.2017) 5 Hardware 6 CAN2/LIN2 6 Infineon DAP Active Probe 6 ARM HSSTP Active Probe 6 USB 6 CPU Support 6 PowerPC 6 Cortex 6 TriCore 6 RH850 7 Software 7 Internal SFR database 7 Analyzer 7 Renesas E1 plugin 7 SDK 7 9.17.19.0.73116 (21.10.2018) 8 Software 8 9.17.39.0.78401 (10.4.2018) 9 Hardware 9 ADIO 9 FNet triggering system 9 CPU Support 9 Cortex 9 PowerPC 9 RH850 9 TriCore 9 Software 10 Analyzer 10 Deprecates 10 9.17.57.0.78804 (30.4.2018) 11 Software 11 Project View 11 Special Function Registers 11 Editor 11 Analyzer 11 SDK 11 9.17.79.0.82040 (3.9.2018) 12 © iSYSTEM, November 2018 1/39 Software 12 Analyzer 12 9.17.80.0.82246 (7.9.2018) 13 Software 13 Editor 13 9.17.81.0.82679 (20.09.2018) 14 Hot Attach 14 Internal flash troubleshooting for Cortex M devices 15 SDK 15 9.17.84.0.83132 (9.10.2018) 16 Software 16 Hardware Configuration 16 9.17.85.0.83132 (29.10.2018) 18 Software 18 Build Manager 18 Probe selection 18 CPU Support 18 Cortex 18 TriCore 18 9.17.88.0 (15.11.2018) 19 Software 19 FLASH Programming 19 CPU Support 19 MPC5xxx/SPC5x 19 TriCore 19 9.17.89.0.84550 (27.11.2018) 20 Software 20 FLASH programming 20 ETF support 20 SFRs 20 Bitstream programming 21 CPU Support 21 RH850 21 9.17.90.0.84924 (6.12.2018) 22 Software 22 RTOS 22 FLASH programming 22 Build Manager 23 CPU Support 23 RH850 23 9.17.92.0.85290 (17.12.2018) 24 Software 24 BlueBox synchronization configuration 24 3rd Party Debug Hardware Support 24 Editor 24 CPU Support 24 RH850 25 © iSYSTEM, March 2019 2/39 Download flash programming has changed 25 Debug port JTAG support has been deprecated 25 9.17.93.0.85666 (9.1.2019) 26 Hardware 26 CAN/LIN add-on module 26 Software 26 IDE 26 FNet operation 26 Tricore SoC presets 26 9.17.94.0.85908 (16.1.2019) 28 Software 28 EVE (Embedded Virtual Engine) 28 CPU support 28 Cortex 29 9.17.95.0.86249 (29.1.2019) 30 Software 30 FLASH programming 30 Initialization 31 Analyzer 31 IDE 32 Project window 32 Watch window 32 CPU support 33 Cortex 33 9.17.96.0.86416 (3.2.2019) 34 Software 34 Networks configuration 34 9.17.97.0.86519 (5.2.2019) 35 Software 35 FLASH programming 35 CPU support 35 TriCore Aurix 35 9.17.98.0.86628 (10.2.2019) 36 Software 36 Profiler timeline 36 CPU support 36 Cortex 36 RH850 36 9.17.99.0.87051 (21.2.2019) 37 Software 37 IDE 37 Initialization 37 CPU support 37 Cortex 37 9.17.101.0.87376 (3.3.2019) 38 Software 38 IDE 38 © iSYSTEM, March 2019 3/39 FLASH programming 39 3rd party hardware support 39 Infineon DAS Wiggler + TriCore 39 © iSYSTEM, March 2019 4/39 9.17.0.0.69386 (14.06.2017) Verified build for Cortex, PowerPC, V850, RH850 and TriCore family. Deprecates The following HW / architectures have been deprecated and are now maintained in legacy winIDEA version 9.12.288. ● iC3000 (iC3000HS and iC3000GT remain supported with 9.17.) ​ ​ ​ ​ ● NXP HC08, HCS12 and 68K Active POD ● ActivePRO POD / ActiveGT POD o all Renesas V850 Active / ActivePRO / ActiveGT PODs (Fx2, Fx3, Fx4,…) o Renesas 78K ActivePRO POD, 78K0R and RL78 ActiveGT POD o all NXP S12X ActivePRO / ActiveGT PODs o all NXP MPC5xxx ActiveGT PODs ● iTRACE / iTRACE PRO / iTRACE GT (ARM7 ETM, ARM9 ETM, MPC5xxx Nexus, MPC56x Nexus, PPC4xx Nexus, TMS570, Guidant,…) ● iC3000 / iC3000HS / iC3000GT iCARD on-chip debugging: o ST STM8 o ARM7, ARM9 o Intel XScale o NXP HCS08, HC12, S12, S12Z, S12X, ColdFire, CPU32 o NXP PPC4xx, MPC6xx, MPC7xx, MPC82xx, MPC83xx, mobileGT (51xx/52xx), QorIQ (MPC85xx, P10xx, P20xx, P30xx) o Renesas 78K, 78K0R, RL78, SuperH (SH-2A) ● iC5000 / iC5500 / iC5700 o ST STM8 o ARM7, ARM9 o NXP HCS08, HC12, S12, S12Z, S12X o NXP MPC56x Nexus o NXP QorIQ (MPC85xx, P10xx, P20xx, P30xx) o Renesas 78K, 78K0R, RL78, SuperH (SH-2A) © iSYSTEM, March 2019 5/39 9.17.17.0.73896 (13.11.2017) Verified build for PowerPC, V850, RH850 and TriCore family. Use winIDEA 9.17.0 for Cortex microcontrollers, unless instructed otherwise by iSYSTEM support. Hardware CAN2/LIN2 Supported iC5700 add-on module CAN2/LIN2 which enables tracing and analysis of CAN, CAN-FD and LIN protocols. Note that support for LIN networks is not yet finalized and a new winIDEA version will be released soon to address that. Infineon DAP Active Probe Supported DAP Active Probe, iC5700 add-on module for TriCore debug and trace. It supports DAP debug protocol, as well as dual-channel operation with DAPE support (found on Aurix+ devices). DAP / DAPE frequencies up to 160MHz supported. ARM HSSTP Active Probe Supported HSSTP Active Probe, iC5700 add-on module for Cortex debug and trace. Note that support for HSSTP trace is not yet finalized and a new winIDEA version will be released soon to address that. USB Improved USB device enumeration on RDP. Devices that use RemoteFX for USB forwarding are now seen in winIDEA. Fixed USB support on Cirtrix servers. CPU Support PowerPC Added support for: ● ST Chorus2M Unlock with password now enabled on Cobra and Cobra55 MCUs. Cortex Added support for: ● NXP LPC546xx family ● Cypress Traveo II family TriCore Added support for: ● TC1738 Aurora trace supported on TC3xx family. Compact Function Trace supported, which limits the amount of trace data needed for program flow reconstruction. © iSYSTEM, March 2019 6/39 RH850 Added support for: ● RH850/D1M1A ● RH850/P1x (R7F701311, R7F701313) ● RH850/F1K (R7F701580x) Aurora trace supported on RH850/P1H-C. Software Internal SFR database Internal SFR database switched to SFRv2 revision. This is no longer compatible with older winIDEA versions and will be stored to a separate directory: %APPDATA%\ASYST\winIDEA\SFRv2. Analyzer Reordering of profiler items now possible through drag-and-drop. ​ ​ ​ ​ ​ Renesas E1 plugin Renesas E1 plugin EXEC updated to version E4.00.00.11 SDK Added new functions: ● CFunction::getLocalVars() - returns list of function local variables (including parameters). ● CDataController2::evaluateComposite() - provides simple evaluation of structure and array members. All addresses in isystem.connect functions are now 64-bit to provide support for new-generation MCUs: ● Python: no change, handled internally by Python ​ ● Java: No changes will be required, as long type was already used due to the lack of unsigned integer types. ​ However, this means that large addresses will be stored as negative values. To handle them properly as unsigned values, use functions in class Long, for example Long.compareUnsigned(), Long.toUnsignedString()... ● C#: All addresses are now 64-bit and the scripts will need to be updated. Change declaration of variables ​ containing addresses from 32 to 64 bits. ● All languages: VectorDWORD was replaced with AddressVector. ​ If the script needs to run on multiple versions of isystem.connect, create addresses this way: major, minor, build = ic.getModuleVersion().split('.') is64BitAddresses = int(major) >= 9 and int(minor) >= 17 and int(build) >= 16 if is64BitAddresses: addrs = ic.AddressVector() else: addrs = ic.VectorDWORD() Otherwise use AddressVector() only. © iSYSTEM, March 2019 7/39 9.17.19.0.73116 (21.10.2018) Hotfix build Software JTAG debug interface scan speed configuration moved to the CPU Setup dialog. Previously in the Emulation Options dialog. Previous Current © iSYSTEM, March 2019 8/39 9.17.39.0.78401 (10.4.2018) Verified build for PowerPC, RH850, and TriCore family. Use winIDEA 9.17.0 for Cortex microcontrollers, unless instructed otherwise by iSYSTEM support. Hardware ADIO Supported iC5700 Analog/Digital Input/Output add-on module (ADIO) which offers basic HIL capabilities with several digital IO ports and two analog IO ports, which can be controlled either manually or through isystem.connect interface. ADIO can also be traced to correlate HIL activity with on-chip trace data. FNet triggering system IOM6 add-on modules (CAN2/LIN2, ADIO) can generate FNet triggers based on observed network traffic. The triggers can be used to trigger various actions on ADIO module. Upcoming winIDEA versions will support FNet triggers as trace triggers, as well as additional actions, such as CAN message injection and debug operations. Please refer to winIDEA Help to learn more about FNet Triggers. Renesas E1 ● Renesas E1 plugin EXEC updated to version E4.00.00.11. ● RL78 DLL updated to version 1.09. ● winIDEA Open now supports 128kB code size with no license required. CPU Support Cortex Added support for: ● Cypress Traveo S6J334x, ● Dialog DA1468x, ● Synergy S5/S7. Renesas Synergy R7FS7, R7FS5 and Cypress PSoC5-LP devices now available for selection in separate CPU groups. This change will require a re-selection of the CPU in the Hardware / Emulation Options dialog. Improved memory access performance on Cypress Traveo, which significantly improves debugging experience. PowerPC Added support for: ● Chorus2M Emulation Device, ● SPC584C60, ● S32R372 (Race Runner Skinny). RH850 Added support for: ● RH850/D1L1 (R7F701401), ● RH850/D1L2 (R7F701402), ● RH850/F1K (R7F701567, R7F701582), ● RH850/F1KM-Sx(R7F7016xx) ● RH850/F1KM-S4, ● RH850/P1M (R7F701304). TriCore Added support for: ● TC387QP, ● TC389QP, ● TC397XA, © iSYSTEM, March 2019 9/39 ● TC397XA Step Bx, ● TC397XE, ● TC397XL Step Ax. Implemented connection to password protected TC3xx MCUs. Improved Flash programming speed on Aurix and Aurix+ devices. Software Analyzer Introduced Inspectors, new type of profiler areas, which, among other usages, allow complex event chain analysis. ​ ​ Refer to winIDEA Help to learn more about Inspectors, intended use-cases and configuration details.
Load more

Recommended publications
  • MIPI Alliance Test and Debug - Nidnt-Port White Paper
    MIPI Alliance Test and Debug - NIDnT-Port White paper Approved Version: 1.0 – 10 January 2007 MIPI Board Approved for Public Distribution NOTE and DISCLAIMER: This is an informative document, not a MIPI Specification. Various rights and obligations which apply solely to MIPI Specifications (as defined in the MIPI Membership Agreement and MIPI Bylaws) including, but not limited to, patent license rights and obligations, do not apply to this document. The material contained herein is not a license, either expressly or impliedly, to any IPR owned or controlled by any of the authors or developers of this material or MIPI. The material contained herein is provided on an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and MIPI hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR MIPI BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Freescale In-Circuit Emulator Base User Manual
    Freescale In-Circuit Emulator Base User Manual Rev. 1.1 1/2005 FSICEBASEUM How to Reach Us: Information in this document is provided solely to enable system and software implementers to use Freescale Semiconductor products. There are no express or implied copyright licenses USA/Europe/Locations Not Listed: granted hereunder to design or fabricate any integrated circuits or integrated circuits based on Freescale Semiconductor Literature Distribution Center the information in this document. P.O. Box 5405 Freescale Semiconductor reserves the right to make changes without further notice to any Denver, Colorado 80217 products herein. Freescale Semiconductor makes no warranty, representation or guarantee 1-800-521-6274 or 480-768-2130 regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability arising out of the application or use of any product or Japan: circuit, and specifically disclaims any and all liability, including without limitation Freescale Semiconductor Japan Ltd. consequential or incidental damages. “Typical” parameters that may be provided in Freescale Technical Information Center Semiconductor data sheets and/or specifications can and do vary in different applications and 3-20-1, Minami-Azabu, Minato-ku actual performance may vary over time. All operating parameters, including “Typicals”, must Tokyo 106-8573, Japan be validated for each customer application by customer’s technical experts. Freescale 81-3-3440-3569 Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed, intended, or authorized for use as Asia/Pacific: components in systems intended for surgical implant into the body, or other applications Freescale Semiconductor Hong Kong Ltd.
    [Show full text]
  • Renesas RX62N RDK User's Manual
    Renesas Demonstration Kit (RDK) for RX62N User’s Manual: Hardware RENESAS MCU 32 RX Family / RX600 Series / RX62N Group R20UT2531EU0100 All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). i Disclaimer By using this Renesas Demonstration Kit (RDK), the user accepts the following terms. The RDK is not guaranteed to be error free, and the User assumes the entire risk as to the results and performance of the RDK. The RDK is provided by Renesas on an “as is” basis without warranty of any kind whether express or implied, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, title and non-infringement of intellectual property rights with regard to the RDK. Renesas expressly disclaims all such warranties. Renesas or its affiliates shall in no event be liable for any loss of profit, loss of data, loss of contract, loss of business, damage to reputation or goodwill, any economic loss, any reprogramming or recall costs (whether the foregoing losses are direct or indirect) nor shall Renesas or its affiliates be liable for any other direct or indirect special, incidental or consequential damages arising out of or in relation to the use of this RDK, even if Renesas or its affiliates have been advised of the possibility of such damages.
    [Show full text]
  • ARM Debugger
    ARM Debugger TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... ICD In-Circuit Debugger ................................................................................................................ Processor Architecture Manuals .............................................................................................. ARM/CORTEX/XSCALE ........................................................................................................... ARM Debugger ..................................................................................................................... 1 History ................................................................................................................................ 7 Warning .............................................................................................................................. 8 Introduction ....................................................................................................................... 9 Brief Overview of Documents for New Users 9 Demo and Start-up Scripts 10 Quick Start of the JTAG Debugger .................................................................................. 12 FAQ ..................................................................................................................................... 13 Troubleshooting ...............................................................................................................
    [Show full text]
  • The ZEN of BDM
    The ZEN of BDM Craig A. Haller Macraigor Systems Inc. This document may be freely disseminated, electronically or in print, provided its total content is maintained, including the original copyright notice. Introduction You may wonder, why The ZEN of BDM? Easy, BDM (Background Debug Mode) is different from other types of debugging in both implementation and in approach. Once you have a full understanding of how this type of debugging works, the spirit behind it if you will, you can make the most of it. Before we go any further, a note on terminology. “BDM” is Motorola’s term for a method of debugging. It also refers to a hardware port on their microcontroller chips, the “BDM port”. Other chips and other manufacturers use a JTAG port (IBM), a OnCE port (Motorola), an MPSD port (Texas Instruments), etc. (more on these later). The type of debugging we will be discussing is sometimes known as “BDM debugging” even though it may use a JTAG port! For clarity, I will refer to it as “on-chip debugging” or OCD. This will include all the various methods of using resources on the chip that are put there to enable complete software debug and aid in hardware debug. This includes processors from IBM, TI, Analog Devices, Motorola, and others. This paper is an overview of OCD debugging, what it is, and how to use it most effectively. A certain familiarity with debugging is assumed, but novice through expert in microprocessor/microcontroller design and debug will gain much from its reading. Throughout this paper I will try to be as specific as possible when it relates to how different chips implement this type of debugging.
    [Show full text]
  • Attiny1607 Curiosity Nano Hardware User Guide
    ATtiny1607 Curiosity Nano ATtiny1607 Curiosity Nano Hardware User Guide Preface The ATtiny1607 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the ATtiny1607 microcontroller (MCU). Supported by Atmel Studio/Microchip MPLAB® X Integrated Development Environment (IDE), the kit provides easy access to the features of the ATtiny1607 to explore how to integrate the device into a custom design. The Curiosity Nano series of evaluation kits include an on-board debugger. No external tools are necessary to program and debug the ATtiny1607. © 2019 Microchip Technology Inc. User Guide DS50002897B-page 1 ATtiny1607 Curiosity Nano Table of Contents Preface...........................................................................................................................................................1 1. Introduction............................................................................................................................................. 3 1.1. Features....................................................................................................................................... 3 1.2. Kit Overview................................................................................................................................. 3 2. Getting Started........................................................................................................................................ 4 2.1. Curiosity Nano Quick Start...........................................................................................................4
    [Show full text]
  • The Design of a Debugger Unit for a RISC Processor Core
    Rochester Institute of Technology RIT Scholar Works Theses 3-2018 The Design of a Debugger Unit for a RISC Processor Core Nikhil Velguenkar [email protected] Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Velguenkar, Nikhil, "The Design of a Debugger Unit for a RISC Processor Core" (2018). Thesis. Rochester Institute of Technology. Accessed from This Master's Project is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. The Design of a Debugger Unit for a RISC Processor Core by Nikhil Velguenkar Graduate Paper Submitted in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering Approved by: Mr. Mark A. Indovina, Lecturer Graduate Research Advisor, Department of Electrical and Microelectronic Engineering Dr. Sohail A. Dianat, Professor Department Head, Department of Electrical and Microelectronic Engineering Department of Electrical and Microelectronic Engineering Kate Gleason College of Engineering Rochester Institute of Technology Rochester, New York March 2018 To my family and friends, for all of their endless love, support, and encouragement throughout my career at Rochester Institute of Technology Abstract Recently, there has been a significant increase in design complexity for Embedded Sys- tems often referred to as Hardware Software Co-Design. Complexity in design is due to both hardware and firmware closely coupled together in-order to achieve features forlow power, high performance and low area. Due to these demands, embedded systems consist of multiple interconnected hardware IPs with complex firmware algorithms running on the device.
    [Show full text]
  • USB3 Debug Class Specification
    USB 3.1 Debug Class 7/14/2015 USB 3.1 Device Class Specification for Debug Devices Revision 1.0 – July 14, 2015 - 1 - USB 3.1 Debug Class 7/14/2015 INTELLECTUAL PROPERTY DISCLAIMER THIS SPECIFICATION IS PROVIDED TO YOU “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE. THE AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PROPRIETARY RIGHTS, RELATING TO USE OR IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. THE PROVISION OF THIS SPECIFICATION TO YOU DOES NOT PROVIDE YOU WITH ANY LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS. Please send comments via electronic mail to [email protected]. For industry information, refer to the USB Implementers Forum web page at http://www.usb.org. All product names are trademarks, registered trademarks, or service marks of their respective owners. Copyright © 2010-2015 Hewlett-Packard Company, Intel Corporation, Microsoft Corporation, Renesas, STMicroelectronics, and Texas Instruments All rights reserved. - 2 - USB 3.1 Debug Class 7/14/2015 Contributors Intel (chair) Rolf Kühnis Intel Sri Ranganathan Intel Sankaran Menon Intel (chair) John Zurawski ST-Ericsson Andrew Ellis ST-Ericsson Tomi Junnila ST-Ericsson Rowan Naylor ST-Ericsson Graham Wells ST Microelectronics Jean-Francis Duret Texas Instruments Gary Cooper Texas Instruments Jason Peck Texas Instruments Gary Swoboda AMD Will Harris Lauterbach Stephan Lauterbach Lauterbach Ingo Rohloff Nokia Henning Carlsen Nokia Eugene Gryazin Nokia Leon Jørgensen Qualcomm Miguel Barasch Qualcomm Terry Remple Qualcomm Yoram Rimoni - 3 - USB 3.1 Debug Class 7/14/2015 TABLE OF CONTENTS 1 TERMS AND ABBREVIATIONS .......................................................................................................
    [Show full text]
  • Iot Security-Part 14 (Introduction to and Identification of Hardware Debug Ports)
    ⌂ Home › ☷ All Blogs › ✍ Shakir › IoT Security-Part 14 (Introduction To And Identification Of Hardware Debug Ports) Shakir 26-September-2020 IoT Security-Part 14 (Introduction to and Identification of Hardware Debug Ports) This blog is part of the IoT Security series where we discuss the basic concepts pertaining to the IoT/IIoT eco-system and its security. If you have not gone through the previous blogs in the series, I would urge you to go through those first. In case you are only interested in the Hardware debug ports, feel free to continue. IoT Security - Part 1 (101 - IoT Introduction And Architecture) IoT Security - Part 13 (Introduction To Hardware Recon) In the previous blog, we discussed how to perform reconnaissance on hardware. In this blog, we will discuss Hardware debug ports, what are the different debug ports, and how to find debug ports using different methods. Finding the hardware debug port process consists of several steps like looking at the various test pads, pinouts, headers. Rarely these pins are labeled on PCB so we have to identify pins manually. Information from the microcontroller datasheet about pins and simple continuity check using a multimeter is good enough for IC packages like DIP/TSOP, TQFP (for more information about IC packages refer this blog IoT Security-Part 13 (Introduction To Hardware Recon) but for packages like QFN, BGA, etc. where pins are not accessible on PCB it is difficult to identify manually. For such cases where continuity check is not possible, tools like Bus Auditor or Jtagulator come very handy. Once JTAG/SWD, UART, I2C pins are identified on PCB, access to the microcontroller, firmware extraction, root shell access is possible.
    [Show full text]
  • C166S on Chip Debug Support
    User’s Manual, V 1.1, August 2001 C166S On Chip Debug Support Microcontrollers Never stop thinking. Edition 2001-08 Published by Infineon Technologies AG, St.-Martin-Strasse 53, D-81541 München, Germany © Infineon Technologies AG 2001. All Rights Reserved. Attention please! The information herein is given to describe certain components and shall not be considered as warranted characteristics. Terms of delivery and rights to technical change reserved. We hereby disclaim any and all warranties, including but not limited to warranties of non-infringement, regarding circuits, descriptions and charts stated herein. Infineon Technologies is an approved CECC manufacturer. Information For further information on technology, delivery terms and conditions and prices please contact your nearest Infineon Technologies Office in Germany or our Infineon Technologies Representatives worldwide (see address list). Warnings Due to technical requirements components may contain dangerous substances. For information on the types in question please contact your nearest Infineon Technologies Office. Infineon Technologies Components may only be used in life-support devices or systems with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system, or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body, or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered. User’s Manual, V 1.1, August 2001 C166S On Chip Debug Support Microcontrollers Never stop thinking.
    [Show full text]
  • Stm32h7x5/X7 Dual-Core Microcontroller Debugging
    AN5286 Application note STM32H7x5/x7 dual-core microcontroller debugging Introduction The STM32H7x5/x7 dual-core microcontroller lines as described in Table 1. Applicable products (named STM32H7x5/x7 microcontrollers in this document) are based on the high-performance Arm® Cortex®-M7 and Cortex®-M4 32-bit RISC cores. The STM32H7x5/x7 microcontrollers require a specific development approach so the application can take maximum advantage dual core architecture. This application note provides guidelines for the debug of custom applications which run on the STM32H7x5/x7 microcontrollers using the software Toolchains: EWARM, MDK-ARM and SW4STM32. The following subjects are addressed; • An overview of the new IDE features which supports the dual core products. • How to use EWARM, MDK-ARM and SW4STM32 with a dual-core device using the ST-LINK debug. For more information on the STM32H7x5/x7 microcontrollers, refer to the following documents on www.st.com: • STM32H745xI/G datasheet (DS12923) • STM32H755xI datasheet (DS12919) • STM32F7 Series and STM32H7 Series Cortex®-M7 processor programming manual (PM0253) Table 1. Applicable products Generic part numbers Applicable product lines STM32H7x5/x7 STM32H745/755, STM32H747/757 AN5286 - Rev 1 - July 2019 www.st.com For further information contact your local STMicroelectronics sales office. AN5286 General information 1 General information This document applies to the STM32H7x5/x7 dual-core Arm®-based microcontroller lines. Note: Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. AN5286 - Rev 1 page 2/45 AN5286 Dual debug main features 2 Dual debug main features A multicore processor is composed of either heterogeneous cores (which means different cores) or homogenous cores (identical cores).
    [Show full text]
  • Quick Start Guide Sr S Manual User’
    Guide Start Quick User’Manual s RA2L1 Group Evaluation Kit for RA2L1 Microcontroller Group EK-RA2L1 Quick Start Guide Renesas RA Family RA2 Series All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). www.renesas.com Rev.1.00 Oct.22.20 Notice 1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation or any other use of the circuits, software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third parties arising from the use of these circuits, software, or information. 2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims involving patents, copyrights, or other intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or technical information described in this document, including but not limited to, the product data, drawings, charts, programs, algorithms, and application examples. 3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 4. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics product, whether in whole or in part.
    [Show full text]