什么是十六进制代码PIC16F1704

谷歌英特尔十六进制格式。



      以下为原文

    Google Intel HEX format.

它不是英特尔十六进制格式。它看起来像是ASCII十六进制闪存输出的内容，每行一个14位字，从地址0开始。但这是猜测。



      以下为原文

    It's not Intel HEX format. It looks like just the contents of flash output as ASCII hex, one 14bit word per line, starting at address 0. But that's a guess.

实际上，它看起来像是程序存储器的顺序转储。它不是任何微芯片编译器的输出。它是从哪里来的？



      以下为原文

    Indeed, it looks like a sequential dump of program memory.
It's not the output of any Microchip compiler. Where did it come from?
 

我明白你的意思。我在记事本+ +中重新打开它，我看到的是一个2字节的单列。不超过14位。



      以下为原文

    I see what you mean. I reopened it in notepad++ and I see is a single column of 2 bytes. Nothing above 14bits.  

我同意，这是什么样子（和DIS组装类似）。



      以下为原文

   
I agree, that's what that looks like (and dis-assembles like).

前几行是：



      以下为原文

    The first few lines are:
3186    movlp   6
2E02    goto    0x0602
3187    movlp   7
2FD4    goto    0x07D4
3010    movlw   0x10
003D    movlb   29
00A0    movwf   0xEA0

它看起来像是一个有效的代码，但我怀疑它是从地址0x000开始的。



      以下为原文

    It looks like valid code, but I doubt it's starting from address 0x0000 then.
 

MOVLP/GOTO可以是复位向量，但是在中断向量上的那些操作码我不太确定。



      以下为原文

    That MOVLP/GOTO could be the reset vector, but those opcodes at the interrupt vector I am not so sure.

嗨，伙计们，谢谢你们的帮助和支持！不，这个代码不是转储。在PIC16F1704中，我对转储HEX文件进行了攻击。最后，我只想知道PIC正在做什么……程序“PIC.TXT”可以通过程序（C++）通过BiBeBigeBead板闪现，但这是什么样的代码？我还从1704 & GT；PICTIT3和MPLAB X IDE得到了HEX文件，但是当我比较时，它是不同的。所以我的问题是，pic.txt是什么？我怎么能读/转换它？附上的代码和地址等。用于编码和编程PIC-C代码，非常感谢大家的推荐和帮助！再见，亚历克斯
PIC16F1704.HEX.TXT（22.59 KB）-下载55次



      以下为原文

    Hi guys,
 
Thanks for help and support!
No, this code is no dump/disasm. from the PIC16F1704, I attched the dump hex file.
 
In the end, I "just", want to know what the PIC is doing...
 
The programm "pic.txt" can be flashed via program (c++) at/via blackbeaglebone board, BUT which kind of code is this pic.txt?
I also got the hex file from 1704 -> PICKit3 and MPLAB X IDE, but when I compare, it's different.
So my question is, what's that pic.txt and how could I read/convert it?
 
Attached is the code and address, etc... which are used to code/program the PIC - C code.
 
Thanks a lot for recommendation and help!
 
Bye, Alex


   Attachment(s)

PIC_flashing_sample_c_code.txt (1.06 KB) - downloaded 56 times
PIC16F1704.hex.txt (22.59 KB) - downloaded 55 times

只是猜测，它看起来像PIC.txt中的操作码将被闪存到PIC16F1704的程序内存位置0x0600到0x0f7f。



      以下为原文

    Just a guess, it looks like the opcodes in pic.txt are to be flashed into program memory locations 0x0600 to 0x0F7F of the PIC16F1704.
 
Edit:
address  opcode  instruction
0600     3186    movlp 6
0601     2E02    goto  0x0602
0602     3187    movlp 7
0603     2FD4    goto  0x07D4
0604     3010    movlw 0x10
0605     003D    movlb 29
0606     00A0    movwf 0xEA0

附上的C代码（PICA FLASIGIN SAMPADYC.CODEX.TXT）看起来像一个Bootloader，文件（PIC16F1704.HEX.TXT）是一个由Bootloader加载的应用程序文件。？？？？



      以下为原文

    The attached c code (PIC_flashing_sample_c_code.txt) looks like a bootloader and the file (PIC16F1704.hex.txt) is an application file to be loaded by the bootloader????

