读取设备内存

随着时间的推移，我可能建议使用类似Git的东西来避免这种不幸的情况，再次使用HTPS5.//E.WiKiTo.Org/WiKi/Git。



      以下为原文

    As time progresses might I suggest the use of something like GIT to avoid this unfortunate circumstance again https://en.wikipedia.org/wiki/Git

您可能或可能没有读取一个工作设备。如果工作设备没有代码保护，并且您正确地读取设备，您应该有预期的原始板的副本应该按预期操作。



      以下为原文

    You may or may not of managed to read a working device.
If the working device was not code protected and you correctly read the device you should have every expectation a duplicate of the original board should operate as expected.

谢谢您。我认为负责这个项目的人不这么认为，但我会调查一下。我会通知那些最终被赋予这些设备编程任务的人。



      以下为原文

    Thank you. I don't think the person who was in charge of this project thought of this, but I will look into it.  I will inform whomever is eventually given the task of programming these devices. 

“你可能或可能没有读过一个工作装置。”我们已经明确地阅读了一个工作装置，并且用任何被读取的程序编程了一个新的设备。新产品虽然不完全相同，但老产品。但这不是问题。“……你正确地阅读了这个装置……”这是个问题。我们怎样才能确保我们正确地“阅读”工作装置。我简单地选择了菜单命令“读取设备内存到文件……”并选择了我的程序员工具（ICD 3）并创建了一个文件。如果你同意我遵循正确的程序，我会假设：“你应该有一个预期的副本，原来的董事会应该按照预期操作。”我知道这是愚蠢的，但我们完全被这种情况感到惊讶。谢谢你的帮助。



      以下为原文

    "You may or may not of managed to read a working device."
We have definitely read a working device and programmed a new device with whatever was read. The new product  works, though not exactly the same and the old product. But that is not in question.
 
"...you correctly read the device..."  
This is the question. How can we be sure that we correctly "read" the working device. I simply selected the menu command "Read Device Memory to File..." and selected my programmer tool (ICD 3) and created a file. If you agree that I followed the correct procedure, I will assume:
"..you should have every expectation a duplicate of the original board should operate as expected."
 
I know it's silly, but we were taken completely by surprise by this situation.
Thank you for your help. 
 
 

除非在ICD 3中选择了某个选项，这是我的经验，该设备是正确读取的。您可以尝试IPE来验证您所读取的内容。可能在板上有一些设备/跳线改变了它的反应方式。ESS。你确定板是原板的100%倍吗？你有一个以上的原始板，你可以编程与代码读取，尝试它？



      以下为原文

    Unless some option has been selected in the ICD 3 it has been my experience the device is correctly read.
You might try IPE to verify what you read.
Maybe there is/are some devices/jumpers on the board that change the way it reacts.
Without a schematic and photo of the board it will be difficult to guess.
Are you quite sure the board is a 100% duplicate of the original board ?
Do you have more than one of the original boards you could program with the code that was read to try it ?

这个小项目被发现是有点灾难性的。由于所有的文件被发现是完全不可靠的，包括产品的材料清单。因此，我认为我们可以合理地断定新批次的产品装配不当。换句话说，没有。我们还不确定董事会已经复制了100%次。显然它们是相同的，但这并不意味着它们是。目前，我们只是试图消除错误的阅读旧设备的可能性。原来的板被认为是“黄金”，但我会推动牺牲。



      以下为原文

    This little project has been found to be a bit of a disaster. Due to the fact that all the documentation has been found to be completely unreliable, including the bill of materials for the product. Because of this, I think we can reasonably conclude that the new batch of product was assembled improperly. In other words, no.. we are not 100% sure the board has been duplicated properly. Visibly they are the same, but that doesn't mean they are. At the moment, we are simply trying to eliminate the possibility of incorrectly reading the old device. 
 
The original boards are considered "golden" but I will push to sacrifice one.
 
BTW, The IPE verifies what we've read with no problem.
 

也许你会尝试克隆一个不是你的设备？因此没有示意图和板照片。



      以下为原文

    Perchance might you be trying to clone a device that is not yours ?
Hence no schematic and board photo.

看看你读到的文件。如果它是全零（除了校验和地址），则该设备受到保护，您将无法读取它。



      以下为原文

    Look at the file you have read. If it's all zeroes (except checksums and addresses), the device is protected and you won't be able to read it.

我的理解是，恢复的HEX文件是正确的，但它将不包含对Y-Y-CONFIG寄存器的设置，因此您使用默认设置，通常是所有1个。您必须查找设备的配置寄存器，并确定什么设置应该是合适的。没有太多，所以如果你不能决定，尝试用不同的选项编程，直到它的行为正确。



      以下为原文

    It is my understanding that the recovered hex file be correct but it will not contain the settings for __CONFIG register(s) so you are using the default settings, typically all 1's.
You will have to look up the CONFIG registers for your device and decide what settings should be appropriate.  There are not too many so if you can't decide, try programming with different options selected until it behaves correctly.
 
Ann-Marie.

配置文件应该在HEX文件中。这听起来像是OP需要让至少知道PIC编程的人来检查整个过程。



      以下为原文

   
The config settings SHOULD be in the hex file.
It sounds like the OP needs to get someone who knows at least something about PIC programming to check the whole process.

不正确。阅读PIC设备可以读取所有的东西。编辑和Qub用一秒钟的时间来击败我。



      以下为原文

   
Not correct.  Reading a PIC device can read everything.
 
Qub beats me to it by a second.
 
FYI, The config bits can be read even when the PIC device is code protected.
 

我会提供一个示意图，但我不知道如何把它附加在这里，而且它是不正确的，不反映什么是真正的董事会。它是电气不正确的，它缺少组件清楚地在板上。请告诉我如何附加图像，我会很乐意提供它们。



      以下为原文

    I'd provide a schematic but I don't know how to attach it here, and besides it is incorrect and does not reflect what is actually on the board. It is electrically incorrect and it is missing components that are clearly on the board. Please tell me how to attach images and I will be happy to provide them.
 

你必须使用“完全编辑器”，而不是快速回复框。点击编辑框上的“打开完整版”就可以到达那里。然后右边有一个“附加图像”按钮。附件限制在200 KB。



      以下为原文

    You have to use the "Full editor", not the quick reply box.
You get there by clicking "Open Full Version" just above the edit box.
there is then an "Attach image" button over to the right.
Attachments are limited to 200 kB.
 

谢谢。附上你会发现一个图像的顶部侧的董事会的问题。



      以下为原文

    Thanks. Attached you'll find an image of the top side of the board in question.
   Attached Image(s)

这里是示意图。



      以下为原文

    And here's the schematic.
   Attached Image(s)

谢谢。附上你会发现一个图像的顶部侧的董事会的问题。



      以下为原文

    Thanks. Attached you'll find an image of the top side of the board in question.

你到底在哪里？



      以下为原文

    where in the world are you ?

我在森尼维耳。



      以下为原文

    I'm in Sunnyvale CA. 

远离苏塞克斯英国：：



      以下为原文

    bit far from sussex uk :)