TMS320F280049: How to pop up the password input interface window with CCS8

Hi Rayna,

We do not have pop-up window for this instead user need to enter the password in Flash plug-in GUI. You can bring-up the Flash plug-in GUI by clicking on "Tools -> On-Chip Flash" in CCS.

Regards,

Vivek Singh

Hi Vivek,

Does that mean customer should clicking "Tools -> On-Chip Flash" to input the password before clicking the "debug" to download the code?

Thanks!

Rayna

In that case you should be able to open the project property (right click on project in CCS and select "Properties") and select Flash setting under Debug. In this GUI you can provide the password and click on Apply -> Apply and Close.

Now when you launch the debug session it should be able to unlock the zone using password provided before flashing new program. Please try this and let me know if you still face some issue.

Regards,

Vivek Singh

Hi Vivek,

After try the above method, there's still a issue as below. However, there's no such issue when customer uses CCS3.

Is there any other precaution to unlock the chip? Thanks!

Best Regards

Rayna

Rayna,

F280049 device is not supported by CCS3 so not sure what do you mean by "there's no such issue when customer uses CCS3" ? Are you using same device or some other device with CCS3 ? 

Regards,

Vivek Singh

Also we have CCS10 now. I would recommend to user latest CCS and try this.

Regards,

Vivek Singh

Hi Vivek,

Yes, customer use CCS3 with XDS510 emulator could unlock the same device. When use CCS8 with XDS200 emulator, the device could not be unlocked.

Now, the .ccxml file could be connected, but after put the passwords to click "unlock" button, it shows "Target is not connected or does not support current Flash operation.". And I could also repeat this error, by click the "unlock" button in CCS8/CCS10.

Could you repeat the error or tell us how to solve the error to unlock and program the device? Thanks!

Best Regards

Rayna

I have never used CCS3 with this device (CCS3 does not support F280049 device debug). After launching the ccxml you need to connect to target and then only perform lock/unlock operation. Can you send me the snapshot of how are you unlocking in CCS8/CCS10 ? 

Regards,

Vivek Singh

Hi Vivek,

It seems that after changing the boot mode to wait mode, the issue is solved. I'll double check it with customer tomorrow.

In F28035 TRM, the content in page 50 seems to explain it, however, I'm still confused with the description.

Could you please help to explain what the problem need to use the “Branch to check boot mode” boot option, 128bit password? Thanks!

Best Regards

Rayna

Hi Vivek,

From the above content, I have some sample questions would like to ask. Thanks!

1. Does that mean that the device should set in Wait Boot Mode, if connect emulation to unlock the device?
2. Should the Wait Boot Mode be selected only by changing hardware GPIO voltage?
3. If the user's application bootloader mode is SPI mode, after changing the hardware to unlock the device, does customer need change the software bootloader mode configuration? If yes, how to solve it if customer could not change the bootloader mode?
4. If customer also need to unlock F28035, is the method same with F280049?

Thanks!

Best Regards

Rayna

Hi Rayna,

Does that mean that the device should set in Wait Boot Mode, if connect emulation to unlock the device?

That is correct.

Should the Wait Boot Mode be selected only by changing hardware GPIO voltage?

Yes, that is correct.

If the user's application bootloader mode is SPI mode, after changing the hardware to unlock the device, does customer need change the software bootloader mode configuration? If yes, how to solve it if customer could not change the bootloader mode?

There is no alternative to this. What is connected to SPI on board for SPI BOOT ? Is it possible to not send any data to SPI during boot process ? In that case BOOTROM may keep waiting for SPI data and that may allow user to connect to CCS. 

If customer also need to unlock F28035, is the method same with F280049?

No, it is different. On older device we had Wait-In-Reset" mode based on EMU0/EMU1 pin which has been removed to get more functional pin. 

Regards,

Vivek Singh

Hi Vivek,

Because customer need to debug the production boards, the voltage of GPIO34& TDO pins of F28035 are high. And the hardware could not be changed to fix this issue.

I find a thread about the same requirement/issue. However, CCS8/10 still can't connect with C2000 device, with checking the box "Halt the target on a connect", as suggested.

Could you please help to debug it or find method to fix the issue from software  configuration?

Thanks!

Best Regards

Rayna

Hi Vivek,

The below figure is from F28035 TRM.

I'm quite confused now. I try to analyze the about the figure content as below, and could you please correct me, if there's any mistake? Thanks!

1. For the first point, " use the Wait-In-Reset emulation mode", it seems to require a emulator which support "Wait-In-Reset" mode, not changing the hardware boot pin state to "Wait mode", right? If so, maybe XDS510 could support this mode, but XDS100/200 could not, I guess it from the test result.
2. For the second point, " use the “Branch to check boot mode” boot option", there's two ways, one is "You can select this boot mode and then exit this mode once the emulator is connected by re-mapping the PC to another address"(the software way?), the other is "by changing the boot mode selection pin to the desired boot mode."(the hardware way?). If the first way uses software method, could you provide some code snippet/configuration figure? Thanks!

Best Regards

Rayna

Hi Rayna,

This is for older device. I'll have to refer to other expert for this. 

Regards,

Vivek Singh

Rayna,

For the first point, " use the Wait-In-Reset emulation mode", it seems to require a emulator which support "Wait-In-Reset" mode, not changing the hardware boot pin state to "Wait mode", right? If so, maybe XDS510 could support this mode, but XDS100/200 could not, I guess it from the test result.

"Wait in Reset" is not working on CCS and we suspecting a CCS software bug which needs to be fixed. This bug fix will rolled-out in subsequent CCS release. I unfortunately don't have a timeline when this will be fixed.

For the second point, " use the “Branch to check boot mode” boot option", there's two ways, one is "You can select this boot mode and then exit this mode once the emulator is connected by re-mapping the PC to another address"(the software way?), the other is "by changing the boot mode selection pin to the desired boot mode."(the hardware way?). If the first way uses software method, could you provide some code snippet/configuration figure? Thanks!

I don't see how you can connect to the device using software method. Your realistic option is using hardware method:-

1) Hold the device in reset (pull XRSn low) and try connecting the device. CCS will report device is held in reset. Press retry and release device from reset. This will connect you to the device after which you can unlock using password

2) Change the boot mode pins settings to either parallel boot / SCI boot. This will prevent the ECSL from tripping the JTAG connection. Once connected you can unlock the device using password.

Regards,

Manoj

Hi Manoj,

Thanks for your reply.

As your reply, that it seems there's no method to connect the device by changing software, right?

And from your answer, I guess that ""Wait in Reset" is not working on CCS " may be ""Wait in Reset" is not working on emulator", right?

for "2) Change the boot mode pins settings to either parallel boot / SCI boot. This will prevent the ECSL from tripping the JTAG connection. Once connected you can unlock the device using password."

--> Just confused that according F2803x/F280049 TRM, it seems the boot mode pin should set to "wait mode". Just want to double check with you. Thanks!

Best Regards

Rayna