Hello!
I have a board working with LPC2368 uC, I talked to some NXP representative and he told me that LPC1769 were pin compatible.
The problem is, the board works fine with LPC2368, but when I change to LPC1769 I upload the code with success using Flash Magic, but anything works..even a simple blink LED test, the pins state go crazy.. Nothing works..
Does anybody know if I have to do some extra configuration in uVision4 to work with LPC1769? Or another configuration in Flash Magic?
Waiting for your help!!
Did you _recompile_ your code for the LPC1769...? You do remember that the LPC2368 Is an ARM7 chip, while the LPC1769 is a cortex M3...!
Yes, I start another project for LPC1769. I think that is a hardware problem..
That is the schematic: img515.imageshack.us/.../diagramd.jpg
If the LPC1769 is used, R172 is not mounted.
I have LEDs connected to some ports, and even when the memory of uC is empty, the LED is a litle bit ON, there is a weird voltage..
Running some more tests, I figure that the weird pin state were just for high impedance..
I guess the problem is that the program is not starting in the uC..
Using Flash Magic I can see the memory, and the code is there.
It's possible some problem with the bootloader of the uC?
After reset, if you have cleared chip or held the pin to force the boot loader, then all GPIO pins should have a weak pull-up.
So you have created a new project for LPC1769, so far so good. Have you added the C:\Keil\ARM\Startup\NXP\LPC17xx\system_LPC17xx.c file in the project (better copy it)? You also need to use the wizard of this file to set your clocks and dividers.
Did you also change the register names since the header of the LPC17xx uses structures to access the registers, I assume you have done that since the code compiles.
The pins of the mcu have an internal pullup that enabled by default and this is probably why you see the led turn on.
Alex
View all questions in Keil forum