Hi Detlev and Wolfgang
Thanks for your quick answer and I got a few steps further.
First I created my own version of "connect" (see attached Ruby script).
Now at least I can connect and it seems to work.
Am Donnerstag 30 Juli 2009 12.14:14 schrieb Detlev Zundel:
Hi Niklaus,
<..>
I would appreciate any hints. As the section "I"ntroducing suppport for a new VL " is just a little be too small for me. E.g. how can I add a new VL. Is there an example I just can copy and adjust it? Where do I specify the tty device for the sequoia?
Clone config/self-hosted* to config/<whatever>* and work from there. Then use "duts -c <whatever> sequoia" and dive in :)
The "context" stuff is definitely something we need to work on. It wasn't on my top-priority list as it currently works for us and generalizations are only done correctly when we have multiple test cases...
@Detlev:
I think that my config files don't get loaded (seen with -v and verify by putting "p_err "was in ngiger_uboot_context.tcl" into my files. Here is my snippet:
./duts -v -c ngiger -tc UBootVersion sequoia <..> DUTS: no such directory: './testsystems/dulg/testcases/sequoia' DUTS: no target specific TCs for sequoia DUTS: Date is 073014232009 DUTS: ./config exists DUTS: './config' exists and accessible, OK DUTS: loading configs from ./config/configs.cfg DUTS: Loading config description: _default DUTS: validating: './config/VL_uboot_context.tcl' DUTS: file exists and accessible, OK DUTS: validating: './config/VL_linux_context.tcl' DUTS: file exists and accessible, OK DUTS: validating: './config/VL_host_context.tcl' DUTS: file exists and accessible, OK DUTS: validating: './config/VL_ops.tcl' DUTS: file exists and accessible, OK DUTS: loaded 1 config decriptions DUTS: method '_device_power_on' found, OK DUTS: method '_device_power_off' found, OK DUTS: method '_device_connect_target' found, OK DUTS: method '_device_connect_host' found, OK Selected config: ngiger List of selected test cases: UBootVersion
confirm to start execution? [y]
And I am not good at hacking using TCL. I do most of my scripting in Ruby as it is one of the few languages I have a chance to read my old code and still understand it.
Is this a easy fix for you?
Best regards
Niklaus
Cheers Detlev