Content originally posted in LPCWare by Hobbiest on Fri Jul 06 02:45:41 MST 2012 Hi,
I just received my LPCXpresso (LPC11C24) and are struggling through the User Manual. Unfortunately there are a errors and missing informations which make it not easier for a beginner, e.g. jumping from page to page collecting informations and different register or bit names are used.
Of course errors are normal, but I didn't find a way to find a receiver for these informations. Microchip e.g. (at least has had) an emailaddress for such things where I received a (personal!) answer a few days later.
Although this forum doesn't seem to be the right place (official NXP member wrote in http://knowledgebase.nxp.com/showthread.php?t=1803 to fix this error at 04-19-2011, but this error still exists in actual Rev. 8 from 03-08-2012), hopefully someone will sometime bring these informations to the right place.
So my idea is to post all found errors and suggestions according to this manual in this thread. Do you think this could be usefull?
Content originally posted in LPCWare by Hobbiest on Fri Jul 06 06:28:46 MST 2012 Thanks for the link I didn't know. But obviously this page (I suggested http://www.lpcware.com/forums/microprocessors-forums/lpc11xx would be the best fitting place) seems to be visited rarely. Just 3 replies in the last 4 weeks. So I'll try it here.
All following (assumed) errors and suggestions are based on UM10398 Rev. 10 (which I only found on lpcware.com; the latest available on www.nxp.com/documents/[B]user[/B]_[B]manual[/B]/UM10398.pdf is Rev. 8 ...)
- 25.5.3, page 404, description symbol ADGINTEN: Typo ADGDR or AD0GDR instead of ADDR.
- 24.2, page 396, 2.: "The system tick timer clock is fixed to half the frequency of the system clock." That is the reset value but this sentence with the word "is fixed" implies to me, that it is the only option. But 24.3 shows that system clock is avaiable as well.
- Table 103, page 103: IOCON_PIO0_1 should be referenced by Table 108 instead of 105.
- 26.7, page 429: "The maximum number of parameters is 5, passed to the "Copy RAM to FLASH" command." I think more correct should be "command and 4 parameters" which results in 5 mandatory array elements.
- Table 245, page 279: Headline must be CANCTRL instead of CANCNTL.
- 16.6.1.2, page 280, last block: "in the CANINT" instead of "CANIR".
- Table 255, page 288: Description symbol TXRQST: TXRQST instead of TXRQSRT. Description symbol MASK: "Identifier MSK + MDIR..." instead of "Identifier MASK + ...". Same in table 256.
- Table 259+260, page 290-291: I'm totally confused about the description of ID[15:0] and ID[28:16]. Both say 11 and 29 bit identifier? Should be only 29-bit-identifier at ID[15:0]. Additionally should be the info that 11 bit identifiers have to be written to ID[28:18].
- Table 274: bit code for PLCK divided by 4 ist still wrong ...
- 16.7.2.2, page 298, block 4: TXRQST instead of TXRQUT.
- 16.7.2.4, page 299: (Probably) "the bits TX[1:0]" instead of "TX1, TX0". ".. the state of pin CAN_RXD ..." instead of "... pins RD0,1 ...".
- 16.7.3.6, page 305: "... it is programmed to ID[28:18]. In this case ID17 to ID0 can ..." instead of "... it is programmed to ID28. In this case ID18, ID17 to ID0 can ..."
- 17.4.2, page 314: CanApiClkInitTable differs to CanApiCanInitTable. Also the second parameter (interrupts) is missed in the example call. And "pCANAPI" must be "pCAND". btw.: The UM says ROM **rom = (ROM **)(0x1fff1ff8 + 2 * sizeof(ROM **)); but all examples in the zip say ROM **rom = (ROM **)0x1fff1ff8; Is it equal? Edit: Obviously not, because 0x1FFF1FF8 and 0x1FFF2000 contain different values. So probably an error as well.
- 17.4.4, page 315: There should be an example for 29-bit call added. Or msg_obj.mode_id = 0x000; should be extended like msg_obj.mode_id = 0x000 | CAN_MSGOBJ_STD; so usage should be clear as well with just one example
- 17.4.5, page 315: "can_receive" instead of "config_rxmsgobj"
- 17.4.6, page 315: "can_transmit" instead of "config_rxmsgobj"
- 17.4.7, page 316: In struct CAN_CANOPENCFG member "isr_handled"-flag is missed. Instead it is in struct CAN_ODENTRY (wrong; has moved to incorrect position).
- 17.4.9, page 318: Prototype above "Example call" is missed. And in the example call only "&callbacks" should be the parameter.
- 17.4.10, page 318: Why does a void function have a return statement (at the end of the function)?
- 17.4.11, page 319: Why does a void function have a return statement (at the end of the function) ?
- 17.4.12, page 319: Why does a void function have a return statement (at the end of the function)?
- 3.5.10, first Block: SYSPLLCLKUEN instead of SYSPLLUEN
- 3.5.22, first block: CLKOUTUEN instead of CLKCLKUEN
- Chapter 22, headline: Not for LPC11Cxx (has no WINDOWED watchdog timer)
Content originally posted in LPCWare by Ex-Zero on Fri Jul 06 03:04:56 MST 2012 Quote: Hobbiest Although this forum doesn't seem to be the right place (official NXP member wrote in http://knowledgebase.nxp.com/showthread.php?t=1803 to fix this error at 04-19-2011, but this error still exists in actual Rev. 8 from 03-08-2012), hopefully someone will sometime bring these informations to the right place.
