• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 876 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.

Unprogrammed TMS320F28335ZJZQ is CSM password locked and cannot be programmed.

Kjell-Kristian Grane Torgersen
Prodigy 140 points

Other Parts Discussed in Thread: SM320F28335-HT

Hi,


We've tried to program program a TMS320F28335ZJZQ microcontroller but we always get an error message about that it isn't able to unlock the F2833x CSM. At this point of time we weren't sure if the processor was being ruined by some earlier errorous programming, so we got another one which was unprogrammed (and not touched by anyone else) and tried to connect the C2000 debugger and clicking Verify in Blackhack Flashburn. This should obviously fail since it is unprogrammed, however it should not report that it fails to unlock the F28xx CSM. The reason we clicked Verify and not program, was to clarify if it was the programming of the first device that had ruined it or if a blank device also was locked initially.

C:\Program Files (x86)\Blackhawk\BHFlashburn_v4.0\bin\BhFlashBurn.exe  -p 0 -n 0 -d "bhemu28x.dvr" -f "LF28XX_USB2000.dat" -q- -r -c 20x10/2   -u FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF   -vo  "C:\Program Files (x86)\Blackhawk\BHFlashburn_v4.0\bin\Flash28xx\Algorithms\28335\FlashAPIInterface28335V2_10.out" "C:\Users\kjto\Documents\HVBLDC_Sensorless_2014-07-01-1201.out"
 Opening driver 'bhemu28x.dvr', dat-file 'LF28XX_USB2000.dat', port 0, target 0
 Connecting to DSP
Target 'tms320c2800_0', type B, word/char/int 16/16/16 bits, big-endian 0
 Resetting DSP
 Unlocking F2833x CSM (PWL at 0x33FFF8)
  Password FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF
Error: Failed to unlock F28xx CSM
 Running DSP

Process exited with code: 3

So here it seems that this device also is locked and behaves the exact same way as the first one we tried to program. We do have another variant of this microcontroller, the SM320F28335-HT with another casing that we are able to program successfully. It seems that the communication between the microcontroller and programmer works.

Basically the same error message pops up whatever we do either in Code Composer Studio and Blackhawk Flashburn. We are two engineers that have set up the development tools independently on our PCs trying on different microcontrollers but getting the same error messages.

Anyone having any ideas about how this can be unlocked/how we can program these devices? Other things to check and so on?

Regards

Kjell Kristian Torgersen

  • 0
    TI__Guru 61235 points

    Kjell,

    This is most likely a board issue.  The devices come from TI with the flash all 0xFFFF.  I seriously doubt this is a chip issue.

    Is this your own board design (vs. a EVM board)?  If your own, do any of these boards work, or do they all show the same issue?

    Check the power supplies on the board.  Are the 1.9V and 3.3V supplies valid?

    Check the PD pin on the JTAG header.  Is it 3.3V?

    Can you access XCLKOUT pin on the device?  If so, scope it.  What does it show?

    - David

  • 0 in reply to David M. Alter
    Prodigy 140 points

    No, I agree that it probably not is a chip issue. However, just wanted to check if there could be some minor difference between the chips that we haven't taken into account.

    We have our own board design, and it works with the SM320F28335-HT which had a ceramic pin grid array house. But when some of these MCUs got a physical shock, sometimes bonding wires inside shorted and it reset. We cannot avoid this shock for the moment, so we made a adapter board which are between the microcontroller mentioned in the previous post (that has a ball grid array) and our board. I don't think all of the lines on the adapter board have been physically verified to be correct yet, only schematically.

    I think that the 1.9 V and 3.3 V is OK. Also the JTAG data lines seems to be fine and the oscillator is oscillating at the correct frequency as far as I know.

    I will forward your tips to the "hardware guy" here that has done most of the troubleshooting and we will look into that.

    Thank you for the reply