Yahoo Groups archive

Lpc2000

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

Message

Re: LPC2148 USB

2006-02-23 by varuzhandanielyan

New questions.

Thanks to Bertrik!  I checked the P0.23 pin and there was wrong
level, because by factory mistake, the R38 and R39 resistors values on
my MCB2140 board were messed.  When I re-soldered them in right way,
the USBHID worked.  But...
1. After I reset the microcontroller, I must again select the KEIL
MCB2140 HID in the HID Client utility Device menu to reconnect the
board.
Could anybody help and tell how the HID Client should be changed to
solve the problem, i.e. to reconnect the microcontroller automatically
after reset?

2. Is 48 MHz the maximal frequency to run LPC2148 with USB?

Great thanks in advance,
Varuzhan  
 

--- In lpc2000@yahoogroups.com, Bertrik Sikken <bertrik@...> wrote:
>
> Maybe this helps:
> 
> In my USB code, I have P0.31 configured as CONNECT and P0.23
> as VBUS sense. With that configuration I found that P0.31 can
> only become active when P0.23 sees a high level.
> 
> Regards,
> Bertrik
> 
> varuzhandanielyan wrote:
> > Nothing helps.
> > 
> > I am going step-by-step using ULINK and watching the P0.31
> > state by scope.
> > If I configure P0.31 as output, I can easily set it to 0 or
> > 1, but when I configure it for CONNECT inside the USB_Init() :
> > PINSEL1 |=  0x80004000;
> > and try to set the SoftConnect_N active, P0.31 remains in
> > high (inactive) state.
> > I tried both calling the USB_Connect(TRUE) and immediate
> > by commands
> > CMD_CODE = 0x00FE0500;
> > CMD_CODE = 0x00010100;
> > placing them in different places, particularly after
> > USB_Reset() as recommended - no effect.
> > 
> > Please, help me, what is wrong?
> > 
> > Great thanks in advance,
> > Varuzhan
> > 
> > 
> > 
> > --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@> wrote:
> >>
> >> Varuzhan,
> >>
> >>     On Keil's website, there is an app-note how to use the soft
> >> connect: http://www.keil.com/support/docs/3141.htm
> >>
> >>     It's a regret that, unlike Olimex and IAR board, Keil's board
> >> doesn't have the soft connect feature on the board. So, you will
> >> have to rewire the board as seen on the Olimex schematics or Keil's
> >> app-note.
> >>     I have tested with both external power supply and USB power
> >> with soft connect logic. It works just fine. What Joel said is true:
> >> set PINSEL1 to use "soft connect", then send SET_DEVICE_STATUS
> >> command to protocol engine by calling "USB_Connect(TRUE)" as seen in
> >> Keil's example. I think you may want to check your H/W logic again.
> >>
> >>     In Keil's example, you may want to add "USB_Connect(TRUE)"
> >> in the ISR handler, right after USB_Reset(), to deal with bus reset
> >> interrupt, just to be safe.
> >>
> >> Regards,
> >>
> >> Tom
> >>
> >>
> >> --- In lpc2000@yahoogroups.com, "varuzhandanielyan" <dan@> wrote:
> >> >
> >> > Hi, Joel
> >> >
> >> > I changed P0.31 to be configured as CONNECT:
> >> >   PINSEL1 |= 0x80004000; // 0x40004000;                   /* Select
> >> > USB Link, VBUS */
> >> >
> >> > The CON bit (page 225) is already set by the call in the Keil
> >> example:
> >> >   USB_Connect(TRUE);                        /* USB Connect */
> >> >
> >> > But it still does not work.
> >> >
> >> > By the way, my previous project with LPC2138 and FTDIChip FT2232C
> >> > started to work without any problem.  It is pity, that the LPC2148
> >> USB
> >> > usage requires such effort.
> >> >
> >> > Varuzhan
> >> >
> >> >
> >> > --- In lpc2000@yahoogroups.com, "Joel Winarske" <joelw@> wrote:
> >> > >
> >> > > Hi Varuzhan,
> >> > >
> >> > > > > When PINSEL0 P0.31 is configured for CONNECT, refer to page
> >> 225 of
> >> > > > the User
> >> > > > > Manual for control of this pin.
> >> > >
> >> > > Did you configure PINSEL0 P0.31 for CONNECT?
> >> > > Are you sending command as per page 225 to connect/disconnect?
> >> > >
> >> > >
> >> > > Joel
> >> > >
> >> >
> >>
>

Attachments

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.