Open Source Mobile Communications: Issueshttps://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092023-09-15T15:44:53ZOpen Source Mobile Communications
Redmine SIMtrace 2 - Bug #6181 (Feedback): Unexpected INS code with simtrace2-sniff: 0x7fhttps://projects.osmocom.org/issues/61812023-09-15T15:44:53Zv.marinos
<p>Hello,</p>
<p>I used `simtrace2-sniff` to sniff the messages between my sysmocom SIM cards and a Google Pixel 5, during 5G SA registration. I captured the traffic with tcpdump over port 4729 (pcap file attached).</p>
<p>I am using Open5GS and srsRAN (5G) for the core and RAN respectively. The phone connects to the core successfully and has internet access.</p>
<p>When I replay the captured messages with pySim-trace I get the following error: "ValueError: Unknown CLA=A4 INS=7F". Wireshark also shows the same INS code, as Unknown (0x7f).</p>
<p>I looked at ETSI TS 102 221 V17.1.0 (2022-02), Table 10.5, and couldn't find any reference of APDU with INS code 0x7f.</p>
<p>Do you have any insights on why this APDU is showing up?</p>
<p>Thanks,<br />Marinos</p> SIMtrace 2 - Bug #5921 (In Progress): simtrace2 cardem vs. Linux kernel USB autosuspendhttps://projects.osmocom.org/issues/59212023-02-23T17:40:01Zlaforge
<p>(at least) after the following patch was merged, simtrace2-cardem doesn't work with Linux kernels' USB autosuspend anymore:<br /><pre>
commit a5d537973db9359804e82a506057f3dd6d53fab9
Author: Harald Welte <laforge@osmocom.org>
Date: Mon Jul 25 19:59:08 2022 +0200
cardem: reset the uC in case of USB disconnect
</pre></p>
<p>The problem is that the USB kernel notices the simtrace2 device is not in use (no application using it), which in turn means it will power-down the device after 5s. The device then recognizes this as USB disconnect, and we use that to reset the firmware:</p>
<pre>
=============================================================================
SIMtrace2 firmware 0.8.1.58-773d, BOARD=simtrace, APP=cardem
(C) 2010-2019 by Harald Welte, 2018-2019 by Kevin Redon
=============================================================================
-I- Chip ID: 0x299b0a60 (Ext 0x00000000)
-I- Serial Nr. 44203020-48574336-30303931-32323032
-I- Reset Cause: software reset (processor reset required by the software)
-I- USB init...
USBD_Init
SetAddr(22) -W- Sta 0x888A8 [0] -W- _ -W- Sta 0x888A8 [0] -W- _ -W- Sta 0x888A8 [0] -W- _ SetCfg(1) cfgChanged1 -I- calling configure of all configurations...
-I- calling init of config 1...
-I- Modem 0: physical SIM
-I- 0: Use local/physical SIM
-I- entering main loop...
-I- USB is now configured
-I- Resetting uC on USB disconnect
=============================================================================
SIMtrace2 firmware 0.8.1.58-773d, BOARD=simtrace, APP=cardem
(C) 2010-2019 by Harald Welte, 2018-2019 by Kevin Redon
=============================================================================
-I- Chip ID: 0x299b0a60 (Ext 0x00000000)
-I- Serial Nr. 44203020-48574336-30303931-32323032
-I- Reset Cause: software reset (processor reset required by the software)
-I- USB init...
USBD_Init
SetAddr(23) -W- Sta 0x888A8 [0] -W- _ -W- Sta 0x888A8 [0] -W- _ -W- Sta 0x888A8 [0] -W- _ SetCfg(1) cfgChanged1 -I- calling configure of all configurations...
-I- calling init of config 1...
-I- Modem 0: physical SIM
-I- 0: Use local/physical SIM
-I- entering main loop...
-I- USB is now configured
-I- Resetting uC on USB disconnect
</pre>
<p>This in turn will make the device enumerate and re-enumerate in 5s cycles:</p>
<pre>
[585591.174222] usb 1-1: new full-speed USB device number 84 using xhci_hcd
[585591.330180] usb 1-1: New USB device found, idVendor=1d50, idProduct=60e3, bcdDevice= 0.02
[585591.330216] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=11
[585591.330231] usb 1-1: Product: SIMtrace 2
[585591.330242] usb 1-1: Manufacturer: sysmocom - s.f.m.c. GmbH
[585591.330253] usb 1-1: SerialNumber: 44203020485743363030393132323032
[585594.759881] usb 1-1: USB disconnect, device number 84
[585595.530214] usb 1-1: new full-speed USB device number 85 using xhci_hcd
[585595.682690] usb 1-1: New USB device found, idVendor=1d50, idProduct=60e3, bcdDevice= 0.02
[585595.682697] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=11
[585595.682701] usb 1-1: Product: SIMtrace 2
[585595.682704] usb 1-1: Manufacturer: sysmocom - s.f.m.c. GmbH
[585595.682706] usb 1-1: SerialNumber: 44203020485743363030393132323032
[585598.802549] usb 1-1: USB disconnect, device number 85
[585602.158170] usb 1-1: new full-speed USB device number 86 using xhci_hcd
[585602.313720] usb 1-1: New USB device found, idVendor=1d50, idProduct=60e3, bcdDevice= 0.02
[585602.313757] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=11
[585602.313772] usb 1-1: Product: SIMtrace 2
[585602.313784] usb 1-1: Manufacturer: sysmocom - s.f.m.c. GmbH
[585602.313795] usb 1-1: SerialNumber: 44203020485743363030393132323032
[585606.602416] usb 1-1: USB disconnect, device number 86
</pre> SIMtrace 2 - Feature #5826 (Stalled): SAM4S4BA support in firmwarehttps://projects.osmocom.org/issues/58262022-12-13T16:27:45Zlaforge
<p>This ticket is about supporting the SAM4S4BA from our firmware, in addition to the SAM3S4BA, SAM3S8BA and SAM4SD8BA we've been using so far for simtrace2 devices.</p>
<p>This is a spin-off of <a class="issue tracker-2 status-2 priority-1 priority-lowest parent" title="Feature: Hardware / Circuit board update for SAM3S based SIMtrace2 with 1.8V/5V support (In Progress)" href="https://projects.osmocom.org/issues/1706">#1706</a></p> SIMtrace 2 - Feature #5805 (New): SIM Trace 2 Build for Windowshttps://projects.osmocom.org/issues/58052022-11-30T11:52:04Zjelson_simEng
<p>Hello all,</p>
<p>I have been working on trying to have SIMTrace2 build for windows.<br />I am checking just in case someone has already done that and has something that might share.</p>
<p>Thank you,<br />Jelson G.</p> SIMtrace 2 - Bug #5770 (Feedback): simtrace2 firmware ignores any but the first USB message sent...https://projects.osmocom.org/issues/57702022-11-14T17:46:04Zlaforge
<p>The simtrace2 firmware appears to have a problem (probably a race condition of some sort, with the USB stack) where it accepts the first USB message sent by simtrace2-list after a reset, but then ignores others. During investigation, it was noticed that when sending two commands in a row from a single instance of simtrace2, the first is ignored, and the second is processed.</p>
<p>So, in <a class="external" href="https://gerrit.osmocom.org/c/simtrace2/+/26864">https://gerrit.osmocom.org/c/simtrace2/+/26864</a> a hack was put into `simtrace2-tool` so that it sends a fake, empty, error message, to kick the remote SIM firmware into accepting the second, real message. The strange thing is, that when you send two messages like this, it has the side effect of keeping the processor from getting stuck.</p>
<p>So, something about sending two messages has two effects 1.) it kicks the SIM firmware, if it is stuck, and 2.) prevents the SIM firmware from getting stuck in the first place.</p> SIMtrace 2 - Bug #5639 (Feedback): No packet captured but only "Card state change:"https://projects.osmocom.org/issues/56392022-07-31T16:18:56Zg1bbs
<p>Hello, I'm facing a problem when using the trace function. It doesn't capture any packets and the phone (iphone se/iphone xs) shows "No SIM card".</p>
<p>I used the latest version firmware, flashed with dfu-util. I inserted the valid sim card into the simtrace board, inserted the cable-sim into the phone, start the sniff program and turn on the phone. But it keep output "Card state change:". Is it a bug or my problem? Thanks!</p>
<p>(the board version on the back is v1.5 with ATSAM3SD8B chip)</p>
<p>Here's the console output when flushing.
*<strong><b></strong>*</b>**<strong>**</strong>*******************************<br />test@1-NUC8i7BEH:~/SIMtrace$ sudo dfu-util --device 1d50:60e3 --cfg 1 --alt 1 --reset --download simtrace-trace-dfu-latest.bin <br />dfu-util 0.8</p>
<p>Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.<br />Copyright 2010-2014 Tormod Volden and Stefan Schmidt<br />This program is Free Software and has ABSOLUTELY NO WARRANTY<br />Please report bugs to <a class="email" href="mailto:dfu-util@lists.gnumonks.org">dfu-util@lists.gnumonks.org</a></p>
<p>dfu-util: Invalid DFU suffix signature<br />dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!<br />Opening DFU capable USB device...<br />ID 1d50:60e3<br />Run-time device DFU version 0100<br />Claiming USB DFU Runtime Interface...<br />Determining device status: state = appIDLE, status = 0<br />Device really in Runtime Mode, send DFU detach request...<br />Device will detach and reattach...<br />Opening DFU USB Device...<br />Claiming USB DFU Interface...<br />Setting Alternate Setting <a class="issue tracker-2 status-5 priority-5 priority-highest closed" title="Feature: port Dieter's windows code to mISDN (Closed)" href="https://projects.osmocom.org/issues/1">#1</a> ...<br />Determining device status: state = dfuIDLE, status = 0<br />dfuIDLE, continuing<br />DFU mode device DFU version 0100<br />Device returned transfer size 512<br />Copying data from PC to DFU device<br />Download [=========================] 100% 23532 bytes<br />Download done.<br />state(7) = dfuMANIFEST, status(0) = No error condition is present<br />state(2) = dfuIDLE, status(0) = No error condition is present<br />Done!<br />dfu-util: can't detach<br />Resetting USB to switch back to runtime mode</p>
<p><strong><b>the console will stuck here</b></strong><br />------------------------------------------------</p>
<p>Here's the console output when tracing.
*<strong><b></strong>*</b>**<strong>**</strong>**********************************<br />test@1-NUC8i7BEH:~/SIMtrace/simtrace2/host/src$ ./simtrace2-list <br />USB matches: 2<br /> 1d50:60e3 Addr=6, Path=1-4, Cfg=1, Intf=0, Alt=0: 255/1/0 (SIMtrace Sniffer)<br /> 1d50:60e3 Addr=6, Path=1-4, Cfg=2, Intf=0, Alt=0: 255/255/0 (0.8.1.36-a5d53)<br />test@1-NUC8i7BEH:~/SIMtrace/simtrace2/host/src$ sudo ./simtrace2-sniff <br />simtrace2-sniff - Phone-SIM card communication sniffer <br />(C) 2010-2017 by Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br />(C) 2018 by Kevin Redon <<a class="email" href="mailto:kredon@sysmocom.de">kredon@sysmocom.de</a>></p>
<p>Using USB device 1d50:60e3 Addr=6, Path=1-4, Cfg=1, Intf=0, Alt=0: 255/1/0 (SIMtrace Sniffer)<br />Entering main loop<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted, reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />^Ctest@1-NUC8i7BEH:~/SIMtrace/simtrace2/host/src$ sudo ./simtrace2-sniff <br />simtrace2-sniff - Phone-SIM card communication sniffer <br />(C) 2010-2017 by Harald Welte <<a class="email" href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>><br />(C) 2018 by Kevin Redon <<a class="email" href="mailto:kredon@sysmocom.de">kredon@sysmocom.de</a>></p>
<p>Using USB device 1d50:60e3 Addr=6, Path=1-4, Cfg=1, Intf=0, Alt=0: 255/1/0 (SIMtrace Sniffer)<br />Entering main loop<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />Card state change: reset de-asserted<br />Card state change: reset asserted<br />^Ctest@1-NUC8i7BEH:~/SIMtrace/simtrace2/host/src$ <br />------------------------------------------------</p> SIMtrace 2 - Feature #5600 (Feedback): SIMtrace2 fails to emulate EMV cardshttps://projects.osmocom.org/issues/56002022-07-03T19:43:09Zboggy123
<p>Greetings!</p>
<p>I acquired a SIMtrace2 with the hopes of using it for my undergrad dissertation. Many thanks for the hardware and software. I want to relay an EMV ISO-7816 card and observe the communication. I've set the simtrace2-cardem-pcsc to use data found in a virtual smart card interface. When I attempt to make a payment(Ingenico 5000/Square reader) it fails as the command that I have to return to the card fails to transmit. There are traces in the log for an 'Unknown APDU case 0'.</p>
<p>My assumption is that the command received by the emulator(GPO - Get Processing Options) is not interpreted correctly.<br />Command in question: DLGLOBAL INFO => DATA: flags=0x01 (HDR ), <strong>80 a8 00 00 02</strong>. I can only assume that <strong>02</strong> is the length of data that should follow but no data is available.</p>
<p>firmware: latest -- simtrace-cardem-dfu-0.8.1.34-e450.bin<br />Terminal output: <a class="external" href="https://pastebin.com/raw/tYUGSc6k">https://pastebin.com/raw/tYUGSc6k</a></p>
<p>Many thanks</p> SIMtrace 2 - Bug #5578 (Stalled): osmo-remsim-client-st2 hangs after usb-reset without power loss...https://projects.osmocom.org/issues/55782022-06-15T21:50:45Zroh
<p>in case of a osmo-remsim-client-st2 session which gets restarted after being stopped by a usb-disconnect<br /> (terminates with "DST2 FATAL user_simtrace2.c:221 USB IN transfer failed, status=1" as expected)</p>
<p>osmo-remsim-client-st2 gets stuck and then terminates after some time:</p>
<pre>
root@raspberrypi:~# /usr/bin/osmo-remsim-client-st2 -i 10.15.1.135 -V 1d50 -P 4004 -C 1 -I 0 -H 1-1.3.1 -c 1 -n 0
DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server at 10.15.1.135:9998
DLINP NOTICE simtrace2_api.c:267 [0] <= osmo_st2_cardem_request_config(features=00000001)
DLINP NOTICE input/ipa.c:128 10.15.1.135:9998 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:125 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 10.15.1.135:9998 UP
DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at 10.15.1.135:9999
DLINP NOTICE input/ipa.c:128 10.15.1.135:9999 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:125 RSPRO_CLIENT(bankd){REESTABLISH}: RSPRO link to 10.15.1.135:9999 UP
DLINP NOTICE simtrace2_api.c:168 [0] <= osmo_st2_cardem_request_card_insert(inserted=1)
DLINP NOTICE simtrace2_api.c:317 [0] <= _modem_sim_select(remote_sim=1)
DLINP NOTICE simtrace2_api.c:250 [0] <= osmo_st2_cardem_request_set_atr(3b 00 )
DLINP NOTICE simtrace2_api.c:285 [0] <= _modem_reset(asserted=2, pulse_ms=300)
DLINP NOTICE simtrace2_api.c:250 [0] <= osmo_st2_cardem_request_set_atr(3b 9f 96 80 1f 87 80 31 e0 73 fe 21 1b 67 4a 4c 75 30 34 05 4b a9 )
DST2 INFO user_simtrace2.c:65 SIMtrace => PTS req: ff 10 96 79 00 00
...
<modem starts, usb enumeration of serials/wwlan>
...
USB OUT transfer failed, status=2
</pre>
<p>later restarts remain the same in behaviour but a bit different in output:</p>
<pre>
root@raspberrypi:~# /usr/bin/osmo-remsim-client-st2 -i 10.15.1.135 -V 1d50 -P 4004 -C 1 -I 0 -H 1-1.3.1 -c 1 -n 0
DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server at 10.15.1.135:9998
DLINP NOTICE simtrace2_api.c:267 [0] <= osmo_st2_cardem_request_config(features=00000001)
DLINP NOTICE input/ipa.c:128 10.15.1.135:9998 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:125 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 10.15.1.135:9998 UP
DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at 10.15.1.135:9999
DLINP NOTICE input/ipa.c:128 10.15.1.135:9999 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:125 RSPRO_CLIENT(bankd){REESTABLISH}: RSPRO link to 10.15.1.135:9999 UP
DLINP NOTICE simtrace2_api.c:168 [0] <= osmo_st2_cardem_request_card_insert(inserted=1)
DLINP NOTICE simtrace2_api.c:317 [0] <= _modem_sim_select(remote_sim=1)
DLINP NOTICE simtrace2_api.c:250 [0] <= osmo_st2_cardem_request_set_atr(3b 00 )
DLINP NOTICE simtrace2_api.c:285 [0] <= _modem_reset(asserted=2, pulse_ms=300)
DLINP NOTICE simtrace2_api.c:250 [0] <= osmo_st2_cardem_request_set_atr(3b 9f 96 80 1f 87 80 31 e0 73 fe 21 1b 67 4a 4c 75 30 34 05 4b a9 )
USB OUT transfer failed, status=2
</pre>
<p>please note that the modem does not seem to reboot on later restarts of osmo-remsim-client-st2, which is odd.</p>
<p>osmo-remsim-client version 1.0.0.18-f5f5<br />qmod firmware 0.8.1.33-9088</p>
<p>osmo-remsim-bankd version 1.0.0.18-f5f5<br />osmo-resmim-server version 1.0.0.18-f5f5</p>
<p>maybe this is a rerun of <a class="issue tracker-1 status-7 priority-1 priority-lowest" title="Bug: osmo-remsim-client-st2 (or firmware?) gets stuck on PTS (Stalled)" href="https://projects.osmocom.org/issues/4409">#4409</a></p>
<p>for this test the server/bankd were on x86_64 and the client was on armv7l (rpi) but i don't think it matters.<br />i have also tried a older qmod firmware (0.7.0.57-f46d) for comparison but i can see no difference in behavior.</p>
<p>please note that i could not reproduce this issue with a modem on st34, only on st12. i suspect it has to do with st12 staying powered all the time and not reset/rebooted on usb-connect properly somehow.</p>
<p>this may as well be a firmware issue on the qmod.</p> SIMtrace 2 - Bug #5464 (In Progress): cardem firmware unable to attach to cardhttps://projects.osmocom.org/issues/54642022-02-21T19:07:57Zk_o_
<p>I'm using a Nexus 5 phone. I have a permanent problem that the remote SIM cannot be attached. I always see several RESETs after the phone is restarted. The trace firmware together with the command line works. The adapter cable is in a prepared SIM tray and works. What could be the issue?</p>
<pre>
simtrace2-cardem-pcsc --usb-vendor 1d50 --usb-product 60e3 --usb-path 2-1.4 --usb-config 1 -n 2
simtrace2-cardem-pcsc - Using PC/SC reader as SIM
(C) 2010-2020, Harald Welte <laforge@gnumonks.org>
(C) 2018, sysmocom -s.f.m.c. GmbH, Author: Kevin Redon <kredon@sysmocom.de>
<0002> simtrace2_api.c:267 [0] <= osmo_st2_cardem_request_config(features=00000001)
<0002> simtrace2_api.c:168 [0] <= osmo_st2_cardem_request_card_insert(inserted=1)
<0002> simtrace2_api.c:317 [0] <= _modem_sim_select(remote_sim=1)
<0002> simtrace2_api.c:250 [0] <= osmo_st2_cardem_request_set_atr(3b 9f 96 80 1f c7 80 31 e0 73 f6 21 13 67 56 03 27 00 89 01 02 28 )
<0002> simtrace2_api.c:284 [0] <= _modem_reset(asserted=2, pulse_ms=300)
Entering main loop
-> 01 08 00 00 00 00 0d 00 01 00 00 00 00
SIMtrace IRQ 01 04 00 00 00 00 15 00 00 00 00 00 00 00 01 01 0a 80 25 00 00
SIMtrace IRQ STATUS: flags=0x0, fi=1, di=1, wi=10 wtime=9600 ()
SIMtrace IRQ 01 04 00 00 00 00 15 00 10 00 00 00 00 00 01 01 0a 80 25 00 00
SIMtrace IRQ STATUS: flags=0x10, fi=1, di=1, wi=10 wtime=9600 (RESET )
SIMtrace IRQ 01 04 00 00 00 00 15 00 00 00 00 00 00 00 01 01 0a 80 25 00 00
SIMtrace IRQ STATUS: flags=0x0, fi=1, di=1, wi=10 wtime=9600 ()
SIMtrace IRQ 01 04 00 00 00 00 15 00 10 00 00 00 00 00 01 01 0a 80 25 00 00
SIMtrace IRQ STATUS: flags=0x10, fi=1, di=1, wi=10 wtime=9600 (RESET )
</pre> SIMtrace 2 - Bug #5423 (New): "trace" firmware continuous test setuphttps://projects.osmocom.org/issues/54232022-01-27T12:24:54Zlaforge
<p>Similar to <code>cardem</code> in <a class="issue tracker-2 status-2 priority-2 priority-default" title="Feature: "cardem" continuous testing setup (In Progress)" href="https://projects.osmocom.org/issues/5422">#5422</a>, we should also create a continuous test setup for passing SIM protocol tracing. The IUT is the simtrace2 firmware.</p>
<p>We can use diffeent modems / CCID readers accessing a SIM card via a SIMtrace2 device while tracing the communication.</p> SIMtrace 2 - Feature #5422 (In Progress): "cardem" continuous testing setuphttps://projects.osmocom.org/issues/54222022-01-27T12:22:10Zlaforge
<p>We shuold create a test setup where we can continously test the <code>cardem</code> firmware for the various targets, such as at least simtrace2 and qmod.</p>
<p>The idea would be to use the TTCN3 test ports for SIMTRACE USB protocol on the one hand side and CCID USB protocol on the other hand side.</p>
<p>Tests should ideally not just test interop with one specific CCID reader model but with a larger number of different readers to cover reader-specific issues (I'm seeing different issues with different readers in manual testing).</p>
<p>The tests can then be executed with the latest cardem firmware of the day, on different IUT hardware (simtrace2, qmod) against different readers.</p>
For QMOD testing we would have to either
<ul>
<li>insert a modem with CCID capability (they do exist)</li>
<li>use a custom PCB adapter or some solder wire to hook up the SIM traces of the mCPIE sockets with some external reader</li>
</ul>
<p>But let's focus on simtrace2 for the initial setup, and then expand from there.</p> UmTRX - Feature #3747 (New): LMS6002D RX Gain Controlhttps://projects.osmocom.org/issues/37472019-01-08T02:53:19Zjahredibanez
<p>Hi, with OSMO Rx-Gain Setting for UmTRX</p>
<p>osmotrx rx-gain <0-50><br />Set the receiver gain (configured in the hardware) in dB</p>
<p>LMS6002D Transceiver has gain blocks for RXLNA, RXVGA1, RXLPF, and RXVGA2.</p>
<p>which block does this setting change? and how does it change these values?</p> Z-Netz - Feature #2814 (New): Create + Document classic CrossPoint setup on DOS (dosemu)https://projects.osmocom.org/issues/28142018-01-01T13:41:48ZlaforgeZ-Netz - Feature #2813 (New): Create + Document OpenXP setup on Linuxhttps://projects.osmocom.org/issues/28132018-01-01T13:41:26ZlaforgeZ-Netz - Bug #2809 (New): Build ZConnect <-> UseNet gatewayhttps://projects.osmocom.org/issues/28092018-01-01T13:09:32Zlaforge
<p>possibly looking at <a class="external" href="https://www.daneben.de/odoconnect.html">https://www.daneben.de/odoconnect.html</a> as a tool</p> Z-Netz - Bug #2808 (New): Create + Document VM/emulation setup for running ZERBERUShttps://projects.osmocom.org/issues/28082018-01-01T13:09:06ZlaforgeZ-Netz - Bug #2807 (Stalled): Obtain ZERBERUS software build[s] and manual[s]https://projects.osmocom.org/issues/28072018-01-01T13:08:48Zlaforge
<p>I've sent mail to padeluun + rena about this.</p> UUCP and UseNet - Feature #2806 (New): Create Dockerfile and/or ansible playbook for UseNet nodehttps://projects.osmocom.org/issues/28062018-01-01T13:04:27Zlaforge
<p>Should be possible using stock debian packages for taylor UUCP, inn2, exim, ...</p> UmTRX - Feature #1518 (New): Upper limit of the clock is too lowhttps://projects.osmocom.org/issues/15182016-02-19T22:52:49Z
<p>Upper limit of the clock is too low.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1517 (New): U_FL (UMC) connectors are not reliable after few connectionshttps://projects.osmocom.org/issues/15172016-02-19T22:52:49Z
<p>U_FL (UMC) connectors are not reliable after few connections.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1516 (New): There are no port to control external equipment like PAhttps://projects.osmocom.org/issues/15162016-02-19T22:52:49Z
<p>There is no port to control external equipment such as a PA.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1515 (New): Heat dissipation and mounting issuehttps://projects.osmocom.org/issues/15152016-02-19T22:52:49Z
<p>Heat dissipation and mounting issue.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1511 (New): Solve Tx and Rx I/Q imbalance for wideband signalshttps://projects.osmocom.org/issues/15112016-02-19T22:52:48Z
<p>Solve Tx and Rx I/Q imbalance for wideband signals.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1510 (New): Complete UHD integrationhttps://projects.osmocom.org/issues/15102016-02-19T22:52:48Z
<p>Complete UHD integration.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1509 (New): Store calibration values in EEPROMhttps://projects.osmocom.org/issues/15092016-02-19T22:52:48Z
<p>Store calibration values in EEPROM.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1508 (New): Implement UmSEL diversity switch controlhttps://projects.osmocom.org/issues/15082016-02-19T22:52:48Z
<p>Implement <a class="wiki-page new" href="https://projects.osmocom.org/projects/umtrx/wiki/UmSEL">UmSEL</a> diversity switch control.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1507 (New): Implement UmSEL tuner controlhttps://projects.osmocom.org/issues/15072016-02-19T22:52:48Z
<p>Implement <a class="wiki-page new" href="https://projects.osmocom.org/projects/umtrx/wiki/UmSEL">UmSEL</a> tuner control.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1506 (New): Move to the latest stable UHDhttps://projects.osmocom.org/issues/15062016-02-19T22:52:48Z
<p>Move to the latest stable UHD.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Bug #1505 (New): OHM4 footprint incorrecthttps://projects.osmocom.org/issues/15052016-02-19T22:52:48Z
<p>OHM4 footprint incorrect.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1504 (New): LMS6002 phase error increases when Rx is enabled and varies with tem...https://projects.osmocom.org/issues/15042016-02-19T22:52:47Z
<p>LMS6002 phase error increases when Rx is enabled and varies with temperature.</p>
<p>[Migrated from old Google Code tracker]</p>