(duplicate)
Section <em>21.6.1 Memory map after any reset</em> says '...The RAM usage is described later in this chapter...' but as far as I can see it is not.
Peter
Ok, my bad.
The struct itself is according to the document.
<code>typedef struct
{
__IO uint32_t CFG; /* 0x00 */
__IO uint32_t CTRL;
__IO uint32_t STAT;
__IO uint32_t INTENSET;
__O uint32_t INTENCLR; /* 0x10 */
.....
</code>
Hi Kimmo,
Looks like you are mistaking alphabetical ordering for register ordering. The tool you are using is listing the registers alphabetically and the order in the document is address order.
Noah
Following things also are strangely in UM10601 rev 1.2
ADDRDET description in table 161. I would keep descriptions, just swap "Enabled" and "Disabled".
<span class="inline inline-left"><img class="image image-preview " src="http://www.lpcware.com/system/files/images/addrdet.preview.png" border="0" alt="" title="" width="640" height="216" /></span>
Second is register address offsets for INTENSET and INTENCLR -registers in table 159
<span class="inline inline-left"><img class="image image-preview " src="http://www.lpcware.com/system/files/images/INTENSET1.png" border="0" alt="" title="" width="281" height="379" /></span>
The registers INTENSET and INTENCLR are defined in struct in different order, and they work as expected. How ever in manual seems that they are in wrong place.
<span class="inline inline-left"><img class="image image-preview " src="http://www.lpcware.com/system/files/images/INTENSET2.png" border="0" alt="" title="" width="378" height="241" /></span>
Maybe this will be useful for someone
-kimmo
Mike
Thanks again for bringing this to our attention. I have made a note of the problem, and it should hopefully be fixed in the next revision of the user's manual.
Paul