• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 82 subscribers
  • Views 1680 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

F28027 XRS is allways toggling with variable frecuency

Matias F. VANNI
Prodigy 90 points

Other Parts Discussed in Thread: TMS320F28027

Hi, I have problems to program the F285027 with XDS100V2 in a OEM PCB. I made a lot of measurements and hardware revision. Apparently everything is well but I can't program any new MCU.

Something that struck me is that the reset pin XRSn, witch have a 2k2 pull-up resistor, is allways toggling. Why could this happen?

This is the result of my test connection:

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\Matias\AppData\Local\.TI\693494126\
0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jan 21 2014'.
The library build time was '12:29:33'.
The library package version is '5.1.402.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

Thanks and sorry for my english!

Matías V.

  • 0
    TI__Guru** 117001 points

    Hi Matias,

    Can you check what's the value on BOOTMODE pins (GPIO72 & GPIO84)? If it's 1/1 then please change it to a value other than 1/1 and try it again. Value 1/1 is "GET Mode" which default to "Flash Boot". Since Flash is not programmed on this part, CPU fetch a value 0xFFFF_FFFF from there which is ITRP and BOOTROM enables the WD to reset the device incase of ITRAP. WD reset pull the XRSn pin low.

    Let me know your observation.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 90 points

    Hi Vivek and thank you for your prompt reply!

    The first time I try to program I use "Get Mode" because I obseve on the datasheet that with the EMU connected no matter the values of GPIO-34/GPIO/37.

    Then I changed the BOOTMODE to "Wait", same as now.

    The values of voltages are GPIO-34:0.4V - GPIO-37:2.6V

    Can it be that in attempting to program the MCU in "Get mode" has been locked?

    Thanks.

    Matías V.

  • 0 in reply to Matias F. VANNI
    TI__Guru** 117001 points

    Hi Matias,

    I misunderstood the part number with another device hence provided different BOOTMODE pins.

    I'll have someone else (F28027 device expert) to look into this issue.

    Regards,

    Vivek Singh

     

  • 0 in reply to Vivek Singh
    Prodigy 90 points

    OK Vivek.I'm waiting.

    Thanks.

    Matías V.

  • 0 in reply to Matias F. VANNI
    TI__Mastermind 19810 points

    Matias,

    you mentioned you have a problem programming the f28027 device on your board. are you able to load anything to RAM or is it that neither RAM nor flash loads work.

    Can you try below sequence

    1.> power off the board; remove JTAG connections.

    2.> set the boot mode pins to WAIT BOOT

    3.> power on the board

    4.> connect JTAG 

    5.> open CCS and go to view menu and open target configurations and choose the proper one for your device. if there is none then create one with proper emulatior and device selections.

    6.> now right click on the target configuration and Launch. 

    7.> Now in the CCS debug perspective, select the CPU and click target connect

    are you able to connect to the device? if yes, do a debug reset and load program.

    Best Regards

    Santosh

  • 0 in reply to Santosh Athuru
    TI__Mastermind 19810 points

    also when the device is in wait boot mode, no emulator connected (after step 4, above), if you observe the XRSn pin on a scope you should see the device getting reset at a constant freq, it shouldn't be variable.

    Also try to check the same on at least another silicon.

    Best Regards

    Santosh

  • 0 in reply to Santosh Athuru
    Prodigy 90 points

    Hello Santosh,

    I performed the steps you asked and I have obtained the following message:

    C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
    C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.

    I never could program this device and never started the erasing. I do not understand why might be locked the device.

    I hope you can help me with this issue.

    Thank you!

     

    Matías V.

  • 0 in reply to Santosh Athuru
    Prodigy 90 points

    Hi Santosh,

    I build a new PCB with a new silicon and I obtained the same result:

    C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
    C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.

    I have checked the Reset and this has a constant frecuency now but I can't connect with the device.

    I have checked the signals of the emulator and this are very nice.

    I have checked VDD and this haven't noise.

    It is a new device and the only difference I noted is that maybe the target is connected becuase CCs gave me this message "No source available for "0x3ff7bf" ", but I'm not sure.

    What do you think is the next step?

    Thnks-

    Matías V.

  • 0 in reply to Matias F. VANNI
    TI__Mastermind 19810 points

    Matias,

    it could be possible that you have accidentally programmed passowrds. Inspect your linker command file and MAP file to see if anything is getting linked to the CSM passwords region in flash. And until we figure out don;t attempt programming the same flash image onto a new silicon, you might end up locking them as well.

    Did you try loading anything to RAM, like a blinky or GPIO Toggle RAM example? 

    Matias F. VANNI said:

    I performed the steps you asked and I have obtained the following message:

    C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
    C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.

    I never could program this device and never started the erasing. I do not understand why might be locked the device.

    also on this device, can you confirm the below for me?

    1.> after step 7 in my list of steps, if you do a debug reset and view dis-assmebly or memory window at 0x3D7C80 what do you see? or please check for the value at 0x3D7C80 in the expressions window (*(unsigned long *)0x3D7C80).

    Also, please send me your MAP file, linker command file and COFF file for inspection, if that is ok with you.

    Best Regards

    Santosh

  • 0 in reply to Santosh Athuru
    Prodigy 90 points

    Hi Santosh,

    The value of 0x3D7C80 is 4029568.

    The value of PartID (0x3D7FFF) is 4030463

    8512.C2kLaunchPadDemo.rar

    I'm using an example from LaunchPad LAUNCHXL-F28027, so the MAP file, the linker command file and COFF file are the same as I was using with LaunchPad. I changed only the Target configuration.

    I view the same output message with a new part that never has been erased/programed.

    If you need I send you the files. (I can't find the COFF file)

    Thank you!

    Matías

  • 0 in reply to Matias F. VANNI
    TI__Mastermind 19810 points

    Matias,

    Matias F. VANNI said:

    The value of 0x3D7C80 is 4029568.

    The value of PartID (0x3D7FFF) is 4030463

    the above doesn;t make sense, they are just decimal conversion of the hex addresses. are you sure you are seeing those values, would you be able to send the CCS memory window snapshot of these addresses?

    are you able to load any RAM based example?

    Best Regards

    Santosh Athuru

  • 0 in reply to Santosh Athuru
    Prodigy 90 points

    I can't load any RAM based example. I am using Example_F2802xGpioToggle.

    I can laod the same program with same configurations and files in LaunchPad.

    I don't understand what is wrong. 

    I have 2.2uF caps with a VDDIO 3.32 / 1.92 from internal regulator.

    3.3k pull.down resistors on TDO and GPIO-34, pull-up 0.82K on TDO, pull-down 2k2 on XRSTn, and pull-up of 4k7kon EMU0/1

    I hope you can find the problem.

    thanks.

  • 0 in reply to Matias F. VANNI
    Prodigy 90 points

    Sorry Santosh, here you are the correct values:

  • 0 in reply to Matias F. VANNI
    TI__Mastermind 19810 points

    Matias,

    I looked at your map file, looks like you have the below linked to CSM Locations and if you have left that source at the default then you might nit have programmed any passwords by mistake, else you might have.

    csm_rsvd 0 003f7f80 00000076
    003f7f80 00000076 driverlib.lib : F2802x_asmfuncs.obj (csm_rsvd)

    Now, assuming you left the F2802x_asmfuncs at its default, then the next suspect would be the tartget config you created and if you have any proper GEL files or not that run the CSM unlock on debug reset. Since your 0x3D7C80 location value comes back as zero I suspect you don;t have proper target config created with GEL files. 

    would you be able to inspect the target config that worked with the launch pad and compare it with the one you created, is there any reason you are not using the same target config that worked with launch pad with your board?

    by the way you can view the target configs from the CCS->VIEW->TargetConfigs menu and double click the file would open it up.

    Best Regards

    Santosh