PIC16F1613不支持MPLAB模拟器的秒表功能吗？

MPLAB 8或X，只是为了知道？



      以下为原文

    MPLAB 8 or X, just to know?

必须是MPLABX，PIC16F1613不支持MPLAB V.92



      以下为原文

    Must be MPLABX, the PIC16F1613 is not supported by MPLAB v8.92

我有这样的感觉，但不确定-一些增强的模型是由老MPLAB支持的



      以下为原文

    I had that feeling but was not sure - some Enhanced models are supported by old MPLAB

是的，它是MPLAB X。我没有看到任何特别说明秒表不支持在PIC16F设备的模拟器中。我知道PICTIT3不支持PIC16F设备的秒表。



      以下为原文

    Yes it is MPLAB X. I don't see anything that specifically states that the stopwatch is not supported in the simulator for the PIC16F devices. I know the PICKIT3 does not support the stop watch for PIC16F devices.

此代码与MPLAB V3.61中的模拟器秒表一起工作，您需要描述模拟器秒表不工作所看到的内容。



      以下为原文

    This code works with the simulator stopwatch in MPLAB v3.61/*
 * File:   main.c
 * Target: PIC16F1613
 *
 * Created on July 6, 2017, 10:07 PM
 */
#pragma config FOSC = INTOSC     /* Oscillator Selection Bits (INTOSC oscillator: I/O function on CLKIN pin) */
#pragma config PWRTE = OFF       /* Power-up Timer Enable (PWRT disabled) */
#pragma config MCLRE = ON        /* MCLR Pin Function Select (MCLR/VPP pin function is MCLR) */
#pragma config CP = OFF          /* Flash Program Memory Code Protection (Program memory code protection is disabled) */
#pragma config BOREN = OFF       /* Brown-out Reset Enable (Brown-out Reset disabled) */
#pragma config CLKOUTEN = OFF    /* Clock Out Enable (CLKOUT function is disabled. I/O or oscillator function on the CLKOUT pin) */
#pragma config WRT = OFF         /* Flash Memory Self-Write Protection (Write protection off) */
#pragma config ZCD = OFF         /* Zero Cross Detect Disable Bit (ZCD disable.  ZCD can be enabled by setting the ZCDSEN bit of ZCDCON) */
#pragma config PLLEN = OFF       /* PLL Enable Bit (4x PLL is enabled when software sets the SPLLEN bit) */
#pragma config STVREN = ON       /* Stack Overflow/Underflow Reset Enable (Stack Overflow or Underflow will cause a Reset) */
#pragma config BORV = LO         /* Brown-out Reset Voltage Selection (Brown-out Reset Voltage (Vbor), low trip point selected.) */
#pragma config LPBOR = OFF       /* Low-Power Brown Out Reset (Low-Power BOR is disabled) */
#pragma config LVP = OFF         /* Low-Voltage Programming Enable (High-voltage on MCLR/VPP must be used for programming) */
#pragma config WDTCPS = WDTCPS1F /* WDT Period Select (Software Control (WDTPS)) */
#pragma config WDTE = OFF        /* Watchdog Timer Enable (WDT disabled) */
#pragma config WDTCWS = WDTCWSSW /* WDT Window Select (Software WDT window size control (WDTWS bits)) */
#pragma config WDTCCS = SWC      /* WDT Input Clock Selector (Software control, controlled by WDTCS bits) */
/*
 *
 */
#include
/*
 *
 */
void PIC_Init( void )
{
    INTCON = 0;
    PIE1 = 0;
    PIE2 = 0;
    PIE3 = 0;
    PIE4 = 0;
    
    OSCCON = 0x78;  /* select 16MHz HFINTOSC no PLL */
    TRISA  = 0xFF;  /* all ports bits as inputs */
    TRISC  = 0xFF;
    ANSELA = 0;     /* all ports bits as digital */
    ANSELC = 0;
    OPTION_REG = 0xFF;
    OPTION_REGbits.nWPUEN = 0; /* weak pull-up enabled */
    OPTION_REGbits.T0CS   = 0; /* TIMER0 clock source is FOSC/4 */
}
/*
 *
 */
void main( void )
{
    PIC_Init();
    
    for(;;)
    {
        NOP();
    }
}
You will need to describe what you see as the simulator stopwatch not working.

它在我的系统上工作得非常好。我使用MPLAB X V3.62和编译器XC8 V 1.42。我在编译过程中附加了ZIP文件和项目，同时在ZIP中使用秒表进行仿真。
SnAPTestTest16.Zip（168.42 KB）-下载41次



      以下为原文

    It's working perfectly fine on my system.
I am using MPLAb X v3.62 and Compiler XC8 v 1.42.
I have attached zip file of the project  and Snap of Project while simulating with stopwatch working in zip .
 
   Attachment(s)

test_16.X.zip (90.03 KB) - downloaded 34 times
snap_test_16.zip (168.42 KB) - downloaded 41 times

我能让它工作。我有两个断点。当我把模拟器放到调试模式中时，我可以在两个断点之间进行步进，秒表显示两个断点之间的执行时间。这个数字与我的估计非常接近，而且是一致的。我不能确定为什么我不能明确地指出一个断点是起始断点，一个是停止断点。文件就是这样说明它应该工作的。无论如何，多亏了他们的投入。马克



      以下为原文

    I was able to get it to work. I have two breakpoints. When I put the simulator into debug mode, I can step between the two breakpoints and the stopwatch displays the execution time between the two breakpoints. The number is very close to my estimate and it is consistent. I am not sure why I can't specifically state that one breakpoint is the starting breakpoint and one is the stopping breakpoint. That is how the documentation states it should work. In any case, thanks to all for their input.
 
Mark

我从来没有听说过这个特性，但我不是“X”的大用户，所以它可能是



      以下为原文

   


I never heard of this feature, but I am not a big user of "X", so possibly it can be

是的，这是模拟器，…缺乏。（见附件截图）。没有理由模拟器不能做到这一点，我们只是从来没有去做它。可能是因为你周围的简单工作已经发现了。（清除第一个断点时的秒表）。无论如何，我为这个特性写了一个增强请求。不知道我们多久能到达它，但至少现在是“系统”了。



      以下为原文

    Yes, this is a simulator,... deficiency.  (See attached screenshot).  There is no reason the simulator can't do this, we've just never gotten around to doing it.  Likely due to the simple work-around you already discovered.  (ie, clear the stopwatch when you hit the first breakpoint).
 
Anyway, I wrote an enhancement request for this feature.  Not sure how soon we'll get to it, but at least it's "in the system" now.
   Attached Image(s)

哦，天哪。已经有了这个特性的增强请求，写在2013中。粉红色：



      以下为原文

    Oh goodness.  There is ALREADY an enhancement request for this feature, written in 2013.  pink:

那么，这里的外卖是仿真器开发团队需要4年的时间来处理bug，然后文档化的特性才能得到实现。乔治，可怜的枪。我不应该在他情绪低落时揍他。（踢他更容易）



      以下为原文

   
So is the take away here that the Simulator development team needs 4 years dealing with bugs before documented features get a shot at being implemented?

George, sorry for the cheap shot.
I should not hit a man when he's down.
(Kick him it's easier)

不，容易和明显的工作使这个问题的优先级很低。



      以下为原文

   


No, the easy and obvious work-around keeps the priority of this issue pretty low.