The jump to my code from the main jumps to ram where there is no code. I can see in the O.lst the addresses are in first page ram. I believe I need to set it for absolute location. Works in debug mode but standalone when unplug and reset pressed
Solved! Go to Solution.
I posted below just the keep my thought process docoed.
I added a SECTION command at the start of my code in the second file. This worked. The concept of modularity using commands is something I have not done before. I am just used to one straight asm file code. I don't need the modularity as of yet but the learning curve is new.
Thank you for the help. If you have any remarks to further me along this path it would greatly appreciated.
I truck on now to the finish...
**********************************************
I understand what you are saying. Overnight I thought more about a better question. I have a main file and then my test.asm file. I have XDEF the START routine so main does call the START in the test.asm. The problem is the address resolution puts the test code at address $B7 in ram but the code really doesnt sit there. The reference to absolute was to hook the test code directly after the main code so It would create a single code file in rom. I hope this helps. M test.asm runs great in debugger. I am very pleased with the progress I have made with this tool and the DEMO9s08AC60 board. The migration i went through from the MC6805 platform to this one progressed in less than 2 hours of actual work. The analysis of the platform switch took 1 week. To say it again I am very, very pleased. Here is my project: http://74.63.154.225/~pauldenv/phyzx.htm and scroll down to Finish Line.
Thanks for the help.
Hi Paul,
Just in case this will help you.
Just found an example containing 2 targets:
- absolute project using 1 asm file.
the .abs file is generated directly by assembler tool
- relocatable project using 2 asm files.
Have a great day,
Pascal
Freescale Technical Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Paul,
Most of the time when the application is loaded with the debugger, the application will run at main function.
To run in standalone mode you should have the reset vector initialized to your entry program.
By default this is managed when the application is created with relocatable assembly project.
In this case your application could contain several assembly files which are linked in a abs file with the linker tool.
If you're using Absolute assembly, this means your project contains 1 file only.
This file should define the memory location, stack address, ... etc ...
Have a great day,
Pascal
Freescale Technical Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
I posted below just the keep my thought process docoed.
I added a SECTION command at the start of my code in the second file. This worked. The concept of modularity using commands is something I have not done before. I am just used to one straight asm file code. I don't need the modularity as of yet but the learning curve is new.
Thank you for the help. If you have any remarks to further me along this path it would greatly appreciated.
I truck on now to the finish...
**********************************************
I understand what you are saying. Overnight I thought more about a better question. I have a main file and then my test.asm file. I have XDEF the START routine so main does call the START in the test.asm. The problem is the address resolution puts the test code at address $B7 in ram but the code really doesnt sit there. The reference to absolute was to hook the test code directly after the main code so It would create a single code file in rom. I hope this helps. M test.asm runs great in debugger. I am very pleased with the progress I have made with this tool and the DEMO9s08AC60 board. The migration i went through from the MC6805 platform to this one progressed in less than 2 hours of actual work. The analysis of the platform switch took 1 week. To say it again I am very, very pleased. Here is my project: http://74.63.154.225/~pauldenv/phyzx.htm and scroll down to Finish Line.
Thanks for the help.