Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092022-11-30T11:52:04ZOpen Source Mobile Communications
Redmine SIMtrace 2 - Feature #5805 (New): SIM Trace 2 Build for Windowshttps://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://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://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://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://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 #5423 (New): "trace" firmware continuous test setuphttps://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://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 - Bug #4430 (New): firmware can get in endless out-of-memory loop on OUT EP floodhttps://osmocom.org/issues/44302020-03-01T15:06:25Zlaforge
<p>When flooding the OUT EP with too many messages, the firmware can get into an OOM situation from which it doesn't recover anymore. All it will do is print the below messages:</p>
<pre>
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
-E- _talloc_zero() out of memory!
</pre>
<p>I'm currently reproducing this with a test case that sends 1000 bogus OUT EP transfers to the device.</p> SIMtrace 2 - Bug #4041 (New): implement SIMTRACE_CMD_BD_BOARD_INFOhttps://osmocom.org/issues/40412019-06-04T15:57:19Zlaforge
<p>this command is supposed to return the hardware manufacturer, hardware version as well as software version information. It would be very useful to obtain the currently running firmware versin as well as other details.</p> SIMtrace 2 - Bug #3815 (New): simtrace2 fails USB-IF CH9 testhttps://osmocom.org/issues/38152019-02-23T15:10:02Zlaforge
<p>When running the Chapter9 tests of the USB IF against a simtrace2 device, they fail. The test claims SET_CONFIGURATION is failing, which is quite odd.</p> UmTRX - Feature #3747 (New): LMS6002D RX Gain Controlhttps://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> SIMtrace 2 - Bug #3712 (New): TRACE_FATAL not printinghttps://osmocom.org/issues/37122018-11-27T10:57:30Ztsaitgaist
<p>TRACE_FATAL should print and enter an endless loop (until the watchdog bites).<br />currently is only does the later and no debug message is printed.<br />check if it uses the synchronous/un-buffered UART output</p> SIMtrace 2 - Feature #3501 (New): Multi-sim addon board ideahttps://osmocom.org/issues/35012018-08-26T18:12:10Zdemodulate
<p>If the SIMTrace2 board is redone, I would like to propose that the bottom of the board, or free space on the board, is used to hold additional SIM slots with the understanding that only one slot would be used at any given point in time. A single LED could indicate which SIM is in use, if the SIM selection used a software controlled switch. Alternatively, a second board could be created as an add on to hold any number of SIMs based on the area of the board. A physical slider switch for selecting the electrical path would be suitable in either case.</p>
<p>Would this be useful for anyone using the SIMTrace2?</p> SIMtrace 2 - Feature #3371 (New): migrate to use arm-none-eabi build of libosmocore.githttps://osmocom.org/issues/33712018-06-29T20:35:16Zlaforge
<p>We currently have some partial copied hack of libosmocore inside simtrace2.git, which is of course a bad idea.</p>
<p>Instead, we should use a libosmocore from libosmocore.git which was built + installed using</p>
<pre><code>./configure --enable-static --prefix=/usr/local/arm-none-eabi --host=arm-none-eabi --enable-embedded CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs -Werror"</code></pre>
<p>This library can then be used by a variety of embedded/firmware builds, such as OsmocomBB and others.</p> Z-Netz - Feature #2814 (New): Create + Document classic CrossPoint setup on DOS (dosemu)https://osmocom.org/issues/28142018-01-01T13:41:48ZlaforgeZ-Netz - Feature #2813 (New): Create + Document OpenXP setup on Linuxhttps://osmocom.org/issues/28132018-01-01T13:41:26ZlaforgeZ-Netz - Bug #2809 (New): Build ZConnect <-> UseNet gatewayhttps://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://osmocom.org/issues/28082018-01-01T13:09:06ZlaforgeZ-Netz - Bug #2807 (Stalled): Obtain ZERBERUS software build[s] and manual[s]https://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://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://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://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://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://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://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 - Bug #1505 (New): OHM4 footprint incorrecthttps://osmocom.org/issues/15052016-02-19T22:52:48Z
<p>OHM4 footprint incorrect.</p>
<p>[Migrated from old Google Code tracker]</p> UmTRX - Feature #1510 (New): Complete UHD integrationhttps://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://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://osmocom.org/issues/15082016-02-19T22:52:48Z
<p>Implement <a class="wiki-page new" href="https://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://osmocom.org/issues/15072016-02-19T22:52:48Z
<p>Implement <a class="wiki-page new" href="https://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://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 - Feature #1504 (New): LMS6002 phase error increases when Rx is enabled and varies with tem...https://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>