Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 389 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.

TMS320F2800137: XDS110 not able to program device

Johnny Chen
Expert 4060 points
Part Number: TMS320F2800137

Hi Champ,

I am asking for my customer.

The source of 3.3V is supplied by DC source to JTAG 14 pin header.

The test connection in target configuration is shown "The JTAG IR Integrity scan-test has succeeded." , while to program a new device on customer's own board, there is an error shown as below. The JTAG schematic is also shown below, C80 & R59 are removed. 

Look into customer's schematic, it was found out the boot pins (GPIO24&32) weren't initially pull high to 1 as flash boot. 

(1). I am asking if the boot pins weren't set properly to boot to flash, could the image be programmed successfully via XDS110 into a new device ? Or the two things are independent and not relative to each other ? 

(2). After asking customer to both PU to 3.3V on GPIO24&32, the new device wasn't still unavailable to program with below new error. From other C2k series DS, such as F2837x, there is a note for The default behavior of Get mode is boot-to-flash. On unprogrammed devices, using Get mode will result in repeated watchdog resets, which may prevent proper JTAG connection and device initialization. Use Wait mode or another boot mode for unprogrammed devices. Is it still valid for F280013x if we try to program a new unprogrammed device ? 

(3). What is the troubleshoot or place to dive into to address such unable to program a new device ?

Thanks and regards,

Johnny

  • 0
    TI__Guru** 112995 points

    Hi,

    Johnny Chen said:
    (1). I am asking if the boot pins weren't set properly to boot to flash, could the image be programmed successfully via XDS110 into a new device ? Or the two things are independent and not relative to each other ? 

    That should not matter. What is the value driven on boot pins ?

    Johnny Chen said:
    (2). After asking customer to both PU to 3.3V on GPIO24&32, the new device wasn't still unavailable to program with below new error. From other C2k series DS, such as F2837x, there is a note for The default behavior of Get mode is boot-to-flash. On unprogrammed devices, using Get mode will result in repeated watchdog resets, which may prevent proper JTAG connection and device initialization. Use Wait mode or another boot mode for unprogrammed devices. Is it still valid for F280013x if we try to program a new unprogrammed device ? 

    Yes, this is still valid. User can probe the XRSn pin to see if device is in reset loop.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Expert 4060 points

    Hi Vivek,

    Vivek Singh said:
    That should not matter. What is the value driven on boot pins ?

    Is it confirmed that even though the boot pins weren't boot to flash, the device should still be programmed via JTAG, correct ? Since the boot pins only decide how it boot to in boot ROM code, correct ?

    Currently, the value driven on boot pins are initially pulled high. 

    Vivek Singh said:
    User can probe the XRSn pin to see if device is in reset loop.

    I agree with that, may I reconfirm during programming, the XRSn pin should be always active high, right ?

    By the way, I have never seen the error of 6311, what does the PRSC module failed mean ? And what cause it failure, any root cause of the error ?

    Thanks and regards,

    Johnny

  • +1 in reply to Johnny Chen
    TI__Guru** 112995 points
    Johnny Chen said:
    I agree with that, may I reconfirm during programming, the XRSn pin should be always active high, right ?

    Yes, it need to be high.

    Johnny Chen said:
    By the way, I have never seen the error of 6311, what does the PRSC module failed mean ? And what cause it failure, any root cause of the error ?

    These are errors from driver and very low level details which are not documented for user. 

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Expert 4060 points

    Hi Viviek,

    Thanks for the help. The issue is solved on XRsn causing device reset.

    Johnny