• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 287 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TL16C2552: Register difference compared with NS16C2552

Go
Genius 4220 points
Part Number: TL16C2552
Other Parts Discussed in Thread: NS16C2552

Hi,

My customer is evaluating TL16C2552 for replacing NS16C2552.

But customer found any INT wasn't asserted with TL16C2552.

(Regarding MCR bit3 of TL16C2552 and NS16C2552, it's assigned as INT enable for TL16C2552, but OUT2 for NS16C2552.)

Customer set MCR bit3 as 0 with their current S/W , and already checked INT was asserted when they set MCR bit3 as 1.

So, Do we have to set MCR bit3 as 1 for INT assertion?
or is there any other way to enable INT without any S/W change
(means, set MCR bit3 as 0 )

Actually, they don't want to change S/W...

Thanks,

Go

 

  • 0
    TI__Guru 73271 points

    Hi Go,

    Our device does require the MCR bit 3 to be set to '1' in order for the it to enable INTs functionality on the pin. There is no workaround for keeping the MCR bit3 '1' without modifying software. 

    -Bobby