TWR-K60 : Medical USB Stack : Memory Config File Not Found

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

TWR-K60 : Medical USB Stack : Memory Config File Not Found

Jump to solution
2,258 Views
F_Phidgets
Contributor I

I am currently trying to make use of the medical USB stack from freescale. I am using Codewarrior 10.1, and USB Stack v3.1.1.

 

I have installed the usb stack, and have imported the Device-HID project into codewarrior. The project builds correctly, but when i try to debug the project, it goes to the debug screen and displays an Error

 

---------------------

Problem Occured

'Launching kinetis_MK60N512VMD100_hid_mouse MK60N512VMD100_INTERNAL_RAM' has encountered a problem.

 

Failed to resume target process., Could not open memory configuration file

----------------------

 

I have attached the screenshot.

 

I have tried other sample projects(HID keyboard, etc) for the USB-Device stack and the same issue occurs.

 

I have tried un-installing and re-installing the stack numerous times, so that is not a fix. 

 

This issue does not arise when i make a bareboard project from scratch, or any other type of project for that matter. This only occurs with the USB stack projects.

 

Any suggestions would be helpful, thanks.

 

Fraser

 

Current Setup:

Windows 7

CodeWarrior 10.1

USB Stack 3.1.1

TWR-K60N512 w/ attached TWR-SER

Labels (1)
0 Kudos
1 Solution
382 Views
J2MEJediMaster
Specialist I

The use of the word "import" worries me. Did you use the CodeWarrior IDE's File > Import choice, or did you follow the instructions in the Freescale USB Stack with PHDC Device Users Guide? I am going to assume that you followed the guide for now, because if you did, you still will see that error. :smileysad: That's because to confirm the problem, I downloaded the guide, the USB stack, followed the directions, and got the same error.

 

As a side note, the .launch configuration file is not located in the Project Settings folder, but in the Debugger folder now. Assuming you figured that out, then the next hurdle is correcting the file path for both the memory and initialization files. Proceed as follows:

 

1) Call up the Debug Configuration window (Run > Debug Configurations) . Select the desire debug configuration. Under the Remote System group, for the System option, click Edit.

 

2) In the Properties window that appears, Click on the System tab.

 

3) Under the Initialize group, for the Initialize Target option, click on the navigate button. (It has the ellipsis  character "...".)

 

4) Navigate to the initialization file, init_kinetis.tcl. It's located on the path:

 

C:\Program Files\Freescale\Freescale USB Stack v3.1.1\Source\Device\app\hid\cw10\kinetis_k60\Debugger\init_kinetis.tcl

 

Your path name may vary, of course. Click OK.

 

5) Under the System group, for the Memory Configuration Target option, click on the navigate button.

 

6) Navigate to the memory config file, iMK60N512VMD100.mem. It's located on the path:

 

C:\Program Files\Freescale\Freescale USB Stack v3.1.1\Source\Device\app\hid\cw10\kinetis_k60\Debugger\MK60N512VMD100.mem

 

Your path name might vary. Click OK.

 

7) Click OK to dismiss the Properties Window.

 

8) Click Apply in the Debug Configuration window to save your changes.

 

You should be able to download and run the application now.

 

---Tom

 

View solution in original post

0 Kudos
2 Replies
383 Views
J2MEJediMaster
Specialist I

The use of the word "import" worries me. Did you use the CodeWarrior IDE's File > Import choice, or did you follow the instructions in the Freescale USB Stack with PHDC Device Users Guide? I am going to assume that you followed the guide for now, because if you did, you still will see that error. :smileysad: That's because to confirm the problem, I downloaded the guide, the USB stack, followed the directions, and got the same error.

 

As a side note, the .launch configuration file is not located in the Project Settings folder, but in the Debugger folder now. Assuming you figured that out, then the next hurdle is correcting the file path for both the memory and initialization files. Proceed as follows:

 

1) Call up the Debug Configuration window (Run > Debug Configurations) . Select the desire debug configuration. Under the Remote System group, for the System option, click Edit.

 

2) In the Properties window that appears, Click on the System tab.

 

3) Under the Initialize group, for the Initialize Target option, click on the navigate button. (It has the ellipsis  character "...".)

 

4) Navigate to the initialization file, init_kinetis.tcl. It's located on the path:

 

C:\Program Files\Freescale\Freescale USB Stack v3.1.1\Source\Device\app\hid\cw10\kinetis_k60\Debugger\init_kinetis.tcl

 

Your path name may vary, of course. Click OK.

 

5) Under the System group, for the Memory Configuration Target option, click on the navigate button.

 

6) Navigate to the memory config file, iMK60N512VMD100.mem. It's located on the path:

 

C:\Program Files\Freescale\Freescale USB Stack v3.1.1\Source\Device\app\hid\cw10\kinetis_k60\Debugger\MK60N512VMD100.mem

 

Your path name might vary. Click OK.

 

7) Click OK to dismiss the Properties Window.

 

8) Click Apply in the Debug Configuration window to save your changes.

 

You should be able to download and run the application now.

 

---Tom

 

0 Kudos
382 Views
F_Phidgets
Contributor I

I guess the word import was not well chosen. But for clarification I had done both methods of bringing the project into codewarrior. Both ways produced that error, in the case of File->Import, it was because it would set the default memory location to {MQX_ROOT_DIR}/etc/etc, because i guess that is what it does when you import? And when you drag the .project file into codewarrior, it seemed to have set the default .mem location to a folder within the 3.1.1 directory that didnt exist.

 

At any rate, the good news is you are a genius and solved my problem, thank you. I spent waaay too long looking for the place to set the config files and couldnt find any documentation on how. That was probably the only place in all of codewarrior i didnt look.

 

Again, thanks.

 

Fraser

0 Kudos