comparison rvinterf/doc/rvtdump.usage @ 431:5c75d84ffa81

rvinterf/doc: started documenting the usage of rvinterf tools
author Michael Spacefalcon <msokolov@ivan.Harhan.ORG>
date Sat, 21 Jun 2014 23:36:13 +0000
parents
children
comparison
equal deleted inserted replaced
430:14618bd924ec 431:5c75d84ffa81
1 Rvtdump is a utility that listens on a serial port, receives traces or any other
2 packets emitted by the running firmware of a GSM device in TI's RVTMUX format,
3 decodes them into readable ASCII and emits them to stdout and/or to a log file.
4 It is to be invoked as follows:
5
6 rvtdump [options] /dev/ttyXXX
7
8 where the sole non-option argument is the serial port it should open and listen
9 on.
10
11 The available options are:
12
13 -b
14
15 Normally the rvtdump process remains in the foreground and emits its
16 output on stdout. The -b option suppresses the normal output and causes
17 rvtdump to put itself in the background: fork at startup, then have the
18 parent exit while the child remains running. -b is not useful and not
19 allowed without -l.
20
21 -B baud
22
23 Selects which RVTMUX serial channel baud rate our tool should listen
24 for. Defaults to 115200 baud, which appears to be TI's default and is
25 correct for mokoN, leo2moko and Pirelli's fw. Use -B 57600 for Compal's
26 RVTMUX, the one accessible via **16379#.
27
28 -d <file descriptor number>
29
30 This option is not meant for direct use by human users. It is inserted
31 automatically when rvtdump is launched from fc-xram as the secondary
32 program that immediately takes over the serial channel.
33
34 -l logfile
35
36 Log all received and decoded packets into the specified file in addition
37 to (without -b) or instead of (with -b) dumping them on stdout. Each
38 line in the log file is also time-stamped; the timestamps are in GMT
39 (gmtime(3)) instead of local time - Spacefalcon the Outlaw dislikes
40 local times.