• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 1619 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

LPC1111 - Flash time-out

Erwin Steffens

Hello,

I'm debugging with my custom LPC1111 board. My code size is around 3000 kB.

When my code size gets around 4 kB I get a Flash Timeout error from keil when programming the chip. The code size of the chip is 8 kB.

Any ideas on this problem ??

Best regards,

Erwin

Parents
  • 0 in reply to Tamir Michael

    Hi

    I've got the tip from Keil support.

    As I understand needs the uLink some RAM for buffering the code data and for some additional internal variables to control the programming algorithm. It seems that if more than 4k code should be downloaded a conflict happens between this to kind of RAM user. If the hole RAM is defined for the buffer no space is left for the internal varibables.Why it happens at the 4k boarder I don't know. As I know Keil only tested the programming algorithm with a LPC11xx device with more RAM than the 0x0800, so the proble din't show up.

    regards

Reply
  • 0 in reply to Tamir Michael

    Hi

    I've got the tip from Keil support.

    As I understand needs the uLink some RAM for buffering the code data and for some additional internal variables to control the programming algorithm. It seems that if more than 4k code should be downloaded a conflict happens between this to kind of RAM user. If the hole RAM is defined for the buffer no space is left for the internal varibables.Why it happens at the 4k boarder I don't know. As I know Keil only tested the programming algorithm with a LPC11xx device with more RAM than the 0x0800, so the proble din't show up.

    regards

Children
  • 0 in reply to Raphael L�ffel

    Here is the reply from support:


    Dear Erwin,

    Correct. This is also what NXP states in the manual that IAP uses the last 32bytes of RAM. So that must not be used by the uVision flash algorithm.
    As far as I know, the current default settings should take care about this. So if you create a new project, it should be correct.

    Best Regards
    Andreas Barth