The specific UART names mapped to pins are found in the device specific peripheral apis: http://mbed.org/users/mbed_official/code/mbed-src/file/5fa2273de5db/vendor/NXP/LPC1768/hal/serial_api.c

Also in that neighbourhood, in the CMSIS directory, the complete list of definitions is (not mapped to pins, but by combinging that with earlier links you can figure most out): http://mbed.org/users/mbed_official/code/mbed-src/file/5fa2273de5db/vendor/NXP/LPC1768/cmsis/LPC17xx.h

Hello. Thank you for the efforts so far. So I am finally looking for the file that has the real items for "UARTName" in it. What is this files name and where is it located?

I do embedded engineering (hardware/software C, C++/firmware) and I am determining wether or not the NXP mBed LPC1768 40 pin module can be used in a commercial demonstration and a small prototype run. The pure hardware side is trivial but on the mBed development environment side I still have an unanswered question on the UART or other device(s) software names. Where is that documented? If this documentation does not exist and I have to Sherlock Holmes for hours for each nut of normally available information it will be a total commercial disaster. Where is the substantial documentation to get full USB, Ethernet and Wi-Fi going in a couple of days? The little code snippets are useful but are NOT as substitute for decent documentation. Len

UARTName is defined here: http://mbed.org/users/mbed_official/code/mbed-src/file/5fa2273de5db/vendor/NXP/LPC1768/hal/PeripheralNames.h. But just assuming the numbers stayed the same would be easier.

But those names are only used in the internal mbed functions. If you want to use them, you don't need to know the peripheral numbers. If you don't want to use them, you can just combine the user manual + LPC17xx.h.

I am definately not part of the mbed team: I do wonder what it is exactly that you are searching for. For example the first picture and table I linked you already tells which UART number is connected to which pins, why for example do you need to know where UARTName is defined? But the entire idea is that for 99% of your requirements you do not need to know which UART number you are addressing, or which bit of the status register you need to read. You just use library/standard C++ functions.

In the case of USB for example there is also an imo quite extensive list of standard libraries and implementation examples here: http://mbed.org/handbook/USBDevice. (I assume you are interested in USB device, USB host is here http://mbed.org/handbook/USBHost), with documentation for the architecture and the full source code with Doxygen documentation.

If you want to make your own register-level implementation, then yes that isn't nearly enough. Then you need the user manual, and probably also some app-notes. But that will be the same also with boards from other manufacturers. In that case you are ignoring a major advantage of mbed: the standard libraries.

So can you explain what exactly it is you are looking for? For example why do you need to know where UARTName is defined?

Disclaimer: Just to be sure, considering your second part was aimed at mbed devs, I am not one, this is purely my personal thingie :)

Hello Thanks again, that looks like what I am looking for. I certainly have no desire to write any low level code. Done enough of that in my life. Using the library/standard C++ functions if I want to send a character to come out on the UART2 TX pins on the mBed LPC1769 module what is the exact syntax and argument? Where are these I/O hardware related function arguments documented? Regards Len

The handbook has a list of standard library functions: http://mbed.org/handbook/Homepage. Also in the compiler if you click on the mbed library you can get the documentation.

For the UART you need the Serial code: http://mbed.org/handbook/Serial. So you make a serial object connected to the RX/TX pins you want it on (and that are supported obviously). Then for Serial it doesn't list all options, since it inherits some functions and also supports standard C++ functions. But just sending a character is done with putc.

So in your case something like:

#include "mbed.h"

Serial uart(p28, p27); //Pin 28 TX, pin 27 RX. 

int main() {
  uart.putc('A');
  while(1);

  //Printf is also completely supported
  int i = 100; 
  float f = 0.5;
  char h = 0x05;
  uart.printf("i = %d, f = %f, h = %02X\n", i, f, h);
}

Hello Erik. Thanks for the latest links. I now get the mBed scheme for the serial port arguments and pins. I owe you a beer or two for putting up with me so patiently on my first two days at the mBed coal face. Len. Perth Australia

Np, good luck with it. Btw i had an error on line 6, it said pc.putc instead of uart.putc.