I made a reverse compiler for my Model III 20+ years ago and it did a fine job.done on a 'bet you can't do it'.took about 2 weeks of long, long nights (as I had a real job back then). Imagine what is involved in re-creating the piece of metal from the swarf. Especially given how rapidly CCS changes.Ĭompiling is more akin to milling a piece from a lump of stock, than 'translating'. A few free ones do exist for the PC, but all are 'dubious' in the quality of their output.įor a specialist compiler like CCS, the basic work is not there, and to write such a program would be many hundreds of times more complex than writing the PIC program again from scratch. Just how successful they were is illustrated by how many exist now. Historically for some compilers in the early days of computers people did try to make reverse compilers. Then add the optimiser, and 'reverse compiling' gets more complex than writing the code in the first place. There are probably at least 20 possible C lines for any particular compiler output, for things like loops etc. When we compile a c file to hex through ccs compiler, again can we convert hex file to c ? This needs somebody send the hex file only. Please do not post bug reports on this forum. Another way to learn embedded development is through the Arduino (AVR) system, but that gets you out of C and into a beginner language.CCS :: View topic - Convert hex file to cįAQ Forum Help Official CCS Support Search Register Profile Log in to check your private messages Log inĬCS does not monitor this forum on a regular basis. Also, the AT89C51 (now the AT89S51) uses an older 8051 core, you may find more modern processors like the ATmega, PIC18, or (much more new, but more complex) ARM cores (Cortex-M3/M0, probably) to be more user-friendly and well-supported. You may find native programming a bit easier if you want a slower learning curve. These are some of the most basic steps of embedded software development. The usual way to do this is to use a programmer, though it is often convenient to program the device with a bootloader first, and then use this program to copy the. This is generally referred to as a toolchain, but may be informally referred to as a compiler. It also brings in any external object files for which you don't have the source code (or have already compiled it in a previous iteration). hex file, and gives them the addresses required by the device. The linker puts all the object files together into the series of hex digits in the.
The preprocessor converts #include and #define macros, and also processes any conditional compilation (#if) symbols.There are a number of steps which have to happen between the C code you have and loading data onto the device:
0 kommentar(er)
