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.
Don't guess - use the Debugger to find out for sure!!
How use the debugger? The uC doesn't work!
If the boot loader considers that there are no valid image in the memory, then you can check if the serial port responds to boot loader commands.
If the boot loader thinks there is an image, then you can try to set breakpoints and see if you can debug the initial instructions potentially sending the processor into a spin.
The good thing with many microcontrollers are that if they just have a reasonable clock signal and reasonable power, then you can do some form of debugging even if the external circuit have contains errors.
So - have you tried to figure out yet, if the boot loader do find a valid image or not?
How can I check that? Sorry..I don't know..
"How can I check that?"
To repeat myself: "If the boot loader considers that there are no valid image in the memory, then you can check if the serial port responds to boot loader commands."
You have read the chapter in the processor manual about the built-in boot loader?
Thank you for your help! Unfortunately some people use this forum to feel better with themselves.. To feel then they are the best programmers in the world, and for this make fun of the begginers and forget that one they they were one too. Please you don't answer my questions again, let someone else do this.
@Xavi@
Unfortunately some people use this forum to feel better with themselves..
yeah i got the same with my last post. the know all likes to write like hes big but hes probably a short ***!
Yeah.. I read a lot of posts in this forum and that kind of thing happens every time..
So the answer is that you have not checked the chapter about the built-in monitor - and have not checked on the serial port if the processor is waiting in the boot loader instead of starting any program.
Problem is - we can't check it for you.
What, exactly, do you expect from this forum? The user manual for the processor is mandatory reading for everyone using the processor. And the chapter about in-system programming is very much relevant to this problem.
Problem solving is about trying different things to try to collect enough evidence to finally know what is wrong.
But we can't spend significant time explaining the information that is available in this chapter of the manual. That would cost us lots of time. Time that we can spend on better things. After all - it isn't our project that is stuck with this problem.
www.keil.com/.../gsac_debugapplication.htm
http://www.keil.com/support/man/docs/uv4/uv4_debugging.htm
Look for tutorials and "lab exercises" here: http://www.keil.com/download/list/arm.htm
http://www.keil.com/books/