| Ich nutze: C164CI-ControllerBoard, CC2-Application-Board |
Just wanna put some of my experiences with the Keil C compiler (vers. 4.11)
and the C-Control2 here to help others with the same setup.
At the moment I use the C2 without the OS, and load the .hex (.H86) file
with Andre's nice upload tool as one would do when replacing the OS.
Mind you this may not be the definitive solution to this combination, but at least
it works (well, at the moment).
My programs hex file is about 3500 bytes long now and it has ca. 4k array variabes
declarations, I have no idea if this setup will work with a bigger program, but...
Memory setup in Options for Target:
Target page:
memory model: Small
op. system: none
use onchip rom / use onchip can: unchecked
data near 6
near memory: 16 / 16
external memory:
1# rom 0x0 0xDFFF
2# ram 0xF600 0x200 (can't fit in the rom space at 0x40000 and make it work,
I need to learn more about the linker methinks)
3# ram 0x80000 0xFFFF
#4 ram 0xEF10 0xEF
Output page:
Create HEX file: checked
HEX format: HEX-386(H167)
(no offset when you replace the OS with a C program)
everything else at default settings.
if you have assembler code in a source file, remember to right click the
file entry in the Source Group listing on the left
and enable: Generate Assembler SRC File + Assemble SRC File.
It has happened a few times on download that I've had a byte error
message from the upload tool, but when analyzing the serial transfer log
it has come from a couple of extra feedback FF bytes after the file was
successfully transfered, and in my case the program worked fine none the less.
If any of you have ideas or if you can se blatant faults I've made, I'd be
most thankful for your input.
Antwort schreiben
Antworten:
Re: Keil compiler (von krassos - 2.07.2006 16:06)Re: Keil compiler (von mike DK - 4.07.2006 9:19)