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.

TMS320F280025C: C2PROG couldn't programming with new device

Part Number: TMS320F280025C

Hi Team,

  My customer used F280025C,  and reported an unexpected issue that the F280025C couldn't programmed by C2PROG but could programmed by JTAG and also run correctly.

  The C2Prog version is V1.8,  and report below information:

     1) Connecting with target(autobaud).. OK

      2) Bootloading.. OK

      3) Connecting with target..OK

      4)Loading.. failed(no responding)

  also tried with previous lot of F280025C, which could use C2Prog worked well.

  Could you kindly give comments how to solve the C2Prog issue?

Best Regards

Benjamin

  • Benjamin,

    C2Prog does support F28002x. Can you share the failure snapshot?  

    Are you saying that C2Prog V1.8 works for a previous lot of F280025C but not for the latest lot?

    Please clarify.

    Thanks and regards,
    Vamsi

  • Hi Vamsi,

       Yes, with previous lot of F280025C which worked well but failed at latest lot. 

       The failure snapshot shown as below figure.

    Best Regards

    Benjamin

  • Benjamin,

    Please ask customer to launch C2Prog via the "C2ProgShell.exe" executable and program the MCU via *JTAG* (not SCI). The console window might provide some additional diagnostic information.

    Also, please inquire with the customer if this last lot of MCUs has been programmed before. In particular, find out of these chips have non-default OTP settings.

    Thanks,

    Beat

  • Hi team,

       For the device lot couldn't use c2Prog SCI way:  F280025PNS  $7A-09A4XOW        &     F280025CPNS $7A-09A4XEW;

       For the device lot could use C2Prog SCI way: F280025CPNS $7-01AELDW;   

       Updated the information as below figure while run "C2ProgShelll.exe" with JTAG programming. 

    Expect for your kindly reply, thanks.

    Best Regards

    Benjamin

  • Hello Benjamin,

    Thank you for providing the screenshot. This confirms that the problem is not OTP related.

    Maybe it is not the device lot that creates the problem, but rather a different lot of boards? Is your customer using TI evaluation hardware, or have they designed their own boards?

    To further investigate the problem, I would like to inspect the communication logs.

    Please instruct your customer to do the following:

    1) create a folder named "c2plogs" in the current user directory, e.g. "C:\Users\jdoe\c2plogs".

    2) attempt programming over SCI on a target that exhibits the problem.

    3) send you the files named "bootlog.txt" and "loadlog.txt" that will be located in the "C:\Users\jdoe\c2plogs" folders.

    Then you can email those files to info@codeskin.com so that I can review them.

    Thanks,

    Beat

  • Hi Team,

      The failure reported in customer board, and also echo my previous comments, has done the change with previous old lot F280025 in same board which works well.

      Also I've review the schematic, the board should has no wrong connection.

      I've mailed to you with the log information based on steps your provided.  Expect for your kindly reply, thanks.

    Best Regards

    Benjamin

  • Benjamin,

    Since we are discussing this offline, I will keep this E2E thread in pause for now.

    Thanks and regards,
    Vamsi

  • Benjamin,

    I am closing this post since we did not hear back from you on the email discussion.

    Thanks and regards,

    Vamsi