CW Lite w/M52259DEMO board, cannot erase/program NEW projects (demos work) all set for OSBDM

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CW Lite w/M52259DEMO board, cannot erase/program NEW projects (demos work) all set for OSBDM

Jump to solution
2,949 Views
froggie
Contributor II

OS is WinXP SP3

CW v7.1.2

Board: M52259DEMO

 

Every time I try to create my own project (with or without MQX) and I then try to erase or flash the memory, CW has a seg fault and I have to select abort to kill it:

 

 

---------------------------
CodeWarrior Error
---------------------------
CodeWarrior encountered an unhandled exception 0xc0000005 at address 0x1001e78f
(The memory at address 0x00000000 could not be read)

Location: IDE_MSL_DLL90_x86.dll:0x1001e78f

Crash dump written to C:\Program Files\Freescale\CodeWarrior for ColdFire V7.1\bin\IDE.exe.b3024.20091013.213433A.dump

Choose 'Abort' to end the program, 'Retry' to debug, or 'Ignore' to continue (at your own risk!)
---------------------------
Abort   Retry   Ignore  
---------------------------

 

The erase log  shows some calls to the GDI API and when it tries the first memory read, it croaks.

 

I have spent a long time comparing the set-up files for the MQX web hvac demo and my new project, and (except for the path info) the info seems identical.  The web hvac projects erases & programs fine.  I have also tried non-MQX projects and have the same error.

 

My projects & the demos are all set to use the OSBDM USB debugger.

 

There may be a path problem finding the right m52259demo.cfg file, but I can't see the error.  I've tried switching the paths between project relative/absolute/MQX_PATH and all that did was trash the project file (the IDE showed multiple entries afterwards which I was unable to correct).

 

Anyone else have this problem and found a solution?

 


Thanks

Labels (1)
0 Kudos
1 Solution
591 Views
froggie
Contributor II

I examined a lot of the setting files created with CW and compared them with the demos and I realized that almost all the setting files were FUBAR with wrong MQX versions, wrong board config files, etc.  So I did a complete uninstall and re-install:

 

a) I used CW Lite from the website;

b) then the 7.1.2 patch;

c) followed by the OSBDM zip file;

d) and finally the MQX download from the website.

 

I also installed everything into a shorter directory path & stripped the spaces from the directory names.

 

It appears to work properly, although the lite version now complains the web hvac demo is too big.  But I'm slowly migrating the pieces I need to my own project which I can now flash.

 

Thanks.  Sorry to have bothered you.

View solution in original post

0 Kudos
6 Replies
591 Views
J2MEJediMaster
Specialist I

If you are certain the problem is with the path, could it be that:

 

1) The path to your project directory is too long, or

 

2) Does one of the directory names along the path contain blanks?

 

Can you transplant your project directory into the demo directory and get it to work?

 

---Tom

0 Kudos
591 Views
froggie
Contributor II

re: moving the project to the demo directory--

 

Yes-- I tried that & had the same problem.

 

I tried something else which was to copy a demo project to another directory & use the instructions I found here for re-setting the dirs in the project & rebuilding.

 

The rebuild worked, but when I tried to erase memory, I got an error msg saying the initialization file could not be found.

 

Do you know how to set that in the project?

 

The new projects I create may have the initialization file name set to a bad config file, so it finds the file but with bad settings, causing the seg fault (???).

 

re: spaces in path

 

Since the MQX projects install into an MQX directory with spaces in the name, I'm not sure that is the problem.  Or, must CW itself be installed somewhere without a space in the path (i.e., not "Program Files")??

 

I also have seen some references to a variable "(CodeWarrior)" in the config files-- do you know how I can see what that is set to and or change it?

 

Thanks again for all the help.

0 Kudos
591 Views
J2MEJediMaster
Specialist I

Go to your project's settings (type Alt+F7) and then select the CF Debugger Settinga panel. In this panel, there is a Use Target Initialization file. Click on the Browse button and select a .cfg file that matches your board type or, lacking that, the processor type. When the CodeWarrior wizard makes the project, it places a cfg directory in your project directory that contains the necessary .cfg files.

 

Also, what target did you set CodeWarrior to build? Typically there are several targets, one that has to do with loading the project in SRAM for debugging. If you have selected this as the target, then you will get errors when trying to program flash because the code addresses are all wrong.

 

---Tom

0 Kudos
592 Views
froggie
Contributor II

I examined a lot of the setting files created with CW and compared them with the demos and I realized that almost all the setting files were FUBAR with wrong MQX versions, wrong board config files, etc.  So I did a complete uninstall and re-install:

 

a) I used CW Lite from the website;

b) then the 7.1.2 patch;

c) followed by the OSBDM zip file;

d) and finally the MQX download from the website.

 

I also installed everything into a shorter directory path & stripped the spaces from the directory names.

 

It appears to work properly, although the lite version now complains the web hvac demo is too big.  But I'm slowly migrating the pieces I need to my own project which I can now flash.

 

Thanks.  Sorry to have bothered you.

0 Kudos
591 Views
J2MEJediMaster
Specialist I

You did not bother us. I hope that all of our suggestions got you pointed in the right direction. The HVAC demo's code is bigger than the code size limit allowed in the Special Edition of CodeWarrior, so that behavior is "normal." I am going to look into getting that fixed...

 

---Tom

Message Edited by J2MEJediMaster on 2009-10-16 08:18 AM
0 Kudos
591 Views
fcorra
Contributor I

Hi, i experienced the same erase problem with the m5229demo board, it worked with telnet2ser demo project and crash with any new project i created. 

 

After several tests i found the problem arise from the "Int flash debug settings" panel in the field

"Use target initialization files" and "Use memory configuration file".

 

I made a copy the two files from the original directory in another one ( C:\Documents and settings\user .. etc) and set an absolute path.

 

It works.

 

fcorra

 

 

 

0 Kudos