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.
Tool/software: Code Composer Studio
I upgrade CCS from version 9.2 to version 9.3.
I'm not able to connect to the TARGET utilizing XDS110 probe.
I receive the following error message.
C28xx_CPU1: Flash Programmer: Error erasing Sector A. FMSTAT value = 1040. Operation Cancelled (0).
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\MyFile.out: Load failed.
With version 9.2 everything is working fine.
Hello,
It looks like the issue is not a target connection issue, but a flashing issue.
Massimo Tomazzolli said:C28xx_CPU1: Flash Programmer: Error erasing Sector A. FMSTAT value = 1040. Operation Cancelled (0).
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\MyFile.out: Load failed.
Are those all the messages? Did you see anything about an unlocking issue? Something like:
C28xx_CPU1: Warning: Failed unlocking device (zone 1) after reset.
Massimo Tomazzolli said:but the same confoguration works well with CCS 9.2
You still have 9.2 and it still works fine?
Did you get any error regarding unlocking the device (as mentioned in my last post)?
ki
No,
this was the only error I had with version 9.3
C28xx_CPU1: Flash Programmer: Error erasing Sector A. FMSTAT value = 1040. Operation Cancelled (0).
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\MyFile.out: Load failed
Since 9.2 works fine, it is likely an issue with the emu pack version or flash dll.
In 9.3, can you enable debug server logging and reproduce the issue? Then zip up the generated log and attach it to this thread:
https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html
Thanks
ki
Hi Massimo,
I am able to successfully erase, program and verify a F28075 device on CCSv9.3 using XDS100V2 emulator.
Can you provide a sample project that we can use to reproduce this behavior on our side? Please make sure to remove any proprietary info from your project/code.
Thanks and regards,
Vamsi
Also, please check for updates in CCS and install them to make sure that you are using the latest drivers.
Thanks and regards,
Vamsi
Yes,
I verified. I'm working with the last upgrade.
Did you verified the log file I sent you?
Massimo,
Yes, our team reviewed the log file.
As I mentioned, we are not able to reproduce the failure.
Could you send us a sample project to reproduce the failure?
Thanks and regards,
Vamsi
I'll try to do it next week.
I need some time to remove part of the code before to send it
Hi,
Enclosed you'll find a simple project that works with CCS 9.2 but doens't work with CCS 9.3
I confirm you that the problem is caused from the password unlocking because:
1. I modified it in the enclosed project and I received the same error message if inside the FLASH settings I write the simple password.
2. If I write the right password it works with CCS 9.2 but not with CCS 9.3
Waiting for your reamrks I remain.Test_CCS_93.zip
Massimo,
Thank you for the sample project.
Since you said it is related to password unlock, I will ask our security expert to help you further.
Thanks and regards,
Vamsi
Hi,
Did you verified if with the sample project I sent you are able to see the issue ?
Massimo,
I assigned this post to our security expert. He will respond in a day or two.
Thanks and regards,
Vamsi
I am looking into your project and will try to get back to you before end of this week.
Regards,
Vivek Singh
Hi,
We have found an issue with CCS9.3 which is causing this problem. Can you use CCS9.2 till we fix this issue in next release ?
Regard,
Vivek Singh
Massimo,
The bug fix is currently targeted to be included in the next CCS release (v10.0), which is scheduled for a mid-March release.
We are also working on releasing an update patch for CCS9.3; we are still working out the details on this, and once we have more information on when the patch will be available, I will share it with you.
Sorry for the inconvenience this bug is causing you.
Thank you,
Ricky