TMS320F28033: TMS320F28033

Hi Rani,

These errors sometime tend to disappear by restarting CCS. If still you get the error, do a Test Connection under Target Configuration window and share the result window with us.

Regards,
Gautam

Please check the attached Image.

Regards,

Rani.

Dear Sir, We tried this connection many times by restarting CCS, Target board etc. Please check the attached image of error.

Regards,

Rani.

Hi Rani,

Did you try importing a sample project from controlSuite?

Regards,
Gautam

Yes , Importing controlSuite project I tried this, but still same error occured, image attached.

Regards,

Rani

So now its very clear that the fault is either at the debugger or mcu end. Can you try replacing the mcu?

We placed order for TMS320F28033,  it may recieve in next week, after replace I will inform the result.

Regards,

Rani

Great Rani! Keep us updated.

Goodluck & Regards,
Gautam

After replaced DSP TMS320F28033, it get connected .

But replacing DSP on every such cards is not feasible, need to know about the root cause.

Thanks & Regards,

Rani.

Rani Sonawane said:

After replaced DSP TMS320F28033, it get connected .

Great!

Rani Sonawane said:

But replacing DSP on every such cards is not feasible, need to know about the root cause.

The controller can get permanently locked if the erasing procedure gets disrupted (power failure or disconnection of debugger) while programming.

Also, by mistake if you program a CSM password then you need to unlock the controller with the same password else you'll keep getting these error messages.

Regards,

Gautam

Rani,

I would recommend you to try "Wait" boot mode. By using this mode, you should be able to connect to the device before ECSL logic breaks JTAG connection. Once you establish JTAG connection, you can try unlocking the device. Have you already tried this option?

Regards,

Manoj

Please give procedure for the "wait" boot Mode steps.

Thank you.

Rani,

This information is already available in TMS320x2803x Piccolo Boot ROM Reference Guide (Rev. B) (Pg : 16) 

Rani,


Here the procedure to enter wait bootmode depending upon whether the emulator is connected. For more details refer www.ti.com/.../sprugo0b.pdf

when in standalone boot (when emulator is not connected), GPIO37 should be pulled high and GPIO34 should be pulled low

When emulator is connected, set 0xD00 = 0x55AA and set 0xD01 = 0x2 to enter wait bootmode.


Regards,
Manoj

Hi,

After configuration of "WAIT" boot mode, Device get unlock and firmware downloaded successfully.

Thank so much for support.

Regards,

Rani

 

Rani,

Good to know. Could you please close this post?