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.

TMS320F28335: Wait In Reset Mode Failure

Part Number: TMS320F28335
Other Parts Discussed in Thread: TMDSEMU200-U

Hello there,

 

I am using the TMS320F28335.

 

I have finished developing the firmware and activated the CSM, to connect controller, if I change the boot mode of the chip to 'Branch to check boot mode' everything is fine. However, i have to use the "wait in reset mode".

 

I cannot access the JTAG emulator with "wait in reset mode".

 

I do some changes in the target configuration file, advanced settings, The JTAG nTRST Boot-Mode and nothing changed.

 

I think i can't change the emu0 and emu1 pins status. 

 

When I check the card's schematic, the EMU0 and EMU1 pins seem to reach the JTAG connection.

 

Code Composer Studio Version: 11.2.0.00007 

Docking-Stn USB-EMU (R3)

XDS200 Debug Probe TMDSEMU200-U 

  • Hi Halit,

    Currently, what are your EMU0 and EMU1 pins configured to be?

    Kind regards,
    AJ Favela 

  • Dear Favela, 

    As stated in Table 7.2 of the spru430F document, the JTAG n TRST Boot-Mode is set with EMU1 high and EMU0 low. I tried other options too, but nothing changed. I tried to upload image but the system gave an error.

  • Hi Halit,

    I have brought this to the attention of the CSM expert, as I believe that is what is preventing you from accessing the JTAG emulator while in wait in reset mode. 

    Additionally, please note that due to the holidays there might be a delay in responses.

    Kind regards,

    AJ Favela 

  • Hello,

    When I check the card's schematic, the EMU0 and EMU1 pins seem to reach the JTAG connection.

    Yes, EMU0 and EMU1 are pinned out to JTAG debug probe. 

    I do some changes in the target configuration file, advanced settings, The JTAG nTRST Boot-Mode and nothing changed.

     

    I think i can't change the emu0 and emu1 pins statu

    What are you setting in the target configuration file? Can you please confirm with a scope that TRSTn/EMU0/EMU1 are being properly set by CCS? 

    Best,

    Matt

  • Dear Matt, Hello,

    As a debugger, I was able to activate the "wait in reset" mode using the xds560v2 System Trace. I did this with the same configuration and the same ccs11.2 software.

    Then I reinstalled ccs11.2 on another computer from TI's own website and tried again, but still couldn't get it into the "wait in reset" mode with the xds200 debugger.

    Best Regards,

  • Hello,

    To make sure we're on the same page:

    • XDS560v2 works on CCS 11.2 with PC #1
    • XDS200 does NOT work on CCS 11.2 with PC #2

    Have you checked if the XDS560v2 works on PC #2? Does the XDS200 work on PC #1?

    Best,
    Matt

  • Dear Matt,

    Let me clarify situation,

    • XDS560v2 works on CCS 11.2 with PC #1 and PC #2 with the "wait in reset" mode feature. 
    • XDS200 work on CCS 11.2 with PC #1 and PC #2. If CSM is not active, the program can be loaded. XDS200 does NOT work on CCS 11.2 with PC #1 and PC #2 with the "wait in reset" mode feature.

    Best Regards,

  • Halit,

    XDS560v2 works on CCS 11.2 with PC #1 and PC #2 with the "wait in reset" mode feature. 

    Are you doing this by setting the properties like the below for XDS560v2?

  • Hi Ki,
    Actually, I configure the XDS560 debugger as follows and can actively use the wait-in-reset mode.

    The JTAG NTRST Boot-Mode   --> Enabled - EMU1 is high, EMU0 is low,

    The Power-On-Reset Boot Mode  ---> Disabled - Both EMU pins remain hi - z 

    When I do the same configuration with xds200, "wait in reset mode" doesn't work, that's the problem.

    Regards,

  • When I do the same configuration with xds200, "wait in reset mode" doesn't work, that's the problem.

    Ah I see. With XDS560v2, you see the EMU 0/1 pins in correct state as specified while with XDS200, it is not.

    Please note that you are using a very old and unsupported version of CCS. Could you try the latest CCS version to see if the same issue exists?

    Thanks

    ki