Thanks, but just to be clear, let me restate my question.
Is there protection in hardware that prevents the counter register from
changing while the firmware reads its value?
Since my external counter clock is varying and not related to any clock on
chip I worry about occasionally getting bad readings.
I currently ensure that this can't happen by using a capture register. I
trigger the capture by changing the state of a port pin when my firmware
needs the counter value. That port pin is externally wired to the capture
input in order to force the capture, then my firmware reads the capture
register, not the counter register. This should be safe, and it works, but
it ties up two port pins and adds some extra code. If it's not necessary
I'd rather not do it, but I do need to be sure that the counter reading is
never garbled, and it would take some time to prove...
*Klaus Renner | Cooper Perkins, Inc. | **10 Maguire Road, Bldg. 4 |
Lexington, MA 02421*
desk: 781-761-4807 | http://www.cooperperkins.com
This email message contains confidential information.
On Wed, Jul 11, 2018 at 3:17 PM, victorjimenez <admin@community.nxp.com>