baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

jtag trouble j100i
by Mathias K. 09 May '12

09 May '12

Hello, i try to connect the j100i with the latest openocd (git) but there is always something wrong with the embedded ice module. My configuration script is based on openocd_calypso.cfg and the calypso_magic.svf. The main difference i can see is the idcode and the irlen. My changes in the script looks like this: set _CPUTAPID 0xf9001807 jtag newtap $_CHIPNAME dsp -expected-id 0x00000000 -irlen 5 jtag newtap $_CHIPNAME arm -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID This changes are based on some appended svf scripts that simple scan the jtag chain to get more informations. The jtag_idcodes.svf returns the shifted idcodes like this: SDR 32 TDI(ffffffff); length = 32 TDI = 0xFFFFFFFF TDO read = 0xF200300E SDR 32 TDI(ffffffff); length = 32 TDI = 0xFFFFFFFF TDO read = 0xFFFFFFFF The jtag_devices.svf told me the device count and the possible ir register count/length: SIR 32 TDI(ffffffff); length = 32 TDI = 0xFFFFFFFF TDO read = 0xFFFFFE25 TDO: 11...11000100101 Looks like 3 ir registers with 4,3 and 2 bit length SDR 32 TDI(ffffffff); length = 32 TDI = 0xFFFFFFFF TDO read = 0xFFFFFFFC TDO: 11...1100 Looks like 2 devices But every access to the embedded ice registers (they are located in the internal scan chain 2) result in random (most time zero) values for the comms ctrl register and a cpu halt state. Is there anything wrong? Is there a different "magic" 0x0b jtag command or argument for this kind of cpu? Thanks & Regards, Mathias

2 4

Re: How to send a sms using BB
by Henk 09 May '12

09 May '12

It works Chengcheng Gou <gouchengcheng(a)gmail.com>schreef: >Hi, >anyone did try it? >

1 0

How to send a sms using BB
by Chengcheng Gou 09 May '12

09 May '12

Hi, anyone did try it?

1 0

Re: Sagem OT-290 trace phone / GSMTAP integration
by Tyson Key 09 May '12

09 May '12

Hi list, It's my first time posting here, and I've just subscribed - so apologies for totally wrecking archive threading. I've just received a copy of the e-mail regarding the OT-290, thanks to Andrew Back; and I'm wondering it's possible to discuss the feasibility of implementing this functionality with Harald - since it doesn't seem to have generated much interest from others, and I'm "fortunate" enough to live in a small British town without EDGE coverage (which should make it easier to test GPRS-related tracing functionality). Although I'm unfamiliar with how things work in Osmocom, I've previously worked on Wireshark dissectors for USB-encapsulated AT commands, and various NFC/smartcard-related protocols (PN532, FeliCa and MiFare); and am also familiar with Nokia's proprietary ISI baseband protocol, and parts of ETSI's GSM/UMTS specifications - so this sort of stuff isn't totally alien to me. I'm also currently studying Computer Science as an undergraduate (at the University of Bradford) - but I should be able to make time to work on this. Thanks, Tyson. -- Fight Internet Censorship! http://www.eff.org http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844

3 2

[PATCH] Adding the manufacturer id of STMicroelectronics (try 2)
by Christian Inci 07 May '12

07 May '12

For supporting the flash on a Motorola C118. Note: Flashing rssi on it worked fine. Signed-off-by: Christian Inci <chris.pcguy.inci(a)gmail.com>

2 1

key generation on SIM failed (cause 2)
by Alojzij Sinur 07 May '12

07 May '12

