• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 84 subscribers
  • Views 267 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.

Original question:

TMS320F280039C: After DCSM setup, JTAG cannot connect.

TMS320F28377D: DCSM change from EMUBOOT flash boot to wait boot

Jesus Chung
Prodigy 60 points
Part Number: TMS320F28377D

Hello,

I am having issues connecting the JTAG to the C28377D processor after programming the DCSM (pwdlock is not yet programmed).
During testing, I programmed the DCSM password first. This would still work.

I then programmed the GRABSECT/GRABRAM in OTP

Now, the device is in low power mode when trying to connect via JTAG.

From other forums, it is indicated that I should use "WAIT BOOT" in this case.

how can I externally change the EMUBOOT data in ram, if this is now in a secured area?

The EMUBOOT was originally programmed to BOOT TO FLASH (0x0B).

how do you recommend starting "wait boot" externally?

Thanks,

Jesus

  • 0
    TI__Guru** 113725 points

    Hi,

    Wait BOOT setting is done by changing the value of BOOT MODE pin on the board. Below is snapshot from device TRM.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 60 points

    Hello Vivek,

    We currently have the board setup with the boot pins set to HIGH (or Get/FLASH).
    Is there a way to leave the pins as they are and have the board use "Wait Boot" when using the Emulator?

    I noticed that I am setting the EMU_KEY to 0x5A and EMU_BMODE to 0x0B (Boot to flash).
    Would I have to change the EMU_BMODE to 0x03 (WAit Boot) or leave EMU_KEY to != 0x5A so it defaults to wait boot.
    Would this work?

    Also, is there a way to then use the emulator with DCSM programmed and allow the JTAG to connect automatically after a power reset?
    The reason I programmed EMU_KEY and EMU_BMODE for Boot to Flash is so that the code will restart automatically after a reset command.

    Originally, with Wait Boot, the JTAG would stop and a reset is required after every reset/restart.

    Thanks,

    Jesus

  • 0 in reply to Jesus Chung
    TI__Guru** 113725 points

    Hi,

    Jesus Chung said:
    Is there a way to leave the pins as they are and have the board use "Wait Boot" when using the Emulator?

    No, wait boot is based on pin setting only.

    Jesus Chung said:
    Would I have to change the EMU_BMODE to 0x03 (WAit Boot) or leave EMU_KEY to != 0x5A so it defaults to wait boot.
    Would this work?

    Unfortunately no, because this setting is only used when you are already connected to emulator. 

    Jesus Chung said:
    Also, is there a way to then use the emulator with DCSM programmed and allow the JTAG to connect automatically after a power reset?
    The reason I programmed EMU_KEY and EMU_BMODE for Boot to Flash is so that the code will restart automatically after a reset command.

    No, after power cycle, emulation connection will be lost and also these settings. So it'll not re-connect using Wait Boot. It'll boot in Get/Flash boot after power cycle.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 60 points

    Hello Vivek,

    Thanks for the information. I'll try setting the Boot pins to Wait Boot and debug.

    If I change the boot pins to "Wait Boot", when I am not using the emulator/JTAG, then the device will stay in this While(1) due to wait boot?
    Is there a way to keep the Wait Boot using the boot pins, and still have the CPU jump to FLASH/application for standalone mode?

    Thanks,

    Jesus

  • 0 in reply to Jesus Chung
    TI__Guru** 113725 points
    Jesus Chung said:
    If I change the boot pins to "Wait Boot", when I am not using the emulator/JTAG, then the device will stay in this While(1) due to wait boot?

    Yes, that is correct.

    Jesus Chung said:
    Is there a way to keep the Wait Boot using the boot pins, and still have the CPU jump to FLASH/application for standalone mode?

    You need to change the BOOT pin setting for Get/FlashBoot in this case.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 60 points

    Vivek,

    I have modified the board so the BOOT PIN is set to WAIT BOOT. 
    I programmed CPU1 with the CSM settings but not the PSWDLOCK.
    I have been able to connect to the board with the JTAG and everything is good.

    I now programmed CPU2 and now am getting issues and cannot consistently connect to the JTAG.

    On connect, I am able to get CPU1 and CPU2 DcsmZ1Regs.Z1_CR = 0x0060 - which means the device is unlocked.

    CPU1 will boot to flash, run its code and part of the application is to reset CPU2.
    This seems to re-lock the DCSM on CPU2 which is not locked. Z1_CR = 0x0040.

    Seems that any reset to either CPU1 or CPU2 will re-lock the DCSM. Is there a method to ensuring that the DCSM is unlocked while the JTAG is connected?

    Thanks,

    Jesus

  • 0 in reply to Jesus Chung
    TI__Guru** 113725 points

    Hi,

    Jesus Chung said:
    Seems that any reset to either CPU1 or CPU2 will re-lock the DCSM.

    This is correct. After reset the DCSM will get re-lock.

    Jesus Chung said:
    Is there a method to ensuring that the DCSM is unlocked while the JTAG is connected?

    No, that is not possible but after reset, PC points to BOOTROM code so even if DCSM is enabled, it should not cause JTAG to be disconnected. 

    Regards,

    Vivek Singh