PM Asembler and Melab U2 Programmer Problems with PIC16F1939


Closed Thread
Results 1 to 13 of 13

Hybrid View

  1. #1
    Join Date
    Jan 2009
    Location
    Miami, Florida USA
    Posts
    699

    Default PM Asembler and Melab U2 Programmer Problems with PIC16F1939

    Hi,

    Here is another question regarding these PIC16F193x chips. First of all, let me say that this chip is supported with the new PBP 2.60 version. But, I couldn't use the PM asembler that comes with PBP. I got the following error and was forced to use MPASM.

    Name:  Pic01.JPG
Views: 1001
Size:  15.4 KB

    This is not really an issue since using MPASM is a workaround and should be fine. But, isn't PM supposed to work with all the 16F series chips? It was my understanding that MPASM was only required for the 18F series.

    Now, it comes the real problem . When I try to program my 16F1939 using my Melab U2 Programmer, the software can not find the chip. So, I went ahead and upgraded the firmware hoping to get support for this new chip.

    Name:  Pic02.JPG
Views: 1202
Size:  66.8 KB

    But, still the programmer software doesn't support this chip. Is there something that I'm missing here? Or, am I getting forced to buy the PickIt3 programmer ?

    Thank you for your help,

    Robert
    "No one is completely worthless. They can always serve as a bad example."

    Anonymous

  2. #2
    Join Date
    Jan 2009
    Posts
    78


    Did you find this post helpful? Yes | No

    Default

    I have the pic16F1939 on mine (ver 4.32)

    Name:  u2 ver 4.32.gif
Views: 830
Size:  39.1 KB

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


    Did you find this post helpful? Yes | No

    Default

    There is NO good reason to use PM as far as I know. Just stick to MPASM. You have much more great "hidden" features in...
    Steve

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

  4. #4
    Join Date
    Jan 2009
    Posts
    78


    Did you find this post helpful? Yes | No

    Default

    welcome back !

  5. #5
    Join Date
    Jan 2009
    Location
    Miami, Florida USA
    Posts
    699


    Did you find this post helpful? Yes | No

    Default

    Bogdan,

    Tonight I will check to see what software version I have. I bought my U2 programmer about two years ago, so it is probably an old version. I need to research this issue a little bit more.

    Mister_e,

    It is very nice to see you back . I have a program >8000 words that I developed using PM. This program uses interrupts on a PIC16F727 to read values for a built-in capacitance touch sensor. However, if I use MPASM the sensors don't work properly. I suspect it has to do with different interrupt intervals if I use MPASM, but I haven't tested this yet. This is the reason why I use PM for my touch sensor projects.

    Robert
    "No one is completely worthless. They can always serve as a bad example."

    Anonymous

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


    Did you find this post helpful? Yes | No

    Default

    Or it's working as design with MPASM, but have problem with PM, but... ya never know.

    Do yourself a big favor, isolate the problem, keep the ISR and a simple short and sweet main loop, see if the problem's still there.

    Usual Convention: Keep the ISR as short as possible.


    Get rid of PBP interrupt and use ASM one, or DT.

    Maybe not a bad idea to make sure you're using the latest MPASM version.
    Steve

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

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