Hi, I have a question. When using osmocombb with C118, we are getting error when SIM tries to authenticate itself to the network. Here are the messages: <0005> gsm48_mm.c:3902 (ms 1) Received 'RR_DATA_IND' from RR in state location updating initiated (sapi 0) <0005> gsm48_mm.c:4091 (ms 1) Received 'MT_MM_AUTH_REQ' in MM state location updating initiated <0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq 2) <0005> subscriber.c:955 Generating KEY at SIM <000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO (handle=00000006) <000f> sim.c:697 go MF <000f> sim.c:241 SELECT (file=0x3f00) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000f> sim.c:876 received APDU (len=0 sw1=0x00 sw2=0x00) <000f> sim.c:952 command failed <000f> sim.c:151 sending result to callback function (type=1) <0005> subscriber.c:990 key generation on SIM failed (cause 2) SIM is new. It works if you start phone without osmocom. And It also works if you start without osmocom and when SIM logs into network you restart the phone with osmocom. We tried several new cards and there was always same result. There is also no PIN set up (SIM is not locked). We tried with USIM. When we try old cards (>2 years old) osmocom works without problem. Have you ever encountered this kind of trouble? Is there any fix for it? Thank you. Regards, Alojzij

4 9

Sagem OT-290 trace phone / GSMTAP integration
by Harald Welte 07 May '12

07 May '12

Hi all! Thanks to a generous donor, we have received a couple of OT-290 trace phones. These are commercial products intended for taking L2/L3 air interface traces. If you've read any of the fabulous GSM papers by Prof. Dr.-Ing. Joachim Goeller: The OT-phones is what he used to generate all his traces. The majority of what those phones can do is now also possible with OsmocomBB. However, OT-290 support GPRS tracing/testing - for CS-1 throguh CS-4. I would be willing to give away one of the two remaining OT-290 (for free) to anyone who would in return commit to developing a GSMTAP interface for it. The message format on the serial UART between phone and PC is documented (PDF documentation by Sagem included with the phones). So based on this documentation and an OT-290 phone, it should be possible to write a small command-line program that receives the GSM/GPRS messages from the OT-290 and sends them via GSMTAP into wireshark. The result would then be similar to what http://cgit.osmocom.org/cgit/dct3-gsmtap/ is for DCT-3 phones. If you're interested, please respond to this message. Please don't apply for the phone if you are not able to find the required time and interest for actually doing the GSMTAP integration. Thanks! -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

Adding the manufacturer id of STMicroelectronics
by Christian Inci 07 May '12

07 May '12

For supporting the flash on a Motorola C118. Note: Flashing rssi on it worked fine. Signed-off-by: Christian Inci <chris.pcguy.inci(a)gmail.com> --- src/target/firmware/flash/cfi_flash.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/target/firmware/flash/cfi_flash.c b/src/target/firmware/flash/cfi_flash.c index 69369d5..8ecd206 100644 --- a/src/target/firmware/flash/cfi_flash.c +++ b/src/target/firmware/flash/cfi_flash.c @@ -71,6 +71,7 @@ struct cfi_query { /* manufacturer ids */ enum cfi_manuf { + CFI_MANUF_ST = 0x0020, CFI_MANUF_INTEL = 0x0089, }; @@ -532,8 +533,7 @@ int flash_init(flash_t * flash, void *base_addr) if (res) { return res; } - if (m_id != CFI_MANUF_INTEL) { - /* we only support intel devices */ + if (m_id != CFI_MANUF_INTEL && m_id != CFI_MANUF_ST) { return -ENOTSUP; } -- 1.7.8.6 --------------090106030808000805030408--

1 0

[PATCH] Adding the manufacturer id of STMicroelectronics (resend)
by Christian Inci 07 May '12

07 May '12

For supporting the flash on a Motorola C118. Signed-off-by: Christian Inci <chris.pcguy.inci(a)gmail.com>

2 1

[ticket] RSSI fails to sync on 1800Mhz bands
by Henk 07 May '12

07 May '12

Version: OSMOCOM Monitor Tool (revision osmocon_v0.0.0-1346-g186fefc-modified) RSSI is running from flash There seems to be a problem when trying to sync to the DCS bands also the spectum window is not that what you expect. There seem to be a few very strong peaks but the rest is flat.

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel