Quote:
Code isnt working as expected
Well ... that's normal. Writing code that compiles - or in this case assembles - correctly, does not mean your code is right!
Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling / assembling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.
So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.
Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it.
Once you have an idea what might be going wrong, start debugging to find out why.
If you have debug facilities (JTAG / whatever) then use it: Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
If you don't, then fall back on older methods: add logging code to show you where it got to and what it was looking at.
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!