PIC16F1827 EEPROM位置是什么

它在0xF000，与所有其他扩展的中程芯片一样。您可以看到链接器文件：C:Microchip  MPLABXV3.26MPASMXLKR16F1827 G.LKROR Inc：程序文件（x86） Microchip  MPLABXV3.26MPASMXMadioCODE16F1827 TEMP.ASMor，您可以在编程规范中找到它。阳离子。



      以下为原文

    It is at 0xF000, the same as all other extended midrange chips.
You can see this the linker file:
C:Program Files (x86)MicrochipMPLABXv3.26mpasmxLKR16f1827_g.lkr
CODEPAGE NAME=eedata START=0xF000 END=0xF0FF PROTECTED
 
or in C:Program Files (x86)MicrochipMPLABXv3.26mpasmxtemplatesCode16F1827TEMP.ASM
;------------------------------------------------------------------------------
 
; EEPROM INITIALIZATION
;
; The 16F1827 has 256 bytes of non-volatile EEPROM, starting at address 0xF000
;
;------------------------------------------------------------------------------
 
DATAEE ORG 0xF000
DE "MCHP" ; Place 'M' 'C' 'H' 'P' at address 0,1,2,3
 
or you can find it in the programming specification.
 

编辑：QHB首先到达。这不是真正的EEPROM位置，因为EEPROM不在程序存储器地址空间中。微芯片已经定义了一个约定，即一个特定的未使用的程序地址空间块将被它们的编程工具映射到EEPROM。它只是一个软件惯例，如果他们想明天就可以改变它（虽然这会破坏每个人的旧项目）。找到正确的基地址（ORG）最简单的方法是查看MPASM模板。如果它不存在，选择具有相同大小的EEPROM的最近的部件号。在你的例子中，找到你的MPLABX程序文件夹，然后查看：MPASMX/PATS/Obj/16F1827 TMPO.ASM。



      以下为原文

    Edit: QHB got there first.
That's *NOT* the real EEPROM location, as the EEPROM is not in the program memory address space.  Microchip have defined (by fiat) a convention that a particular unused block of program address space will be mapped to the EEPROM by their programming tools.  Its only a software convention and if they wanted to they could change it tomorrow (although that would break everybody's old project).
 
The mapping remains the same within each PIC family.   The easiest way to find the correct base address (ORG) is to look in the MPASM template for your PIC.  If it doesn't exist, pick the nearest part number with the same size EEPROM. 
 
In your case, find your MPLABX program folder, then look in: mpasmx/templates/Object/16F1827TMPO.ASM

我想我把伊恩掐了几秒钟；



      以下为原文

    I think I pipped Ian by a few seconds ;)
 

…或者在MPASM用户指南中查找De指令，其中每个家庭都有EEPROM起始地址表。&编辑；GT；我将再次重复这里，Microchip应该包括EEPROM起始地址的符号，每个EEPROM起始地址在具有EEPROM的设备的每个特定的包含文件中。



      以下为原文

    ... or look up the DE directive in the MPASM User's Guide where there's a EEPROM Start Address table for each family.
 
I'm going to repeat here again, Microchip should include a symbol for the EEPROM start address in each device specific include file for devices that have an EEPROM.
 
 

同意。这是我检查的第一份文件，很惊讶它不在那里。



      以下为原文

   
Agreed.
That was the first file I checked, and was surprised it's not in there.
 

在.Inc文件中会有这样的事情：



      以下为原文

    Something like this in the .INC file will do:

;----- EEPROM Equates -------
_EEPROM_ADDR     EQU  H'F000'
_EEPROM_SIZE     EQU  H'0100'

每个人都回答得很好。这就是我想知道的。顺便说一下，我使用MPLAB IDV856。我需要转换到MPLABX吗？在MPLAB 8.56中，不包含芯片临时文件。



      以下为原文

    Everyone Perfectly answered. That's what I want to know.
 
By the way I'm using MPLAB IDE v8.56. Do I need to shift to MPLABX?In MPLAB 8.56 those never chips temp files isn't included.

MPLAB892当然有PIC16F1827的文件，但是有许多新芯片不支持。没有真正的理由不从V856升级到8.92，这是最终的MPLAB8版本。



      以下为原文

   
MPLAB8.92 certainly does have the files for the PIC16F1827, but there are many newer chips it won't support.
There's really no good reason not to upgrade from v8.56 to 8.92, which was the final MPLAB8 version.
 

MPLAB IDE V856是什么？似乎有相当多的用户仍在使用这个版本。根据档案，有17个新的MPLAB8版本，因为V.56。



      以下为原文

    What's with MPLAB IDE v8.56? There seems to be quite a few users still using that version. According to the archive, there are 17 newer MPLAB8 versions since v8.56.

      以下为原文

   

VR5X时代的IrcMPLAB存在严重的稳定性问题。有些版本比其他版本更稳定，所以一旦找到了一个在硬件上稳定的版本，就有强烈的升级动机，特别是因为它经常损坏工作区文件，所以即使您将程序回滚到以前的版本，也可能还有很多工作要做。为您的活动项目重新创建开发环境。



      以下为原文

    IIRC MPLAB in the v8.5x era had serious stability problems.  Some versions were more stable than others so once one found one that was stable on your hardware, there was a strong disincentive to upgrade, especially since it frequently corrupted workspace files, so even if you rolled back the program to a previous version, there could be a lot of work left to do to recreate the development environment for your active projects.

我发现桌面文件（MCW）倾向于不断增长，有时当它变得太大时会导致问题。项目在MCP文件中，这样您就可以安全地删除MCW文件。在最坏的情况下，你会丢失编辑器中打开的文件。



      以下为原文

    I've found the desktop file (MCW) tends to keep growing, and sometimes causes issue when it gets too big.
The project is in the MCP file, so you can safely delete the MCW file. At worst you lose which files were open in the editor.