Sorry to ask such a very simple question:
I have the P&E Multilink USB-ML-12E connected to my board and it works. Now I need to know how to verify code that is on the board.
Background: I downloaded code into my MC9S08QE8 a couple months ago. Now I want to go back and compile the source code I have and make sure it was the source code that generated what I downloaded into the MC9S08QE8 at that time.
I do not want to download the code I am now compiling - just verify that it matches what is in the chip. I am using codewarrior V10.
How do I do this?
Renee
Solved! Go to Solution.
Hello
Did you consider using a connect launch configuration and dumping memory content to a file.
In order to define a Connect launch configuration follow these steps:
1- In CodeWarrior MCU V10 open the Debug Configuration dialog (Select Run > Debug Configuration).
2- Click on CodeWarrior Connect on the left hand side of the dialog.
3- Click on the New Launch Configuration icon to create a Connect Launch Configuration.
This is the first icon to the left.
4- In the main tab specify the Project and System the launch configuration applies to
5- Specify a name for your launch configuration (this will be the name of the .launch file)
6- Switch to the Common tab and check Shared file. Then browse for {ProjectDir}\Project_Settings\Debugger
in the edit box.
7- Click Apply. Your Connect Launch Configuration is created.
Now Click debug to connect to your board. This should not erase the flash.
Once you are there you can open a Debugger shell view (Select Window > Show View > Other > Debug > Debugger Shell).
You can use the command SAVE to save content of memory as Motorola S record file.
Please refer to {Install}\MCU\Help|PDF\Targeting Microcontrollers.pdf manual, chapter Scripting, section Microcontrontrollers-Specific HIWARE Commands for more info about the syntax of this command.
Alternatively just type help save in the debugger shell view.
If you prefer using a GUI to dump memory content you can define a Target Task of type Import/Export/Fill memory to retrieve the content of memory.
There are some information on target task in the Targeting Microcontrollers.pdf manual as well.
Search for Creating Target Task to Import Memory.
I hope this helps
CrasyCat
Hello
Did you consider using a connect launch configuration and dumping memory content to a file.
In order to define a Connect launch configuration follow these steps:
1- In CodeWarrior MCU V10 open the Debug Configuration dialog (Select Run > Debug Configuration).
2- Click on CodeWarrior Connect on the left hand side of the dialog.
3- Click on the New Launch Configuration icon to create a Connect Launch Configuration.
This is the first icon to the left.
4- In the main tab specify the Project and System the launch configuration applies to
5- Specify a name for your launch configuration (this will be the name of the .launch file)
6- Switch to the Common tab and check Shared file. Then browse for {ProjectDir}\Project_Settings\Debugger
in the edit box.
7- Click Apply. Your Connect Launch Configuration is created.
Now Click debug to connect to your board. This should not erase the flash.
Once you are there you can open a Debugger shell view (Select Window > Show View > Other > Debug > Debugger Shell).
You can use the command SAVE to save content of memory as Motorola S record file.
Please refer to {Install}\MCU\Help|PDF\Targeting Microcontrollers.pdf manual, chapter Scripting, section Microcontrontrollers-Specific HIWARE Commands for more info about the syntax of this command.
Alternatively just type help save in the debugger shell view.
If you prefer using a GUI to dump memory content you can define a Target Task of type Import/Export/Fill memory to retrieve the content of memory.
There are some information on target task in the Targeting Microcontrollers.pdf manual as well.
Search for Creating Target Task to Import Memory.
I hope this helps
CrasyCat
CrasyCat,
Thank you for your reply on this matter. Between your response and my research I finally figured out how to verify the code. I was looking for a "verify" button but I quickly figured out it was a little more involved.
Thanks Again,
Renee