lpcware

[lpc15xx] LPCOpen compilation warnings for IAP and EEPROM APIs

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 15, 2016 by lpcware
Content originally posted in LPCWare by miccio on Thu Nov 05 09:05:17 MST 2015
Hello everyone,

As many may know, compiling LPCOpen for lpc15xx series issues the following compiler warnings:


DescriptionResourcePathLocationType
passing argument 2 of 'iap_entry' from incompatible pointer typeeeprom.c/lpc_chip_15xx/srcline 61C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeeeprom.c/lpc_chip_15xx/srcline 76C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 58C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 73C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 87C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 100C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 111C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 122C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 136C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 147C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 158C/C++ Problem
passing argument 2 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 172C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeeeprom.c/lpc_chip_15xx/srcline 61C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeeeprom.c/lpc_chip_15xx/srcline 76C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 58C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 73C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 87C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 100C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 111C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 122C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 136C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 147C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 158C/C++ Problem
passing argument 1 of 'iap_entry' from incompatible pointer typeiap.c/lpc_chip_15xx/srcline 172C/C++ Problem


This is all due to the different definition for iap_entry arguments (unsigned int in the signature, uint32_t inside the iap functions).
I'd like to substitute either of those and get rid of all these annoying messages althogether, but which one of the two is the correct one? Thanks in advance!

Outcomes