Forgotten packages

[lpcware]

Content originally posted in LPCWare by R2D2 on Thu Jun 27 09:51:56 MST 2013
Where are LQFP48, LQFP64 and HVQFN33 package Figures of Chapter 8 in UM10524 Rev. 4 — 12 March 2013?

Do I need User Manual and Data sheet to check a pin position :confused:

[lpcware]

Content originally posted in LPCWare by ktownsend on Sun Jul 07 15:23:49 MST 2013

---

Quote: Rob65
One thing I like on the LPC800 series is the I/O configuration tool.
It would be nice to have something like this for the other devices as well. I have a few projects with an lpc175x where it took me a few days to find a configuration where I could export all I/O functions I needed to pins.

---

Hi Rob:

There is a similar tool for the LPC18xx/LPC43xx chips, and I don't know how I would have survived without it finding a good pinout for everything I needed on the LPC4357 BGA256 package with no conflicts (LCD, SDRAM, Ethernet, and dual USB). It still took me 2 days to make the footprint, but it would have been far more error prone a process without this tool:

http://www.lpcware.com/content/nxpfile/lpc43xx-pin-mux-tool

[lpcware]

Content originally posted in LPCWare by Rob65 on Fri Jun 28 03:25:13 MST 2013
That is indeed confusing.
Before posting I of course have checked other UMs as well - I have the other manuals that do not contain footprints.

IMHO, placing the footprints in the user manual is the confusing part.
I like the split between the hardware model and the programmers model. The only reason I could think of for having the foorprint of the chip is because I have to measure signals for debugging purposes but then I prefer the schematics/board layout pointing me to places where I can put my probes. For the HVQFN packages putting a probe on a pin is difficult and for BGAs it's even impossible.

I have been working a lot with high integrated devices (multi core ARM devices for smart phones and tablets) and these devices are BGA devices with 200-400 'pins' as well as the smaller LPC1xxx/2xxx chips. These large devices have large datasheets with lots of (hardware) design constraints and the user manual mostly spans a complete 3-ring binder.
So it might just be that I am 'broken' and learned to accept this split in information :D

But I completely agree that it should be the same across all chips.
Even more confusing is the fact that in some user manuals the Cortex specific registers are mentioned whereas other manuals refer to the original ARM manuals.
Yes - when you need to go "all the way" and need the details about interrupt handing or ARM Cortex specific registers you need to consult the ARM Cortex manuals and if you want to know exactly how the assembly instructions behave you need the ARM Cortex programmers model also.

One thing I like on the LPC800 series is the I/O configuration tool.
It would be nice to have something like this for the other devices as well. I have a few projects with an lpc175x where it took me a few days to find a configuration where I could export all I/O functions I needed to pins.

Rob

[lpcware]

Content originally posted in LPCWare by R2D2 on Fri Jun 28 00:54:45 MST 2013

---

Quote: Rob65
that is the whole idea of splitting the documentation in a datasheet and a user manual.

---

:confused:

And what do think is the rule for this idea?

Old LPC1343 UM is including package figures, new LPC1347 is not. LPC11 UM is including it, LPC17 UM is including simple symbols.

That no idea, that's confusion.

[lpcware]

Content originally posted in LPCWare by Rob65 on Fri Jun 28 00:34:33 MST 2013
Yes,

that is the whole idea of splitting the documentation in a datasheet and a user manual.

The datasheet contains all hardware related stuff (package descriptions, dimensions, electrical ratings) and includes a short list with of the chip.
This is for hardware engineers to be able to design the board, calculate power needs and check for I/O constraints.

The user manual contains the programmers model. There you will find detailed information on each block needed to create the program.
You will not find any package information in the user manual (except maybe for some footnotes that certain pins are not available on certain packages).

Rob