Err led on TMS570 USB kit always turn on at start. What does that means?

Hello Mr. Rossi,

This is a known errata in the Rev A silicon of the '3137.  You can find more information about it in the errata document online at: www.ti.com/lit/spnz181  Issue no.: DEVICE#140.  Rev B silicon fixes this issue.  Sorry for the inconvenience.

Hi, that solves my doubt, but still i am looking at the whole errata for A and B devices and it seems to be unusable for the current release right?  The errata list is huge and some of them are really an issue if the device is used for safety critical operations right? Or i am wrong. One question about the DEVICE#145 errata. What is a cold temperature? Below 0 Celcius? And the errata just says that error "usually occurs". So even following all the workaround the error stil might happen? When it is expected to have a TMS device?

Thank you!

Hi, i tryed to follow the ERRATA workaround but still got a problem at the coldstart. 

I added the following code to turn the err led off:

	esmREG->ESMSR2 = 0;
	CCMR4Reg->CCCMSR &= ~0x10000;
	if(!esmREG->ESMEPSR)
		esmREG->ESMEKR  	= 0x5;
 	while(!esmREG->ESMEPSR);

However the code is stoping at the swi_enable_fiq_irq(); line.

Any comment related to that problem? If i reset the board it runs ok, so i belive the problem is related to the coldstart.

PS: is the TMDX570LS20 a more stable silican than the TMDX570LS31?

Thank you!

Hello,

The TMS570LS devices are highly complex semiconductors.  It is quite rare for a device of such complexity to be developed without the presence of some design issues.  As this product is intended for safety applications TI has taken a policy of being extremely open in sharing known issues in the design as well as providing work-around suggestions when possible.  As a result it may appear that we have more issues noted than some other products you have used.  

Regarding impact on safety critical operation, this is something which our customers must evaluate for each system.  Every end product development will have different safety functions implemented and different safety goals.  The intent of the errata document is to provide enough information that you, the customer, can determine which issues are safety critical to your specific application and may require the addition of external measures to ensure that you achieve your system safety goals.

Best Regards,

Karl

Hi Karl, thank you for your explanation. I think i got overimpressed with the errata size. But you are right, and actually i see a lot of errata on the pre-release silicon version all the time. I am really liking TMS570 for now, do you have any idea when a TMS version will be released? For the kits, are all of them (USB Stick and HDK) mounted with an A version, or i can find a B version already?

About the errata i was trying to fix, it was my mistake, i did it all wrong. For others that might need it, a working solution is the following:

	esmREG->ESMSR2 = 0x04;
	CCMR4Reg->CCCMSR = 0x10000;
	if(!esmREG->ESMEPSR)
		esmREG->ESMEKR  = 0x5;
 	while(!esmREG->ESMEPSR);

Finally, i could find a problem at the USB Stick demo software. When you launch the CAN demo it will call the loopback demo and not the standard CAN receiver demo. It wont change the Baudrate either and it will be set to 1Mbps. As i have no access to the PC software code i had to change the TMS570 code. 

Just one last question. I have a few doubts regarding some erratas. Should i ask here in this topic, on a new topic or directrly for the TI tech support?

Thank you for all the help. 

Hello,

I'm afraid I personally do not have a date I can share for TMS silicon or information on availability of Rev B material.  However, if you do have a question on any errata please feel free to start a new discussion topic with your questions.

Regards,

Karl