Lpc2000

Nick,

Thanks for letting me know about your LPC 2106 problems. Since I'm 
working from home today I do not have any other cables but I'll get 
back to you as soon as I have tried a different one. As I wrote 
earlier, I have tested different baudrates and made sure that the 
comport was correctly setup. I'll check that with a scope tomorrow. 

Best regards 
/Anders


-- In lpc2000@yahoogroups.com, "nma550n" <nma550n@...> wrote:
>
> Anders,
> 
> I am also having problems with the Philips LPC2000 flash utility 
> (olimex LPC2106), and was just about to post a message on this 
board 
> to see if the problem lies with my development board.
> I am just trying to upload the simple blink LED hex file to flash, 
> and it just comes up with cannot communicate. I too have tried 
many 
> different com ports, jumper settings and different reset 
conditions, 
> to no avail. This is the first time I have tried to use this 
board, 
> so i have no idea if the thing works.
> 
> I am almost certain the problem does not lie with the Philips 
LPC2000 
> flash utility as I have scoped out the Rx signal (3.3v low, 0v 
high) 
> on the board and found it to receive data. 
> However, my Tx pin on the chip is always at ground and does 
nothing.
> 
> Does anyone know if Tx should be held at 0v???
> 
> Not sure if this will help you Anders, but just to let you know 
your 
> not alone.
> 
> cheers,
> 
> Nick
> 
> > --- In lpc2000@yahoogroups.com, "Anders Kjellberg" <akj@> wrote:
> > >
> > > Hi,
> > > I'm trying to establish connection with Philips Flash Utility 
and 
> > an Olimex 2106 mt board without success. TheBSL jumper is 
shorted 
> > and the frequency set at 14745kHz (14.7456MHz). Different 
baudrates 
> > have been tried without success. I am not sure about the DTR/RTS 
> > settings however. Also I may be using the wrong RS232 cable. 
Null 
> > modem or not? I'll have to check that. I intend to use the 
> > bootloader and ICCARM. Any ideas that may help?
> > > 
> > > Thanks in advance!
> > > /Anders
> > > 
> > > [Non-text portions of this message have been removed]
> > >
> >
>