questions about HALCOGEN

Hi,

Our Halcogen experts will get back to you on this.

Hi Jiaming,

HALCoGen does not do intialization table copy by default, it relies on the KEIL library function __main().
calling "_main()" will help you gothrough all intiailization and branch to main.

The problem is if I don't change "__main" to "main" , I can't go to main , the program can't start. 

But by default choosing the right Device while creating the project should be sufficient. Could you zip and send the uVision project folder with HALCoGen generated files.

7485.ls.zip

I choose the safety function ,then errors occur

sorry ,I reply the other questions ,the question is if I enable the safety function .The errors occur .

Now  I post my problems file  about "__main"7558.ls.zip

Jiaming,

Sorry my uVision does not open up, have to check.

Meanwhile couple of things I would like you to know
1) startup_TMS570LS.s is not needed since sys_startup.c is equivalent of it. So remove startup_TMS570LS.s from your project and bring back __main() in sys_startup.c
2) If you have Enabled CCM Self Test you cannot have the Debug tool connected. It is already mentioned in the tool tip, just reminding you. Just Flash the code, disconnect the tool and power cycle / reset to run the code. OTherwise this test would get stuck / or cause other failures.
3) I think you are aware the CPU Selftest will cause a reset - twice ( 1 for STC self Check , 2 actual CPU selftest ).

Though startup_TMS570LS.s is in soure folder ,I don't add it to project

I tried running the code without JTAG, the error pin of TMS570 is low too

I don't understand the 3) you suggested , what is the affection of this twice reset?

Hi Jiaming,

Still I waiting to get a working KEIL licensing setup working at my desk. 

I am not sure if Flash ECC location has been programmed in your micro. I would recommend you to install nowecc tool from below link. Give your executable as input to the tool and get the ECC appended to the executable, then download it to the micro. If there is a postbuild option in KEIL you can configure them too. 

Please refer the user guide for more details how to use it. 

http://www.ti.com/tool/nowecc

Something similar to this 

For TMSxxx Devices
------------------
“<nowECC path>\nowecc.exe” -F021 16M_ADD -R4 -a YOUR Executable
For RMxxx Devices
-----------------
“<nowECC path>\nowecc.exe” -F021 16M_ADD -le -R4 -a YOUR Executable

Regards
Prathap 

I change the IDE from KEIL to CCS,and choose the Auto ECC Gereration option ,then the error disappear

By the way ,I tried the nowecc software,it only support 32bit operation system ,my win7 is 64bit ,so I can't use the nowecc software

Hi Jiaming,

Even I do have Win7 64-Bit, I run nowECC with no problem. Did you notice any error while invoking nowECC?