Please confirm: Missing Modem interrupt enable in UxIER register on LPC11xx/LPC13xx

lpcware · ‎06-15-2016

Content originally posted in LPCWare by RA1981 on Wed Apr 06 12:50:41 MST 2011
Hi,

I'm working on a common code base for LPC11xx/13xx/17xx devices. Currently I'm examining the commons and differences of the device UARTs.

It looks like that the NxP datasheet guy has gone the copy&paste approach (which [B]always [/B]will produce faulty datasheets):
The UART chapters of LPC11xx/13xx datasheets mentions a modem line interrupt (see U0IIR UART interrupt identification register description). However, the UART interrupt enable register U0IER doesn't have a enable flag.
Now comparing this with the UART1 interrupt enable register U1IER description of LPC17xx datasheet gives the difference in bit 3: modem status interrupt enable flag.

Now, I wonder if it might be that the corresponding flag also exist on LPC11xx/13xx UART and the datasheet simply is the result of a copy-from-somewhere/paste/[B]forget-to-check[/B] action... Can anybody confirm this? Or am I missing something?

How can I check such things by myself (without writing a additional test application) ?
And how can I point NXP to this issue (if it's really a issue)?

Regards,

Ralf

lpcware · ‎06-15-2016

Content originally posted in LPCWare by RA1981 on Thu Apr 07 09:49:24 MST 2011

Quote: larryvc
I find that writing the additional test application, in these cases, affords me the luxury of wasting my time and in the process I might learn something new.

Yes, of course writing test applications is always part of a learning process. But in my opinion it should be a TA for a usefull purpose, not to clarify if a datasheet has errors :)

Quote: larryvc
NXP, the documentation could definitely be improved upon.:(

Indeed, and get rid of asking for project title and annual quantity etc. when a [B]developer[/B] wants to get support. A developer doesn't want to be called by [B]distributors[/B] etc.

Quote: larryvc
Ralf, I like the devkit idea.:)

:D

Regards,

Ralf

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Thu Apr 07 09:41:30 MST 2011

Quote: RA1981

How can I check such things by myself (without writing a additional test application) ?

I find that writing the additional test application, in these cases, affords me the luxury of wasting my time and in the process I might learn something new.:rolleyes::)

NXP, the documentation could definitely be improved upon.:(

Ralf, I like the devkit idea.:)

Larry

lpcware · ‎06-15-2016

Content originally posted in LPCWare by RA1981 on Thu Apr 07 09:24:58 MST 2011
Hi Larry,

yes, I'll forward it to NxP support.

Hmmm... maybe I should ask them if they will give a gift for finding errors which could be avoided. Something like a devkit :)
This maybe would increase the quality of their documentation when people would go hunting for datasheet errors :D

Regards,

Ralf

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Wed Apr 06 13:59:48 MST 2011

Quote: RA1981
And how can I point NXP to this issue (if it's really a issue)?

Hi Ralf,

You can ask about this at NXP tech support.

[COLOR=#5174a3]http://www.nxp.com/techsupport/index.php[/COLOR]

Larry