• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 62 subscribers
  • Views 254 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

UCD3138: The problem of programming via jtag

Alexandr Emelyanov
Prodigy 10 points
Part Number: UCD3138
Other Parts Discussed in Thread: , UNIFLASH

When trying to program UCD3138RHA via Jtag, XDS110 shows that I am using UCD3138A and programming is prohibited. UCD3138 is selected in the Target Configuration and the connection test is successful.

use CCS11

Console:

Texas Instruments XDS110 USB Debug Probe_0/ARM7_0 : Target must be connected before loading program.
ARM7_0: GEL Output: /nMemory Map Initialization Complete/nARM7_0: GEL Output: /tMemory Map Setup for Flash at Address 0x0ARM7_0: Device Identification (DEV) 0x847F, Device is UCD3138A
ARM7_0: Flash Programmer: Target configuration does not match the connected chip; expected:UCD3138, actual:UCD3138A
ARM7_0: Boot ROM Region at memory range 0x0000A000 - 0x00001000
ARM7_0: Data RAM Region at memory range 0x00019000 - 0x00001000
ARM7_0: Flash Region #0 at memory range 0x00000000 - 0x00008000, erase page 0x400 bytes
ARM7_0: Flash Region #1 at memory range 0x00018800 - 0x00000800, erase page 0x20 bytes
ARM7_0: Writing Flash @ Address 0x00000000 of Length 0x000018d2
ARM7_0: [WriteData Error]Target configuration does not match the connected chip; expected:UCD3138, actual:UCD3138A
ARM7_0: File Loader: Memory write failed: Unknown error
ARM7_0: GEL: File: D:\Git_Local\WDIT1500\Source_code\UCD3138\WDIT1500_UCD3138.x0: Load failed.
ARM7_0: Unable to terminate memory download: NULL buffer pointer at 0x320

Perhaps when selecting USD3138, the configuration does not change and it is necessary to manually select the device in the target code, but I do not know where it is located

  • 0
    TI__Genius 17090 points

    You need to go to CCS, right click on the project in the project explorer window, and select Build Options.  

    Click on manage configurations.

    Click on UCD3138A, then on set active.

    Then click on the 2 OK buttons necessary to exit the menu, and it should put in the UCD3138A as the active processor.

    Then rebuild the project, and you should be good to go.  

  • 0 in reply to Ian Bower
    Prodigy 10 points

    I have a UCD3138 chip and I have chosen a configuration for it.

    in the target configuration also ucd3138

    as soon as I click the debug button, a message appears:

    I always flashed on PMBUS with settings for UCD3138 (not UCD3138A) and everything was fine.

  • 0 in reply to Alexandr Emelyanov
    TI__Genius 17090 points

    The UCD3138A is different from the UCD3138.  It is possible that if you download a 3138 code to a 3138 that an issue could occur, so it seems the firmware stops you from downloading to the UCD3138A.  The debug is a separate issue from the download. If you need to debug on the 3138A I can try to figure that issue out for you.  I suspect you need to reconfigure the debug for the 3138A as well, but I'm not an expert on that.  

    The debug configuration is different from the Uniflash, which I assume you are using to download the code to the UCD?  Please try my suggestions for the download and let me know if it fixes it.  

  • 0 in reply to Ian Bower
    Prodigy 10 points

    no, I don't use uniflash. I am trying to run debugging via CSS for UCD3138 (not UCD3138A).
    But before debugging, I try to flash the UCD via JTAG, and errors are displayed by the messages above. I chose UCD3138 in all settings (not UCD3138A), but the error

    does not disappear.

    This error is confusing. UCD3138RHA is it UCD3138 or UCD3138A?

  • 0 in reply to Alexandr Emelyanov
    TI__Genius 17090 points

    A UCD3138RHA is a UCD3138, not a UCD3138A.  However the PMBus based flashing will let you program a UCD3138A with a UCD3138 program because it is almost all backward compatible.

    Can you hook the problematic chip up to a PMBus interface and scan for device in ROM mode?  

    for a 3138, it should say Found ROM v2 IC v3 UCD3138 Rev2 or something similar.

    for a 3138A it should say Found ROM v2 IC v3 UCD3138A Rev2

    I can't believe that the debugger would misidentify the chip.  

  • 0 in reply to Ian Bower
    Prodigy 10 points

    Yes, I made a mistake, PMBus showed UCD3138A. I'll try using Jtag again for new settings and let you know. Thanks for the hint