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.
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.
I think I have at least found something and now this might be easier to explain.
This doesn't seem like just a size issue. It looks like a USB issue as well. I've been able to break it while the .HEX file is under 64KB
Prior to inserting code to flash LEDs to test if the NXP is even executing any code, the only way to tell if the NXP was up and running was to see if Linux ( on another processor connected to the NXP via USB ) could see the NXP ( via lsusb ).
After inserting code to flash LEDs (is at the end of main to insure it was exectued), I always see the flashing LEDs whether or not USB fails or succeeds the LEDs still flash. This tells me the code has been executed.
I do a full shutdown power cycle on the system and on power up it doesn't see the USB, but doing a reboot it does.