This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Startup.a51

Is it always important to include the file "startup.a51"?

Should anything else be included for it to work properly?

Thanks

Parents
  • Hi Mohammad,

    I always include startup.a51 in my project. The reasons are:
    1. I am using winbond 78E516, and it has an AUX-RAM on the chip. I have to modify the startup.a51 to init this memory area.
    2. I want to have a full control of my source code. Even if I don't have to change the startup.a51, I'd prefer to have it included in my project, then I can step through the code before it jump to main. It's useful especially when you have a hardware problem (I mean bad mem W/R).

    As to the detail explaination, I think you can read the source code of startup.a51, It's kind of self-explained to me.

    Have a nice day!
    Frank

Reply
  • Hi Mohammad,

    I always include startup.a51 in my project. The reasons are:
    1. I am using winbond 78E516, and it has an AUX-RAM on the chip. I have to modify the startup.a51 to init this memory area.
    2. I want to have a full control of my source code. Even if I don't have to change the startup.a51, I'd prefer to have it included in my project, then I can step through the code before it jump to main. It's useful especially when you have a hardware problem (I mean bad mem W/R).

    As to the detail explaination, I think you can read the source code of startup.a51, It's kind of self-explained to me.

    Have a nice day!
    Frank

Children