Output hex file and Microchip direct


Closed Thread
Results 1 to 10 of 10

Hybrid View

  1. #1
    Join Date
    Jul 2005
    Posts
    78


    Did you find this post helpful? Yes | No

    Default

    MPLAB can be your friend here!

    First, set Configure | Set Device to the PIC you use.

    Next, load your hex file into it via File | Import.

    Now, you get the hex checksum top left corner. To insure the "fuse bits" are correct, drill down Configure | Configuration Bits and have a look at them.

    I've used Digi-Keys programming service a few times, they also require the config bits to be sent, I screen-shot them right from MPLAB.

  2. #2
    Join Date
    Jul 2003
    Location
    Lancashire
    Posts
    50


    Did you find this post helpful? Yes | No

    Default Errors!

    Hi All


    OK I imported the hex file into MPLAB and it generated the check sum fine. Sent the hex file plus the checksum to Microchip but it failed to pass. Heres the relevent part of the message from microchip:

    The Programming Team advises the Checksum value submitted: "de73" does not match the actual Checksum value of the program.
    The file submitted is in non-MPLAB standard format. Headers within the file are uniquely different than those produced by MPLAB and the memory map is incomplete.

    Its generated using Microcode studio and PBP. I compile using the PBP compiler. Any clues whats wrong here?.

    Cheers Pete

  3. #3
    Join Date
    Jul 2005
    Posts
    78


    Did you find this post helpful? Yes | No

    Default

    Interesting. Try this:

    Change the MCS View | Compile and Program | Assembler Options tab to have it use MPASM as the assembler. That way, you have a Microchip product generating your hex code.

    I bet that will help some.

  4. #4
    Join Date
    Jul 2003
    Location
    Lancashire
    Posts
    50


    Did you find this post helpful? Yes | No

    Default Mpsm

    Hi

    Altered MCS to use MPSM and I get an error on my code which isnt there when I compile through MCS without MPSM. Seems to dislike this line:
    @ device protect_on, pwrt_off, bod_off, INTRC_OSC_NOCLKOUT
    particulary the error states protect_on to be illegal opcode. Device is 16F648A

    Cheers Pete

  5. #5
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    Do a search in the FAQ for a thread name "How to set Config fuse" or something like that.

    MPASM don't use the same Directive as PM.
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

Similar Threads

  1. Can anyone help at getting OWIn & OWOut to work @ 16MHz?
    By jessey in forum mel PIC BASIC Pro
    Replies: 9
    Last Post: - 24th January 2006, 11:08
  2. Couldnt read hex file extension
    By sooyewguan in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 18th January 2006, 15:37
  3. No hex file...?
    By mypylon in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 28th November 2005, 14:02

Members who have read this thread : 0

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