Support for DMA transfers

Bertrik Sikken — Fri, 16 Jan 2009 04:43:48 -0000

Added example code for doing DMA transfers with isochronous IN/OUT endpoints, testable with sample linux code used in the non-dma sample.

During previous testing we were able to achieve full theoretical speed of 1023000 bytes/sec for a single ISOC IN endpoint (when setting max data size to 1023 and doing transfers every frame, the sample isn't configured to run that fast but a tweak to the configuration descriptor will do the trick)

Support for isochronous mode transfers

Bertrik Sikken — Wed, 14 Jan 2009 05:03:15 -0000

Sample device code and linux host side devfs-based code has been added to demonstrate communications in isochronous mode.

Moving away from interrupt-on-NAK

Bertrik Sikken — Mon, 22 Oct 2007 21:57:28 -0000

I plan to completely get rid of usage of the interrupt-on-NAK feature. It causes a very high interrupt rate which results in a lot of questions by people using the stack.

The virtual COM port example is already converted (now uses the frame interrupt to trigger the first packet of a sequence of bytes going from device to host). Next target is the mass storage example.

Migration from CVS to SVN

Bertrik Sikken — Mon, 11 Dec 2006 18:23:28 -0000

I'm considering to move the sources over from CVS to SVN sometime in the coming days.

BSD license

Bertrik Sikken — Wed, 18 Oct 2006 19:29:20 -0000

I've decided to change the license from LGPL to BSD.
The BSD license will be applied soon to the core of the lpcusb code. Some of the application examples still use LGPL code, so those parts will take some time for the license to be changed.

Release v20060903

Bertrik Sikken — Sun, 03 Sep 2006 21:42:05 -0000

I've just created release v20060903, consisting of a couple of bug fixes and simplification of the API. Also the source code is now updated to be used with doxygen to create 'automatic' source code documentation. Sorry, no interrupt support yet in this release.

Some stuff I'm thinking about to improve lpcusb:
* Finally add the interrupt support
* Add DMA support. I initially skipped this because I thought it would be complicated. It now seems a lot easier than I initially thought.
* Figure out the exact requirements for USB mass storage and implement them.

Bugfix release v20060729

Bertrik Sikken — Sat, 12 Aug 2006 12:44:02 -0000

A serious bug was discovered in the sources, possibly causing random memory overwrites.
This bug has been fixed in version v20060729.

Planned for the next version:
* interrupt support for USB virtual COM port
* better documentation of source code with doxygen

USB mass storage

Bertrik Sikken — Fri, 26 May 2006 10:24:47 -0000

Current CVS now contains an initial version of a USB mass storage application example. It already passes the MSC compliance tests, but there are still minor issues making it work in Windows (reading / writing data / quick format succeeds, full format still fails).
It will be part of the next release.

Anonymous CVS problems

Bertrik Sikken — Mon, 08 May 2006 13:25:01 -0000

As you may have noticed already, anonymous CVS has not been updated for some time now (several weeks). Normally, the anonymous CVS repository is kept in sync with developers' CVS (with just a few hours delay), but it appears there are some sitewide problems with it, see the sourceforge status page:
http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1

Development is still going on. An implementation of USB mass-storage on an SD-card is almost ready and planned for the next release (currently passes most tests of the USB compliance verifier and appears as a removeable disk with read/write access under both Windows XP and Linux 2.6)

USB virtual COM-port

Bertrik Sikken — Mon, 03 Apr 2006 16:58:58 -0000

The current CVS version now has an example showing how to implement a virtual COM port. This means that (under Windows) plugging in the LPC214x results in an additional COMx port that you can use to talk to your device (e.g. through hyperterminal).
On Linux, the serial port can be accessed with the cdc_acm driver through a /dev/ttyACM0 device file.

To try it out, check out the code from anonymous CVS, or wait until the next release (which is planned as soon as current CVS problems are resolved).

Recent posts to news