Recent changes to bugs

sctl-0.2.3 doesn't check for SG bc245 compat

Roger — Thu, 07 Apr 2005 03:53:57 -0000

sctl-0.2.3 doesn't check for SG bc245 compatability.

$ sctl idreport
ID report mode enabled

04/06 20:46:24 end ID: 000002
*** Error: The command failed because an error
condition was returned.
Command: SG
Reply: ERR

This command is not support for the bc245 scanners (as
well as radio shacks PRO-2052).

Insert if/then or elseif code to check for these models
should surfice.

sctl-0.2.3 load/write hang

Anonymous — Sat, 02 Apr 2005 01:36:54 -0000

I'm getting a load/write hang while using sctl-0.2.3.
I've been able to repeat this bug over and over.

dump.null file is a file with null conv freqs (ie. 0 F
F N F 0)
Hang at "read(4,"

If I use a file loaded with conv frequencies, it will
sometimes fully upload itself (sometimes after a couple
of tries... but it finally goes). But repeating to
upload the same file creates a hang such as this
"dump.null" file loaded with null frequencies.

$ strace ./sctl load e dump.null

write(4, "PM129 00000000\r", 15) = 15
read(4, "C129 F00", 1024) = 8
read(4, "000000 T", 1024) = 8
read(4, "F DF LN ", 1024) = 8
read(4, "AF RF N0", 1024) = 8
read(4, "0\n", 1024) = 2
nanosleep({0, 100000}, {0, 0}) = 0
write(4, "DLF\r", 4) = 4
read(4, "OK\n", 1024) = 3
write(1, "Set delay OFF for this channel.\n", 32Set
delay OFF for this channel.
) = 32
nanosleep({0, 100000}, {0, 0}) = 0
write(4, "LON\r", 4) = 4
read(4, "OK\n", 1024) = 3
write(1, "Set lockout ON for this channel."..., 33Set
lockout ON for this channel.
) = 33
nanosleep({0, 100000}, {4222451713, 3221219440}) = 0
write(4, "MA121\r", 6) = 6
read(4, "C121 F00", 1024) = 8
read(4, "000000 TF DF LN ", 1024) = 16
read(4, "AF RF N00\n", 1024) = 10
write(1, "130 00000000 F F N F 00\n", 24130 00000000 F
F N F 00
) = 24
nanosleep({0, 100000}, {4222451713, 3221219328}) = 0
write(4, "PM130 00000000\r", 15) = 15
read(4, "C130 F00000000 T", 1024) = 16
read(4,

sctl-0.2.3 dump file incorrect header for load command

Roger — Thu, 31 Mar 2005 20:46:45 -0000

sctl-0.2.3 dump file incorrect header for load
command/function.

header of dump file:

MD01

raw mode: 1
version 1
1217500 F F F F 0
1264000 F F F F 0

And will fail to be uploaded with the load command
because (as stated within the format.txt) that the
first line read "version 1".

Instead, load sees "MD01" and "raw mode: 1" as the
version.

So it looks like the dump function/command should be
writing the version at line number 1, but is instead
writing data before "version 1".

sctl-0.2.3 will WRITE/UPLOAD!

Roger — Thu, 31 Mar 2005 20:42:11 -0000

sctl-0.2.3 will WRITE/UPLOAD to my BC245XLT
successfully with the following code uncommented within
commands.c line #648 to show:

/* too bad we can't just upload them as easily as we
downloaded them! */
printf("%03d %08d %c %c %c %c
%02d\n", channel, r_freq, r_trunk, r_delay, r_lockout,
r_record, r_ctcss);

I'll beit, a bit scary, but I just checked with
uploading the data file back to a diff bank and the
write was succesful but hung (probably because I'm
screwing around with my pcmcia modem at the same time
creating a resource conflict ;-)

I'm reading the commands.c file now and am noting the
open commented areas where functions are yet to be
implemented.

strace of sctl-0.2.3 shows mmap DENIED

Roger — Sat, 26 Mar 2005 21:37:47 -0000

strace of sctl-0.2.3 shows mmap DENIED
I think this is because I'm using a hardened kernel.
However, I'm seeing no mention of these mmap DENIED
within syslog. (I also have yet to debug this by using
another standard kernel.)

From what I'm seeing though, I can read the output from
the port as when the scanner activates on a frequency,
I will see a stream of "read" output from the active
strace of sctl.

In breif, looks like my kernel is denying memory writes
to the tty device.

(So, this data is just posted for other users to see
incase they run into a similar problem -- if I resolve
it by using my initial suspicions!)

$ strace sctl light
... begin clipping ...
fstat64(3, {st_mode=S_IFREG|0755, st_size=1218960,
...}) = 0
mmap2(NULL, 1154348, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x401d3000
mprotect(0x402e6000, 27948, PROT_NONE) = 0
mmap2(0x402e7000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x113) = 0x402e7000
mmap2(0x402eb000, 7468, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x402eb000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e1d000
mprotect(0x402e7000, 4096, PROT_READ) = 0
set_thread_area({entry_number:-1 -> 6,
base_addr:0xb7e1d8e0, limit:1048575, seg_32bit:1,
contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
... end clipping ...

sctl-0.2.3 dot config file denotes "unknown" for bc245xlt

Roger — Sat, 26 Mar 2005 21:28:14 -0000

sctl-0.2.3 dot config file denotes "unknown" for bc245xlt.

I'm guessing sctl cannot distinguish the bc245xlt
scanner automatically.

As such, users need to edit the sctl dot config file
manually.

<=sctl-0.2.3 requires 9600 baud_base only

Roger — Sat, 26 Mar 2005 21:22:42 -0000

<=sctl-0.2.3 requires 9600 baud_base only

Documentation should state this someplace and that one
needs to use setserial to set the port baud_base.

ie.
# setserial /dev/ttyS0 baud_base 9600

Also, set 9600 within the scanner by holding the "E"
remote key while turning on the scanner. Press the "2"
key and then use the "down" (limit) & "up" (hold) keys
to toggle to "9600".

The documentation should continue to state to set the
scanner remote mode by turning the scanner on and then
holding the "E" (remote) key down until it beeps.

Now one can use sctl with the scanner.

sctl-0.2.3 -m switch requires CAPITAL letters only

Roger — Sat, 26 Mar 2005 21:16:15 -0000

sctl-0.2.3 -m switch requires CAPITAL letters only

While this is true, the sctl dot config file requires
the model number to be specified in lower case letters
only.

From my view, the -m switch should accept lowercase
letters (only).

I will try to trace and track and submit a patch, seems
like a really easy one to fix.

sctl-0.2.0 segfaults

Roger — Tue, 29 Jan 2002 05:33:22 -0000

segfaults while reading ~/.sctl config file on exectution.

fstat64(3, {st_mode=S_IFREG|0755, st_size=1285480,
...}) = 0
old_mmap(NULL, 1301800, PROT_READ|PROT_EXEC,
MAP_PRIVATE, 3, 0) = 0x4003c000
mprotect(0x40171000, 36136, PROT_NONE) = 0
old_mmap(0x40171000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x134000) = 0x40171000
old_mmap(0x40176000, 15656, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40176000
close(3) = 0
munmap(0x40017000, 150320) = 0
brk(0) = 0x8054558
brk(0x80546d8) = 0x80546d8
brk(0x8055000) = 0x8055000
open("/home/roger/.sctl", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0666, st_size=30, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
read(3, "port /dev/ttyS1\nmodel unknown\n", 4096) = 30
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

Here's my $bash script to dump all banks

Anonymous — Sat, 13 Oct 2001 20:17:45 -0000

pretty straight forward.

Edit where your sctl binary is located &

$ chmod a+x dump-all

$ ./dump-all