Loaded code "disappears" after a power cycle

I am using the MPC2300 with an LPC2368 NXP / Philips processor with uVision 3.

The problem I am having is with file/image size. When loading anything lower than 64KB the program works and runs perfectly fine after doing a full power cycle. The LPC2368 acts as a slave to another processor which runs the OS, etc.

Anything over 64KB it's like the code loaded in isn't even there after the power cycle. After doing a power cycle and the system is booted, issuing a reboot then solves the problem. I am going to assume there is some default size limitations? Is there some modifications I need to make to be able to load files over 64KB onto the LPC2368 such as changing the memory map?

Is it a uVision setting I am missing?

I've tried setting --entry Reset_Handler / main / __main / 0x00000000

I've tried increasing stack and heap size.

Still stuck with this problem. Any ideas on a solution?

Thanks all.

Parents
  • All rather antiquated. I guess I'd look at what flashing algorithm is being used, if it's correct, or if there's an issue wrapping at 64KB and erasing the first block again.

    Is there an issue with the .HEX file? Does the flashing successfully verify what has been written?

    What's actually in the memory of the failing devices, is it blank, or some other data? Can you use SAVE in the debug command window?

Reply
  • All rather antiquated. I guess I'd look at what flashing algorithm is being used, if it's correct, or if there's an issue wrapping at 64KB and erasing the first block again.

    Is there an issue with the .HEX file? Does the flashing successfully verify what has been written?

    What's actually in the memory of the failing devices, is it blank, or some other data? Can you use SAVE in the debug command window?

Children
More questions in this forum