Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

New Wizard for Atmel AVR projects

(1/3) > >>

BrianSidebotham:
Hi guys,

I've attached a wizard for Atmel AVR projects as a zip file. This contains all of the files needed.

I have also attached a patch for current svn which strips the processor choice out of the standard compiler options (This is now done via the wizard). Although this is easier for someone to manage when starting a project, the main benefit is that the processor type now gets passed to the linker as it should really.

I also added a few commonly used code generation compiler options for the AVR.

There are various options provided by the wizard, which cover 95% of AVR projects. Although, I'm sure over time it can be improved a lot.

Let me know your comments and/or suggestions.

Oh, if anyone fancies doing the graphics differently for the wizard, please do! I just put the quickest of quick png's together to get the wizard done!

edit: The patch also modifies the config.script and common_functions.script files to allow c::b to set the debug and optimization options properly.

[attachment deleted by admin]

Biplab:
Thanks for the wizard. I can't test it's functionality. But I'll just test it (to see how it works ;)) and put it in repo tomorrow. :)

BrianSidebotham:
No problem.

There is one issue I can think of. I use --no-change-warnings with avr-objdump to prevent avr-objdump resulting in an error when there is no section .eeprom in the .elf output

This happens when the user hasn't initialised any .eeprom variables. This works for the current binutils avr-objdump, but not for the avr-objdump currently supplied with winavr (the option is non-functional).

This is only really a problem if someone chooses to create more than one output type, as you'll see with the wizard.

If there is a way of getting c::b to ignore an error from a command, then it would be good to incorporate it on the avr-objcopy post build commands.

Biplab:

--- Quote from: BrianSidebotham on September 24, 2007, 06:06:55 pm ---If there is a way of getting c::b to ignore an error from a command, then it would be good to incorporate it on the avr-objcopy post build commands.

--- End quote ---

You can mark that error message as an warning message by changing the appropriate regex string. I don't do embedded programming and honestly I can't suggest anything beyond that. :)

BrianSidebotham:
Okay, I'll look into that approach. Thanks for the pointer.

Navigation

[0] Message Index

[#] Next page