This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LPC1769 issue

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!!

Parents
  • 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.

Reply
  • 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.

Children
  • @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.