• AVR Freaks

Hot!MCC Bootloader configuration issue

Author
ssh19
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2019/12/21 09:15:33
  • Location: 0
  • Status: offline
2020/05/03 15:29:02 (permalink)
0

MCC Bootloader configuration issue

I have trouble to compile MCC bootloader for PIC18, getting an error, when building the main application:
(944) data conflict at address 300000h between dist/default/production/bootloader_test.X.production.hex and /bload.X/dist/No_Configuration/production/bload.X.production.hex
I did disable the option of default config in the bootloader project (attached s1.jpg)
but after building I still have this:
::: warning: (1311) missing configuration setting for config word 0x300000; using default
::: warning: (1311) missing configuration setting for config word 0x300003; using the default
I guess these defaults causing later data conflict with the main project.
 
 

Attached Image(s)

#1

4 Replies Related Threads

    ssh19
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2019/12/21 09:15:33
    • Location: 0
    • Status: offline
    Re: MCC Bootloader configuration issue 2020/05/04 06:42:54 (permalink)
    0
    Problem resolved Smile: Smile
    #2
    mlp
    boots too small
    • Total Posts : 913
    • Reward points : 0
    • Joined: 2012/09/10 15:12:07
    • Location: previously Microchip XC8 team
    • Status: offline
    Re: MCC Bootloader configuration issue 2020/05/04 09:09:21 (permalink)
    +1 (1)
    ssh19
    Problem resolved

    So, document here how it was resolved, so that when someone else has a similar problem they can benefit from your experience.

    Mark (this opinion available for hire)
    #3
    ssh19
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2019/12/21 09:15:33
    • Location: 0
    • Status: offline
    Re: MCC Bootloader configuration issue 2020/05/04 09:25:30 (permalink)
    0
    It was a mistake on my side. I added #ifdef OMIT_CONFIGURATIOS to the MCC.C file, as it was recommended in the document.
    But it must be in the device_config.c, where the actual configuration is.
    #4
    cTucker
    New Member
    • Total Posts : 14
    • Reward points : 0
    • Joined: 2014/04/14 13:51:49
    • Location: 0
    • Status: offline
    Re: MCC Bootloader configuration issue 2020/05/22 15:03:31 (permalink)
    0
    This error is indicating that there is a conflict or overlap when attempting to 'merge' the hex files from the two projects together. Hex mat will unify them and is running into conflict at that memory location. You should be able to load the raw .hex files and identify the overlap. 
     
    The Warning is then saying that there was no definition for the Configuration Word; so the default was being used.
     
    That option in the Linker shouldn't be required. 
    The User Guide has some details on the process required. https://www.microchip.com/promo/8-bit-bootloader
     
    Inside MCC Generated Files --> device_config.c of the project will be the generated #pragma's which configure the Configuration Words.
     
    To Unify the two projects, these need to match (or not conflict) between the Bootloader project and the Offset Application Project. It's typically best to have the Configuration Words defined in the Bootloader project; and let it define how the 'system' will operate. 
    #5
    Jump to:
    © 2020 APG vNext Commercial Version 4.5