Explain "Define Loader_Used 1"


Closed Thread
Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2009
    Location
    Las Vegas - Nevada
    Posts
    3

    Default Explain "Define Loader_Used 1"

    Would someone please explain "Define Loader_Used 1"

    What does it do?

    Thank you

  2. #2
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default

    It just makes sure there's no code in the first 4 program memory locations.

    When using a bootloader, those locations are used to jump to the boodloader code, before running the user code.
    DT

  3. #3
    Join Date
    Jan 2009
    Posts
    24


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Darrel Taylor View Post
    It just makes sure there's no code in the first 4 program memory locations.

    When using a bootloader, those locations are used to jump to the boodloader code, before running the user code.
    So, in effect, different bootloaders could be used with PBP "define LOADER_USED 1" command ?

    I note that the MCS 877 bootloader uses all 4 locations. The Tiny 877 bootloader only uses the first 3 and the ds30Loader 887 uses only the first 3 also.

    Now, I have used "define LOADER_USED 1" in a simple test program to flash a LED but the program doesn't run - though it downloads OK via the ds30 Loader PC interface (loader).

    This doesn't make sense, as the bootloader should know where to jump back to in order for the code to start running assuming that you haven't overwritten the bootloader code while downloading your code to the micro.

    Does my fist question hold true ? or have I missed something else completely?

    Regards, Chris

Members who have read this thread : 1

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts