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.
Hello
I get the following error while trying to load the Concerto F28M35H52C1 C28x Core for the first time after a flash erase.
SEVERE: C28xx_0: Error occurred during flash operation: Timed out waiting for target to halt while executing pwrite_en.alg SEVERE: C28xx_0: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
My device is an experimental F28M35x, does this play a role in such a behavior?
Regards
Sandeep
Hello Vamsi
Yes the M3 is connected to the debugger and halted. I used the DSS Script to do this.
However when i use CCS to halt the M3 and program the C28x, i do not get the error.
Is there something wrong in the DSS Script then.
Can i share the same with you to have a look?
Regards
Sandeep
Hi Vamsi
It is an experimental board.
Boot mode pins are set to all 0's.
Regards
Sandeep
Sandeep,
Try these.
Open the M3 debug session first and then for C28x.
Connect to M3 first and reset M3. Then Connect to C28x and reset C28x.
Also, try removing the resets.
If above does not help, try loading some code to M3 first and then to C28x.
Let me know how it goes.
Make sure to check for CCS updates and install all of them.
Thanks and regards,
Vamsi
Sandeep,
Can you try inserting the unlock sequence before loading the code?
Thanks and regards,
Vamsi
Hi Sandeep,
Please refer "1.10.3.2 CSM Password Match Flow" in device TRM to know how to unlock the device. This is only needed if you have security enabled by programming the password values in flash at password locations. If not then this step should not be needed.
Regards,
Vivek Singh
Hello Vamsi
Yeah we are still facing this issue.
The device is an experimental board. Can you let me know how to check the PLL Configuration.
I am unsure about this.
Regards
Sandeep
Sandeep,
Looks like you are not configuring the PLL in your script. That should cause the Plugin to use the default settings, which is fine.
1) Can you send a snapshot of your device?
2) When you try the CCS, did you change any GUI settings? If yes, you have to set them in DSS script as well.
3) Based on the error that you got, I feel that the device is either secured or is not initialized properly. If we execute BootROM (issue a reset -> then resume -> then halt after a minor delay like 500us) after the reset and before loading the code, the device should get initialized properly and this might get solved.
You can accomplish this in your script.
(a) After the reset in script, run the bootROM by calling session.target.runAysch();
This is same as hitting the resume button in CCS.
(b) You can put a delay using Java Thread like below
Thread.sleep(1000);
(c) And then you can issue a halt as below:
session.target.halt();
Then load the code.
4) Also, can you generate logs for us (since we are not able to make your script fail in our setup) when using both CCS and script?
(a) In CCS, you can enable logging via "CCS Help menu -> CCS Support -> Select Debug Server Log -> Click on Properties -> Select Enable Debug Server Logging + Choose a log file location -> Click Ok".
(b) When using DSS, you can enable log generation by setting the following environment variables in your command prompt before running the script.
set TI_DS_ENABLE_LOGGING=1
set TI_DS_LOGGING_OUTPUT=c:/path/file.log
Thanks and regards,
Vamsi
Hello Vamsi
thanks for your detailed reply. I will look into the steps you proposed later today. I am sorry i was debugging some other issues with the latest version of TI Compiler so i got stuck with this.
Will check and revert back before EOD today along with the snapshots.
Thanks and Regards
Sandeep