Read LPC54113 UUID

[eduardocarletti]

Hello,

I am trying to retrieve the UUID from my LPC54113 using the IAP commands. I followed the instructions on the chip manual.

The problem is that the return value is always 0000FFFF 00000000 00000000 00000000 , and I'am pretty sure that this isn't right. This seems to occur only whith the read UUID command, as other commands (i.e Read Part Identification) return correct values.

The code I use for reading the UUID is:

/***************************************/
#define IAP_LOCATION 0x03000205

unsigned command_param[5];
uint32_t status_result[5];

typedef void (*IAP)(unsigned int [],unsigned int[]);
IAP iap_entry = (IAP) IAP_LOCATION;

void read_serial_number(uint32_t *ptr) //read serial via IAP
{
   command_param[0] = 58; //IAP command
   __disable_irq();
   iap_entry(command_param,status_result);
   __enable_irq();
   if(status_result[0] == 0) //return: CODE SUCCESS
   {
      ptr[0] = status_result[1];
      ptr[1] = status_result[2];
      ptr[2] = status_result[3];
      ptr[3] = status_result[4];
   }

}
/***************************************/

To read the UUID, just  call "read_serial_number" passing the pointer to save the data as argument.

Does anyone knows what am I doing wrong or if is there any other way to do this?

[jeremyzhou · Accepted solution]

Hi Eduardo Carletti,

Thank you for your interest in NXP Semiconductor products and
for the opportunity to serve you.
There's a bug in the LPC5411x series MCU (as below figures present), and the unique serial number (four 32-bit words) can be directly read from address locations 0x0100 0100 to 0x0100 010C.

Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[eduardocarletti]

Hi jeremyzhou, this worked. Should I be worried about this address changing on newer chips? Do you know if are there newer revisions of the MCU being sold or under development?

Thank you.

[jeremyzhou]

Hi Eduardo Carletti,

Thanks for your reply.
1) Should I be worried about this address changing on newer chips?
-- No.
2) Do you know if are there newer revisions of the MCU being sold or under development?
-- No.
Hope this is clear.

TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------