Memory configuration file error

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Memory configuration file error

跳至解决方案
3,277 次查看
NeilVP
Contributor II

I am using CW10.1 Eclipse for the very first time and have rebuilt an old project originally built with CW6 to a MC9So8QE part. On trying to run debug I get the error message 'Could not open memory configuration file', on clicking Details, I get 'could not open memory configuration file'  which is not exactly helpful.

Could someone please tell me which memory configuration file I should look for and where to look for it or how to generate it in the first place.

 

Many thanks

 

Neil

标签 (1)
标记 (1)
0 项奖励
回复
1 解答
2,472 次查看
BlackNight
NXP Employee
NXP Employee

Hello,

any special reasons why you are using 10.1, and not 10.2? I ask because 10.2 so much better and faster that I have put away my old 10.1 installation a while back. So I cannot try it right now with a 10.1 (until I have it installed).

 

But the debugger is looking for a memory configration file. It is usually inside your project the Project_Settings folder.

So for your device it is probably Project_Settings\Debugger\MC9S08QExx.mem.

 

The simplest would be if you create a new project with the wizard (File > New > Bareboard project) and then use this one as a reference. The link to the .mem file is made in the debug configurations. The place of the .mem file specified in the debugger is a little bit different for 10.1, but for 10.2 it is in the debug run configurations (menu Run > Configurations).

Attached is the screenshot of my 10.2.

 

Hope this helps,

BK

在原帖中查看解决方案

0 项奖励
回复
5 回复数
2,473 次查看
BlackNight
NXP Employee
NXP Employee

Hello,

any special reasons why you are using 10.1, and not 10.2? I ask because 10.2 so much better and faster that I have put away my old 10.1 installation a while back. So I cannot try it right now with a 10.1 (until I have it installed).

 

But the debugger is looking for a memory configration file. It is usually inside your project the Project_Settings folder.

So for your device it is probably Project_Settings\Debugger\MC9S08QExx.mem.

 

The simplest would be if you create a new project with the wizard (File > New > Bareboard project) and then use this one as a reference. The link to the .mem file is made in the debug configurations. The place of the .mem file specified in the debugger is a little bit different for 10.1, but for 10.2 it is in the debug run configurations (menu Run > Configurations).

Attached is the screenshot of my 10.2.

 

Hope this helps,

BK

0 项奖励
回复
2,472 次查看
BlackNight
NXP Employee
NXP Employee

Finally here is what I have in 10.1 (in case the problem has not been solved yet).

The memory configuration file setting is in the launch/run configuration.

 

See attached screenshot.

 

I have attached a S08QE128 project as reference.

 

Hope this helps,

BK

0 项奖励
回复
2,472 次查看
NNeff
Contributor III

Hi BK (Erich?),

I found this question and answer when I searched for "memory configuration file", because I'm having the same problem.  I'm running CW 10.6 for MCUs, I've created a bareboard project for the FRDM-KL25Z board, selecting ProcessorExpert, and I'm connecting with the board over OpenSDA. When I try to run/debug the executable, CW complains that it can't find the memory configuration file, which one error message identified as MKL25Z128.mem in ProjectSettings/Debugger, and sure enough, it's not there.  I have been looking in all the configurations and properties I can find to find how to get CW to generate the .mem file, without success.  How do I generate the MKL25Z128.mem file in the first place?

I hope you are still at Freescale and can help me out!  Thanks, Nancy

0 项奖励
回复
2,472 次查看
BlackNight
NXP Employee
NXP Employee

attached is the MKL25Z128.mem file from one of my CW projects.

I hope this helps,

Erich

0 项奖励
回复
2,472 次查看
NNeff
Contributor III

Thanks for the file--that appears to be working.

I accidentally found out how to generate them.  My path to the Processor Expert files was to the PEx Driver Suite instead of CW installation. Fixing that fixed another problem, and inadvertently fixed the mystery of the missing memory configuration files as well.

Nancy

0 项奖励
回复