This is, of course, assuming your hardware is correct. Object - to - hex converter gives the hex file for use by the device. To actually see your LED blink, you must program a large delay between turning on the LED, and turning it back off again - say something like 1/2 second or so.Īdd some delays, like long for-loops that do nothing, in your while-loop and you will see the LED blink. It provides for easy inclusion of the modules in other source files and C library. If you are checking with a scope, you could see the change in polarity of the pin, but it would be very fast. If you think about it, the LED won't be able to respond that quickly, nor would your eyes be able to see this kind of phenomenon. Now look at your while loop - You have the uC turning on a port pin, and then turning it off very quickly, over and over again. To answer the second question, remember that you uC can execute instructions very fast - about 1/12 of the clock frequency. Examine this startup module carefully, but for the most part, the default settings in it will get you up and going.After you recompile your software, you can be sure the main() function will be found. When you include the STARTUP.A51 file in your project, the linker now has instructions for jumping to the main() function. The very first thing that happens after reset is the uC fetches it's first instruction from address 0x0000.
To answer the first question, you must consider what happens at power on. Array data is created as C file and copied to Application Project. When it actually executes main(), what will it be doing? Converted hex file into Array type (outbootcode.c). How will the uC know where the main() program is located?Ģ. Several things must be considered when programming the uC you have chosen.ġ.
0 kommentar(er)
