User forums > Embedded development

Project Template For AVR GCC Compiler

<< < (2/7) > >>

MortenMacFly:

--- Quote from: scarphin on November 03, 2010, 06:00:06 pm ---Hmm any tutorial on this?

--- End quote ---
I believe it's pretty straight forward. You can read the docs about virtual targets, macro expansions and project settings if you want to:
http://www.codeblocks.org/docs/main_codeblocks_en.html

scarphin:
Well ok, now I got what u mean but I still think using a shortcut would be easier. Just curious, whether it's logical or not, would it be easy to implement a compiler specific menu item?

scarphin:
I modified the template further to make some changes related with the filename extensions and added the extraction of the signature byte. The template extracts the fuse data into seperate files for 'hex' output depending on the fuse byte so the programming of the AVR can be automated with the following command:


--- Code: ---avrdude -c dragon_isp -P usb -p $(MCU) -u -U flash:w:${TARGET_OUTPUT_FILE}.hex -U eeprom:w:${TARGET_OUTPUT_FILE}.eep -U lfuse:w:${TARGET_OUTPUT_FILE}.lfs -U hfuse:w:${TARGET_OUTPUT_FILE}.hfs -U efuse:w:${TARGET_OUTPUT_FILE}.efs -U lock:w:${TARGET_OUTPUT_FILE}.lock
--- End code ---

This considers an 'AVR Dragon' is used as programmer hardware. '$MCU' is the variable that contains the mcu type information which I had included in the template before. If an ATXMEGA mcu is used, the template should be further modified to extract the other fuse bytes. The current template distributed with CodeBlocks lacks the extraction of 'fuse, lock & signature' bytes from the resulting flash file which may cause problems if those bytes are used. So I request this template to be verified and used in further distributions. I only modified the original template so the thanks and credits go to the original author.

May I also request 'Project/properties/debugger/additional shell commands' option to be implemented as soon as possible. It's a very important feature for the embedded programmer. ;) And 1 last question, do I have an option to redirect standart output to say 'debugger' tab for my custom tools on the tools menu?

scarphin:
I updated the script. It now has the option to extract the fuse, lock and signature files if needed. The extraction of the fuse byte into separate files needs the installation of 'srec_cat' and is only available for hex output. As said before I only modified the script, thanks and credits goes to the original author. Should I insert my name into the script to inform about the changes or leave it as it is?

Regarding my previous post I guess no one is interested in this script to be verified, is there some specific developer responsible for the embedded part of codeblocks I have to contact? Please advice!

scarphin:
I managed to make a patch after a couple of hours to get used to svn. I made it for the debuggers branch located in 'svn://svn.berlios.de/codeblocks/branches/wxpropgrid_debugger', do I also have to make it for the trunk? File is attached, don't know if it requires a specific naming though. Thnx...

Navigation

[0] Message Index

[#] Next page

[*] Previous page