The LPC1343 comes with code bundle from Keil. Among the examples one can find the virtual serial port example, using the USB CDC class. Unfortunately the original .inf file works only for 32-bit systems. To solve the problem, I have grabbed the template file for usbser.sys from the following source CDC class for Atmel MCUs (many thanks to Pavel K). What is interesting, the file was actually based on the driver file for the LPC134x family. For some reason the VID/PID combinations did not work for me (some of them were for Atmel, but some seemed to be still valid for NXP). Nevertheless, the only thing I had to do was to enter the right VID/PID combination. You can download the modified "driver" here: CDC class driver for LPC1343. Now it works well with NGX Technologies mX-LPC1343-S starter kit. In case you use the CooCox to compile the USB CDC example, here goes the useful hint: in case of trouble, change the SystemCoreClock to SystemFrequency (and include system_LPC13xx.h).
Tag - driver
Tuesday, January 1 2013
By Olek on Tuesday, January 1 2013, 23:39
By Olek on Tuesday, January 1 2013, 20:24
I have recently experienced considerable trouble related to installing SEGER J-Link driver for the on-board debugger on Atmel board on the Windows 7 64-bit machine. It may be important that I have earlier installed J-Link driver for the Freescale KwikStik board. The ATSAM4S-XPLD board support comes in form of online available archive, that contains further archives and sometimes even one more level of archives. Somewhere there is a directory called "Setting up", in which you will find the "Setup_JLinkARM_V442", you probably do not want to use it on machine similar to mine. You might also want to download the newest drivers from Segger directly, but if these are in version "Setup_JLinkARM_V458a" (as they were at the moment of writing this entry), you should also not use these. What have finally worked for me, is "Setup_JLinkARM_V459c", downloaded from the beta versions section. The older drivers were just impossible, for example windows could not install them because of "The name is already in use as either a service name or a service display name". And a final word - reboot your machine before the installation.