Yahoo Groups archive

Lpc2000

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

Message

Re: [lpc2000] Philips Utility Problem (Part 2)

2005-11-01 by Peter Jakacki

Leighton,

I had problems downloading when I used to use a particular USB-RS232 
adapter which funnily enough was based on an older Philip's chipset. 
There does not appear to be any problem if I use an internal coms port 
or a Silabs based USB adapter. This may be related to some timeout or 
handshake issue. Even at lower baud-rates I would have coms failures.

The laptop I used at the time was running on a power-pack and I would 
also notice mains leakage on the order of 100's of microamps (it 
bites!). This may not be a problem but I use my own isolated USB coms now.

Could your problem be anything along these lines?

*Peter*



Leighton Rowe wrote:
> Hey guys,
>
> I recently mentioned a problem where the Philips Flash utility 
> partially works with my lpc2114 board and gives communication errors 
> whenever attempting to Erase Flash or Download code to the board. 
>
> I troubleshooted the RS232 interface, and all rs232 signals are 
> working OK now, but I still get comm errors with the Phillps 
> Utility. I think that I'm possibly dealing with a more serious 
> problem here, as I can't even download code into flash memory of the 
> same board thru the JTAG interface. 
>
> I sometimes use the Debug Utility in the IAR Software as an 
> alternative to flash program and debug applications on the lpc2114 
> chip. This surely works. However, the above method didn't even work 
> with the same board. The IAR flash programming tool executed 
> normally while downloading code unto the board. However afterwards, 
> the memory dump showed no sign that the flash memory got programmed. 
> The application's memory area showed nothing but 1's or 0xFF's, 
> while the reset vectors supposedly points to the bootloader and not 
> the application.
>
> Let me know what you think. I think that I'm possibly dealing with a 
> corrupted chip.

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.