User forums > Embedded development

Project Template For AVR GCC Compiler

(1/7) > >>

scarphin:
Hi,
I think the project template for AVR GCC is obsolete. The 'fuse, lock & signature' information is not extracted from the resulting hex file which should be programmed into the correct areas on the ucontroller and not into the flash. I know u guys are not embedded programmers mostly but that's a serious issue for embedded programmers using AVR, GCC and Codeblocks. ;) So I modified the current template to update the scripts and added some extra stuff like defining the '$MCU' variable to be used in tools menu to automate the programming process, etc... Will it be ok if I attach the template here for some1 to verify and I'll try to help and make other changes if need be?

Also there is another important issue, can the tools menu be compiler specific? Like it shows only the tools linked to the compiler chosen. That would be great when working with lots of mcus which need their own programming and debugging command scripts. Thnx...

MortenMacFly:

--- Quote from: scarphin on November 03, 2010, 11:38:36 am ---Will it be ok if I attach the template here for some1 to verify and I'll try to help and make other changes if need be?

--- End quote ---
Yes.


--- Quote from: scarphin on November 03, 2010, 11:38:36 am ---Also there is another important issue, can the tools menu be compiler specific?

--- End quote ---
this makes no sense. A tool must not be compiler related at all. In fact all tools I've embedded are not related to any compiler. So how to differ?

scarphin:

--- Quote from: MortenMacFly on November 03, 2010, 03:50:36 pm ---
--- Quote from: scarphin on November 03, 2010, 11:38:36 am ---Also there is another important issue, can the tools menu be compiler specific?

--- End quote ---
this makes no sense. A tool must not be compiler related at all. In fact all tools I've embedded are not related to any compiler. So how to differ?

--- End quote ---

Say I'm developing with AVRGCC, I wrote the code, compiled it. Then I need to download the code into the microcontroller. Here comes the distinction. I have quite a few options here if I'm using the debugger in 'debugwire' mode then I need to download the code also in 'debugwire' mode which is specific to AVR. Or if in ISP or JTAG, those make another 2 commands for the 'avrdude' on the tools menu. Then I may decide not to program the fuse bits everytime and insert another entry for program without fuse bits. I also need to run the 'gdb-server' (avarice for AVR, gdb-proxy for msp430 or openocd for ARM maybe) before I run the debugger so add another entry. When I said compiler specific I meant target specific which in case turns out to be compiler specific. It will be a long list if these are all on the same menu for all the targets, it would be a tidy version if tools menu could be customised to the compiler like same shortcuts for same actions but target specific executables. Just an idea. ;)

I attached the script file. Need a little more work I think.

MortenMacFly:

--- Quote from: scarphin on November 03, 2010, 05:15:55 pm ---Then I need to download the code into the microcontroller. Here comes the distinction.

--- End quote ---
Are you aware that there is also a "commands only" project type, where you can in the pre- or post-compilations steps add commands using macro expansion very well. Using virtual targets you can "baind" these targets to the compiler you've chosen to compile the actual compilation. Maybe this fits your needs better than pressing everything into the tools menu.

scarphin:
Hmm any tutorial on this?

Navigation

[0] Message Index

[#] Next page