• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 1184 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.

booting process of new unprogrammed devices TMS320F28377S

MARK PESACH
Intellectual 850 points
Other Parts Discussed in Thread: TMS320F28377S

hi 

I have another question related to the booting process:

i came a cross the next note : 
"The default behavior of Get mode is boot-to-flash. On unprogrammed devices, using Getmode 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."

if i am planning to use the boot from flash option ( meaning both GPIO 84 and GPIO 72 with pull up resistors ) i cant enter the wait mode, from what i understand from this note - for new unprogrammed devices i have to add another booting option?


can you please advise me

best regards 
Mark

  • 0
    TI__Mastermind 19810 points
    Mark,
    that note is just a caution and tells why you might see repeated resets when you put the device in GETMODE with flash unprogrammed. The result is, if you are trying to connect JTAG when the device is booting to GETMODE->Flash on unprogrammed device, depending on when you click target connect on CCS the JTAG might fail to connect if the device is going through a reset at that point.

    If you plan to program flash then it is safe to use GET MODE to boot to flash. I would suggest to have WAIT MODE option available because that will let the device execute a loop in boot ROM and it might help if you want to catch the CPU before it gets to the application. SCI Boot mode will help as well with same but the SCITX and SCIRX could be pulled up.

    Hope this helps.

    Best Regards
    Santosh Athuru
  • 0 in reply to Santosh Athuru
    Intellectual 850 points
    hi Santosh

    thank you for your reply .
    i read note application about the boot process many times, but still i dont fully understand it.
    it would be great if you can simplify it for me:
    i am using xds100v2 external emulator to debug and upload firmware .

    - our application in stand alone whould run from FLASH - so we pulled up the GPIOS to enter the GETMODE in the boot option.
    - now that we DEBUG our application i use the set active RAM conifguration in the build configuration , the final product will run with the set active FLASH option .

    so basically for my needs , when i start to work with a new TMS320F28377S chip
    is there any other special configurations i need to do , what about the EMU_KEY and EMU_BMODE , do i need to change there default values for some reason?

    best regards
    MARK
  • 0 in reply to MARK PESACH
    TI__Guru 55700 points

    Mark,

    When device is connected to emulator. You should follow Table 3-3. Emulation Boot (TRSTn == 1)

    Boot to RAM in emulation boot mode:

    (1) EMU_KEY       = 0x5A

    (2) EMU_BMODE = 0x0A

    Boot to Flash in emulation boot mode:

    (1) EMU_KEY       = 0x5A

    (2) EMU_BMODE = 0x0B


    Both EMU_KEY & EMU_BMODE are defined in Table 3-2. EMU_BOOTCTRL Definition.

    Regards,

    Manoj

  • 0 in reply to MARK PESACH
    TI__Expert 6525 points

    hi Manoj,

    Now my customer also use unprogrammed F28377S. They also got same issue which watch dog reset is enabled. And JTAG can't be connected. I change the Boot mode setting to parallel IO and check the RST pin after power up device. RST pin didn't pull low periodically which mean watchdog didn't generate reset. However, when i connect XDS100 to customer board and try to connect to target. TRST pin still didn't be pulled high. JTAG connection still fail. Please see the attach waveform.  I also change boot mode to wait boot mode and TRST pin didn't pull high and JTAG connection still failed. Could you please tell me after i change the boot mode, can i use JTAG to connect device. If yes, why i still can't connect to target after change boot mode. thanks for your reply in advance. 

    Power up board

    CH1 : RST CH2: TRST

    Try to connect to target

    CH1 : RST CH2: TRST

  • 0 in reply to Lisa Ding
    TI__Guru** 113185 points

    Hi Lisa,

    How are you probing TRSTn pin (at which point). TRSTn pin is input to device and driven by emulator. If it's not going high when trying to connect, I would suspect some issue with board and should check the connection.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Expert 6525 points

    Hi Vivek,

    OK. I see. I found out the board short TRST with XRS pin. Wait for customer to double check. thanks for your help!