Hi Norman,
I'm ok with that. I've already discussed this with Stefan. He'd introduced the SPEC-way in base-hw and said that he simply copied it from another case (in base-nova i think). Why this spec is needed wasn't that interesting for me, i think he said that the imx53 uBoot behaves a little strange (images must get extra-processed to work on it) and thus requires distinction. I only wanted to know wich way should be targeted as final solution.
Cheers, Martin
On 12/17/2012 03:35 PM, Norman Feske wrote:
Hi Martin,
By now when doing a build there are two ways of defining the boot method. In 'base-mb' one writes 'RUN_OPT="--target jtag" make demo' or 'RUN_OPT="--target qemu" make demo' while qemu is set by default. At least in base-hw with imx53 one must enrich the SPECS e.g. in etc/specs.mk by the 'uboot' spec to get an appropriate Uboot image.
Are there pros or cons for one of these methods, because i would prefer to use only one them.
admittedly, I am not familiar with the rationale behind the 'uboot' spec value. As far as I know, it hasn't entered genodelabs/master yet. Maybe Stefan can clarify?
Because the selection of the boot method is outside of the scope of the build system but in the scope of the run tool, I regard the 'RUN_OPT' variable as the most natural way to steer the boot method.
I'd like to keep the purposes of both tools (build system and run tool respectively) well separated. By adding spec values for the boot method just to be picked up by the run tool but not the build system, we would blur the boundaries between those tools.
Cheers Norman