I don't know how to register and interface programs like easypdkprog to C::B. Maybe a plugin is required, I have to find out.
I suppose that would fall under the categorisation of a Code::Blocks 'Tool'. That's how I have, for instance, stm8flash and stm8gal set up in C::B. You can use variables in the command-line parameters of each tool for things like the output file, etc.
For example, I have the parameters set up for stm8flash like so:
Executable:
C:\[...]\stm8flash.exeParameters:
-c stlinkv21 -p ${MCU} -s flash -w "${TARGET_OUTPUT_FILE}"Working Dir:
${PROJECT_DIR}The
MCU variable is defined in the project's build options (e.g.
MCU = STM8S208RB).
So, I think in the case of easypdkprog, because the chip model needs to be passed both as a macro definition when compiling, as well as to the programmer command line, then for the new project wizard you'd want it to set up an
MCU (or whatever appropriate name) variable in the build options (with value e.g. "PFS154"), then also in build options compiler settings add a #define of
${MCU} (so it gets passed as a
-D option to the compiler).
Then, the tool could be configured as follows:
Executable:
\path\to\easypdkprogParameters:
--icname=${MCU} write "${TARGET_OUTPUT_FILE}"Working Dir:
${PROJECT_DIR}The one thing I don't know is whether you can have pre-defined tool definitions be installed, or whether they're only user-configurable.