gdbMann_Program arguments

gdbMann

Required arguments:

• -elf
• --client

Application Arguments

Testing

-elf

elf file which gets loaded by the testMode-Client to decode target names

This command defines a binary file that gets executed on the host or on the target. If the execution is on a remote target it might be necessary to flash it with "-f"

short: -bin 
long : -elf 

number of additional parameter: 1

This argument is requires

--server

command to call and configure the testMode-Server

Is this command set the defined gbd-server gets started. This is necessary if the target is a remote target. Alternative it is possible to start a gdbserver manual. If e.g. the clients port has changed it must be adjusted in this call too!

It may be necessary to add the entire application path

short: -s 
long : --server 

number of additional parameter: 1

--client

command to call testMode-Client

This command defines the location/command for the gdb-client.

It may be necessary to add the entire application path

short: -c 
long : --client 

number of additional parameter: 1

This argument is requires

--port

port for the GDB-Client (Not Server!)

This command defines the port for the gdb-client and server (if defined).

short: -p 
long : --port 

number of additional parameter: 1

--flash

flash the target with the given elf file

This command does flash the target. It only has effect if the target is a remote one.

short: -f 
long : --flash 

--testLevel

set the testLevel to

This command defines the test level. The test level it the amount of information about the test execution that gets shared between the target and the host. The more information gets shared the longer does the test execution take.
Levels are: "justSuccess" : boolean information about the test-status "testName" : (default) + name and group of the executed test "testResults" + result and expected value of an failed test "lineNumber" + line number of the failed tests

short: -t 
long : --testLevel 

number of additional parameter: 1

allowed parameter: testResults lineNumber testName justSuccess

--runMode

define the execution mode of this application

This command defines the run Mode. Each Mode defines a different gdnManipulator behavior. The mode "--runMode" does does connect to the target and continue its execution to execute gdb commands by using –runGdbScriptAfterExec. The mode connects to the target and wait for the first message and try’s to execute all test and mocks The mode

short: -mode 
long : --runMode 

number of additional parameter: 1

allowed parameter: testMode runMode flashMode

--timeout

When the target has not send in ms a signal the target returns out of the current function

Communication Timeout. This command enables in TestMode a timeout. On each communication with the gdbMan a timer gets reseted(wachdog). Does this timer expire a Timeout Assert gets added and the target continues after the current function. The timeout is given in milliseconds.

short:  
long : --timeout 

number of additional parameter: 1

--disableGroups

Start string of test groups that shall not get executed multible string are seperated by <:>

Disable on runtime test groups. -d Each group gets checked whether the group starts with the argument . If multiple arguments shall get opt out it is possible to separate each group with <:> -d TEST_TIMER*:TEST_HAL:TEST_LCD

short: -d 
long : --disableGroups 

--enableGroups

Start string of test groups that shall get executed multible string are seperated by <:>

Enables on runtime test groups. -d Each group gets checked whether the group starts with the argument . If multiple arguments shall get opt out it is possible to separate each group with <:> -d TEST_IIC*:TEST_LCD

short: -e 
long : --enableGroups 

--runGdbScriptAfterExec

executes a gdb-script after executen the curretn runMode --runGdbScriptAfterExec

This command executes the gdb command defined in the parameter. Each command gets executed after the runMode has finished.

short:  
long : --runGdbScriptAfterExec 

number of additional parameter: 1

--runOnHost

run test on host and not on target

Is this command set the the elf file gets executed local.

short: -host 
long : --runOnHost 

--resetFunction

expect to stop in this function after startup

This command does change the default startup function where the target stops after flashing. By default this is "Reset_Handler".

short: -r 
long : --resetFunction 

number of additional parameter: 1

--failgdbManIfOneTestWasNotSuccessfull

gdbMan returns -1 if at least on test failed

short:  
long : --failgdbManIfOneTestWasNotSuccessfull 

additional output

--xml

generate xml output file

To create a xml output file use this command.

short: -x 
long : --xml 

number of additional parameter: 1

--statistic

create test statistic

This command enables to local statics about the test execution like time and amount of gdb commands.

short: -stat 
long : --statistic 

logging

--logFileName

change the fog file name

This command defines to logfile name.

short: -lfn 
long : --logFileName 

number of additional parameter: 1

--logLevel

change the cli loglevel enum name e.g -l Error

This command does adjust he amount of information that gets printed on the cli an and into the logfile.

short: -l 
long : --logLevel 

number of additional parameter: 1

allowed parameter: None UserInfo CriticError Error Message Info Debug DebugL2 DebugL3

--logLevelSeparate

change the log level for cli and logfile separate to e.g -lls Error DebugL3

This command does adjust he amount of information that gets printed on the cli an and into the logfile sperate.

short: -lls 
long : --logLevelSeparate 

number of additional parameter: 2

--noHighlighting

disables the cli highlighting

short: -nh 
long : --noHighlighting 

--version

print build version

short: -v 
long : --version