HEX文件来自我所做的转储。PX.TXT加载了“C代码”，但仅用于更新，所以正常使用。我的想法是比较PX.TXT与HOXDUP，但我不知道PIC.txt是哪种格式。那么，我怎么能像1和0那样转换它呢？谢谢



      以下为原文

    The hex file is from the dump I have done. The pic.txt is loaded with the "c code", but only for updates, so normaly not used. My idea was to compare the pic.txt - available with the hexdump, but I don't know which format the pic.txt is. So how can I convert it like 1and0 has done it?
Thanks

它被称为“DIS汇编”。你可以通过使用数据表中的指令操作码列表，一次一个的“手工操作”。有几个“拆卸器”可用，一些更智能，更容易使用，然后其他。



      以下为原文

   
It is referred to as "dis-assembly". You can do it "by hand" one instruction at a time by using the instruction opcode list from the data sheet, very long and tedeous. There are several "disassembers" available, some smarter and easier to use then others.

感谢信息/提示，我使用GPDASM并得到了攻击结果。现在我只需要理解代码并将其与PIC.TXT进行比较，但是如何？有人能帮助我理解代码吗？我如何将PIC.TXT转换成ASM代码（不是手工），我已经尝试了GPDASM，但是，这不起作用。编译攻击者的代码是工作的，HEX文件与HEX转储相同。非常感谢！



      以下为原文

    Thanks for the info/hint, I used gpdasm and got the attched result.
Now I "only" need to understand the code and compare it with the pic.txt but how?
Can anybody help me in understanding the code?
 
Also how can I convert pic.txt to ASM code (not by hand) I've tried with gpdasm but,
this doesn't work.
 
To compile the attched code is working and hex file is the same as hex dump.
 
Thanks a lot!
   Attachment(s)

pic16f1704.asm (209.45 KB) - downloaded 33 times

我不会浪费时间去理解从某人的HEX文件中分解的汇编代码。从头开始编写源代码将花费更少的时间。



      以下为原文

    I would not waste time on trying to understand a disassembled assembly code from someone's hex file. It will take less time to write a source code from scratch.

嗨，1和0，当然，但你必须知道什么“老六角计划”做什么？有没有办法将PIC.TXT转换成“正常”的英特尔HEX文件/格式，像转储文件一样，这样我就可以比较PIC.txt和HEX转储文件吗？谢谢！



      以下为原文

    hi 1and0,
 
for sure, but then you have to know what the "old hex program" does?
 
Is there a way to "convert" pic.txt to "normal" intel hex file/format like the dump file,
so I can compare the pic.txt with the hex dump file?
 
Thanks a lot!

把它编程到你的PIC设备中，然后用PICTIT3从PIC上读取它，前提是PIC不是代码保护的。



      以下为原文

    Program it into your PIC device and then read it off the PIC with your PICKit3, provided the PIC is not code protected.

好主意！当然，“PIC.TXT”已经在PIC中了。为什么？因为在C代码/程序中有一个例程，它检查PICUPUPDATEY需要，如果值X在那里，它就进行更新。（子程序PICA FlasgIn示例）它不检查PIC.TXT的变化或类似的东西，它检查程序中的固定PIC号/版本-X是/否- GT；E与PIC.TXT，到目前为止，我很确定PIC.TXT已经在“PIC”中。对于我的理解，PIC.TXT在PIC中的“相同”/整个程序，像是HEX转储，还是PIC.TXT只是其中的一部分？谢谢再见



      以下为原文

    good idea!
of course the "pic.txt" is already in the PIC. Why? because there is a routine in the c code / program which checks, PIC_update_needed and if the value x is there, it makes a update.(subroutine PIC_flashing_sample)
It doesn't check the pic.txt for changes or something like that, it checks fixed PIC number/version in the program - x yes/no -> update with pic.txt, so far I'm quite sure pic.txt is already "in" the PIC.
 
For my understanding, is the pic.txt the "same" / whole programm in the PIC like the hex dump or is the pic.txt just a part of it?
 
Thanks and bye

它只是一个部分，因为引导装载程序代码也会在那里。我们没有办法知道是否还有其他东西没有改变。



      以下为原文

    It will just be a part, because the bootloader code will be in there too.
There's no way any of us can know if there's also something else in there that doesn't change.