2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Hello, I am using "old" LPC2106, and had to manually upgrade their bootloader to version 1.52. I can always program the prototypes using ISP, but some of the prototypes (about 10%...) become non functional when they are upgraded using IAP. At that point of the code, the core is running at 60MHz with the PLL enabled (4 * 14,475,600Hz). I am wondering if there is still a bug in this bootloader version? Is it possible that the bootloader has not been fully reprogrammed? I used the Philips tool v1.0.2. Could it be too old? In this situation: Would I still be able to program the prototypes in the ISP mode? Would I still be able to retrieve the bootloader version? I am currently able to program in the ISP mode and to read the bootloader version on every prototype, even the non-functional ones. Thanks for your help. Gilles

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )