pic片内eeprom读写的注意事项及代码（Pic EEPROM read and write notes and code）.docVIP

下载本文档

6
0
约1.09万字
约 21页
2017-09-05 发布于河南
举报
版权申诉

pic片内eeprom读写的注意事项及代码（Pic EEPROM read and write notes and code）.doc

1、本文档共21页，可阅读全部内容。
2、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。
3、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
5、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
6、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
7、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
8、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

pic片内eeprom读写的注意事项及代码（Pic EEPROM read and write notes and code）

pic片内eeprom读写的注意事项及代码（Pic EEPROM read and write notes and code） There is a problem with EEPROM in writing The following subroutine is written in EEPROM. There is no problem with writing only one byte. It crashes when you write two bytes continuously. (with the programmer, you can see that the first byte has been rewritten.) You can insert a delay between two bytes of writing. WRITE_EEPROM subroutine in the WR bit detection, it should not delay, but also can do. WRITE_EEPROM BSFSTATUS, RP1 BSFSTATUS, RP0 BTFSCEECON1, WR GOTO$-1 BCFSTATUS, RP0 MOVFADDR, W; address in addr, data in value MOVWFEEADR MOVFVALUE, W MOVWFEEDATA BSFSTATUS, RP0 BCFEECON1, EEPGD BSFEECON1, WREN BCFINTCON, GIE BTFSCINTCON, GIE GOTO$-2 MOVLW0X55 MOVWFEECON2 MOVLW0XAA MOVWFEECON2 BSFEECON1, WR BSFINTCON, GIE BCFEECON1, WREN BTFSCEECON1, WR GOTO$-1 BCFSTATUS, RP0 BCFSTATUS, RP1 RETURN After joining the delay, the BTFSCEECON1, WR GOTO$-1 These two before the semicolon removed, the same appears to write EEPORM will crash. (the programmer can see that only the first byte has been rewritten). Please point out DX, this problem has been stranded for a day, but also did not find the reason. Hurry up! Authors: eyuge2, 2005-2-4, 13:07:00 Reply 1 completely wrong. Six hundred and twenty-nine thousand two hundred and seventy-three A lot of mistakes, data manuals have very good routines, how do you not see? WRITE_EEPROM BSFSTATUS, RP1 BSFSTATUS, RP0 BTFSCEECON1, WR GOTO$-1 BCFSTATUS, RP0 MOVFADDR, W; address in addr, data in value MOVWFEEADR MOVFVALUE, W MOVWFEEDATA BSFSTATUS, RP0 BCFEECON1, EEPGD BSFEECON1, WREN BCFINTCON, GIE BTFSCINTCON, GIE; this is absolutely unnecessary GOTO$-2 MOVLW0X55 MOVWFEECON2 MOVLW0XAA MOVWFEECON2 BSFEECON1, WR BSFINTCON, GIE BCFEECON1, WREN; you should wait for a break after the BSF EECON1 WR, and if you dont open the interrupt, check the corresponding interrupt flag. The second byte should be written after the interrupt. Like your program, if there is no interrupt service progr