CW 10.1 on XP for Coldfire - Lock during Building Workspace

[jpa]

I'm trying to use the eval edition to, well, evaluate CW and MQX running on the 52233DEMO board. All was fine at first, but after importing a few files, the development studio locks while doing a build...it gets to some low percent (the exact number varies from 1 to 14% so far) and never gets beyond that. Progress bar in the lower right keeps cycling. I can close the Development studio, but the build dialog is still there and has to be killed.

If I exclude the file using compiler defines, everything builds. Add back the first function in the file, and it locks again. The first function just has a "for" loop with printf and a call to another function.

Really, a compile time error locks the environment?

Since the first lockup, I also get messages on startup..."Remote System Changed" "The project 'x' refers to a different version of the Remote System 'blah blah blah_PEBDM' than what is in your current workspace. Four times, two debugger times two releases (debug,release).  Doesn't seem to go away no matter which option I choose, and even if I gracefully shut down the studio and restart.

John

[jpa]

A bit more information.  The function had an undeclared user type as one of the parameters, as in:

void myfunction(MY_USER_TYPE *pInstance)

{

}

where the definition of MY_USER_TYPE was commented out. 

Changing the code to be an empty shell function (like the above) allowed the compiler to finish so I could see the error and fix it.  I then went on, uncommenting more of my code and fixing errors until I hit an error that has once again sent the build process off into the weeds.  

Also, FWIW, after I kill CWIDE with the Task Manager, Windows complains that there isn't enough virtual memory and it's going off to search for some more.  But only AFTER I kill CWIDE. 

John

[J2MEJediMaster]

What are your system specs?

---Tom

[jpa]

XP Pro SP3 running on a  VirtualBox VM with 512MB of RAM, 7GB of free disk space.  Processor is a Core 2 Quad @2GHz, although I think the VM only gets one core.  

John

---

J2MEJediMaster wrote:

What are your system specs?

---Tom

---

[J2MEJediMaster]

OK, most of the system specs look OK except for the RAM. According to this page, CodeWarrior for MCUs v10 requires 1GB of RAM. I would start with that amount of RAM (more if you can swing it) and see if the situation improves. Maybe there are other problems, but right now the key one is that the program is starved for memory.

---Tom

[jpa]

Tom,

Because it's a VM and the problem is so repeatable, I put the bug back into my software, replicated the problem, then restarted the VM with 1GB, then 2GB of memory.  The first time (512MB) it locked at 1%, the other two times it locked at 3%.   

Next step?  

John

[J2MEJediMaster]

 Next step is to start over with a fresh project. If you are using the old project there could be corrupted information.

If you are stating with a new project, then you need to file a service request on the problem.

---Tom