CrossWorks Debug/Download Problem

Started by Chris March 18, 2012
Trying to test out the CrossWorks IDE.

Had a LPC1765 project already compiled and running on my board with another IDE.
Took one of the LPC1768/FreeRTOS examples and modified it, and converted my project files. They all compile.
Flash/Ram images appear to be nearly identical to original build, seem to be correct enough to try running.

Using Olimex ARM-USB-OCD pod. Original CrossWorks demo downloads to the board and runs fine.

However when I try to download/debug my project I get:

- About 4 times: "Line 2: not a function object"
- Then: "LIBMEM RPC Loader has not initialized correctly"

I have checked the other notes on CrossWorks about these errors, but I cannot find any problem.
The hzp/hzs files were taken from the demo, so I think they contain everything needed.

I have not been able to track down the cause of these download/debug error msgs.
Sent msg to Rowley as well.

Thought perhaps you existing CrossWorks users may know the cause.

Chris.



An Engineer's Guide to the LPC2100 Series

--- In l..., "Chris" wrote:
>
> Trying to test out the CrossWorks IDE.
>
> Had a LPC1765 project already compiled and running on my board with another IDE.
> Took one of the LPC1768/FreeRTOS examples and modified it, and converted my project files. They all compile.
> Flash/Ram images appear to be nearly identical to original build, seem to be correct enough to try running.
>
> Using Olimex ARM-USB-OCD pod. Original CrossWorks demo downloads to the board and runs fine.
>
> However when I try to download/debug my project I get:
>
> - About 4 times: "Line 2: not a function object"
> - Then: "LIBMEM RPC Loader has not initialized correctly"
>
> I have checked the other notes on CrossWorks about these errors, but I cannot find any problem.
> The hzp/hzs files were taken from the demo, so I think they contain everything needed.
>
> I have not been able to track down the cause of these download/debug error msgs.
> Sent msg to Rowley as well.
>
> Thought perhaps you existing CrossWorks users may know the cause.
>
> Chris.
>
>
>

Chris,
not that long ago I had a very similar behavior when downloading a converted demo project to the target(LPC1769).
What helped me at the end, was to delete the hzp/hzs files and start with a "New Project" to generate new hzp/hzs files.
Helmut

>>What helped me at the end, was to delete the hzp/hzs files
>> and start with a "New Project" to generate new hzp/hzs files.

Thanks. I finally got a response from Rowley, and the problem was the Target Script parameter
for the xxx_target.js file was not set. Don't know why it got cleared, but I set that, and solved it.

There are so many parameters spread out through CrossWorks
it consumes a fair amount of time finding things and figuring out what does what.
Still trying to find things and getting use to it.

Chris.