CMSIS drivers

[lpcware]

Content originally posted in LPCWare by OXO on Mon Jul 18 03:39:16 MST 2011
Can CodeRed please post the correct way of adding the lpc17xx.cmsis.driver.library to lpcxpresso eclipse.

This one here:

http://support.code-red-tech.com/CodeRedWiki/NXPDriverLibraries

I've got it in but the build keeps referring to C:/Users/Dewrek/Documents/lpcxpresso_3.4/workspace/lpc17xx.cmsis.driver.library/makesection/makerule/LPC17xx/make.LPC17xx.gnu: No such file or directory

And I can't find where to correct it. :mad:

.. I've already corrected one reference in makesection/makeconfig

[lpcware]

Content originally posted in LPCWare by Rob65 on Mon Jul 18 12:48:32 MST 2011

---

Quote: OXO
It's really annoying that they portray all this code as being a functioning system,

---

I'm not sure I see this as being portrayed as a functioning system.
Code Red states that it is "in a format suitable for import" and I think it is clear that it is not their code but just something that import in their tools.
Too bad though that it is not compiling - i would have expected it to and think it is an error that it does not.

I do not agree with qili that it pays to be one version behind the greatest and latest.
Take the LPCXpresso 4.0 compared with the 3.6 tools. The new version is clearly nicer and the included FreeRTOS 7.0.1 project wizard is very nice.
But I do think this cmsis driver project is too new to be matured enough to be adopted as the new driver framework.

If you need drivers, check out some of the work others have done. I made an I2C driver based on the example code - it just has some bugs fixed and it includes handling of missing slaves and incorrect responses from the slave (link) but there are also other versions and other drivers available.

The nice thing about the lpc1xxx variants is that most of the peripherals stay the same between the devices. So an I2C, uart, timer, CAN or usb driver is (almost) the same for an lpc11xx, 13xx or 17xx device.

There is no validated/tested set of driver available (for free). Never trust any code you are given, i don't even trust my own code until it is porperly tested :p
A proper driver must contain documentation, test program(s) and a test report before you should trust and use it. I have used 3rd party drivers and libraries but never without having them tested.

Regards,  Rob

[lpcware]

Content originally posted in LPCWare by qili on Mon Jul 18 07:07:33 MST 2011
it always pays to be a version or so behind the latest and greatest.

[lpcware]

Content originally posted in LPCWare by OXO on Mon Jul 18 05:00:46 MST 2011
Thanks Rob.

It's really annoying that they portray all this code as being a functioning system, yet many here have discovered that a lot of work is required to get it running

Chris

[lpcware]

Content originally posted in LPCWare by Rob65 on Mon Jul 18 04:30:12 MST 2011
This is strange ...
What happens is that $(PROJ_ROOT) in the makefile expands to C:/Users/Dewrek/.... and this is strange since the project properties clearly show that this environment variable is set to "${WorkspaceDirPath}/lpc17xx.cmsis.driver.library".

I find this project a very strange one, it seems that this is not using the LPCXpresso build environment but some tools that are included as binaries (in makesection/tools) in the project :eek:
From a system administrator point of view I don't like projects to include their own binaries (programs) to work with - this should also not be necessary since I already have a perfectly good set of tools on my PC - and there is also the risk of spreading virusses (think of sharing projects with others).

If you like the CMSIS drivers as they are given here, you could copy them into your own project and let the LPCXpresso environment figure out how to compile things. That looks to be the better sustainable solution IMHO ...

Regards,
Rob