Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

Virtual Com with IAR

Virtual Com with IAR

2006-04-10 by ebreuilly

I download the virtualcom.zip file from keil and I try to compile it 
with IAR with LPC2148 IAR board. There are many difference between Keil 
and IAR source (ex __irq doesn't exist in IAR) so I can't compile this 
correctly.

Do anyone have already compile this example with IAR ?

Thank you for your help,
Loïc CHEVALIER

Re: [lpc2000] Virtual Com with IAR

2006-04-10 by Robert Nelson

ebreuilly wrote:
> I download the virtualcom.zip file from keil and I try to compile it
> with IAR with LPC2148 IAR board. There are many difference between Keil
> and IAR source (ex __irq doesn't exist in IAR) so I can't compile this
> correctly.
>
> Do anyone have already compile this example with IAR ?
>
> Thank you for your help,
> Lo\ufffdc CHEVALIER
>
Well to get you started, add this chunk of code to the USB_Init function 
in the "usbhw.c" file after the initializing of the PCONP setting.  This 
will turn on the USB connect transistor on the LPC-2148-E board, that 
isn't present with the keil board.  This will allow you to build the 
software with Keil's evaluation version and get you started on 
development.  For the moment there is no direct port to IAR.

" /* Addes IAR LPC2148-E compatibility */

  #define P0_23 (1<<14)	 /* Enable Vbus */
  #define P0_31 (2<<30)	 /* Enable USB Connect */ 
  
  PINSEL1 = (P0_23 | P0_31);   /* Enable Vbus and USB Connect */
"

Regards,

*/Robert Nelson/*//
Applications Engineer
robert.nelson@...

Re: Virtual Com with IAR

2006-04-11 by ebreuilly

--- In lpc2000@yahoogroups.com, Robert Nelson 
<robert.nelson.work@...> wrote:
>
> ebreuilly wrote:
> > I download the virtualcom.zip file from keil and I try to compile 
it
> > with IAR with LPC2148 IAR board. There are many difference 
between Keil
> > and IAR source (ex __irq doesn't exist in IAR) so I can't compile 
this
> > correctly.
> >
> > Do anyone have already compile this example with IAR ?
> >
> > Thank you for your help,
> > Loïc CHEVALIER
> >
> Well to get you started, add this chunk of code to the USB_Init 
function 
> in the "usbhw.c" file after the initializing of the PCONP setting.  
This 
> will turn on the USB connect transistor on the LPC-2148-E board, 
that 
> isn't present with the keil board.  This will allow you to build 
the 
> software with Keil's evaluation version and get you started on 
> development.  For the moment there is no direct port to IAR.
> 
> " /* Addes IAR LPC2148-E compatibility */
> 
>   #define P0_23 (1<<14)	 /* Enable Vbus */
>   #define P0_31 (2<<30)	 /* Enable USB Connect */ 
>   
>   PINSEL1 = (P0_23 | P0_31);   /* Enable Vbus and USB Connect */
> "
> 
> Regards,
> 
> */Robert Nelson/*//
> Applications Engineer
> robert.nelson@...
>
Thanks for your answer, now the USB seems works. The yellow Led 
become ON and the HID class is create in peripheric PC, but not com3 
& com4. So I can't test this exemple with an hyperterminal.
If you have any idea for help me ?

Thank you in advance,
Loïc CHEVALIER

Re: [lpc2000] Re: Virtual Com with IAR

2006-04-11 by Robert Nelson

ebreuilly wrote:
>
> >
> Thanks for your answer, now the USB seems works. The yellow Led
> become ON and the HID class is create in peripheric PC, but not com3
> & com4. So I can't test this exemple with an hyperterminal.
> If you have any idea for help me ?
>
> Thank you in advance,
> Lo\ufffdc CHEVALIER
>
>


On my system, as soon as the USB cable was plugged in i loaded the 
virtual comm drivers from the build directory, then two com's (com7 and 
com8) are created, but the system needs to be rebooted after first 
install.   After that i had no issues loading hyper terminal on com8 
(usb) and communicating to another hyper terminal on com1 using the On 
board RS232_1 connector.  ASCII data would transfer just as easily.

Robert Nelson
Applications Engineer
Digi-Key
robert.nelson@...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.