[ABANDONED] Jtrace issue connecting with Nuvoton M2354

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] Jtrace issue connecting with Nuvoton M2354

    Using JFlash V7.88c via JTrace pro to attempt to connect to a Nuvoton M2354, getting

    Application log started
    - J-Flash V7.88c (J-Flash compiled May 16 2023 15:44:36)
    - JLinkARM.dll V7.88c (DLL compiled May 16 2023 15:43:58)
    Reading flash device list [C:\Program Files\SEGGER\JLink\ETC/JFlash/Flash.csv] ...
    - List of flash devices read successfully (451 Devices)
    Reading MCU device list ...
    - List of MCU devices read successfully (10343 Devices)
    Opening project file [C:\Users\xxxxx\Nuvoton 2354.jflash] ...
    - Project opened successfully
    No data file specified!
    Failed to open data file [C:\Users\xxxx\]...
    Connecting ...
    - Connecting via USB to probe/ programmer device 0
    - Probe/ Programmer firmware: J-Trace PRO V2 Cortex-M compiled May 16 2023 10:45:39
    - Probe/ Programmer S/N: 752002064
    - Device "M2354KJFAE" selected.
    - Target interface speed: 1000 kHz (Fixed)
    - VTarget = 2.720V
    - Found SW-DP with ID 0x0BF11477
    - DPIDR: 0x0BF11477
    - CoreSight SoC-400 or earlier
    - Scanning AP map to find all available APs
    - AP[0]: Stopped AP scan as end of AP map seems to be reached
    - Iterating through AP map to find AHB-AP to use
    - Attach to CPU failed. Executing connect under reset.
    - DPIDR: 0x0BF11477
    - CoreSight SoC-400 or earlier
    - Scanning AP map to find all available APs
    - AP[0]: Stopped AP scan as end of AP map seems to be reached
    - Iterating through AP map to find AHB-AP to use
    - Could not find core in Coresight setup
    - Found SW-DP with ID 0x0BF11477
    - DPIDR: 0x0BF11477
    - CoreSight SoC-400 or earlier
    - Scanning AP map to find all available APs
    - AP[0]: Stopped AP scan as end of AP map seems to be reached
    - Iterating through AP map to find AHB-AP to use
    - Attach to CPU failed. Executing connect under reset.
    - DPIDR: 0x0BF11477
    - CoreSight SoC-400 or earlier
    - Scanning AP map to find all available APs
    - AP[0]: Stopped AP scan as end of AP map seems to be reached
    - Iterating through AP map to find AHB-AP to use
    - Could not find core in Coresight setup
    - ERROR: Failed to connect.
    Could not establish a connection to target.

    Thoughts? I had similar results at a 1KHz rate... It seems to be able to identify the chip ID so I believe we have the connection to the J-trace wired properly, at least as far as ground. power and SWDIO and SWCLK.

    Note that the USB LED on the J-Trace was orange.

    I am able to program the device with a Nuvoton debugger and we have populated the board with different headers to account for the pinout diferences between the Nuvoton and J-Link/Trace interfaces.

    The post was edited 3 times, last by Cws ().

  • What has caught my attention is the line:
    VTarget = 2.720V

    Is the target expected to work with 2.7V signals on the debug lines (SWCLK, SWDIO, …)?
    3.3V or 1.8V sounds like common target voltages but 2.7V sounds a bit odd.

    If this is a 3.3V target, the 2.7V could indicate an issue with your wiring and explain the flaky effects you are seeing.
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.