Content originally posted in LPCWare by jschuld on Mon May 13 21:04:59 MST 2013Meanwhile I have been able to get a small project working on the LPC4088 that writes to a SPIFI device. I've based this on a uVision project which I ported to LPCXpresso. As the LPC4088 has ROM drivers available for SPIFI, there is obviously no driver that needs to be linked against.
However, for the LPC4333 I'm still struggling. I have again based something on a uVision (http://www.lpcware.com/content/nxpfile/lpc4350apdlzip).
Although the SPIFI example seems to have the software SPIFI library in it (for cortex-m4), I am not succesfull with loading this project using a J-Link. I've ported it to LPCXpresso, the same way I did for
the LPC4088 project but I get a lot of linker errors, mostly "Conflicting CPU architectures 0/13". I have selected the proper core, (LPC4333/M4), and ensured everything is that is build is build for the Cortex-M4.
I figured the issue is likely that I used a library that was part of a uVision project. I have foud a NXP released one (http://www.lpcware.com/system/files/SPIFILib-2012-12-11_0.zip) but this causes the same errors. I suspect it is still caused because of a conflict, as I have based my LPCXpresso project on a uVision project.
So I still have some questions:
Q1: Is it correct that the LPC4333 does NOT have ROM drivers for SPIFI, but the LPC4350 does?
Q2: Am I using the latest SPIFI software drivers? (I found the link in a forum post, but no idea if there is a later one already)
Q3: Are there any examples that use the software drivers on LPCXPresso?
Any help appreciated.
Cheers
J