topic Re: Bug when reading UART0 peripheral memory? in LPCXpresso IDE

Bug when reading UART0 peripheral memory?

lpcware — Thu, 16 Jun 2016 01:11:04 GMT

Content originally posted in LPCWare by luoldeng on Sun Feb 09 00:58:05 MST 2014
There seems to be a bug with the peripheral memory viewer:
(Version 6.1.2, Build 177 on OS X)

[img]http://imgur.com/opm255i.jpg[/img]

I set an interrupt to fire on receive data.
IIR correctly reads 0xC4 when mousing over the expression, but is shown as 0xC1 in the Peripheral memory map.

Re: Bug when reading UART0 peripheral memory?

lpcware — Thu, 16 Jun 2016 01:11:05 GMT

Content originally posted in LPCWare by lpcxpresso-support on Mon Feb 10 01:35:09 MST 2014
Can you tell us which part you are using?

Regards
LPCXpresso Support

Re: Bug when reading UART0 peripheral memory?

lpcware — Thu, 16 Jun 2016 01:11:05 GMT

Content originally posted in LPCWare by luoldeng on Mon Feb 10 09:36:50 MST 2014
Whoops, should have included that, sorry.

I am using LPC17xx family: LPC1751 and LPC1769.

Re: Bug when reading UART0 peripheral memory?

lpcware — Thu, 16 Jun 2016 01:11:06 GMT

Content originally posted in LPCWare by lpcxpresso-support on Tue Feb 11 01:41:01 MST 2014
I think this is consistent - the interrupt is triggering after the memory has been read. I think this is the scenario:
- hit your breakpoint
- peripheral memory is read and displayed
- interrupt fires
- you now hover over the register - the value is read directly from the hover

The values you are seeing are consistent with this explanation.